Cloudflare nameservers causing "This site can’t be reached"

Website, Application, Performance DNS & Network
1

I’m using AWS EC2 to host a node.js server using Nginx,

I use google domains to register my domain, when I switch the name servers to cloudflare’s name servers, many, almost all, internet connections cannot access my website. When they try to visit my website they simply get a This site can’t be reached error.

When I switch back to google’s nameservers, my site works perfectly fine, I also had this issue with AWS Route 53 a while back, with the same exact issue happening. I have no clue how to fix this issue, simply switching the DNS server that all of those internet connections use isn’t viable.

5

It is difficult to tell without knowing the domain, but the problem could very well be explained if you had DNSSEC active but didn’t update the values after changing your nameservers.

If you test you site on https://internet.nl and the result is “DNSSEC exists”, then you need to update the value along with your nameservers.

1 Like
6

Yep, this was most likely the issue.
I don’t have time to test it today, but if I run into any errors after the DNSSEC records publish again, i’ll post here again.
Thanks a whole bunch!

1 Like
7

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.