How DNS work?
When you visit a domain such as dyn.com, your computer follows a series of steps
to turn the human-readable web address into a machine-readable IP address.
This happens every time you use a domain name, whether you are viewing websites,
sending email or listening to Internet radio stations like Pandora.
Step 1: Request information
The process begins when you ask your computer to resolve a hostname, such as visiting
http://abc.com. The first place your computer looks is its local DNS cache, which stores
information that your computer has recently retrieved.
If your computer doesn’t already know the answer, it needs to perform a DNS query to find out.
Step 2: Ask the recursive DNS servers
If the information is not stored locally, your computer queries (contacts) your ISP’s
recursive DNS servers. These specialized computers perform the legwork of a DNS query
on your behalf. Recursive servers have their own caches, so the process usually ends
here and the information is returned to the user.
Step 3: Ask the root nameservers
If the recursive servers don’t have the answer, they query the root nameservers.
A nameserver is a computer that answers questions about domain names, such as IP addresses.
The thirteen root nameservers act as a kind of telephone switchboard for DNS.
They don’t know the answer, but they can direct our query to someone that knows where to find it.
Step 4: Ask the TLD nameservers
The root nameservers will look at the first part of our request, reading from right to
left — www.abc.com — and direct our query to the Top-Level Domain (TLD) nameservers for .com.
Each TLD, such as .com, .org, and .us, have their own set of nameservers, which act like a
receptionist for each TLD. These servers don’t have the information we need, but they can refer
us directly to the servers that do have the information.
Step 5: Ask the authoritative DNS servers
The TLD nameservers review the next part of our request — www.abc.com — and direct our query
to the nameservers responsible for this specific domain. These authoritative nameservers are
responsible for knowing all the information about a specific domain, which are stored in DNS
records. There are many types of records, which each contain a different kind of information.
In this example, we want to know the IP address for www.abcabc.com, so we ask the authoritative
nameserver for the Address Record (A).
Step 6: Retrieve the record
The recursive server retrieves the A record for dyn.com from the authoritative nameservers and
stores the record in its local cache. If anyone else requests the host record for abc.com, the
recursive servers will already have the answer and will not need to go through the lookup process
again. All records have a time-to-live value, which is like an expiration date. After a while,
the recursive server will need to ask for a new copy of the record to make sure the information
doesn’t become out-of-date.
Step 7: Receive the answer
Armed with the answer, recursive server returns the A record back to your computer. Your computer
stores the record in its cache, reads the IP address from the record, then passes this information
to your browser. The browser then opens a connection to the webserver and receives the website.
This entire process, from start to finish, takes only milliseconds to complete.
Was this answer helpful?
It usually takes 24-48 hours for a domain to fully replicate changes, additions, or deletions...
Domain Name Servers (DNS) are the Internet's equivalent of a phone book. They maintain a...
You can Setup your Custom NAME SERVERS on yours Hosting by following Steps. Step 1: Going to DNS...
DNS (domain name system) does not allow multiple A records in a fail over fashion. There are also...
Every domain has a specific IP address it corresponds to. This IP address indicates the “home” or...