ERR_NAME_NOT_RESOLVED (403 Forbidden)
Has anyone here had an issue with a 'www' subdomain not redirecting properly to the root domain? A CNAME exists for the www subdomain, and a universal SSL certificate covers both, but I'm still seeing a "ERR_NAME_NOT_RESOLVED" error message, and a (403) Forbidden at CloudFlare. If so, which setting(s) should I be looking to change?
8 Replies
URL in question - http://www.petiq.com/
To be clear, the 4 variations of the domain name are shown here as working or not working:
https://petiq.com/ - WORKING
http://petiq.com/ - WORKING
http://www.petiq.com/ - NOT WORKING
https://www.petiq.com/ - NOT WORKING
UPDATE: I just changed the old www CNAME to an AAAA record and created a redirect rule, as noted here: https://community.cloudflare.com/t/redirect-www-example-com-to-example-com-using-single-dynamic-redirects/636764
(Waiting to see if this works.)
So far, still not working. Waiting for an hour to pass.
In case others are searching, this is a great tutorial:
https://developers.cloudflare.com/pages/how-to/www-redirect/
Cloudflare Docs
Redirecting www to domain apex · Cloudflare Pages docs
Learn how to redirect a www subdomain to your apex domain (example.com).
Not sure, I'm now seeing a "DNS_PROBE_FINISHED_BAD_CONFIG" error message.
I'm now thinking this is a work proxy issue (VPN), since it works from my phone and my home computer, coupled with other people saying it's working for them. So, ironically, my work URLs work everywhere BUT from the office. Ha ha, figures.
UPDATE: This, indeed, was a work proxy issue after all. Our IT dept was able to fix this internally. While I pulled some hair out on this issue (thinking it was DNS-related), I learned something new, and am glad it's fixed.