Make a DNS record inventory before a website launch

A domain's DNS zone often supports more than its main website. Email delivery, sending authentication, service verification and application subdomains can share the same zone.

Before a launch or nameserver move, record the complete set of records so a website change does not accidentally remove another service.

Identify the authoritative provider

Confirm which nameservers currently serve the domain. Editing a zone at an old provider will not change answers from the active one.

Keep the current record names, types, values and TTLs in a private export or controlled document. Preserve exact technical values rather than translating or retyping them from a screenshot.

Separate the planned change

Mark which website records need to change and which records must remain. A move of the main site does not necessarily require changing email routing or a verification token.

If a new provider imports records automatically, compare the imported zone with your inventory rather than assuming the import was complete.

Verify the services individually

After the change, check the root website and important subdomains. Then test mail delivery, website-generated email and any externally verified application that depends on DNS.

A working home page is not a complete validation of a DNS migration.

Account for caches

Previously cached answers can remain visible for their TTL. Changing the TTL now does not immediately invalidate an answer already stored elsewhere. Cloudflare's TTL reference explains the role of that value.

Use the DNS verification checklist to distinguish authoritative records from cached answers. Keeping the inventory gives you a concrete rollback reference and makes missing-record reports much easier to investigate.