Comment

Comment on Routing local requests directly to server instead of cloudflare tunnel

Pihole seems to upstream your requests although there is a local entry for that domain in your settings. Maybe it has something to do with using IPv6? Maybe your device prefers the cloudflare IPv6 over your local IPv4 address.

Or Maybe your device queries your pihole as well as your Router to get the IP. Check your current dns server on your device: ipconfig /all (Windows)

source

Sort:hotnew top

Scrath@feddit.de ⁨1⁩ ⁨year⁩ ago
I think I fixed the issue by enabling the Never forward reverse lookups for private IP ranges option in Pi-Hole. After that I flushed my dns cache again and called tracert for my domain name. I only get one hop directly to my server now. nslookup also shows only local addresses now.

source
Scrath@feddit.de ⁨1⁩ ⁨year⁩ ago
Looking at the output of that command I get the following for my ethernet network interface

DNS-Server . . . . . . . . . . . : fd98:1919:5915:0:3053:4134:bdc9:295d 192.168.1.60 fd98:1919:5915:0:3053:4134:bdc9:295d

Using nslookup on that IPv4 address tells me that all of those addresses are pointing to my pi-hole

nslookup 192.168.1.60 Server: pi.hole Address: fd98:1919:5915:0:3053:4134:bdc9:295d Name: pi.hole Address: 192.168.1.60

I’ve added another local DNS entry on my Pi-Hole which points the domain I use to the same server but this time uses its IPv6 address. That doesn’t seem to help though or it takes some time to update. I flushed the DNS cache on my machine after adding this entry though.
source