What is DNS? The internet’s address book, explained

The problem it solves

Computers on a network find each other using IP addresses — numerical identifiers with no inherent meaning to a human. Humans, by contrast, remember names far better than numbers, and names can stay stable even when the underlying number changes. DNS bridges that gap: it is a distributed system that maps names to addresses, so “example.com” always resolves to wherever that service currently lives, even if its address changes behind the scenes.

That “behind the scenes” part is the real value. Without DNS, moving a website to a new server would mean telling every visitor a new number. With DNS, you simply update the record, and the name keeps working — the indirection is what makes the modern internet operable at all.

How a DNS lookup works, step by step

When you type a domain name into a browser, a chain of lookups happens in a fraction of a second. In plain terms:

• Your device asks a resolver (often run by your ISP or a public service) if it already knows the answer — if it is cached from a recent lookup, the process stops right here.
• If not cached, the resolver asks a root server, which does not know the answer either but points it toward the right top-level-domain server (the one responsible for “.com”, “.org” and so on).
• The top-level-domain server points the resolver toward the authoritative server for that specific domain — the source of truth for example.com’s records.
• The authoritative server returns the actual answer: the IP address (or other record) requested.
• The resolver caches the answer for a set period and returns it to your device, which can now connect directly to that address.

Common record types, briefly

A domain’s DNS configuration is a set of records, each serving a different purpose. You do not need the syntax to understand the concepts: an A record (or AAAA for the newer IPv6 addresses) maps a name directly to an IP address; a CNAME record maps one name to another name, useful for pointing a subdomain at a service without hard-coding its address; an MX record says which mail servers handle email for the domain; a TXT record holds arbitrary text, commonly used to prove domain ownership or configure email security; and an NS record says which servers are authoritative for the domain in the first place.

Why DNS matters in the cloud

DNS is not just about finding a website — in cloud architecture it underpins routing, load balancing, failover and global traffic management. A load balancer’s DNS record can be updated to redirect traffic away from an unhealthy region; a globally distributed application can use DNS to send each user to their nearest data centre; a failover system can swap which address a name resolves to the moment a health check fails. Much of what looks like “smart” cloud behaviour is, underneath, DNS being updated automatically.

It is also worth knowing that DNS is often a globally scoped service rather than tied to a single region — the same idea our explainer on regions and availability zones touches on for other services. A DNS configuration typically applies everywhere at once, which is part of why getting it right matters so much.

DNS services in AWS, Azure and Google Cloud

All three major providers offer a managed DNS service that handles this for you rather than requiring you to run your own DNS servers. AWS’s is Route 53; Microsoft Azure’s is Azure DNS; Google Cloud’s is Cloud DNS. Conceptually they do the same job — host your domain’s records reliably and resolve them quickly worldwide — though each integrates differently with its own provider’s load balancers, health checks and traffic-routing features.

Because DNS sits underneath so much else, misconfiguration here tends to cause outages that look confusing at first: a service that is running perfectly well but simply cannot be found. That is the honest root of “it’s always DNS” — the infrastructure is so reliable and so invisible that when something does go wrong, DNS is often the last place people think to look, and the first place the problem actually is.

Where DNS appears in certification study

DNS shows up throughout the networking domains of the associate-level exams. On AWS, both the Solutions Architect Associate and CloudOps Engineer Associate expect you to understand DNS concepts and how Route 53 fits into routing and failover design. On Azure, the AZ-104 Administrator Associate exam covers DNS as part of its networking domain, including name resolution for virtual networks. Treat this article as the conceptual foundation, and go deeper with the networking lessons in our revision sections for exam-level detail on each provider’s specific service.