Why old answers can remain after a DNS provider change

Review the new zone, registrar delegation and caches as separate steps.

Prepare the new zone

Create the required records with the new provider before updating the domain’s nameserver settings according to its instructions. Creating a zone in a new control panel does not automatically make outside queries use it.

Confirm the delegation change

Nameservers usually need to be updated at the registrar. Recursive NS answers can help you review the change, but they are not a full delegation trace. For inconsistent answers, compare registrar settings and authoritative responses as well.

Leave room for the transition

Different resolvers may temporarily hold old information. Turning off the previous zone too soon can create avoidable risk. Plan its overlap using the old TTL, provider guidance and checks of the services you actually operate.

This guide explains public DNS responses. Before changing production settings, check the documentation for your current domain and hosting providers.