I have my domain pointed from cloudflare’s ZeroTrust cloudflared-tunnel but I deleted that and pointed the same again to an IP but it doesn’t work
What steps have you taken to resolve the issue?
I’ve head on over to ZeroTrust, opened my tunnels and deleted the configuration I was using.
Then I went to DNS management and added the domain A record pointed to my IP. It’s been over 24 hours and it still refuses to work
What feature, service or problem is this related to?
DNS records
What are the steps to reproduce the issue?
!. Create a Cloudflare tunnel from ZeroTrust, add an application to work on your domain.
2. Delete that configuration and try adding that same domain’s A record to point to an IP - it won’t work.
Suppose I have a domain mydomain.com that was configured in ZeroTrust and pointed to an application and everything was working fine. I later decided I no longer wanted to use a tunnel and point the domain directly to an IP from DNS management, it won’t work.
A bit more detailed description and history of this domain:
I had a server running cloudflared tunnel. Through that tunnel, I pointed an application running on it to my domain and everything worked fine.
Last night, I switched to Vercel so in order to get that to work for my domain, I went back to Zero Trust, selected my tunnel, head over to the public hostnames and deleted the config for the domain - left every other configuration as is.
Since I’ve pointed my domain’s nameservers to cloudflare, I head over to the domain’s DNS management and simple pointed the A record @ to Vercel’s IP and in theory, it should just work - but it doesn’t it never does.
“Never does” I say? What does that mean?
Well, I’ve tried doing the same in the past, but with sub-domains and with multiple domains but I’ve noticed that every time I use a sub-domain in regular DNS management after using it with a Cloudflare tunnel in ZeroTrust as a public hostname, that sub-domain never works. Even though cloudflare’s DNS management shows that domain or sub-domain pointed to an IP, pinging it returns nothing - visiting it does nothing.
This record is not proxied by Cloudflare and currently points to something on AWS (that could be Vercel but in any event it is an issue with the host, not Cloudflare
Nothing isn’t what is happening here. The client is making a DNS query, that query is resolving correctly to the IP address you have specified. The browser is opening a connection to that IP on the correct port. The connection fails because of an issue with SSL on the origin. You will need to determine why the origin is failing, if Vercel is indeed the host review your settings with them and confirm they are correct.
but in any event it is an issue with the host, not Cloudflare