Do not work with VLANS?

[masterj]

Please follow the below template, it will help us to help you!

If you are Experiencing issues with a Pi-hole install that has non-standard elements (e.g you are using nginx instead of lighttpd, or there is some other aspect of your install that is customised) - please use the Community Help category.

Expected Behaviour:

I have Unifi dream machine setup with 4 networks.

Main:
"Pagrindinis" / 192.168.1.0/24

Virtual:
"Svečiams" / VLAN 2 / 192.168.2.0/24
"IoT" / VLAN 3 / 192.168.3.0/24
"IoT be interneto" / VLAN 4 / 192.168.4.0/24

There are no firewall rules applied - inter VLAN devices can ping each other.

Pihole is in 192.168.1.0/24 with IP 192.168.1.53

Devices in all networks get 192.168.1.53 as DNS server set via DHCP.

In pihole there's local record:
Domain: nas.8-2.bijunu.lt
IP: 192.168.1.188

Both the DNS blocking and local DNS records should be working for all the networks through single pihole at 192.168.1.53.

Actual Behaviour:

DNS blocking and local DNS records work only on 192.168.1.0/24 .

Here are nslookups:
From 192.168.1.0/24:

nslookup pi.hole                                                                                                                                                                                                                                                           ✔ 
Server:		192.168.1.53
Address:	192.168.1.53#53

Name:	pi.hole
Address: 192.168.1.53
Name:	pi.hole
Address: fe80::3257:9126:8316:6949

nslookup nas.8-2.bijunu.lt                                                                                                                                                                                                                                                 ✔ 
Server:		192.168.1.53
Address:	192.168.1.53#53

Name:	nas.8-2.bijunu.lt
Address: 192.168.1.188

And here's from 192.168.3.0/24:

nslookup pi.hole                                                                                                                                                                                                                                                           ✔ 
Server:		192.168.1.53
Address:	192.168.1.53#53

** server can't find pi.hole: NXDOMAIN

nslookup nas.8-2.bijunu.lt                                                                                                                                                                                                                                               1 ✘ 
Server:		192.168.1.53
Address:	192.168.1.53#53

** server can't find nas.8-2.bijunu.lt: NXDOMAIN

cat /etc/resolv.conf                                                                                                                                                                                                                                                     1 ✘ 
# Generated by NetworkManager
nameserver 192.168.1.53

Looks as if pihole is not even responding to those queries. What should I debug/do next?

Debug Token:

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

[Bucking_Horn]

Run from a 192.168.3.0/24 machine, what's the output of:

nslookup -class=chaos -type=txt version.bind

[masterj]

@Bucking_Horn

nslookup -class=chaos -type=txt version.bind

nslookup -class=chaos -type=txt version.bind                                                                                                                                                                                                                               ✔ 
Server:		192.168.1.53
Address:	192.168.1.53#53

version.bind	text = "dnsmasq-2.86"

[Bucking_Horn]

It is definitely not Pi-hole answering those requests.
The expected outcome should have looked similar to dnsmasq-pi-hole-v2.xx-xxxxx.

Combined with your own nslookup results, that would indicate that your router is intercepting DNS requests from your VLANs and redirecting them to its own DNS resolver (or -less likely- an additional dnsmasq may run on your Pi-hole machine - your debug log shows no signs of a dnsmasq process, though).

You'd have to consult your router for details of its VLAN DNS configuration.

[masterj]

thank you, I'll ask ubiquity support in the meantime

[masterj]

Looks like I've found the issue... Ubiquity sneakily introduced new option for DNS blocking in network settings. Once I've disabled that - DNS resolution via pihole started to work