DNS records sit between your domain name and your website hosting. When someone types your URL into a browser, DNS records translate that name into the actual server address where your WordPress site lives. Most website owners only think about DNS when something breaks — a new domain that won’t connect, email that stops delivering, or a verification code they can’t figure out where to paste.
In my experience, the biggest DNS mistakes happen when people try to rush the process or don’t understand which record type to change. This guide covers the most common DNS record types, where to find them, and how to edit them safely for a WordPress website. If you’re just getting started with a new domain, understanding how to point a domain to your web hosting first will give you the right context for what each record actually controls.
What DNS Records Do
DNS (Domain Name System) records are entries in your domain’s zone file that control where traffic for your domain goes. Each record has a type, a name, and a value — together they tell the internet how to handle requests for your domain.
Changes to DNS records can take anywhere from a few minutes to 48 hours to propagate globally, depending on the TTL (time to live) setting of each record. The IANA domains registry is the authoritative source for how the DNS root system is structured and maintained.
Where to Find Your DNS Records
For most WordPress websites, DNS records live in one of two places:
- Your domain registrar — where you bought the domain (GoDaddy, Namecheap, Porkbun, etc.)
- Your web hosting control panel — if you’ve pointed your domain’s nameservers to your host
If you moved your nameservers to your hosting provider — common with cPanel hosting — log into your hosting control panel and look for a DNS Zone Editor. If you kept the domain at your registrar, that’s where your DNS records will be. If you’ve ever transferred your domain to a new registrar, your DNS records moved with it to the new provider.
The Most Common DNS Record Types
A Record
The A record points your domain name to an IP address — the physical server where your WordPress site is hosted. This is the most fundamental DNS record. A typical A record looks like:
- Name: @ (represents your root domain)
- Value: your server’s IP address (e.g. 123.456.789.0)
- TTL: 3600 (one hour)
CNAME Record
CNAME records point one domain name to another domain name rather than an IP address. Use these for subdomains — for example, pointing www.yourdomain.com to yourdomain.com. You cannot set a CNAME for your root domain (@); use an A record there instead.
MX Record
MX records direct email for your domain to the correct mail server. If you’re using Google Workspace or Microsoft 365, they’ll provide specific MX record values to add. MX records include a priority number — lower numbers are preferred when multiple MX records exist.
TXT Record
TXT records store plain text information. They’re used for domain verification (Google Search Console asks you to add one), and for email authentication via SPF, DKIM, and DMARC. TXT records don’t affect how your site loads — they’re purely informational records read by external services.
NS Record
NS (nameserver) records point to the authoritative nameservers for your domain — telling the internet where to look for all your other DNS settings. These are set at your domain registrar and are rarely changed directly. When you switch hosting providers and they say “update your nameservers,” this is the record type you’re changing.
How to Edit DNS Records Safely
- Log into your domain registrar or hosting control panel
- Navigate to your DNS settings — look for “DNS Management”, “DNS Zone Editor”, or “Advanced DNS”
- Identify the record you need to change by type and name
- Before changing anything, note the current value so you can revert if needed
- Make the change and save
- Note the TTL setting — a lower TTL (e.g. 300 seconds) means changes propagate faster
Common DNS Changes for WordPress Sites
Pointing Your Domain to a New Host
The cleanest approach is to update your NS records at your registrar to point to your new host’s nameservers — this transfers full DNS management to the new host. Alternatively, update just the A record to your new host’s IP address, which is useful when you want to keep DNS management at your registrar.
Adding Domain Verification Records
Services like Google Search Console verify domain ownership by asking you to add a TXT record. Copy the value exactly as provided, set the name to @ (or as specified), and wait for propagation before triggering the verification step inside the service.
Setting Up Business Email
Connecting a business email provider typically requires MX records (to route incoming email), TXT records (for SPF and DKIM authentication), and sometimes a CNAME record for DKIM signing. The email provider supplies the exact values — copy them precisely, including any trailing dots if shown.
Common Mistakes to Avoid
- Deleting NS records — never remove your nameserver records; it takes your domain entirely offline
- Wrong name field format — most registrars expect just “www” in the name field, not “www.yourdomain.com”
- Not waiting for propagation — DNS changes take time; clear your local DNS cache and test in an incognito window to see the current live state
- Adding duplicate records — check for existing records of the same type and name before adding new ones
- Editing without a backup — write down existing values before changing anything
When to Change Individual Records vs Update Nameservers
If you’re moving your entire WordPress site to a new host, updating your nameservers at the registrar is cleaner than editing individual records — it hands all DNS management to the new host at once. If you’re only making a specific change — adding an email record, verifying a service, or updating a subdomain — edit the individual record and leave nameservers alone.
Conclusion
DNS records aren’t complicated once you know what each type does. A records handle your main domain’s IP address, CNAMEs handle subdomains, MX records route email, and TXT records cover verification and email security. Before making any change, note the current values and allow up to 48 hours for propagation to complete globally.
Etienne Basson works with website systems, SEO-driven site architecture, and technical implementation. He writes practical guides on building, structuring, and optimizing websites for long-term growth.