Fresh Pi Image, Fresh Pihole Install -- No DNS/HTTP access

Hi there,

Weirdest thing is happening to me right now...

I installed pihole on my pi yesterday. Fresh install of each. Worked for about an hour. I tried to reconfigure and test some things, no luck.

So today, I reimaged both the pi and the pihole install. No response on port 53 or 80 to the unit. I can SSH into the unit without an issue. I am able to replicate this across Wifi and Eth ports.

I have a debug log uploaded to tricorder if anyone wants to see the full info.

For networking background of the unit, it is sitting in the same VLAN addressing space as the clients attempting to hit it. No router to traverse out of.

The pihole service itself will resolve look ups on the OS, but not to a client using it.

Thanks in advance!

Please generate a new log, upload and post the token here. This is part of our help template.

https://tricorder.pi-hole.net/llkT8NBh/

Your debug log shows that Pi-hole is receiving queries and blocking per your adlist.

From a client that you believe should be connected to the Pi-Hole for DNS, from the command prompt or terminal on that client (and not via ssh or Putty to the Pi), what are the outputs of

nslookup pi.hole

nslookup flurry.com

Yep, that's what is strange. I can do dig lookups via SSH or GUI on the Pi.

My client: 10.x.x.23
Pihole: 10.x.x.4

(where x is the same and hiding LAN for sake of a public forum)

spare-jk@MBP ~ % nslookup pi.hole
;; connection timed out; no servers could be reached

spare-jk@MBP ~ % nslookup flurry.com
;; connection timed out; no servers could be reached

This timeout occurs when I try to navigate to the admin UI as well.

I've verified the ports are listening:

pi@homepi:~ $ sudo netstat -lptu
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
tcp        0      0 0.0.0.0:http            0.0.0.0:*               LISTEN      609/lighttpd        
tcp        0      0 0.0.0.0:ssh             0.0.0.0:*               LISTEN      579/sshd: /usr/sbin 
tcp        0      0 0.0.0.0:domain          0.0.0.0:*               LISTEN      658/pihole-FTL      
tcp        0      0 localhost:ipp           0.0.0.0:*               LISTEN      544/cupsd           
tcp        0      0 localhost:4711          0.0.0.0:*               LISTEN      658/pihole-FTL      
tcp6       0      0 [::]:http               [::]:*                  LISTEN      609/lighttpd        
tcp6       0      0 [::]:ssh                [::]:*                  LISTEN      579/sshd: /usr/sbin 
tcp6       0      0 [::]:domain             [::]:*                  LISTEN      658/pihole-FTL      
tcp6       0      0 localhost:4711          [::]:*                  LISTEN      658/pihole-FTL      
tcp6       0      0 localhost:ipp           [::]:*                  LISTEN      544/cupsd           
udp        0      0 0.0.0.0:mdns            0.0.0.0:*                           405/avahi-daemon: r 
udp        0      0 0.0.0.0:51985           0.0.0.0:*                           405/avahi-daemon: r 
udp        0      0 0.0.0.0:domain          0.0.0.0:*                           658/pihole-FTL      
udp        0      0 0.0.0.0:bootpc          0.0.0.0:*                           505/dhcpcd          
udp        0      0 0.0.0.0:631             0.0.0.0:*                           645/cups-browsed    
udp6       0      0 [::]:mdns               [::]:*                              405/avahi-daemon: r 
udp6       0      0 [::]:37196              [::]:*                              405/avahi-daemon: r 
udp6       0      0 [::]:domain             [::]:*                              658/pihole-FTL      
pi@homepi:~ $ 

Your debug log shows there's no DHCP server active on the link that your Pi-hole host machine is connected to:

*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
   Scanning all your interfaces for DHCP servers
   
   DHCP packets received on interface lo: 0
   DHCP packets received on interface eth0: 0
   DHCP packets received on interface wlan0: 0

Without a DHCP server, you'd have to manually configure your clients to use Pi-hole for DNS.

If you did so, you may be using a wrong IPv4:

Instead, your debug log shows your Pi-hole host residing at .29 on wlan0, while its eth0 seems to be active, but disconnected.

If that eth0 interface was carrying the .4, then reconnect it or verify the connection.

It would be preferable to connect your Pi-hole via cable, but if you intend to operate Pi-hole via wifi, then you should run pihole -r with Reconfigure.

Sorry - I mistakenly put the LAN IP of 10.x.x.4. A few days of troubleshooting something I've built time and time again has caused me to go mad.

I have an active DHCP server, but it is not local to this VLAN, and is properly handing out configurations.

I'm on my client, switched DNS manually to 10.x.x.29, and see the same output. No access to HTTP Admin either.

For what its worth, I run a PiHole in another area of my network, and it is having no issues. It is only on this unit that the issues surface. NOTE: this pihole is not pointed at that working pihole for DNS lookups.

Clients initiate DHCP communicaton via a broadcast, so there has to be a DHCP server on the same link (or a DHCP relay that would forward those broadcasts to a reachable DHCP server on another link, which would look the same from a client perspective). No answer could mean there is neither, or the relay is not configured correctly, which may be in contrast to your statement that there is an active DHCP server 'properly handing out configurations'.

The fact that Pi-hole does not receive any answers to its DHCP broadcasts then would suggest that your Pi-hole host machine is not connected to the link that hosts your DHCP server, i.e. your VLAN router isn't tagging the connection to your Pi-hole host machine as part of your VLAN, or the associated network interface isn't active, as suggested earlier (wlan0 vs. eth0).

It may also be possible that a firewall is blocking access to DHCP ports, and to DNS and HTTP as well, either on the Pi-hole host or on your VLAN router.

Appreciate you reviewing the log.

It's tough to explain the network without getting too far into the weeds. It's probably something trivial I am over looking. I'll close this topic and look with a fresh set of eyes over the weekend.

If someone stumbles across this, the issue was not with the Raspian nor Pihole.

My environment had a misconfigured bridged port that was not passing traffic across the interfaces properly. Thanks for those for helping debug - it led to a bigger discovery.

Cheers