DNS issue - not responding (pihole)

Please follow the below template, it will help us to help you!

Expected Behaviour:

name resolution

Actual Behaviour:

resource (primary DNS server) not responding per pc - i have restarted dns server via pihole admin page, and also checked local IP which is currently correct

Debug Token:

qy4oqhr072

please run the following on the node running Pi-Hole

dig flurry.com
dig flurry.com @9.9.9.9

then try the same from a device using pi-hole as its dns but swap the dig command for nslookup in command prompt and paste the results here

Your debug log shows a few problems with the Pi connecting to your network. This may be causing problems with clients being able to find the Pi-Hole.

*** [ DIAGNOSING ]: Networking
[✗] No IPv4 address(es) found on the eth0 interface.

[✗] No IPv6 address(es) found on the eth0 interface.

[i] Default IPv4 gateway: 192.168.0.1
   * Pinging 192.168.0.1...
[✗] Gateway did not respond. (https://discourse.pi-hole.net/t/why-is-a-default-gateway-important-for-pi-hole/3546)

   [2019-05-21 09:01:43.546 26317]  -> Unique clients: 2

What is the output of the following (will show the clients that have connected in the previous 24 hours). Check that all expected clients are here, although some may be going through your router and not showing as individual clients.

echo ">top-clients withzero (15)" | nc 127.0.0.1 4711

pi@raspberrypi:~ $ dig flurry.com

; <<>> DiG 9.10.3-P4-Raspbian <<>> flurry. com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61937
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;flurry. com.			IN	A

;; ANSWER SECTION:
flurry. com.		2	IN	A	0.0.0.0

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue May 21 14:01:02 EDT 2019
;; MSG SIZE  rcvd: 55

pi@raspberrypi:~ $ dig flurry.com @9.9.9.9

; <<>> DiG 9.10.3-P4-Raspbian <<>> flurry. com @9.9.9.9
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18849
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;flurry. com.			IN	A

;; ANSWER SECTION:
flurry. com.		300	IN	A	98.136.103.26
flurry. com.		300	IN	A	74.6.136.153
flurry. com.		300	IN	A	212.82.100.153

;; Query time: 89 msec
;; SERVER: 9.9.9.9#53(9.9.9.9)
;; WHEN: Tue May 21 14:01:18 EDT 2019
;; MSG SIZE  rcvd: 87

pi@raspberrypi:~ $ echo ">top-clients withzero (15)" | nc 127.0.0.1 4711

0 6391 192.168.0.38 
1 510 127.0.0.1 localhost
2 1 192.168.0.53 raspberrypi
---EOM---

pc:

Microsoft Windows [Version 10.0.17134.765]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\Users\BEASTMODE>nslookup flurry.com
Server:  rdns01.suddenlink.net
Address:  208.180.42.68

Non-authoritative answer:
Name:    flurry. com
Addresses:  212.82.100.153
          74.6.136.153
          98.136.103.26
C:\Users\BEASTMODE>nslookup flurry. com @9.9.9.9
*** Can't find server address for '@9.9.9.9':
Server:  rdns01.suddenlink.net
Address:  208.180.42.68

Non-authoritative answer:
Name:    flurry. com
Addresses:  98.136.103.26
          74.6.136.153
          212.82.100.153

This shows that your PC is not using Pi-Hole for DNS - it is using the IP shown.

The format should be nslookup flurry.com 9.9.9.9 , without the "@". The formats for dig and nslookup are different in this regard.

1 Like

C:\Users\BEASTMODE>nslookup flurry.com 9.9.9.9
Server: dns.quad9.net
Address: 9.9.9.9

Non-authoritative answer:
Name: flurry.com
Addresses: 212.82.100.153
74.6.136.153
98.136.103.26

What is the IP address of the PC? One of these? If not, this is further confirmation that the PC isn't using Pi-Hole.

the .38 is my pc according to this...

C:\Users\BEASTMODE>ipconfig

Windows IP Configuration

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::25a0:3b9f:9692:87b1%7
IPv4 Address. . . . . . . . . . . : 192.168.0.38
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1

Farther down in the ipconfig output it will show you the DNS server(s). What are they?

C:\Users\BEASTMODE>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : DESKTOP-1HFSMEU
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) I211 Gigabit Network Connection
   Physical Address. . . . . . . . . : 0C-9D-92-82-34-41
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::25a0:3b9f:9692:87b1%7(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.0.38(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Tuesday, May 21, 2019 9:15:52 AM
   Lease Expires . . . . . . . . . . : Wednesday, May 22, 2019 2:55:42 PM
   Default Gateway . . . . . . . . . : 192.168.0.1
   DHCP Server . . . . . . . . . . . : 192.168.0.1
   DHCPv6 IAID . . . . . . . . . . . : 34381202
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-23-7F-3C-1C-0C-9D-92-82-34-41
   DNS Servers . . . . . . . . . . . : 192.168.0.53
   NetBIOS over Tcpip. . . . . . . . : Enabled

That is interesting. This shows that your DNS is Pi-Hole, but the nslookup went to a different DNS server. Run nslookup flurry.com again from that PC and see if shows the same server it previously showed.

Is suddenlink related to your ISP?

C:\Users\BEASTMODE>nslookup flurry.com
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 192.168.0.53

Name: flurry.com
Addresses: ::
0.0.0.0

Did you resolve the Pi IP address problem noted in my first reply?

temporarily, reset pc, came back up, but it'll cut out here and there to where this was the error when troubleshooting

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