As of a few weeks ago I would see my client names instead of IP Addresses in my top list. Something changed a few weeks ago and its just showing the IPs.
I promise I have looked at several guides and seems like I have everything set up properly but perhaps I Missed a step.
My UDM Pro Is serving as my DHCP Server while I have 2 Pi-Holes running on RP4s severing as the DNS
I know I need conditional FWD turned on so on my primary Pi I have under DNS
PiHole DNS
Custom 1: IPv4
127.0.0.1#5335 (Unbound Upstream)
Listen on All Interfaces, Permit All Origins Checked.
Never FWD non-FQDN A and AAA queries CHCEKED
Never forward reverse lookups for private IP ranges UNCHCKED
Use DNSSEC CHECKED
Conditional forwarding CHCKED
Local network in CIDR notation
192.168.0.0/24
IP address of your DHCP server (router)
192.168.1.1
Local domain name (optional)
localdomain
I have all of the Local DNS domains with Client names added under Local DNS Records.
UDM Pro LAN Settings
DHCP Mode – DHCP Server Checked
DHCP Name Server
192.168.1.8 & 192.168.1.13 (My Two PiHoles)
DHCP Gateway: Auto
I think its prob a simple setting because I had it working with this set up for over a year.
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:
Could you provide some examples for those IP addresses?
Also, run from a client, please provide the result of a corresponding reverse lookup of that IP, e.g.:
nslookup 192.168.1.63
or
nslookup fd6b:7dde:adb:3:5fa9:f33a:2379:9ebb
And also that one:
nslookup pi.hole
Your router distributes three DNS servers:
*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
Scanning all your interfaces for DHCP servers
* Received 313 bytes from eth0:192.168.1.1
Offered IP address: 192.168.1.8
DHCP options:
Message type: DHCPOFFER (2)
dns-server: 192.168.1.8
dns-server: 192.168.1.13
dns-server: 192.168.1.15
router: 192.168.1.1
--- end of options ---
Only one of those IPv4 addresses belongs to the Pi-hole that created the debug log. A client may choose any one of those for any given DNS request.
You should verify whether a Pi-hole instance would also be listening for DNS requests on those other two IPs (specifically, you didn't mention the .15).
Also, your RPi is connecting to your network both via Ethernet and wifi:
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] genrugby.com is 0.0.0.0 on lo (127.0.0.1)
[✓] genrugby.com is 0.0.0.0 on eth0 (192.168.1.8)
[✓] genrugby.com is 0.0.0.0 on wlan0 (192.168.1.9)
[✓] doubleclick.com is 142.250.80.46 via a remote, public DNS server (8.8.8.8)
Note that your Pi-hole is listening on eth0, which is perfectly valid.
Since Ethernet is available and would be preferred, you could consider to disable your RPi's wifi completely, provided you are not reyling on wifi for other reasons (would also save a wee bit of power ).
nslookup 192.168.1.63
63.1.168.192.in-addr.arpa name = Dyson_Bedroom.
nslookup fd6b:7dde:adb:3:5fa9:f33a:2379:9ebb
b.b.e.9.9.7.3.2.a.3.3.f.9.a.f.5.3.0.0.0.b.d.a.0.e.d.d.7.b.6.d.f.ip6.arpa name = pi.hole.
Ahh yes the 192.168.1.15 is a third pihole I’ve had set up. WHen i first used PiHole i set up two other spare PiHles for fall over. Both of these have unbound as well. I should look deeper into thier configuration.
Good tip disabling the WiFi I have a few Pis running on both and am doing that now as they are all in a server rack.
Ah, I see you've used the nslookup commands as I provided them, when they were meant as examples.
Please rerun them with some of the IPs you are seeing instead of hostnames.
Also, please include the full output.
If I was lucky enough to include some of those very IPs, then the command output is telling us that Pi-hole indeed knows the names for them and should have no trouble showing them.
So its good news the host names are resolving currently. I flushed the network table 2 days ago and the top lists still have the IPs which I know for sure are named properly.
The new change is the top domain is now
pihole.localdomain
Is the move here to just nuke the hostname list and start over?
).