Scribd
Upload
110 views2 pages

DNS PDF

When a DNS request is made from an endpoint, it first checks the local cache for the domain address. If not found, the request is sent to the recursive DNS server, usually provided by the ISP, which also checks its cache. If the address is still not found, the root DNS servers redirect the request to the top-level domain server for that domain, like .com or .in, which provides the authoritative nameserver for the domain. The authoritative nameserver then returns the DNS record to the recursive server, which caches it and returns it to the original endpoint.

Uploaded by

mikupiku7172
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
110 views2 pages

DNS PDF

When a DNS request is made from an endpoint, it first checks the local cache for the domain address. If not found, the request is sent to the recursive DNS server, usually provided by the ISP, which also checks its cache. If the address is still not found, the root DNS servers redirect the request to the top-level domain server for that domain, like .com or .in, which provides the authoritative nameserver for the domain. The authoritative nameserver then returns the DNS record to the recursive server, which caches it and returns it to the original endpoint.

Uploaded by

mikupiku7172
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

How to DNS work from endpoint to internet

What happens when you make a DNS request


1. When you request a domain name, your computer first checks its local cache to see if
you've previously looked up the address recently; if not, a request to your
Recursive DNS Server will be made.

2- A Recursive DNS Server is usually provided by your ISP, but you can also choose your own.
This server also has a local cache of recently looked-up domain names. If a result is found
locally, this is sent back to your computer, and your request ends here (this is common for
popular and heavily requested services such as Google, Facebook, Twitter). If the request
cannot be found locally, a journey begins to find the correct answer, starting with the
internet's root DNS servers.

3- The root servers act as the DNS backbone of the internet; their job is to redirect you to the
correct Top Level Domain Server, depending on your request. If, for example, you
request www.techclick.in, the root server will recognize the Top Level Domain of .com and
refer you to the correct TLD server that deals with .com addresses.

4- The TLD server holds records for where to find the authoritative server to answer
the DNS request. The authoritative server is often also known as the nameserver for the
domain. For example, the name server
for techclick.com is ns1.google.com and ns2.google.com. You'll often find multiple
nameservers for a domain name to act as a backup in case one goes down.

5- An authoritative DNS server is the server that is responsible for storing the DNS records
for a particular domain name and where any updates to your domain name DNS records
would be made. Depending on the record type, the DNS record is then sent back to the
Recursive DNS Server, where a local copy will be cached for future requests and then relayed
back to the original client that made the request. DNS records all come with a TTL (Time To
Live) value. This value is a number represented in seconds that the response should be saved
for locally until you have to look it up again. Caching saves on having to make a DNS request
every time you communicate with a server.
DNS

You might also like