Infrastructure · 6 min

DNS, website and email migration: three systems that must not be confused

Many migration failures happen because a website move is treated as a single switch. In reality, application hosting, authoritative DNS and email delivery can be controlled by different providers and records.

Record the current authority

Capture nameservers, A and CNAME records, MX routes, SPF, DKIM, DMARC, verification records and application dependencies before any edit.

Move only the intended layer

If the website is changing servers, preserve mail records unless email migration is explicitly in scope. A new web IP should not silently replace the whole DNS zone.

Advertising placementResponsive in-article placement after the second sectionDesign preview only · live AdSense is restricted to production Insights pages.

Lower risk before cutover

Prepare SSL, application configuration, database state and host-based testing first. Reduce TTL early enough to matter and keep the previous service available during convergence.

Verify from outside

Check the public website, form delivery, inbound and outbound mail, DNS propagation and important third-party callbacks from more than one network before closing the rollback window.