Every time you type a domain name into your browser, a small miracle of internet infrastructure fires off behind the scenes — and it all wraps up before you even finish blinking.
You already know what a domain name is. Now let's talk about what it actually does — and how the internet figures out where to send you when you type one in.
The Domain Name System (DNS)
The internet runs on numbers. Every server, every website, every device connected to the internet has a numerical address called an IP address — something like 142.250.80.46. Computers love these. Humans, not so much.
That's where the Domain Name System — or DNS — comes in. DNS is essentially a massive, distributed directory that maps human-readable domain names to the numerical IP addresses computers actually use. When you type google.com, DNS is what translates that into the right IP address so your browser knows where to go.
It's not one giant list sitting on a single server somewhere. DNS is spread across thousands of servers around the world, working together in a hierarchy. That design is what makes it fast, resilient, and nearly impossible to take down entirely.
DNS was invented in 1983 by Paul Mockapetris. Before that, the entire internet's hostname-to-address mapping was maintained in a single text file called HOSTS.TXT that had to be manually downloaded and updated. It worked fine when the internet had a few hundred computers. It did not scale well.
How a DNS Lookup Works
When you type a domain name and hit Enter, your browser doesn't magically know where to go. It kicks off a lookup process that happens in milliseconds. Here's the journey:
-
Your Browser Checks Its CacheYour browser remembers recently visited sites. If you've been to
example.comin the last few hours, it already knows the IP address and skips the rest of the process entirely. -
Ask the Recursive ResolverIf the browser doesn't have it cached, it asks a recursive resolver — usually provided by your ISP or a public DNS service like
8.8.8.8(Google) or1.1.1.1(Cloudflare). This resolver does the heavy lifting on your behalf. -
The Resolver Asks a Root Name ServerThe resolver contacts one of 13 sets of root name servers — the top of the DNS hierarchy. The root server doesn't know the answer, but it knows who does: the name server responsible for the TLD (like
.comor.net). -
Ask the TLD Name ServerThe resolver then asks the TLD name server (managed by the registry for that extension). For a
.comdomain, that's Verisign's servers. The TLD server points to the authoritative name server for the specific domain. -
Ask the Authoritative Name ServerThis is the final stop. The authoritative name server holds the actual DNS records for the domain and returns the IP address. This server is typically managed by whoever hosts the domain's DNS — often the registrar or a hosting provider.
-
Your Browser ConnectsArmed with the IP address, your browser makes a direct connection to the web server and loads the website. The resolver caches the result so future lookups are instant.
The whole process typically takes between 20 and 120 milliseconds. You never notice it happening.
Name Servers: The Gatekeepers
Name servers are the servers that hold the DNS records for a domain. When you register a domain, you assign it to a set of name servers — usually two or more for redundancy. These name servers tell the world where your website, email, and other services are located.
Name servers look something like ns1.yourhostingprovider.com and ns2.yourhostingprovider.com. When you move a website from one hosting company to another, one of the first things you do is update the domain's name servers to point to the new host.
Always set at least two name servers for any domain you own. If the primary name server goes down and there's no backup, your domain stops resolving — meaning your website and email go dark until it's fixed.
DNS Records: The Details Inside
Name servers store individual DNS records — each one is an instruction that tells the internet how to handle a specific type of request for your domain. The most common ones you'll encounter:
- A record — Maps a domain name directly to an IPv4 address. This is the most fundamental record.
example.com → 93.184.216.34 - CNAME record — An alias that points one domain name to another. Useful for subdomains:
www.example.com → example.com - MX record — Tells the internet where to deliver email for your domain. Without a proper MX record, email sent to
[email protected]has nowhere to go. - TXT record — A flexible record used for verification, spam prevention (SPF, DKIM), and other purposes.
- AAAA record — Like an A record, but for IPv6 addresses.
You don't need to memorize all of these right now. But knowing that A records handle website traffic and MX records handle email will save you a lot of confusion when you're setting up or transferring a domain.
DNS Propagation: Why Changes Take Time
Here's something that trips up almost everyone the first time: you update your name servers or DNS records, and nothing seems to happen. Your website still shows the old version. Your email still goes to the old server. What gives?
This is called DNS propagation. When you make a DNS change, that change doesn't instantly appear everywhere on the internet. Resolvers around the world have cached the old information, and they'll keep using it until the cache expires — a window defined by a setting called TTL (Time to Live).
TTL is measured in seconds. A TTL of 3600 means resolvers will cache your DNS record for one hour before checking for updates. Some records have TTLs of 24 hours or more, which is why DNS changes can take up to 48 hours to fully propagate worldwide.
If you're planning a domain migration or transfer, lower your TTL values to 300 (5 minutes) at least 24 hours before making the switch. That way, when you update the records, the old cached values expire quickly and the new ones take effect much faster.
Why This Matters for Domain Investors
If you're buying and selling domains, understanding DNS isn't just academic — it's practical knowledge you'll use regularly.
When you acquire a domain at auction, one of the first things you'll do is update the name servers to point to your own hosting or parking service. That change triggers propagation, and during that window, the domain may resolve inconsistently depending on where in the world someone is accessing it from.
When you sell a domain, the buyer will update the name servers after the transfer completes. Until propagation finishes, the domain may still show your old content or a registrar parking page. That's normal — not a sign that something went wrong.
Understanding propagation also helps you set realistic expectations with buyers. "The domain will be fully live within 24–48 hours" is a much better answer than a confused shrug when they ask why their new domain isn't working yet.
Sites like whatsmydns.net let you check how a domain is resolving from different locations around the world in real time. It's invaluable for confirming that a DNS change has propagated globally.
What's Next
Now that you understand the mechanics of how domain names resolve — from your browser all the way down to an authoritative name server and back — you're ready to go a level deeper. In the next article, we'll explore domain extensions: what the difference is between .com, .net, .org, country-code TLDs, and the hundreds of newer extensions flooding the market. Knowing which extensions hold value — and which ones don't — is one of the most important skills a domain investor can develop.