Cannot Get Client Names to Populate, Only IP's

[TelegruMomma]

Expected Behaviour:

Pihole Running on RPie3, Asus BE98Pro Router serving as DHCP server.
No matter what I try I cannot get hostnames to resolve into client names. I have tried

• manually adding the ips and names to the /etc/hosts file,
• adding local DNS Records in pihole,
• I have conditional forwarding set up
• checking and unchecking " **Never forward non-FQDN A
• AAAA queries**" and " Never forward reverse lookups for private IP ranges"
• checking and unchecking all settings I can think of in both the routers DHCP settings and pihole settings.

Actual Behaviour:

Ips of all clients are the only thing that will populate. I cannot seem to get pihole to automatically grab client names from the DHCP server, or manually input the clients via local DNS records.

Debug Token:

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

[jfb]

Why do I only see my router's IP address instead of individual devices in the Top Clients section and Query Log?

A nice feature of Pi-hole is that you can see which network devices are sending out the most DNS queries. For every device that is using Pi-hole as their DNS server, you can also see which DNS queries each one has made. [image] But depending on a few things, you may only see a single host in your Top Clients section, which is not as useful. [image] This isn't detrimental to the performance of your Pi-hole; it just provides you with less insight into what's happening on your network. So w…

[TelegruMomma]

I can see individual client IPs, not just the routers. My pihole is working correctly as the network DNS Server receiving and serving all requests.

Im Running ASUSWRT Merlin on a BE 98 Pro so there are is a tremendous amount of configuration that can be done. I would be surprised if its not possible to pass through client information. Ive tried multiple settings on back and forth trying to get client names resolved but I've had no luck. The routers IP is not advertised as an additional DNS server. I have tried with ASUS DNS Director on pointing to pihole, and off.

Also, I assumed that even in the event the DHCP server isnt passing through client names if I manually configured local DNS Records on the pihole I could still get at least those client names displayed, but even those still show up with IP only.

Any specific configurations I should try on the router side? If it seems to be a router config issue I can try to take it up with router support pages.

[gilgongo]

What have you got in your conditional forwarding config?

Consistently being unable to resolve LAN IPs implies something is trying to using external DNS to resolve them perhaps?

[TelegruMomma]

conditional forwarding is as follows.
true,192.168.0.0/16,192.168.50.1,poppin.com

I use 192.168.0.0/16 to include VLANS, but I have tried with just the main subnet as well, 192.168.50.0/24

[TelegruMomma]

Ok I have made progress. In the past I was using a regex filter to stop lookup loops that were occurring.

^(.*p.)?(([0-9]{1,3}.){4})in-addr.arpa$

This regex was blocking reverse DNS lookups. I need to monitor the network now to make sure I dont get a cascade of the xx.xx.xx.in.addr.arpa lookups that were crashing the system in the past.