DNS is the distributed naming system that lets people use names instead of memorizing IP addresses. A typical browser lookup involves local cache, a recursive resolver, and authoritative DNS servers for the domain.

Recursive resolver

Your device normally sends the question to a resolver configured by the router, ISP, operating system, VPN, or private-DNS feature. The resolver does the wider lookup work and caches answers.

Authoritative DNS

The authoritative name servers publish the records for the domain. If you change a record at your DNS provider, the authoritative data may update quickly while older cached answers continue to exist until their TTLs expire.

Common records

A/AAAA point to IPv4/IPv6 addresses, CNAME aliases one name to another, MX identifies mail exchangers, TXT carries text-based policy/verification data, NS identifies authoritative servers, and SOA contains zone authority/timing information.

DNS does not carry the webpage

DNS only helps locate services. Once the address is known, the browser still has to establish the network/TLS/HTTP connection. Use the DNS Lookup to inspect published records.

Follow one lookup

The client checks local cache, asks a recursive resolver, and the resolver follows delegations toward authoritative servers if it lacks a cached answer. TTL controls cache lifetime, not instant global propagation.

Record roles

A/AAAA point names to addresses, CNAME aliases names, MX routes email, TXT carries policy/verification data, NS delegates authority and SOA describes the zone.

DNS can work while the website fails

A correct A/AAAA record only gives an address. TLS, firewall, server application and routing still need to succeed.

Video walkthrough for DNS Explained: Resolver, Authoritative Server, A/AAAA, CNAME, MX, and Cache

Explains common DNS record types and how they fit together. DNS resolution is only one layer; a resolved hostname can still have a web, TLS or routing problem.