My Tunnels stopped working with 1.1.1.1 as DNS

Wondering, if I’m the only one who has problems with the reachability of tunnels when using 1.1.1.1 as dns server on the clients.
I’ve about 10 tunnels which are not reachable anymore if you change your dns settings to 1.1.1.1.
With 8.8.8.8 everything ist working as expected.
There is no special config. All Tunnels pointing to https ://localhost:443 or http ://localhost:80.

Anyone else?

Thanks, Stephan!

Hello. Try settings your IPv4 DNS to the following:

  • 162.159.36.1
  • 162.159.46.1

Thanks.

Is it that you’re having issues with tunnels when the host running the internal services has 1.1.1.1 for DNS, or is the issue when clients try to connect to the public-facing tunnel URL with 1.1.1.1?

If it’s the former, I’m interested to see if running my tunnels through 8.8.8.8 will fix my connectivity issues.

It’s the latter.
If clients (mobile phones, notebooks, …) have 1.1.1.1 configured as their primary dns, they can’t connect to the service.
If i change the dns settings to e.g. 8.8.8.8 or any other non-Cloudflare dns server, everything is ok.

Have you tried the following DNS:

  • 162.159.36.1
  • 162.159.46.1

They’re alternative IPs to 1.1.1.1 and 1.0.0.1.

The DNS settings

  • 162.159.36.1
  • 162.159.46.1
    working perfectly.

The problem is, I can’t tell everyone who is accessing my public services to change their dns settings.
According to my understanding, this must be a Cloudflare related problem.

For me, this is easily reproducable:

  1. Create a tunnel
  2. Install the tunnel on a private machine (e.g. on docker)
  3. Let the public hostname point to the local service
  4. Test the setup with tor network → everything is fine
  5. Test the setup on a machine with dns configured to 1.1.1.1 → connection timout

The other option which comes to my mind is, that this could be an ISP problem.

This isn’t a solution to your issue, but I went ahead and switched my tunnel host from 1.1.1.1 to 8.8.8.8 and suddenly my tunnel connections aren’t dropping anymore (after months of having that problem). Seems something is very wrong with 1.1.1.1 recently.

Nevermind, my issue persists.

What is the DNS name the users are trying to resolve? T