CNAME still not working?
Hi all. Just became aware of the outage. I set up a new CNAME for my site (following the Backblaze B2 with Cloudflare CDN guide online "Deliver Public Backblaze B2 Content Through Cloudflare CDN") last night and it is still not working. According to the status page of the outage "DNS Updates: Restored" however this change still is not accessible. I tried re-adding the CNAME again after seeing the updated status but the change is still not accessible on my end and on DNSChecker. Leads me to believe I'm doing something wrong?
Possible unrelated info but provided as background incase (see CNAME info below)
My DNS Records includes only 8 A records 4 of which are "www" and the other four seem to be the root site. They all point to some IPs I think for webpage hosting? It's been a long time since I set this site up so I'm not sure but regardless they are working and not part of the larger problem. Just including this info in case it is relevant. Also these were set up a while ago.
The issue is with the single CNAME record I have with name "forever" and target "f00X.backblazeb2.com" with proxy status enabled just as is done in the above mentioned guide. Going to forever.mysite.com/file/bucketname/filename should result in a download but instead I get
forever.mysite.com’s server IP address could not be found. ERR_NAME_NOT_RESOLVED
Any ideas?
3 Replies
Hey 👋
hmm.. keep in mind with a proxied CNAME you'd only ever see it as A/AAAA records, if you're using dnschecker/etc, you won't see it as the CNAME.
Can you share the real domain name (DMs is fine)? It'd be helpful to ensure it's just not cache/something else.
Otherwise I would check via dnschecker for a/aaaa, might just be local or resolver cache
yes i checked A/AAAA records as well after seeing some older forum posts mentioning it. still nothing unfortunately. and yes ill DM you the link. appreciate the help!
ended up being related to the new zone/dns issues, resolved now