FIELD NOTE · Hosting Fieldbook
Changing the website should not surprise your email
Map website, mail, and nameserver responsibilities before changing DNS.
Separate the services in your inventory
Domain registration, authoritative DNS, website hosting, and email can be supplied by different companies. Write one row for each service with its supplier, owner login, and renewal date. An A or AAAA record can direct a website hostname to an address; MX records identify mail handling. TXT records may support email authentication or service verification. A nameserver change moves the authority for the zone and deserves a fuller review than changing one website record.
Preserve the existing zone before a move
Export the current zone where the provider supports it, and keep a readable copy of all visible records. Include www, mail-related names, verification TXT records, service records, and any delegated subdomains. Cloudflare notes that a quick record scan can miss records; an automatically populated list should not be treated as a complete inventory. Ask about services that do not appear in the obvious website records before approving the destination zone.
Choose the smallest change that fits the move
An illustrative site migration may need only the root website address and www updated while existing mail records stay with the current DNS provider. A separate migration might genuinely require a nameserver change and a complete destination zone. Do not substitute one approach for the other without understanding the service map. TTL values describe caching behavior; they do not provide a universal promise that every visitor or application will switch at one exact time.
Verify with a short acceptance list
After the planned change, check the root site, www behavior, HTTPS, a representative contact path, and sending and receiving on the actual mail service. Record the previous values and the conditions for a rollback. Keep the old service available during the agreed overlap when practical. If a domain also hosts nameservers for other domains, involve the person responsible for those dependencies before changing or retiring that infrastructure.
Check the original guidance
Sources checked October 31, 2026. Supplier requirements and platform rules can change.
Prepared with AI assistance. Examples are constructed for explanation, not reported customer results. Corrections are welcome through the contact page.
← All guides