Cannot resolve name server after moving to another network

but still can't understand how pihole still works

ICMP seems to get through to 8.8.8.8 (from traceroute output).
But DNS doesnt (from dig).
You haven't answered yet if have checked for rebind protection or similar on the router ?
I'm outta ideas.

EDIT: maybe one idea:

dig ns1.pi-hole.net @1.1.1.1

?

ok, I had this option On, and when I switched it off.. it just worked
I'm using GL.iNet GL-AR750S-Ext (Slate) router

image

pi@raspberrypi:~ $ dig ns1.pi-hole.net @8.8.8.8

; <<>> DiG 9.11.5-P4-5.1+deb10u1-Raspbian <<>> ns1.pi-hole.net @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49435
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;ns1.pi-hole.net.		IN	A

;; ANSWER SECTION:
ns1.pi-hole.net.	2966	IN	A	185.136.96.96

;; Query time: 27 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Wed Aug 19 16:57:28 CEST 2020
;; MSG SIZE  rcvd: 60

1 Like

Post make model of the router for others to find ?
And mark your last reply as solution pls ?

Sure, but how this could be related? even if it still sends the DNS 192.168.8.105 hard coded to itself, it should work... right?!

For the Pi-hole host, 8.8.8.8 and 8.8.4.4 is hard coded for DNS:

and the rebind attack is still on
image

Thank you @deHakkelaar and @jfb for your time and troubleshooting :bowing_man:

1 Like

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