If you are like me, application-heavy and network-light, then DNS is a relative mystery to you. A friend (network guy) gave me the following high level explanation.
You type and enter an address into your browser, e.g. http://diablopup.blogspot.com.
The first thing that happens is your computer asks your ISP's (e.g. AT&T's) DNS server (1) "do you know the IP address for this website?" If it does, it will tell your computer what it is, and you connect directly to the Website Server (3).
If your ISP's DNS server doesn't know, it will ask (in a roundabout way) the website owner’s DNS server for the IP address(2). Then it connects to the website server (3).
Once your ISP's DNS server knows the IP address, it keeps it in cache so it doesn't have to ask again, thereby making the connection quicker on subsequent requests. This is why you sometimes experience a slow page load when visiting a website for the first time, but then witness quicker connection on subsequent visits.
There are more "nuts and bolts" to DNS, but this is an intuitive picture for people who can't work with DNS directly.
4 comments:
This will clear lots of confusion that exists with regular programmers, who never bothers to understand how it works. Good topic, keep it up.
Good one, but can you elaborate more? Maybe on the setup part. Try this one >> http://www.server-world.info/en/note?os=ce5&p=dns&f=1
and blog about it :)
hello i like a lot your blog, has very good information. thanks by sharing this information
Brilliant post and useful information…I think this is what I read somewhere…but
Post a Comment