You need to "just point the domain" to the new host. You open the DNS zone, see twenty lines of A, CNAME, MX, TXT — and the temptation to replace everything with what the PDF tutorial says. Fifteen minutes later, the site responds but no email arrives. DNS is not complicated — it is unforgiving.
Understanding a few concepts before touching a zone avoids simultaneous cuts to site, mail and subdomains. DNS is your infrastructure's invisible API: one badly copied line has the same impact as a server outage, without as visible a restore button.
DNS in one useful sentence
DNS is a distributed directory: when a browser asks for www.yoursite.com, it gets an IP (or another name via CNAME). Same logic for email via MX records.
Records you will actually touch
| Type | Role | Example |
|---|---|---|
| A | Name → IPv4 | www → 93.184.x.x |
| AAAA | Name → IPv6 | www → 2001:db8:: |
| CNAME | Alias → other name | www → hosting.example.com |
| MX | Inbound mail | @ → mail.provider.com (priority 10) |
| TXT | Verification, SPF, DKIM | SPF, Google verify |
| NS | Authoritative zone servers | Delegation at Cloudflare |
Editing an A without touching MX is possible. Deleting the whole zone "to start clean" is not.
TTL and propagation
TTL (Time To Live) is cache duration at resolvers. Before migration: note current values (screenshot), lower TTL to 300 seconds if possible 24–48 hours ahead, apply change, then wait the old TTL maximum to judge propagation. Useful tools: dig, whatsmydns.net, dnschecker.org.
Beginner mistakes to avoid
Double CNAME on the same name. CNAME on @ (apex) when registrar requires A or ALIAS. Forgotten MX after site migration. Duplicated SPF — one TXT SPF record per domain only. Changing NS and records same day without a plan.
Who manages what in your stack
The registrar changes NS and sometimes a basic zone. The web host sets A/CNAME to the server. The mail provider manages MX, DKIM, SPF. The CDN (Cloudflare) adds orange proxy and records. Document where the authoritative zone lives before any change.
The climax: DNS is your infrastructure's invisible API
Follow with Business email and SSL certificate once A/CNAME are stable.
Decide and move forward without blind spots
Identify where the zone is hosted by reading NS records. Export or screenshot all current records before editing. Lower TTL before any major change. Apply one change at a time and test after each step. Verify site AND email after every edit.
Frequently asked questions
Registrar vs DNS host?
Registrar sells domain; NS indicate zone host.
How long does propagation take?
Depends on TTL — lower it before migration.
CNAME vs A record?
A → IP; CNAME → alias (watch apex @).
Can I break email editing DNS?
Yes — do not touch MX without copying current values.
DNS rewards slowness and documentation — never the courage of a total reset without backup.