Change made, not everyone sees it yet
DNS propagation depends on TTL plus resolver cache. Patience and the right tools.
support/hosting-domeinen-dns/dns-propagatie-wachtensteps: 4
Try this first
- Verify change at the authoritative NS with dig +short @ns1.provider.nl name
- Compare with public resolvers (1.1.1.1, 8.8.8.8) after minutes
- Use dnschecker.org for worldwide sampling
- Allow 1x TTL for broad propagation, longer for ISP resolvers
When to bring us in
Past 24h drift, check if an old NS set is still active somewhere.
See also
- Domain expires tomorrow and nobody saw the emailAn expired domain doesn't transfer instantly. There's a redemption window, but you pay extra.
- Unsure whether to enable auto-renewDisabling auto-renew only makes sense for domains you'll truly drop. For anything live, just keep it on.
- New registrar asks for auth code, can't find itEPP code or transfer code is the password to move a domain from registrar A to B.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.