My CNAME records are not showing up on dns checkers
I already added it on cloudflare though and everything else is fully propagated. That is the A records, Nameserver and mx records. Also the cname records are not proxies on cloudflare. Does anyone know why this is happening?
17 Replies
There is an A record for khariah.com, this takes precedence
CNAMEs can't exist on apexs/the root of your domain, it'd get flattened to A/AAAA records to be spec compliant
So what can I do?
The website refuses to open without using a vpn
Broken local DNS cache? It should work (works for me with
curl -v https://khairah.com/)I've tried flushing my dns though
No change
You upstream DNS resolver may be strange or broken, try setting your local DNS resolver settings to 1.1.1.1
Never mind
I just understood this guy
The cname is is actually showing when I add www
The problem still remains though
I can't access the website from my country
I'm just so confused
How can I do this?
Some countries enforce doing stupid things with DNS, but you can use different DNS resolvers locally like 1.1.1.1 or 8.8.8.8
Somewhere in your local OS there is a setting for this, Google might help
Okay let me search
I couldn't browse anymore
Ayy bro
I solved it
Thanks guys
It was a simple solution at the end of the day
I just had to change my a record to this ip "23.227.38.72"
And it worked
If you manually set an A record you bypass the Cloudflare proxy and you use Cloudflare only as a fancy DNS manager.
Haha. I really only used it for the free ssl
And I manually set the records from the get-go
So I was never able to use the proxy
If you do not use the Cloudflare proxy, you do not use the free/automatic certificate generation as well.
You really only use the DNS manager of Cloudflare in this case
For real?
I guess I may have never needed it
Probably.