#DNSSEC problem after switching

19 messages · Page 1 of 1 (latest)

copper hinge
#

Hey,

Today we migrated a domain from another registrar to our own, and moved it to Cloudflare. But now the website doesn't work. I think its a DNSSEC problem, dnsviz.net says so. I disabled DNSSEC, which should fix it. But I still can't access the site.

What can I do to remedy this?

harsh root
copper hinge
#

I just re-enabled it a couple minutes ago

#

But yes, I disabled it before

#

I'll disable it again

#

'tis disabled now

harsh root
#

Why did you re-enable it? If you were trying to update it with CF's values, it looks like it's the wrong algorithm and such

copper hinge
#

I tried re-enabling it with cloudflare's values

harsh root
#

If you're expecting things to change faster: These changes are super slow, usually it's advised that it could take up to 24 hours or so. In my experience it's more like 30 minutes max, but it also depends on the TLD & Registrar, some are slower then others

copper hinge
#

Alright

#

So just to confirm, dnssec is the issue here, and disabling it should fix it

harsh root
#

From then end user's point of view it can be even longer with dns cache and such, the ttl on the dnssec records is an hour

harsh root
copper hinge
#

Alright

harsh root
#

I see you disabled it according to whois, still gotta wait for .nl/TLD's nameservers to stop serving it
dig ds tentijesport.nl @ns1.dns.nl
and then cache at DNS Resolvers like 1.1.1.1 should eventually expire and start working again

copper hinge
#

Ah, okay

#

So it should work if we just wait a little bit

copper hinge
#

All the DNSSEC checkers/tools show it's good now

#

Still can't load the page locally, but that's probably gonna take a while