# Yet another conditional forwarding / client name not populating issue

**URL:** <https://discourse.pi-hole.net/t/yet-another-conditional-forwarding-client-name-not-populating-issue/45558>\
**Category:** Community Help\
**Created:** [March 19, 2021, 7:01pm UTC](https://discourse.pi-hole.net/t/yet-another-conditional-forwarding-client-name-not-populating-issue/45558 "2021-03-19T19:01:10Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Derp](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/derp/32/24335_2.png) [@Derp](https://discourse.pi-hole.net/u/Derp)\
**Post date:** [March 19, 2021, 7:01pm UTC](https://discourse.pi-hole.net/t/yet-another-conditional-forwarding-client-name-not-populating-issue/45558/1 "2021-03-19T19:01:11Z")

</div>

**The issue I am facing:**  
client hostnames not populating

**Details about my system:**  
--Hardware--  
UniFi Dream Machine Pro:  
Firmware v1.9.1  
Network Controller v6.1.67.0  
UAP-nanoHD X2  
v5.43.23.12533  
UAP-BeaconHD  
v5.43.23.12533  
US-8  
v5.43.23.12533  
US-8-60W  
v5.43.23.12533  
US-24-G1  
v5.43.23.12533

--Network--  
Dream Machine providing DHCP & egress  
4 VLANs - three on 10.0.X.0/24 one 192.168.1.X/24  
PiHole on VLAN 201 w/IP 10.0.2.2. All VLANS point to PiHole for DNS  
Most clients, excluding IoT are on VLAN 201

--PiHole--  
Conditional forwarding configured to Dream Machine DHCP server on 10.0.2.1  
PiHole DNS configured to use dnscrypt-proxy listening on port 5054  
I have tried wiping PiHole and reinstalling with no luck.

**What I have changed since installing Pi-hole:**  
Things worked in the past. Moved to new paspberryPi hardware using the same SD card.  
debug token [https://tricorder.pi-hole.net/li4f1sakt7](https://tricorder.pi-hole.net/li4f1sakt7)  
created /etc/dnsmasq.d/99-local.conf based on a writeup from [https://practical-admin.com/blog/my-pi-hole-configuration/](https://practical-admin.com/blog/my-pi-hole-configuration/)

```auto
local=/lan/
server=/localnet.lan/192.168.1.1
rev-server=192.168.1.0/24,192.168.1.1
server=/ggc.lan/10.0.2.1
rev-server=10.0.2.0/24,10.0.2.1
server=/iot.lan/10.0.3.1
rev-server=10.0.3.0/24,10.0.3.1
server=/lrgw.lan/10.0.4.1
rev-server=10.0.4.0/24,10.0.4.1
rebind-domain-ok=/localnet.lan/gcc.lan/iot.lan/lrgw.lan/
expand-hosts
server=/use-application-dns.net/

```

reviewed post [https://discourse.pi-hole.net/t/extra-dhcp-server-options/6416/5](https://discourse.pi-hole.net/t/extra-dhcp-server-options/6416/5)  
Added VLAN support

```auto
sudo apt-get install vlan
sudo su
echo 8021q >> /etc/modules

```

---

<div class="post-metadata">

**Author:** ![Derp](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/derp/32/24335_2.png) [@Derp](https://discourse.pi-hole.net/u/Derp)\
**Post date:** [March 20, 2021, 10:56pm UTC](https://discourse.pi-hole.net/t/yet-another-conditional-forwarding-client-name-not-populating-issue/45558/2 "2021-03-20T22:56:35Z")

</div>

--Update--

Oddly, I stumbled across a solution.  
I have a firewall rule in LAN Local blocking all DNS traffic. This was the last rule. I had other rules preceding the block rule allowing DNS TCP/UDP 53 from specified networks to the PiHole. All DNS queries worked as expected as configured.

I disabled the explicit rule blocking DNS and all of a sudden local clients host names started populating in PiHole.

My brain is stuck on WTF since DNS was working as expected with explicit rules but PiHole was not resolving local client hostnames.

Thoughts?

---

<div class="post-metadata">

**Author:** ![Tesserax](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/tesserax/32/11292_2.png) [@Tesserax](https://discourse.pi-hole.net/u/Tesserax)\
**Post date:** [March 21, 2021, 6:22pm UTC](https://discourse.pi-hole.net/t/yet-another-conditional-forwarding-client-name-not-populating-issue/45558/3 "2021-03-21T18:22:17Z")

</div>

FWIW, I have my UniFi FW rules configured to allow DNS requests to my Pi-holes for each VLAN that I wanted to have access to them. I did this with LAN In rules. This also allowed local clients on any of these VLANs to appear in the Pi-holes.

The only reason, for me, to use LAN Local rules is to block any VLAN traffic for specific protocols to the respective VLAN gateways.

---

<div class="post-metadata">

**Author:** ![system](https://discourse.pi-hole.net/uploads/default/original/3X/7/c/7c8792f649eeb921c5d2b4c41564ffa873d9a2b8.png) [@system](https://discourse.pi-hole.net/u/system)\
**Post date:** [April 11, 2021, 6:22pm UTC](https://discourse.pi-hole.net/t/yet-another-conditional-forwarding-client-name-not-populating-issue/45558/4 "2021-04-11T18:22:51Z")

</div>

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