DEV Community

Discussion on: Explain DNS Like I'm Five

Collapse
 
wulymammoth profile image
David • Edited

If you're familiar with a modern smart phone with a "contact list" or "phone book", ask yourself when the last time you've had to recall the actual digits of the phone number are for a friend/family member. Hardly? If ever?

The Internet is made up of IP (Internet Protocol) addresses, the phone numbers of the internet -- an address is simply the location representing an entity and/or resource. It's hard to remember compared to your friend's name or the URL of a site, like Dev.to whose IP from where I am, resolves to 151.101.130.217. That would be difficult to remember each time I wanted to visit this site.

A DNS aka domain name service, provides translation of the URL (top-level domain) to an IP address in a decentralized, semi-federated, fashion that provides essentially a map to take what we can remember and translate it to something that we don't (the actual IP address)

Collapse
 
ferricoxide profile image
Thomas H Jones II

Perhaps even more critically...

Take that contact book and distribute it in a hierarchical fashion: if it's not in your contact-book, your contact-manager app contacts an upstream contact-book to see if it either knows the number or knows "somebody" how knows - or can find out - the person's phone number for you.

...Though that starts bleeding dangerously into "explain LDAP like I'm 5" territory.