The Internal Clockwork of the DNS system

The working of the DNS system is not so hard to understand. Many have incorrect notions about how the heck this system works (or even what the heck thus system is and how it fits into the network’s framework ). If you’re a networking enthusiast and don’t know much about the DNS system then simply put , you know nothing Jon Snow!
So here’s sector 443 bringing you the internal clockwork of thus much ignored ,much trivialized , much underrated but believe me peeps , highly paramount aspect of the network.
First things first, all computers connected on the internet are refereed to using their IP addresses at their lowest level. This is something that the noobiest of noobs would (or should ) know. Now if one had to use these IP addresses every time they had to refer to a node, it would make using the internet a cumbersome disaster of numbers…..shudder

Herp:    Dude did you check out that website I told you about,

Derp:    Yeah, I did, the one with the kiddish games? Those were 2 minutes of my life wasted which I’m never gonna get back. Why on earth would you think I would want to help Dora cross the river man?! Id rather play games on or even for that matter.

Herp:    uuuuuuuh……ypu do realise I’m talking about the music streaming site 1-7-2*point*7-6*point*2-5-0*point*5-7.

Derp:     Ooh! I thought you said, sorry bruh

Herp:  -.- 


See what I mean? So we use domain names , like as an alias of sorts to these IP addresses. Naturally, this calls for a system to resolve these names to obtain the address they point to.

____enter the DNS system___

As soon as you type in a domain name like into your browser, that’s where the hunt for its IP address begins. What it actually looks for, is Notice the terminal dot ? Surprised? Expected. What that is for is to enable it to be recognised by the root server, about which you will come to know by the end of this.

Anyway, coming back to our hunt, as soon as the domain name is typed in, it is checked by the OS and the browser as to whether the IP address corresponding to it is already known or is present in the cache. If not, the OS goes to the Resource Name Server (RNS) following the default mechanism. From here, the RNS takes over the hunt and takes the domain name to the root server. All the root server does,( remember the terminak dot?) is tell the RNS where it can find the .com servers. The RNS takes directions from the root server and continues on its epic journey to the Top Level Domain name Servers (TLDS) handling the .com sites. The .com sites, the .gov sites , the .edu sites etc are all handled by different TLDS. The TLDS then tells our persevering RNS where it can find the name servers of sector 443, called the “authoritative servers”. So how does the TLDS know that ?


Everytime a domain name is bought , a “registrar” is notified as to which authoritative servers will keep a log of them. This registrar  notifies the concerned organisation’s registry and tells the TLDS server to keep its records up to date , so that it knows which authoritative servers to point to , when asked for a site managed by them. So when was bought, the TLDS was accordingly updated.

status check…..? 

Yes, the RNS had just received info regarding which authoritative name servers would have the elusive IP address of and is on its way there. The authoritative name server (finally) tells the RNS the required IP address and brimming with tears of joy, it takes goes back to the OS and hands it over.

cha ching!!! And there we have it, an IP address. This is used by the browser to connect to the required site. And to think that all this happens in less than a fraction of a second makes flash look ….well …..a little less flashy 😉


Leave a Reply

Your email address will not be published. Required fields are marked *