Cloudflare Tunnels only working for some subdomains?

Website, Application, Performance DNS & Network
1

Hi everybody,

I’ve just installed Cloudflare Tunnel on my Raspberry Pi 4 and added some public hostnames in order to safely access my web services installed on the SBC.

I had no issues when adding the public hostnames for Openmediavault, Bitwarden or qBittorrent. What I did was just create a public hostname adding the subdomain.mydomain.xxx and then using the HTTP service to forward to 192.168.1.XXX:YYY

It does work for those 3 mentioned services. However, it doesn’t work for example for Portainer or Heimdall. The idea and the steps I take are the same. However, when trying to access these services, DNS is not resolving any of them when connected at home via my wifi connection. But if I use 4G on my phone, I can access them. It’s quite annoying and just wanted to know which could be the reasons behind this?

Pinging these buggy subdomains on Windows while connected on Wifi will always result in “Ping request could not find host subdomain.domain.xxx. Please check the name and try again.”
But if I ping the same ones using some online ping website it does work, like I said, these 2 are working just fine when connecting to 4G, so that makes sense I guess.

Thank you in advance.

2

Do you have any local DNS records set that would override the upstream records. That is typically the cause of network specific DNS issues.

1 Like
4

That was it! Thank you very much :slight_smile:

5

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.