Domain name servers and DNS explained

DNS, the Domain Name System, is the address book that turns a name a person can remember into the numeric address a computer actually needs. Registering a domain does not, by itself, make a website appear or email arrive. DNS is the separate configuration step that connects the name to both. DNS measures 1,900 searches a month in Australia, the largest single figure in this whole cluster, recorded 3 August 2026 in research/outer-volume-au.json.

Why registering a domain name is not enough on its own

A domain registration establishes who holds the name. DNS records are what tell the rest of the internet where to send traffic for that name: which server hosts the website, which server accepts email, and which other services, if any, sit behind it. A newly registered domain with no DNS configured points nowhere. That is the single most common reason a “finished” website is not yet visible to anyone.

How a DNS query actually resolves: recursive resolver, root and name servers

A device does not hold DNS records itself. It sends a DNS query to a recursive DNS resolver: often the internet provider’s own, or a public DNS server such as Google’s or Cloudflare’s. That resolver does the DNS lookup on the device’s behalf. If the resolver has not seen the domain name recently, it asks the internet’s root DNS servers which top-level DNS servers handle the relevant extension. It then asks one of those DNS servers which name servers are authoritative for the domain. Finally, it queries one of those authoritative name servers directly for the DNS record it needs — an A record, an MX record, whatever was asked for. The answer travels back through the same chain to the device that started it, normally in well under a second. This DNS resolution process is the mechanism every record type below is quietly relying on.

The Domain Name System record types that actually matter to a business owner

A and AAAA records point the bare domain (and usually www) at the numeric address of the server hosting the website. This is the record a hosting move actually changes.

CNAME records point one name at another name rather than at a number directly — commonly used for subdomains pointing at a service provider’s own infrastructure.

MX records direct where email for the domain is delivered. These DNS records are entirely separate from the DNS records controlling the website. A business can host its website with one provider and its email with a different one, purely through DNS, and very commonly does.

TXT records carry verification and authentication information rather than routing traffic anywhere themselves. Most importantly, this means SPF, DKIM and DMARC DNS records, which tell receiving mail servers that email claiming to be from your domain is genuinely authorised to be. This control is covered further in business email on your own domain.

Who controls these DNS records at the authoritative name servers, and why it matters

DNS is typically managed either at the registrar, or at a separate DNS provider the domain has been pointed at. The two are not always the same company, and a business can genuinely lose track of which one actually holds the working DNS configuration. Whoever controls the DNS panel controls where the website and email currently point. That makes DNS access a fourth item, alongside the registrar, the registrant record and the account login, worth confirming explicitly rather than assuming a supplier has handed over.

Propagation, and why a change is not instant

Changing a DNS record does not take effect everywhere at once. DNS records carry a Time To Live, or TTL, telling other systems how long they may keep a cached copy before checking again — commonly minutes to a day depending on how it was set. A DNS change can take up to that period to be visible everywhere. That is why a competent move lowers the TTL in advance of a planned cutover, rather than discovering the delay during one. This exact mechanic is what makes moving hosts without downtime a sequencing problem rather than a single switch to flip.

What to check yourself on the internet, in about five minutes

A domain’s current DNS records can be inspected through any public DNS lookup tool, without needing account access to anything. Confirm the A record points at the hosting you believe is current. Confirm an MX record exists and points where you expect email to be delivered. A missing or unexpected MX record, in particular, is a quiet and common DNS failure. Email can silently stop arriving at a domain long before anyone notices, because nothing about the website itself changes when it happens.

Nameservers, briefly, as the DNS layer above individual records

Before any individual A, MX or TXT record is set, a domain points at a set of DNS name servers — generally the registrar’s own by default, or a separate DNS provider’s if the domain has been pointed elsewhere. Changing name servers moves an entire DNS configuration wholesale to wherever they point. That is a bigger, less common change than editing an individual DNS record, and one worth understanding as a distinct action with its own, sometimes longer, propagation behaviour.

Why DNS changes are worth making outside business hours

Even with a lowered TTL, there is always some residual uncertainty during DNS propagation. Making a DNS change late at night or during a genuinely quiet period, rather than in the middle of a business’s busiest trading hours, reduces the practical impact of anything that does not propagate as cleanly as expected.

Keeping a record of the intended DNS configuration

A simple written note of what each DNS record should point to, kept independently of any single provider’s dashboard, makes it far quicker to notice and correct an unexpected DNS change than relying on memory alone.

A quick DNS sanity check worth repeating after any change

Re-run a public DNS lookup an hour after any change, and again the next day. This confirms DNS propagation actually completed everywhere, rather than only at the point closest to whoever made the change.

Where to go from here

Whether a fast DNS lookup actually delivers a fast page is a separate, hosting-and-server question, covered in does Australian hosting make a site faster. The account that actually controls these DNS records, together with the domain licence itself, is the subject of who owns your business domain. Configuring DNS records correctly is ordinarily included in a supplier’s build work. Where it is not, it is worth asking for explicitly — see web development services.