Imprint №01 · Fremantle, WA · Est. 2024
/ № 02DNS

Understanding DNS: The Internet Phone Book Made Simple

By Cybermonkey

15 April 2026

8 min

Almost everything you do on the internet — opening a website, sending an email, joining a video call — starts with a single, almost invisible question: where exactly on the planet is the computer I am trying to talk to? The answer comes from a system called DNS.

A phone book the size of the world

The shortest correct description of DNS is the one in the title: a phone book. When you type cybermonkey.net.au into your browser, your computer does not know yet which physical machine to connect to. It asks a DNS server: "what is the address for cybermonkey.net.au?" The server replies with a number — say 203.0.113.7 — and your browser opens a connection to that number.

The reason this exists at all is that humans are good at remembering names and computers are good at remembering numbers. DNS is the translation layer between the two. Every time you click a link, send an email, or load an app, DNS is doing this look-up — typically in under fifty milliseconds, often dozens of times per page.

“If the internet has a single point of failure, it is DNS. Most outages dressed up as "the internet is down" are really DNS having a bad day.”

Who actually answers the question

Three layers of resolver work together to answer a DNS query. Knowing which one is which makes the rest of this easier to think about.

  1. 01Your device asks the resolver configured on the local network. By default that is whatever your home router or workplace gateway hands out, often Google (8.8.8.8) or Cloudflare (1.1.1.1).
  2. 02If the resolver does not already know the answer, it asks the root and then top-level (.au, .com) name servers for guidance, eventually reaching the authoritative server for the domain.
  3. 03The authoritative server replies with the address. The resolver caches the answer for a while (the "TTL" controls how long), and the resolver hands it back to your device.

The whole exchange is finished long before the page begins to render. Most people will never know it happened.

Why this matters for your security

Three things make DNS a security topic, not just a plumbing topic.

It is a tracking layer

Every DNS query reveals which sites you intend to visit. By default, queries travel as plain text — anyone who can see your network traffic (the café Wi-Fi, your ISP, your employer) can see the names you are looking up. Switching your device to DNS-over-HTTPS or DNS-over-TLS — both are now built in to every major browser and operating system — encrypts these queries.

It is a phishing surface

A great deal of phishing relies on lookalike domain names — `cybermonkey-au.net` instead of `cybermonkey.net.au`, or homoglyph swaps like а ⇄ a between Cyrillic and Latin alphabets. DNS is the layer that decides whether a name resolves at all. Subscribing to a filtering DNS resolver (Quad9, NextDNS, Cloudflare for Families) means many of those names simply will not resolve on your devices, regardless of who clicks them.

It is the keys to your domain

If a criminal can change the DNS records for your domain — pointing your email or website somewhere they control — every other security control becomes irrelevant. The single most important control around your business domain is therefore not technical: it is the access controls on your domain registrar account. MFA, a password manager, and two trusted humans who can recover the account.

Three signs your DNS is healthy

You do not need to be a network engineer to keep your DNS in good shape. Three quick checks tell you most of what you need to know:

  • Your domain registrar account is on MFA, with a recovery contact you actually trust.
  • Your devices are using an encrypted resolver (DoH or DoT). Most operating systems now expose this in network settings.
  • Your business domain has SPF, DKIM and DMARC records set up — the three records that stop other people impersonating your email. The Australian Cyber Security Centre publishes a very plain-English guide to setting them up [1].

That is enough to put you ahead of the great majority of small businesses on the internet today. The internet is held together by quiet little systems like DNS, and a small amount of attention to them goes a very long way.

If you want a hand auditing your domain, registrar account, or DNS configuration, that is something we do as a single afternoon engagement. Drop us a line.

/ References

  1. [1]ACSC — Strategies to mitigate cyber security incidents (DMARC / SPF / DKIM)
  2. [2]Cloudflare — A primer on DNS-over-HTTPS
← Back to the archive
DNSEducationFundamentals