How domain names become IP addresses, where caching happens, and why record types matter.

What happens during a DNS lookup

Your device first checks local caches, then asks a recursive resolver. If the answer is not cached, the resolver follows referrals from the root zone to the top-level domain and finally to the authoritative nameserver. The returned record is cached for its TTL and sent back to the application.

Records you will use most often

A and AAAA records map names to IPv4 and IPv6 addresses. MX directs mail, CNAME creates an alias, NS identifies authoritative servers, TXT carries policies such as SPF and verification tokens, and CAA limits which certificate authorities may issue certificates.

Caching, security, and performance

DNS is layered: browsers, operating systems, routers, and recursive resolvers may all cache answers. DNSSEC signs records so validators can detect tampering. DoH and DoT solve a different problem by encrypting the query transport. Fast, consistent DNS matters because resolution happens before the browser can connect to a service.

Check it with Net Utils

Use the relevant Net Utils tool and compare the structured output with your expected configuration. Public network data changes, so confirm important conclusions with a repeat test.