Changing nameservers without losing track

First, record the existing zone

Record all existing entries before replacing nameservers. Include website targets, MX and TXT values for SPF, DKIM and service verification. Check subdomains too. A domain can serve several services at once; the visible website is only one.

• Website: root domain, www and other subdomains in use.
• Email: MX, SPF, DKIM, DMARC and service verification records.
• Other services: additional TXT, CAA or SRV records.
• Coordinate existing DNSSEC settings with both services.

Prepare the new zone

Create the DNS zone at the new provider and copy the required records. Use only the nameservers assigned to your account by that provider. The assigned nameservers depend on the DNS provider and service. Guessing a nameserver list can prevent the domain from resolving correctly.

Change delegation and check it

Then replace the nameservers at your domain provider. This changes delegation at the registry. Check website and email from multiple networks afterwards. Cached responses may temporarily show the previous configuration. Keep the old zone available during the transition.

Handle DNSSEC separately

If DNSSEC is enabled, signing and DS records must match the new zone. An outdated DS association can stop resolution for validating resolvers. Coordinate the change with both DNS providers beforehand. DNSSEC management is not enabled in the first atdomain.at release.