However, DNS verification still fails. It says, that www.driggl.com does not point to Netlify servers…
Sometimes the DNS verification succeeds for the root domain, but in other time it also generates errors (i.e.: “driggl(dot)com is not resolvable with a resolver that validates DNSSEC” or: “driggl(dot)com doesn’t appear to be served by Netlify”
The Troubleshooting guide says, to contact support in case one domain succeeds and other fails, so here I am. Is it possible for you to help me with that?
Update:
Unfortunately I needed to revert my DNS configuration and point it out to my old servers.
If there is anybody who could put some light on this topic, I’d appreciate any help.
Thanks, but as I mentioned in the post above - I needed to revert my DNS configuration to keep my site working. I inded have some issues with the domain registrar which I need to solve first. Thank you.
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.