Managing DNS Records: A, CNAME, MX and TXT Records Explained
Summary
This guide helps you troubleshoot and resolve: Managing DNS Records: A, CNAME, MX and TXT Records Explained. Follow the steps below to fix the issue.
Common Causes
Managing DNS Records: A, CNAME, MX and TXT Records Explained
Your Domain Name System (DNS) records act as a directory for your domain, directing web traffic to your server and email to your mail provider. Knowing how to manage A, CNAME, MX, and TXT records lets you keep your website and email online without relying on support for every small change. This guide covers the most common DNS record types and how to update them safely, while minimising the risk of downtime or email delivery failures.
Pre-Change Checklist
Before modifying any DNS records, complete these steps to reduce the risk of service interruption:
- Verify where your DNS is hosted. Changes must be made at the authoritative name server host, not necessarily your domain registrar. If your domain uses external name servers (such as Cloudflare or your web host), log in to that provider's control panel instead of your registrar.
- Lower your TTL. Twenty-four hours before making changes, reduce the Time to Live (TTL) on the affected records to 300 seconds (5 minutes). This reduces propagation time once the new records are live.
- Backup current records. Take a screenshot of your existing DNS zone, or export the zone file if your provider allows it. This gives you a reference to revert if something goes wrong.
Understanding DNS Record Types
- A record — maps your domain or subdomain to an IPv4 address (where your website lives).
- AAAA record — maps your domain or subdomain to an IPv6 address. Increasingly relevant as Australian ISPs and hosting providers adopt IPv6.
- CNAME record — maps an alias (like
wwworshop) to another domain name. - MX record — directs email for your domain to the correct mail server.
- TXT record — used for verification and email authentication (SPF, DKIM, DMARC).
Registrar-Specific Menu Paths
While interfaces vary, here are common paths for popular Australian registrars:
VentraIP
- Log in to the VentraIP client portal.
- Go to Domains > My Domains.
- Select your domain and click Manage DNS or DNS Management.
- Use the zone editor to add, edit, or delete records.
Crazy Domains
- Log in to your Crazy Domains account.
- Navigate to Domain Management > DNS Management.
- Select the domain and click Manage DNS Records.
- Choose Add Record or edit an existing entry.
GoDaddy AU
- Log in to your GoDaddy account.
- Select Domains and click Manage next to your domain.
- Scroll to Additional Settings > Manage DNS.
- Use the DNS zone file editor to make changes.
Adding or Editing DNS Records
- Log in to your DNS provider's control panel.
- Open the DNS Management, Zone Editor, or Manage DNS section.
- Locate the record you want to add or edit.
- Enter the record details:
- Type: A, AAAA, CNAME, MX, or TXT.
- Name/Host: usually
@for the root domain, or a subdomain likewwwormail. - Value/Points to: the IP address, domain, or text string.
- Priority: required for MX records; set as instructed by your email provider.
- TTL: 300 seconds is recommended during changes; revert to a higher value afterwards if desired.
- Save the record and allow time for DNS propagation.
Tip: Take a screenshot of your current DNS settings before making changes, so you have a reference to revert if needed.
Warning: Do not create a CNAME record for the root domain (@). A root-level CNAME conflicts with existing A and MX records and can break email delivery and website resolution. Use an A record for the root domain instead.
Common Record Types
A Record
An A record maps your domain to an IPv4 address. Use it when pointing your website to a specific web server. Enter your domain (@ for root, www for the subdomain) and the destination IPv4 address.
AAAA Record
An AAAA record maps your domain to an IPv6 address. If your hosting provider supports IPv6, adding an AAAA record ensures connectivity for visitors on IPv6-only networks. The format is similar to an A record, but the value is an IPv6 address (e.g. 2001:db8::1).
CNAME Record
A CNAME maps an alias to a true domain name. Commonly used for subdomains like blog, shop, or www. A CNAME cannot coexist with other record types for the same host name.
MX Record
MX records direct email to your mail server. Leave the Name as @ unless your email provider specifies otherwise, and enter the mail server address (e.g. Microsoft 365 or Google Workspace). Set the priority as instructed by your provider.
Warning: Deleting or modifying MX records will interrupt incoming email. Plan MX changes during low-traffic periods and ensure your new email service is fully configured before removing old records. Email downtime can last until propagation completes.
TXT Record
TXT records handle verification and authentication such as SPF, DKIM, and DMARC. Enter the host (usually @) and paste the full text string provided by your service provider.
SPF, DKIM, and DMARC Examples
Email authentication records help prevent spoofing and improve deliverability. Below are common syntax examples:
- SPF (Sender Policy Framework):
v=spf1 include:_spf.google.com ~all— replace_spf.google.comwith your email provider's include mechanism. - DKIM (DomainKeys Identified Mail): typically a long public key string provided by your email host, added as a TXT record at a selector subdomain (e.g.
default._domainkey). - DMARC (Domain-based Message Authentication, Reporting & Conformance):
v=DMARC1; p=quarantine; rua=mailto:dmarc-reports@yourdomain.com.au— adjust the policy (p) and reporting address as needed.
Note: Wildcard records (e.g. * as the host) direct all undefined subdomains to a single destination. Use them cautiously, as they can interfere with specific subdomain records and email autodiscovery.
After You Make Changes
DNS changes are not instant. They typically take anywhere from a few minutes to 48 hours to propagate across Australian and global servers. Use an online DNS lookup tool to verify your records are visible, and clear your local DNS cache or view your site in an incognito window to check from your device.
Verifying DNS Changes
Command-Line Tools
Use these commands to confirm your records are resolving correctly:
- nslookup (Windows, macOS, Linux):
nslookup -type=A yourdomain.com.au - dig (macOS, Linux):
dig yourdomain.com.au MXordig yourdomain.com.au TXT
Online DNS Propagation Checkers
Use global and Australian-focused DNS checking tools to see how your records appear from different locations:
- Google Admin Toolbox Dig
- DNSChecker.org
- WhatsMyDNS.net
Look for Australian nodes (Sydney, Melbourne, Brisbane) to confirm local propagation.
Troubleshooting
Website Not Loading After Changes
Give DNS time to propagate. Clear your browser cache, use a DNS lookup tool to confirm your domain resolves to the new IP, and if the old IP persists after 48 hours, verify you edited the correct authoritative name server. If changes are still not visible, Open a Ticket for assistance from our Brisbane-based support team.
Email Delivery Issues
If email stops after a DNS change, confirm your MX records were not accidentally modified, and check that your SPF and DKIM records still authorise your email sender. If you recently changed name servers, ensure the new host has the correct MX records configured.
Changes Not Propagating After 48 Hours
If records still do not appear after two days:
- Confirm you are editing the authoritative DNS host, not just the registrar.
- Check for syntax errors in the record value or host name.
- Ensure there are no conflicting records (for example, a CNAME at the root domain).
- Clear your local DNS cache or test from a different network.
- If the issue persists, Open a Ticket and our Brisbane team can investigate your DNS zone.
If you host with us: you don't need to do this yourself — just Open a Ticket and our Brisbane team will manage your DNS changes.
Still Having Issues?
💻 Open a Ticket