(please specify the URL of the site on which you are experiencing the problem)
404 (002)
pixie proxy
(please share the FULL error message you see, if applicable)
Moved domain from pork bun to infinity free yesterday by changing ns records. Change has not propagated and from googling it seems it may be because i need someone to turnoff dnssec for me. TIA
Please note that it can take up to 72 hours for the website to work on your side due to DNS caching:
Also, we aren’t a domain registrar, so your domain will still be yours and will be on Porkbun unless you transfer it to another registrar in the future; I also think DNSSEC is disabled because if you had it enabled you couldn’t even change the nameservers to ours in first place.
That’s normal; free hosting nameservers don’t support DNSSEC, so all queries from the nameservers that manage the zones for com. to your domain, after some encrypted queries, will be then sent unencrypted. As long as your website will work fine you don’t need to worry about it.
I never loaded it before until you posted the domain here, plus I always use other DNS servers to avoid DNS cache on my end; since you loaded it before, that’s probably why it got the 404 page you got before cached or Porkbun’s server record still on your DNS cache. You might need to try the workarounds from the article I posted before and, if that still doesn’t work, clear your browser cache by pressing a few times Ctrl+F5 while visiting your website or by following this if your browser is a bit stubborn:
thank you bey much for your help, I will have a go at those trouble fixing steps, but everything appears to be set up correctly and should just resolve itself with time?
Even waiting should work if you’re patient enough, though if you need to visit it as soon as you can (because most people in the forum need their website accessible as soon as possible) then you can troubleshoot with the steps I gave you.
Looking at the DNSViz results, it does seem like DNSSEC is broken for your domain. However, not all DNS resolvers actually check DNSSEC, so this only means some people are unable to access your website, not everyone.
This will probably make it impossible to get an SSL certificate, because SSL vendors do check DNSSEC.
However, we can’t fix this for you. We can’t delete the DNSSEC records for your domain, because our nameservers don’t do DNSSEC to begin with.
Your domain on the other hand is configured to require DNSSEC at the registry level. So to fix this issue, please disable DNSSEC at your domain provider.