Conditional Forwarding not working correctly across VLAN's

[Kroontje]

Expected Behaviour:

Return (local) hostname when looking (nslookup) a local IP address.

Actual Behaviour:

Getting a NXDOMAIN in return

Explanation:

I have setup Conditional Forwarding on my Pi-hole and doing a lookup (nslookup) on a local FQDN returns a valid (local) IP. But doing it the other way around, looking up a local IP I will get a NXDOMAIN.
This is only when looking up client which have got their IP by DHCP.
Static IP mappings will resolve correctly.
Also static mappings do not resolve.

I'm running pfSense behind my Pi-hole.
Conditional Forwarding has been setup correctly, IP and Local Domain Name are correctly. Triple checked.

[jfb]

Please generate a debug log, upload it and post the token here.

Also, please post the outputs of the two lookups you did.

[Kroontje]

Token:
eghwvd3h57!

Did some testing and thinking as well.
I think it's because the clients are on a different VLAN.
How can I circumvent this?

When I use the DNSresolver service of my pfSense box I do not have this problem. (just for the record)

[jfb]

Your debug doesn't shown any problems with the Pi-Hole operation.

See this thread:

Conditional forwarding on multiple VLANs

Hi Gents I'm new to Pihole, and linux for that matter, and am battling with getting the conditional forwarders to work. I've followed what everyone else is doing above by creating a new file called 02-custom.conf in /etc/dnsmasq.d folder. I've edited the file and added the following: server=/localdomain/192.168.5.1 server=/boys/192.168.7.1 server=/frog/192.168.9.1 server=/guest/172.16.4.1 server=/tv/192.168.6.1 As I understand it, the names after the =/name is the domain name for that netwo…

And some other VLAN-related threads as well:

Extra DHCP Server Options

I wanted to post my slog resolving this for a 5 vlan network and coming from a windoze background (hence slowlearner). This is a long post but explains the conjunction of pi-hole, dnsmasq and vlans - hopefully in a way another slowlearner will understand. First thing to say, I honestly don't understand how the changes to network/interfaces are meant to help someone coming from an MS background. Virtually all the advice online is based on defining vlans as interface extensions (e.g. eth0.8 to …

Pi-Hole on two VLANs - not working

Something is really confusing me here From the RPi I ping the following: 10.10.50.1 (GW - Works) 10.10.30.1 (VLAN GW, does not work from DNS, works from others on LAN) 1.1.1.1 (you know ) While sniffing the traffic I get this: Blockquote 09:31:37.833143 IP 10.10.50.2 > 10.10.50.1: ICMP echo request, id 7153, seq 1, length 64 09:31:37.833195 IP 10.10.50.1 > 10.10.50.2: ICMP echo reply, id 7153, seq 1, length 64 09:31:38.834867 IP 10.10.50.2 > 10.10.50.1: IC…

Does Pi-Hole support vlan for my guest SSID (dedicated hardware)

Can I install pihole on a vlan? I always get a little fuzzy when I'm dealing with vlan's, but I have a guest network on my Ubiquiti WAP. To create isolation the guest SSID is on it's own vlan and my pfSense router is blocking access from that network to the internal network. I want to put all of the dangerous devices (yeah, like there are any NOT dangerous devices these days), kids phones, tablets, guests etc on the guest WAP. So effectively I can't use the pihole that I have on my network un…

[Kroontje]

I have checked the threads but I can't seem to get it to work.
I've created /etc/dnsmasq.d/02-test.conf file and put in my other VLAN.
Restarted the Pi-hole server but it doesnt seem to work.

[jfb]

@Kroontje

/etc/dnsmasq.d/02-test.conf

What are the contents of this file?

[Kroontje]

 server=/kroon.lan/10.77.40.1
 server=/10.77.40.in-addr.arpa/10.77.40.1

Also tried

server=/kroon.lan/10.77.40.1
server=/40.77.10.in-addr.arpa/10.77.40.1

[update 1:]
Last entries seem to work except traffic is being blocked on my firewall.
I should be able to fix that.

[update 2:]
It's fixed now!
Created an ALLOW rule for port 53/DNS, destination This Firewall for the VLAN where my Pi-hole is in.

Many thanks for pointing me in the right direction @jfb !!