Problem after changing nameservers to suggested

Hello,
We have added a site to our account at Cloudflare, which is hosted at a server we administrate and is already live. We have copied all A, CNAME, TXT and MX records to Cloudflare and then we changed the nameservers, as suggested. However, the site did not work after these steps. I would appreciate your help.

Don’t orange-cloud your DNS entries until you’ve thoroughly tested to make sure everything is working perfectly as-is. Then (if you want to) you can start gradually orange-clouding, one at a time, doing proper testing in between to identify breakages. As it is nobody can tell you what went wrong without more information. What’s the domain?

2 Likes

The website is climateofchange.info. As I mentioned, it is already live

You’re not on Cloudflare DNS currently so I assume you went back to your previous DNS host? You should try switching back to Cloudflare but make sure none of your DNS entries are orange-clouded. Test that everything works properly, then you can gradually start orange-clouding. If you don’t want to risk downtime of your main site, use a test subdomain, set it up as an alias on your web server (so it displays the same content), and orange-cloud the DNS entry for the test subdomain only. If an issue is encountered when you orange-cloud it, post back with detailed information about what’s not working.

Although it will be invisible to visitors, a change in nameservers will result in a change in the hosting server for the website. The URL that visitors use to access the site may remain exactly the same; however, the website will be hosted on a different computer.

Afraid that is not correct. Changing nameservers won’t change anything about hosting, it simply changes the authoritative nameservers, that’s it. In a reverse proxy case, you’ll also route the requests through the proxy, that still does not change the host.

1 Like