Access to websites through DNS resolution. Running Raspian 9, FTL 5.7, Pi-hole 5.2.4
Actual Behaviour:
The PiHole cannot resolve any dns requests from clients or itself. I have tried pihole -r and it fails because it can't resolve. I can access the web gui and ssh into the pihole, so I don't think the network interface is a problem. I do have DHCP working from the Pihole. If I statically set my laptop to external DNS I am able to access websites. I tried changing nameserver to 9.9.9.9, but that did not resolve. I tried to do a pihole -r w/ reconfigure but same resolution failure.
Please upload a debug log and post just the token URL that is generated after the log is uploaded by running the following command from the Pi-hole host terminal:
I have generated the log, but I can't seem to upload. Where is the token URL located after the log is generated? Below is the messages I get when attempting to upload.
[?] 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
# 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 127.0.0.1
search 75.75.75.75
[?] 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
# 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
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.
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 ---
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?
