Server Administration

DNS Explained for WordPress Site Owners

DNS Explained for WordPress Site Owners

DNS is one of those things that works invisibly until it doesn’t. Most website owners never think about it until they move hosts, set up email or try to connect a new service. Then they’re faced with a screen full of records with cryptic names, and a warning that changes can take up to 48 hours.

I’ve spent a surprising amount of my career fixing DNS mistakes. Websites pointed to old servers, business email that stopped arriving after a migration, SSL certificates that wouldn’t issue, verification records deleted by accident. Almost all of them came from changing DNS without understanding what each record did.

The good news is that DNS is simpler than it looks. Here’s what you actually need to know as a WordPress site owner.

What DNS does

Computers find each other on the internet using IP addresses, strings of numbers like 203.0.113.10. People prefer names like example.com. The Domain Name System translates names into addresses and tells the internet where to find different services for your domain.

When someone types your domain into a browser, their device asks DNS servers where the domain lives. DNS answers with your server’s IP address, and the browser connects. Email works similarly: other mail servers ask DNS where to deliver messages for your domain.

Registrar, DNS host and web host

Three different roles often get confused, partly because one company sometimes does all three.

  • Domain registrar: where you register and renew your domain name.
  • DNS host: the service that stores your DNS records and answers questions about your domain. Often the registrar, sometimes your web host, a CDN or a dedicated DNS provider.
  • Web host: where your WordPress files and database live.

Your registrar points the domain to a DNS host through nameservers. The DNS host holds the records that point to your web host, email provider and other services.

Knowing which company does which job saves a lot of confusion. The most common mistake I see is someone editing DNS records at their registrar when the domain’s nameservers actually point somewhere else. The changes do nothing, because the registrar’s DNS isn’t being used.

Nameservers

Nameserver records tell the world which DNS host is responsible for your domain. They look like ns1.example-dns.com and ns2.example-dns.com.

You change nameservers at your registrar. Changing them moves the whole responsibility for DNS to another provider. Before doing that, make sure the new provider already has all your existing records copied over, or your website and email may stop working.

You can check which nameservers a domain uses with an online DNS lookup tool or the command line:

The records you’ll meet most often

A record

Points a name to an IPv4 address. Your main domain usually has an A record pointing to your web server.

AAAA record

The same as an A record, but for IPv6 addresses. Only add one if your server is properly configured for IPv6. A wrong AAAA record can cause problems for visitors whose networks prefer IPv6.

CNAME record

Points one name to another name, rather than an IP address. Commonly used for www, so www.example.com follows wherever example.com points, or to connect services like email marketing platforms.

A standard CNAME can’t be used on the root domain itself, example.com without www, because the root must hold other records like MX and NS. Some DNS providers offer workarounds, often called CNAME flattening or ALIAS records.

MX record

Tells other mail servers where to deliver email for your domain. MX records have a priority number; lower numbers are tried first.

MX records are the ones that most often get lost during website migrations. If you change DNS hosts and forget to copy them, email stops arriving. Your website may work perfectly while your inbox goes silent.

TXT record

Holds text information, used for many purposes:

  • SPF, listing servers allowed to send email for your domain.
  • DKIM keys for email signing, sometimes as CNAME records instead.
  • DMARC policies for email authentication.
  • Domain verification for services like Google Search Console and Microsoft 365.

A domain often has several TXT records. Don’t delete ones you don’t recognise without checking what they’re for; they may be quietly keeping a service working.

CAA record

Specifies which certificate authorities are allowed to issue SSL certificates for your domain. It adds a layer of protection, but if you add one and forget to include the authority your host uses, certificate renewals can fail.

NS and SOA records

These are managed by your DNS host and define the domain’s nameservers and administrative details. You rarely need to touch them.

TTL: why changes take time

Every DNS record has a TTL, time to live, measured in seconds. It tells other DNS servers how long they can cache the record before checking again.

If your A record has a TTL of 86,400 seconds, one day, DNS servers around the world may keep using the old value for up to a day after you change it. That’s where the warning about changes taking up to 48 hours comes from. In practice, most changes are visible much sooner, but the TTL sets the worst case.

Lower the TTL before planned changes

Before moving a website to a new host, lower the TTL on the records you’ll change to something short, like 300 seconds, five minutes. Do this at least a day before the move, so the old, longer TTL has time to expire everywhere. When you make the switch, visitors pick up the new address within minutes. After everything is stable, raise the TTL again.

This one habit removes most of the stress from migrations.

Propagation

“Propagation” is the common word for the time it takes DNS changes to be seen everywhere. Really, it’s caches expiring at different times. During this period, some visitors may see the old site and some the new one.

To check what different parts of the world see, use online DNS propagation checkers, or query specific public DNS servers:

Your own computer and browser also cache DNS. If you’ve made a change and still see the old site, try another device or network before assuming the change failed.

Moving a WordPress site to a new host safely

Here’s the DNS side of a migration done carefully:

  1. Document all existing records. Take screenshots or export them. Include every A, CNAME, MX and TXT record.
  2. Lower the TTL on the A and www records a day or two in advance.
  3. Set up the site on the new host and test it using your computer’s hosts file before changing DNS.
  4. Change only the records that point to the website, usually the A record for the root domain and the www record. Leave MX and TXT records alone unless email is also moving.
  5. Monitor both servers for a few days. Keep the old hosting active until traffic to it stops.
  6. Raise the TTL once everything is stable.

If you’re also moving DNS hosting, by changing nameservers, recreate every record at the new DNS host first, verify them, and only then change the nameservers.

Common DNS mistakes

  • Editing records in the wrong place, at a registrar or host whose DNS isn’t actually in use.
  • Forgetting MX and TXT records when changing DNS hosts, breaking email and verifications.
  • Multiple SPF records instead of one combined record.
  • Wrong AAAA records pointing to old or incorrect IPv6 addresses.
  • Leaving long TTLs during migrations.
  • Deleting unknown TXT records that were keeping services verified.
  • CAA records that block your host’s certificate authority.
  • Old records pointing to decommissioned servers, which can be a security risk if someone else later gets that IP address or service.

DNS and security

DNS controls where your site and email go, so protecting it matters:

  • Use strong, unique passwords and two-factor authentication on registrar and DNS accounts.
  • Enable registrar locks to prevent unauthorised transfers.
  • Consider DNSSEC, which helps protect against forged DNS responses, if your registrar and DNS host support it.
  • Remove records for services you no longer use. Dangling records pointing to cancelled cloud services can sometimes be claimed by attackers to host content on your subdomain.

Frequently asked questions

Why does my site work for me but not for others after a DNS change?

DNS caching. Different networks and devices update at different times based on TTL. Wait, or check with propagation tools to see where the change has reached.

Should I use my registrar’s DNS or a separate provider?

Either works. Dedicated DNS providers and CDNs often offer faster responses, better tools and extra features. What matters most is knowing where your DNS lives and keeping it secure.

Will changing my website’s DNS affect my email?

Only if you change or remove email-related records, like MX, SPF and DKIM. Changing the A record for your website doesn’t affect email, as long as the mail records stay the same.

What does “pointing the domain” mean?

Usually updating the A record, and often the www record, to your web host’s IP address or hostname, so the domain loads your website from that host.

Final thoughts

DNS is the address book for your domain, and a few records control where your website, email and services live. Know which company hosts your DNS, understand the main record types, lower TTLs before planned changes, document everything before you edit and protect your accounts carefully. With those habits, DNS stops being a source of mysterious outages and becomes just another part of your site you understand.