Change DNS Resolver

[ballonchef]

Dear all,

I'm using cloudflared on homeassistant on my raspberry. Since I upgraded from Pi3 to Pi5 cloudflared creates following error:

2025-04-02T13:32:28Z ERR Request failed error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: dial tcp: lookup homeassistant-internal.my-url.com on 127.0.0.11:53: no such host" connIndex=1 dest=https://tesla.my-url.com/local/tesla/com.tesla.3p.public-key.pem event=0 ip=198.41.200.233 type=http 2025-04-02T13:33:33Z ERR error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: dial tcp: lookup homeassistant-internal.my-url.com on 127.0.0.11:53: no such host" connIndex=1 event=1 ingressRule=1 originService=https://homeassistant-internal.my-url.com

For me, this looks like an issue with DNS resolver. I tried to change /ect/hosts and DNS-servers of homeasstiant. also tried to add DNS entries in the config.yaml. doesn't help.

All the user Cloudflare-tunnels to other xyz.my-url.com work.

On my Pi3 everything was working great - and I don't know how to fix this.

Anyone knows how to fix it?

Thanks for your help!!

Background: I would like to host the public key of my tesla, for tesla access. in cloudflare I created a rule pointing to the file in local/tesla/com.tesla.3p.public-key.pem. From the local network and using the local IP address everything works.

[fernvenue]

Same, and it will be great to change the DNS resolver for cloudflared without changing DNS on system level, environment will so great.