DNS Lookup — How Domain Name Resolution Actually Works

Every time you visit a website, a DNS lookup happens behind the scenes. Learn how it works and why it matters.

Every time you type "google.com" into your browser, your computer needs to figure out the actual IP address of Google's server. That's what DNS (Domain Name System) does — it's the phone book of the internet, translating human-friendly domain names into machine-friendly IP addresses.

The DNS resolution process

When you enter a URL, here's what happens in roughly 50 milliseconds:

1. Your browser checks its cache. Already visited this site recently? Use the cached IP.
2. Your OS checks its cache. Same thing at the system level.
3. Your router may have a cache. Another layer of lookup.
4. Your ISP's recursive resolver does the heavy lifting — querying root servers, TLD servers, and finally the authoritative name server for the domain.

All of this happens before the first byte of the website reaches you.

Common DNS record types

A record — Maps a domain to an IPv4 address. The most fundamental record.

AAAA record — Maps a domain to an IPv6 address.

CNAME record — An alias that points one domain to another. Like saying "www.example.com is the same as example.com."

MX record — Specifies which mail servers handle email for the domain.

TXT record — Holds arbitrary text. Used for email authentication (SPF, DKIM, DMARC), domain verification, and other metadata.

NS record — Specifies which name servers are authoritative for the domain.

Why DNS matters for troubleshooting

When a website is "down," it's often a DNS issue. DNS propagation after changes can take up to 48 hours. Incorrect MX records mean emails bounce. Missing SPF/DKIM records mean your emails go to spam.

Check any domain

Toolozo's DNS Lookup tool lets you query DNS records for any domain. See A, AAAA, CNAME, MX, TXT, NS, and SOA records instantly. Useful for debugging website issues, verifying email configuration, or just understanding how a domain is set up.