Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

DNS Explained – How Domain Names Get Resolved

bhusalmanish.com.np

Post reply on HN
Print view View original

1–10 of 54 posts

Re: DNS Explained – How Domain Names Get Resolved

#6

Post by okchildhood »

biglyburrito wrote: post #5

This might be the easiest-to-understand breakdown of DNS that I've seen to date. I've owned a domain since the late 90s, but never really understood everything the acronyms or concepts involved in making it work. Well done!

Thanks! That was exactly what I was going for - making DNS approachable for everyone, not just sysadmins. Glad it helped!

Re: DNS Explained – How Domain Names Get Resolved

#8

Post by stevekemp »

Only oddity was the reference to the "router cache". I agree if your browser tried to lookup example.com the local cache would be used, but then it would be the system's configured DNS server - and that would most likely be an ISP, rather than your local router.

(Assuming a typical home connection, your router is _probably_ not a DNS server with local cache, it probably is a DHCP server which will hand out the upstream/ISPs' nameservers.)

Re: DNS Explained – How Domain Names Get Resolved

#9

Post by jdsnape »

stevekemp wrote: post #8

Only oddity was the reference to the "router cache". I agree if your browser tried to lookup example.com the local cache would be used, but then it would be the system's configured DNS server - and that would most likely be an ISP, rather than your local router. (Assuming a typical home connection, your router is _probably_ not a DNS server with local cache, it probably is a DHCP server which will hand out the upstre…

I think this is probably quite dependent on what’s normal for ISPs in the region. In the UK for example, every ISP router I’ve had runs a DNS server and it’s that which is given out via DHCP. It then forwards onto the ISPs DNS platform.
Post reply on HN