Concepts
How DNS resolution work ?
Domain Name Resolution: When you type a domain name into your web browser (e.g., "example.com"), your computer needs to know the corresponding IP address of the server hosting that website.
Querying Nameservers: Your computer sends a request to a DNS resolver (usually provided by your internet service provider or configured in your network settings) asking for the IP address associated with the domain name.
Root Nameservers: If the resolver doesn't already know the IP address for the domain, it contacts a root nameserver. The root nameservers contain information about the top-level domain (TLD) servers for every domain extension (like .com, .net, .org, etc.).
TLD Nameservers: The root nameserver directs the resolver to the appropriate TLD nameserver based on the domain's extension. For example, if the domain is "example.com," the resolver is directed to the .com TLD nameserver.
Authoritative Nameservers: The TLD nameserver then directs the resolver to the authoritative nameservers for the specific domain (e.g., "example.com"). These authoritative nameservers are designated by the domain owner and contain the DNS records for that domain.
Note: Meaning owner has specified which server has authority for storing DNS records for their domain.(Adding NS records when setting up Website).
SO TLD server will (.com in this case) will add new NS records to ts zone files. that for example.com which server(NS records) have authority to hold DNS records. Then that Authrotative Nameserver will provide DNS record in next step.
DNS Records: The authoritative nameservers provide the resolver with the necessary DNS records, such as A records (which map domain names to IP addresses), MX records (which specify mail servers for the domain), CNAME records (which provide aliases for domain names), and more.
Response: The resolver receives the DNS records from the authoritative nameservers and returns the IP address to the requesting device.
Caching: To improve efficiency and reduce network traffic, DNS resolvers typically cache the DNS records they receive for a certain period. This caching helps speed up future requests for the same domain.
Last updated