Staying in home, moving around 3 or 4 rooms makes me really sick.. so thought I could dwell into something I barely know.. how DNS exactly works.. and hows BIND its enhanced version works…

DNS came into picture becas ARPANET failed becas of its HOST.TXT file issue. The issue is there were name collisions which was not handled efficiently. Traffic and load were not really maintained properly in ARPANET, since it was basically designed for smal netework, when promoted to host internet, things started screwing up. Finally it missed (can we say messed? ) consistency levels…

So, here comes Paul Mockapetris, released RFCs 882 & 883 [ which later developed into RFC 1034 & 1035, with enhancements ]

Hmm.. what exactly is DNS? nothing serious, its a distributed DB 🙂 based on client server technology. Server is referred as Name Server, and client as Resolver..

——> Hosts
——> Sub-domains

First implementation of DNS was JEEVES by Paul as we know.. and the later implementation of DNS is BIND…
So wats BIND?
BIND => Berkley Internet Name Domain, started out in BSD 4.3 by Kevin Dunlap. Now its maintained by Internet Software Consortium

OK..lets get into something thats more interesting.. leaving behind all these history stuff..

How are things organised and working out in DNS?
So its similar to unix file system type of listing..
top-level domian names, followed by second level domain ..

top-level domain names like (.com, .org etc.. ) use the delegation model to traverse through the second level and further down..
So how does managing a domian, subdomain take place.. well its delegated.. the management is like this..

consider a site
.com is the toplevel domian which delegates the google guys to manage blogspot , which is a subdomain, whereas, blogspot guys delegate archu ( its me!! ) to manage that particular page.. its that way as simple as it is.. no collisions..

Sounds fine.. but wat is data is lost in toplevel domain..?
here comes the kool back up strategy they follow… they have a primary master and secondary master to take care of the same..
check out the RFCs for more detailed info reg the same 🙂