Hello, I have a TP-Link BE3600 router and a Raspberry Pi 3b. The Raspberry Pi has a statically assigned IP address of 192.168.0.20. When I enter it as the DNS server in the TP-Link, all devices set 192.168.0.20 as their primary DNS, but they automatically add 192.168.0.1 (main router) as their se…

[image] Adam2: If I set primary and secondary 192.168.0.20 network crash. This may indicate Pi-hole or Unbound are not correctly configured. Before changing the router settings, please try these commands from a client machine (not from Pi-hole server) and post the output: nslookup google.co…

PS C:\Users\M> nslookup google.com Server: pi.hole Address: 192.168.0.20 *** pi.hole can't find google.com: Server failed PS C:\Users\M> nslookup google.com 192.168.0.20 Server: pi.hole Address: 192.168.0.20 I run sudo pihole -d but I can’t upload log, weird: [?] Would you like to upload the …

[image] Adam2: but I can’t upload log, weird: It's expected, since you are using 192.168.0.20 as DNS server for Pi-hole server, but Pi-hole is not working, so the server can't resolve domains. -rw-r--r-- 1 root root 54 Apr 10 21:34 /etc/resolv.conf nameserver 192.168.0.20 Your log seems …

log: https://tricorder.pi-hole.net/yiDvMNX4/ PS C:\Users\M> nslookup google.com Server: pi.hole Address: 192.168.0.20 Non-authoritative answer: Name: google.com Addresses: 2a00:1450:4025:804::8a 2a00:1450:4025:804::65 2a00:1450:4025:804::66 2a00:1450:4025:804::64 142.250.130.102 142.250.130.…

This output shows Pi-hole is working and the Windows machine is already using Pi-hole as DNS server. It means the issue only happens when you use Unbound as upstream. You can now set 192.168.0.20 as both primary and secondary on your router. Now we can try to debug Unbound. From Pi-hole server com…

; <<>> DiG 9.20.21-1~deb13u1-Debian <<>> google.com -p 5335 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 5383 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1232 ;; QUESTIO…

Yes, pihole is working now after set secondary dns. I suspected it was unbound. Now, what could have gone wrong with it?

[image] Adam2: status: SERVFAIL This means Unbound is not able to resolve google.com. You need to check your unbound config files. Did you follow Pi-hole guide to configure Unbound ?

Did third test. There is a warning: adam@Pihole:~ $ dig @198.41.0.4 version.bind CH TXT +time=3 ; <<>> DiG 9.20.21-1~deb13u1-Debian <<>> @198.41.0.4 version.bind CH TXT +time=3 ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4761 ;; fl…

Did validation tests: adam@Pihole:~ $ dig pi-hole.net -p 5335 ; <<>> DiG 9.20.21-1~deb13u1-Debian <<>> pi-hole.net -p 5335 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 30886 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;;…

Tplink + pihole. Ads leaking

Help Community Help

deHakkelaar April 12, 2026, 5:59am 12

What does below output?

traceroute -n 8.8.8.8

Maybe your ISP applies CGNAT: