DNS Management Guide: Edit A, CNAME, MX And TXT Without Panic

DNS is the control panel behind your domain. Change the right record and the website or email starts working. Change the wrong one and both can break. You do not need to become a network engineer - you need a calm map of the common record types and a registrar that lets you edit them live without opening a ticket. (For the bigger "what is DNS" picture, see our separate explainer. This post is the hands-on version.)

Where You Edit DNS

Two common setups:

1. Registrar DNS - nameservers point at your registrar; you edit records in their dashboard
2. External DNS - nameservers point at Cloudflare, your host, or another DNS host; you edit records there instead

If you switch nameservers to an external provider, the registrar's DNS editor often stops applying. That is expected. Manage records in one place only so you are never updating a ghost zone nobody queries.

At Dab Hand Domains you can add, edit, or remove A, CNAME, MX, TXT and other types straight from the dashboard, live. You can also switch to custom nameservers any time if another provider should own DNS.

The Records You Will Actually Use

A record

Points a name at an IPv4 address.

• Example: @ (the root, yourdomain.com) → 203.0.113.10
• Often used for the main website when the host gives you an IP

Get the IP wrong and visitors hit the wrong server or nowhere.

AAAA record

Same idea as A, but for IPv6. Add it when your host supplies an IPv6 address and you want dual-stack. Skip it if they only gave you IPv4.

CNAME record

Points a name at another hostname (an alias), not an IP.

• Example: www → yourdomain.com or shops.examplehost.com
• Common for www, subdomains, and many SaaS "connect your domain" flows

Rules of thumb: do not put a CNAME on the zone apex if your DNS host forbids it (many still do, though some offer workarounds). Do not point a CNAME at a name that is also forced to be something else conflicting. Follow the host's docs literally - letter for letter.

MX records

Mail exchangers - where email for the domain should be delivered.

• Forwarding and Google Workspace and Microsoft 365 all depend on correct MX
• Priority numbers matter (lower number = higher priority)
• Usually several MX lines for one provider

If MX is wrong, mail bounces or never arrives. If you set two different providers' MX at once, behaviour becomes a lottery. One mail system should own MX.

TXT records

Free-text proofs and policies the internet can read.

Common uses:

• Domain ownership checks (Google, Microsoft, Facebook, Apple, etc.)
• SPF - which servers may send mail as your domain
• DKIM - cryptographic mail signing (often a long TXT or a CNAME to one)
• DMARC - policy for what to do with suspicious mail
• Other verifications

TXT records look ugly. Copy-paste carefully. Extra quotes or a missing character fail verification.

Other types you might see

• NS - nameserver records (usually leave these unless you know you are delegating a subdomain)
• SRV - service location (Microsoft, VoIP, some enterprise tools)
• CAA - which certificate authorities may issue SSL for your domain
• URL forwarding - sometimes offered as a feature rather than a raw record; handy for sending the domain to another site with a 301/302

When You Should Edit DNS

Typical moments:

• New website host - update A/CNAME
• New email system - update MX plus SPF/DKIM/DMARC TXT
• Adding a shop, blog, or status page on a subdomain
• Verifying the domain for ads, Search Console, or Apple Pay
• Turning on registrar email forwarding (often automatic MX under the hood)
• Moving off a builder to a custom host

If nothing is changing in hosting or mail, you rarely need to open the DNS panel. Curiosity is a common cause of outages.

How To Change Records Without Drama

1. Screenshot or export the current records before you touch anything
2. Make one logical change at a time (site first, or mail first - not both at once if you can help it)
3. Use the exact values from your host or email provider
4. Save, then wait - TTL and caches mean not everyone sees the new answer instantly
5. Test from an external lookup tool, not only your own laptop
6. Keep the old host alive until the new DNS is confirmed worldwide if you are migrating

Low TTLs (e.g. 300 seconds) before a planned migration make cutover faster. Raise them again later if you like fewer lookups - optional fine-tuning, not required for every small site.

Live Control Beats Support Tickets

Older registrar panels treated DNS like a privilege. You filed a ticket; someone edited a zone file days later. That model is obsolete for anyone running a business site.

You want:

• Immediate edits in the browser
• Clear record list (host, type, value, TTL)
• No charge per record
• Ability to use external nameservers when a client or host requires it

That is standard on Dab Hand Domains and any registrar worth using for client work.

Safety Habits

• Strong account password and 2FA - DNS access is as sensitive as the website admin login
• Domain lock on so random transfer attempts fail
• Limit who has login access to the registrar account
• Document non-obvious records ("TXT for Google Workspace - do not delete")
• After staff leave, rotate credentials

If an attacker controls DNS, they can point your domain at a phishing site or steal mail. The records themselves are simple; the access control is the real security story.

Quick Recipes

Brochure site on a host with an IP:
A record for @ → host IP. CNAME www → @ or the host's hostname, per their docs.

Site only on www:
CNAME or A for www as instructed; redirect apex using host or URL forwarding.

Google Workspace mail:
Replace MX with Google's; add verification TXT; add SPF/DKIM as their wizard says.

Email forwarding only:
Enable forwarding in the registrar UI; let it set MX; do not also paste Workspace MX.

Domain parked / coming soon:
Point at whatever serves the placeholder; keep privacy and auto-renew on so the asset stays yours.

Bottom Line

DNS management is a short list of record types and a habit of careful copy-paste. A and CNAME for web, MX for mail, TXT for proof and mail policy. Edit live in one dashboard, verify outside your own network, and do not improvise on a Friday before a launch.

If your current registrar still makes you wait on a ticket to change an A record, move the DNS or move the domain. You should own the switches that decide whether your site and email work.