# Cannot resolve name server after moving to another network

**URL:** <https://discourse.pi-hole.net/t/cannot-resolve-name-server-after-moving-to-another-network/37425>\
**Category:** Help\
**Created:** [August 19, 2020, 12:49pm UTC](https://discourse.pi-hole.net/t/cannot-resolve-name-server-after-moving-to-another-network/37425 "2020-08-19T12:49:57Z")\
**Posts on this page:** 9\
**Page:** 2

<div class="post-metadata">

**Author:** ![amratya01](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/amratya01/32/18170_2.png) [@amratya01](https://discourse.pi-hole.net/u/amratya01)\
**Post date:** [August 19, 2020, 2:55pm UTC](https://discourse.pi-hole.net/t/cannot-resolve-name-server-after-moving-to-another-network/37425/22 "2020-08-19T14:55:21Z")

</div>

but still can't understand how pihole still works

 ![image](https://discourse.pi-hole.net/uploads/default/original/3X/e/2/e26b9d8bba6765ab506696316ebe048f6412836e.png)

---

<div class="post-metadata">

**Author:** ![deHakkelaar](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/dehakkelaar/32/674_2.png) [@deHakkelaar](https://discourse.pi-hole.net/u/deHakkelaar)\
**Post date:** [August 19, 2020, 2:55pm UTC](https://discourse.pi-hole.net/t/cannot-resolve-name-server-after-moving-to-another-network/37425/23 "2020-08-19T14:55:38Z")

</div>

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`

?

---

<div class="post-metadata">

**Author:** ![amratya01](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/amratya01/32/18170_2.png) [@amratya01](https://discourse.pi-hole.net/u/amratya01)\
**Post date:** [August 19, 2020, 3:00pm UTC](https://discourse.pi-hole.net/t/cannot-resolve-name-server-after-moving-to-another-network/37425/24 "2020-08-19T15:00:02Z")

</div>

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](https://discourse.pi-hole.net/uploads/default/original/3X/8/0/8079276e835914700a4683e45993d74c64f0c2ba.png)

```auto
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

```

---

<div class="post-metadata">

**Author:** ![deHakkelaar](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/dehakkelaar/32/674_2.png) [@deHakkelaar](https://discourse.pi-hole.net/u/deHakkelaar)\
**Post date:** [August 19, 2020, 3:01pm UTC](https://discourse.pi-hole.net/t/cannot-resolve-name-server-after-moving-to-another-network/37425/25 "2020-08-19T15:01:30Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![amratya01](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/amratya01/32/18170_2.png) [@amratya01](https://discourse.pi-hole.net/u/amratya01)\
**Post date:** [August 19, 2020, 3:04pm UTC](https://discourse.pi-hole.net/t/cannot-resolve-name-server-after-moving-to-another-network/37425/26 "2020-08-19T15:04:12Z")

</div>

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?!

---

<div class="post-metadata">

**Author:** ![deHakkelaar](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/dehakkelaar/32/674_2.png) [@deHakkelaar](https://discourse.pi-hole.net/u/deHakkelaar)\
**Post date:** [August 19, 2020, 3:06pm UTC](https://discourse.pi-hole.net/t/cannot-resolve-name-server-after-moving-to-another-network/37425/27 "2020-08-19T15:06:21Z")

</div>

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

> [@amratya01](#):
>
> ```auto
> interface wlan0
> static ip_address=192.168.8.105/24
> static routers=192.168.8.1
> static domain_name_servers=8.8.8.8 8.8.4.4
> 
> ```

---

<div class="post-metadata">

**Author:** ![amratya01](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/amratya01/32/18170_2.png) [@amratya01](https://discourse.pi-hole.net/u/amratya01)\
**Post date:** [August 19, 2020, 3:09pm UTC](https://discourse.pi-hole.net/t/cannot-resolve-name-server-after-moving-to-another-network/37425/28 "2020-08-19T15:09:25Z")

</div>

and the rebind attack is still on

 ![image](https://discourse.pi-hole.net/uploads/default/original/3X/7/9/7958b8119158cdbdc2585fecbc71c86b97d3f65a.png)

---

<div class="post-metadata">

**Author:** ![amratya01](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/amratya01/32/18170_2.png) [@amratya01](https://discourse.pi-hole.net/u/amratya01)\
**Post date:** [August 19, 2020, 3:20pm UTC](https://discourse.pi-hole.net/t/cannot-resolve-name-server-after-moving-to-another-network/37425/29 "2020-08-19T15:20:07Z")

</div>

Thank you @deHakkelaar and @jfb for your time and troubleshooting 🙇‍♂️

---

<div class="post-metadata">

**Author:** ![system](https://discourse.pi-hole.net/uploads/default/original/3X/7/c/7c8792f649eeb921c5d2b4c41564ffa873d9a2b8.png) [@system](https://discourse.pi-hole.net/u/system)\
**Post date:** [September 9, 2020, 3:20pm UTC](https://discourse.pi-hole.net/t/cannot-resolve-name-server-after-moving-to-another-network/37425/30 "2020-09-09T15:20:14Z")

</div>

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

[Previous page](https://discourse.pi-hole.net/t/cannot-resolve-name-server-after-moving-to-another-network/37425.md?page=1)