PiHole unable to resolve DNS

Help
6

Change the nameserver line to something like 8.8.8.8 and generate a Debug token again.

7

Same:

[?] Would you like to upload the log? [y/N] y
* Using curl for transmission.
* curl failed, falling back to netcat for transmission.
nc: getaddrinfo: Temporary failure in name resolution
[✗] There was an error uploading your debug log.

  • Please try again or contact the Pi-hole team for assistance.
  • A local copy of the debug log can be found at: /var/log/pihole_debug.log
8

Did the changed nameserver really stick?
Just asking because I just noted the warning

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
9 
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 8.8.8.8
search 75.75.75.75
10

Do you block port 53 on your notwork for IPs other than your Pi-hole?

11

No, I have a wireless guest that uses external DNS separate of the pihole and that is working fine.

12

DM me the debug log.

Add: you should consider updating your Pi-hole, you're running an old version.

13

Forgive me but I don't use chats. How can I DM you the debug log. Also I tried to update Pi-hole, but it cannot resolve DNS to update from install.pi-hole.net.

14

It's personal message.

Bildschirmfoto zu 2022-02-06 14-45-55
Bildschirmfoto zu 2022-02-06 14-45-55559×535 36.6 KB

15

When I try and post the debug to you, I get this error message on the chat.

Sorry, new users can't mention other users.
Sorry, new users can only put 5 links in a post.

I'm only copy/paste the output from the debug. Nothing else.

16

Paste it in as "preformatted text". Links won't count within.
Bildschirmfoto zu 2022-02-06 14-54-45

17

Now it says I cannot send a personal message to you

18

Just post it here, I'll hide it afterwards.

20

As I said before: something is preventing your Pi host device from accessing public DNS servers.

Additionally:

*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the eth0 interface:
10.1.0.10/8 does not match the IP found in /etc/pihole/setupVars.conf (Use IPv6 ULA addresses for Pi-hole)

This can be fixed by running pihole -r choose reconfigure

It is unusual, that router IP, and gateway IP differ. Do you have such a setup?

[i] Default IPv4 gateway: 10.1.0.5
   * Pinging 10.1.0.5...
[✓] Gateway responded.

   * Received 303 bytes from eth0:10.1.0.10
     Offered IP address: 10.1.0.109
     Server IP address: 10.1.0.10
     Relay-agent IP address: N/A
     BOOTP server: (empty)
     BOOTP file: (empty)
     DHCP options:
      Message type: DHCPOFFER (2)
      server-identifier: 10.1.0.10
      lease-time: 86400 ( 1d )
      renewal-time: 43200 ( 12h )
      rebinding-time: 75600 ( 21h )
      netmask: 255.0.0.0
      broadcast: 10.255.255.255
      dns-server: 10.1.0.10
      domain-name: "WORKGROUP"
      router: 10.1.0.1
      --- end of options ---
21

My internal gateway died a couple of weeks ago, so I had to move all my devices to the edge router. However, that was weeks ago and this issue with the Pihole just started this morning. I don't see a location in the web gui to change the ip information?

22

Which is the correct routing information?
10.1.0.1 or 10.1.0.5?

23

Currently 10.1.0.1

24

I updated dhcpcd.conf w/ the correct router information and was able to do an update. Please inspect the latest debug file.

25

Ran pihole -r and now DNS is working. Thank you for all your help.

1 Like
26

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