New Pi Hole installation DNS not working even on the device itself

Help
1

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

If you are Experiencing issues with a Pi-hole install that has non-standard elements (e.g you are using nginx instead of lighttpd, or there is some other aspect of your install that is customised) - please use the Community Help category.

Expected Behaviour:

DHCP Server is giving out leases to clients just fine, but DNS is not working on any device, nor the Raspberry Pi with Pi Hole itself. I can ping any numerical address including stuff on the internet. But no host names will resolve.

Actual Behaviour:

Cable modem (Bell GigaHub) has DHCP disabled on it. Brand new Pi Hole installation is set at address 192.168.2.100 and has DHCP server enabled. Devices on my network get an IP from it no problem, and it shows up in the active clients list, but there is no resolution capability. Connected via SSH to the Pi Hole itself, and even it cannot resolve any names. It’s own DNS is malfunctioning?

Please assist because my entire home network is down right now since everything is going through the Pi Hole. I’ve had to manually set DNS to 4.2.2.1 on devices just so I can post here

Help!! I’m a novice user and don’t know where to begin

Debug Token:

Fails t the end because it can’t resolve tricorder.pi-hole.net . Why wouldn’t you guys set this to a numerical IP? Ridiculous that I can’t even upload a log file because you hard coded a host name lmao

2

For the same reason that nobody else on the internet locks in IPs. IPs change, domain names do not.

For your specific problem, do the following:

This will temporarily reset the nameserver on the Pi to bypass Pi-Hole DNS.

sudo nano /etc/resolv.conf

Edit the nameserver line to nameserver 9.9.9.9 or your preferred third party DNS service, save and exit

Run

pihole -d

and upload the debug log.

4

That won’t show any appropriate errors though as the DNS will be working once I change the name server. I need to upload the log that’s failing, don’t I ?

5

Had to copy the file off the Pi and manually paste this

redacted by moderator to protect user privacy

6

Have not been able to fix it, guess I will have to unhook the Pi Hole for now until someone is able to analyze the debug file..

I just don't get it. Everything I try to ping, on any device, has a nice little stall while it attempts then just comes back "Temporary failure in name resolution"

This is even while on the PiHole itself via SSH..

I guess let me know anyone out there is able to assist, thanks anyways, guess this is unusable for now

8

I looks like you are trying to use both the ethernet interface and the wifi interface at the same time on the same subnetwork with the same gateway.

Pull Request to improve our ridiculousness are welcome, lmao, lul, yolo!

1 Like
9

Sorry I'm not sure what that means - but I do know that if you are making a device to upload log files.. for DNS software.. which people experience DNS name resolution problems with.. I would at least try to add a numerical IP based server if all else fails, just so the end user at least has an attempt at completing the upload?

I realize IP addresses change but there are some out there that seem to remain static forever?

Thanks anyways

10

Did you carry out the steps I posted?

12

It means that your Pi has two IP's assigned, one to the wlan0 interface, and one to the etho interface:

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
✓] cd.ladsp.com is 0.0.0.0 on lo (127.0.0.1)
✓] cd.ladsp.com is 0.0.0.0 on eth0 (192.168.2.100)
✓] cd.ladsp.com is 0.0.0.0 on wlan0 (192.168.2.101)
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (8.8.8.8)

Both IP's are responding as DHCP servers:

*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
   Scanning all your interfaces for DHCP servers
   Timeout: 10 seconds
   
   * Received 300 bytes from eth0:192.168.2.100
     Offered IP address: 192.168.2.166
     Server IP address: 192.168.2.100
     Relay-agent IP address: N/A
     BOOTP server: (empty)
     BOOTP file: (empty)
     DHCP options:
      Message type: DHCPOFFER (2)
      server-identifier: 192.168.2.100
      lease-time: 86400 ( 1d )
      renewal-time: 43200 ( 12h )
      rebinding-time: 75600 ( 21h )
      netmask: 255.255.255.0
      broadcast: 192.168.2.255
      dns-server: 192.168.2.100
      domain-name: "lan"
      router: 192.168.2.1
      --- end of options ---
    
   * Received 300 bytes from wlan0:192.168.2.101
     Offered IP address: 192.168.2.167
     Server IP address: 192.168.2.101
     Relay-agent IP address: N/A
     BOOTP server: (empty)
     BOOTP file: (empty)
     DHCP options:
      Message type: DHCPOFFER (2)
      server-identifier: 192.168.2.101
      lease-time: 86400 ( 1d )
      renewal-time: 43200 ( 12h )
      rebinding-time: 75600 ( 21h )
      netmask: 255.255.255.0
      broadcast: 192.168.2.255
      dns-server: 192.168.2.101
      domain-name: "lan"
      router: 192.168.2.1
      --- end of options ---
    
   DHCP packets received on interface lo: 0
   DHCP packets received on interface wlan0: 1
   DHCP packets received on interface eth0: 1

Pi-hole is configured to listen on the wlan0 interface:

*** [ DIAGNOSING ]: Setup variables
    PIHOLE_INTERFACE=wlan0

Depending on which DHCP server answers first, a client may be directed to a non-existent DHCP server.

The fix - choose one or the other of ethernet or WiFi on the Pi. Configure Pi-hole for that interface, and eliminate the other.

As for the Pi DNS resolution, this is what you have in your /etc/resolv.conf file:

-rw-r--r-- 1 root root 63 Sep  6 15:20 /etc/resolv.conf
   domain denali
   nameserver 192.168.2.2

What nameserver is this? It doesn't appear to be able to resolve DNS queries, as evidenced here:

*** [ DIAGNOSING ]: Operating system
[i] dig return code:  10
[i] dig response:  dig: couldn't get address for 'ns1.pi-hole.net': failure
[✗] Distro:  Raspbian
[✗] Error: Raspbian is not a supported distro (https://docs.pi-hole.net/main/prerequisites/)
1 Like
13

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