Hi, @driggl, the following community topics may prove helpful when making the change to Netlify DNS:
- [Support Guide] Minimal downtime for a live site DNS migration
- [Support Guide] How do I migrate a domain to Netlify DNS with zero downtime?
Any previous DNS record must expire for the new records to be used. The caching and expiry of DNS records is controlled by the “time to live” or TTL values in the DNS records themselves.
I currently see the following NS records for this domain:
driggl.com. 21599 IN NS b.zeit-world.co.uk.
driggl.com. 21599 IN NS c.zeit-world.org.
driggl.com. 21599 IN NS e.zeit-world.net.
driggl.com. 21599 IN NS f.zeit-world.com.
The TTL above shows 21599. This is likely 21600 which is the time in seconds - in other words, a six hour time to live.
This means, when the NS records above are changed, the any other DNS servers on the internet beside the ones listed in the NS records themselves will almost certainly cache the old records for another six hours.
Netlify doesn’t control this caching, your DNS records themselves control it.
Again, the two topics above discuss ways to avoid downtime when making the switch to Netlify DNS. Please see those for more information and, if the solutions there don’t work for you, let us know here.