Cloudflare and SiteGround: Diagnose DNS Check Failures
By George Nicolaou
A DNS check failure is a reason to inspect the domain configuration, not to add redirects blindly. This earlier recording shows a Cloudflare and SiteGround troubleshooting case.
Check the domain path
Confirm the authoritative nameservers, the relevant A or CNAME records and the hostname your host expects. Keep mail records intact. DNS updates can be cached, so compare the provider’s settings with the response your browser actually reaches.
Separate DNS from redirects
DNS points the visitor towards a server. A redirect happens after a web request reaches a server. WordPress’s site address, a server rule and a CDN redirect can conflict and create loops if you set them independently.
Use the examples carefully
The older snippets below refer to a specific hostname arrangement. Replace example domains, check the existing server rules and test on staging before adapting them. A hard-coded WordPress URL can help diagnose a configuration problem but should not hide an incorrect migration.
After any fix, check both www and non-www addresses, HTTPS, the administrator login and a form submission. Keep one intentional public address and verify that the others reach it without a chain of unnecessary redirects.
Related guides
# 301 --- https://yourdomain.com => https://www.yourdomain.com
RewriteCond %{HTTP_HOST} ^yourdomain.com$
RewriteRule ^$ https://www.yourdomain.com/? [L,R=301]define('WP_HOME', 'https://www.yourdomain.com');
define('WP_SITEURL','https://www.yourdomain.com');
0 Comments