Foldwren

DNS explained simply

A simple explanation of DNS using an address book analogy, what the common records mean in plain words, and why changes take time to appear.

Computers find each other using numbers. People prefer names. DNS, the domain name system, is the thing that translates one into the other, and it does so billions of times a day without anyone noticing.

You will probably never edit a DNS record yourself. But at some point someone will tell you "it's a DNS issue", and it helps to know what they mean, because DNS quietly controls where your website and your email go.

The address book analogy

Think of the contacts list on your phone. You tap "Mum" and the phone dials a number you have not memorised in years. The name is for you. The number is for the phone network.

DNS is the contacts list for the whole internet. When a customer types yourbusiness.com.au, their device looks up that name and gets back a number called an IP address, which identifies the server where your website lives. The browser then goes to that server and asks for the page.

The useful part of this arrangement is the same as with your phone. If Mum gets a new number, you update the contact and keep tapping "Mum". If your website moves to a new server, the DNS record is updated and customers keep typing the same name.

Where your DNS lives

Every domain has nameservers. These are the computers that hold the official address book entries for your domain. They are run by whichever company manages your DNS, which is often your domain registrar, sometimes your web host, and sometimes a separate DNS service.

This trips people up constantly. The domain can be registered with one company while the DNS is managed by another, and the website is hosted by a third. All perfectly normal, but when something needs changing you have to know which login to use. If you take one thing from this article, find out where your DNS is managed and write it down.

The records, in plain words

Your domain's DNS is a short list of records. Each one answers a different question.

  • A record: "Where is the website?" It points a name to a server's numeric address.
  • CNAME record: "This name is an alias for that other name." Commonly used so that the www version of your address follows the main one, or to connect a subdomain like shop.yourbusiness.com.au to a service such as an online store.
  • MX record: "Where should email for this domain be delivered?" It names your email provider's servers.
  • TXT record: a free text note that other systems read. These are used to prove you own the domain when signing up for a service, and to publish rules about who is allowed to send email in your name.

That is nearly the whole vocabulary. A typical small business has only a dozen or so records in total.

The thing to notice is that website and email are separate lines. The A record sends web visitors one way. The MX record sends mail another. That is why your site and your inbox can be with different companies, and also why changing one carelessly can break the other.

Why changes take time

You update a record, and the person helping you says it could take anywhere from a few minutes to a day or two to take effect everywhere. This sounds like an excuse. It is actually how the system is designed.

Looking things up in the master address book every single time would be slow. So the answers get remembered. Your internet provider remembers them, your office router remembers them, your phone and your browser remember them. This is called caching.

Each record carries a number called a TTL, or time to live, which says how long an answer may be remembered before it must be looked up again. If the TTL is one hour, anyone who looked up your site a minute before the change will keep going to the old place for up to another hour.

Different people looked it up at different moments, so the change rolls out unevenly. For a while, you might see the new site while your business partner across town still sees the old one. Neither of you is doing anything wrong. The remembered answers just have not all expired yet.

So after a change, be patient before declaring it broken. Check from your phone on mobile data, which often has a different remembered answer from your office wifi.

How DNS goes wrong

Because DNS sits underneath everything, a small slip has large effects. The common ones:

  • Email stops after a website move. Someone replaced the whole set of records, or switched nameservers, and the MX record did not come along.
  • A deleted TXT record. It looked like clutter, but it was verifying your email service, and now your messages go to junk.
  • The domain expired. Everything stops at once.

What to keep on file

You do not need to become a DNS expert. Keep these four things and you will be ahead of most businesses.

  • The company where your DNS is managed, and a working login.
  • A copy of your current records. A screenshot or export is fine. Take a fresh one before anyone makes changes.
  • A note of what each record is for, even a rough one such as "website", "email" or "newsletter tool".
  • A rule that whoever changes your DNS tells you what they changed and why.

With that, a DNS problem becomes a ten minute fix instead of a day of detective work.

Your order