Query log - other IP vlans

Hi

I have my devices on 3 different vlan's.
But pihole only shows queries from the same vlan as it resides itself.
How can I get queries from other vlans to show up in the query log?

You have to get under the hood and custom configure dnsmasq. Essentially telling it about the other vlans and where the other gateways are. You will have to create a custom dnsmasq file and put it in the dnsmasq.d config folder. I don't have access right now to copy and paste any links. Duck Duck Go will be your friend to find the details.

ok. maybe I did this right.. hope for some confirmation...

created 05-custom.conf

added this:

server=/iot.lan/192.168.1.1

server=/home.lan/192.168.1.1

server=/guest.lan/192.168.1.1

server=/10.20.10.in-addr.arpa/192.168.1.1

server=/1.168.192.in-addr.arpa/192.168.1.1

server=/0.16.172.in-addr.arpa/192.168.1.1

I still do not see queries from other vlans though..

I rebooted the pi.

I'm now seeing alot of this in my query log

PTR	lb._dns-sd._udp.0.1.168.192.in-addr.arpa	home-usg-01	OK (forwarded)	N/A

These PTR requests are reverse IP lookups - the requesting client has the IP address but wants to know the name of the client at that IP. This is normal network traffic.

Is your pihole doing the DHCP or the router? That makes a difference.
Is you router IP 192.168.1.1 really the gateway for all your VLANs? You may have gateways for each of the VLANs ie.your 10.20.10.XX network would have 10.20.10.1 as the gateway.
You have also defined 3 domains all on the same network for 192.168.1.1.

Here is a copy of one of my old configs:

# global options
#dhcp-authoritative
#domain=home
#dhcp-leasefile=/etc/pihole/dhcp.leases
#quiet-dhcp
#log-dhcp
#server=/home/192.168.1.1
#server=/1.168.192.in-addr.arpa/192.168.1.1
#server=/home/192.168.5.1
#server=/5.168.192.in-addr.arpa/192.168.5.1
#server=/home/192.168.9.1
#server=/9.168.192.in-addr.arpa/192.168.9.1
#server=/home/192.168.13.1
#server=/13.168.192.in-addr.arpa/192.168.13.1
#server=/home/192.168.59.1
#server=/59.168.192.in-addr.arpa/192.168.59.1
#server=/home/192.168.66.1
#server=/66.168.192.in-addr.arpa/192.168.66.1
#server=/home/192.168.107.1
#server=/107.168.192.in-addr.arpa/192.168.107.1

# Set will create sets
#dhcp-range=set:v1,192.168.1.100,192.168.1.254,255.255.255.0,24h
#dhcp-range=set:v5,192.168.5.10,192.168.5.254,255.255.255.0,24h
#dhcp-range=set:v9,192.168.9.10,192.168.9.254,255.255.255.0,24h
#dhcp-range=set:v13,192.168.13.10,192.168.13.254,255.255.255.0,24h
#dhcp-range=set:v59,192.168.59.10,192.168.59.254,255.255.255.0,24h
#dhcp-range=set:v66,192.168.66.10,192.168.66.254,255.255.255.0,24h
#dhcp-range=set:v107,192.168.107.10,192.168.107.254,255.255.255.0,24h

# Tag will match to sets
# DHCP option 6 for gateway
#dhcp-option=tag:v1,option:router,192.168.1.1
#dhcp-option=tag:v5,option:router,192.168.5.1
#dhcp-option=tag:v9,option:router,192.168.9.1
#dhcp-option=tag:v13,option:router,192.168.13.1
#dhcp-option=tag:v59,option:router,192.168.59.1
#dhcp-option=tag:v66,option:router,192.168.66.1
#dhcp-option=tag:v107,option:router,192.168.107.1

# Set DNS
#dhcp-option=6,192.168.1.XXX,9.9.9.9

forgot about this until today.
@capboomer - you were right about the mis-config.
I changed to IP's for gateways and domain and the guest network IP's started coming in to the pihole.
Thanks for the pointer.
So create /etc/dnsmasq.d/05-custom.conf

add your vlans/networks to the conf file and reboot... more or less.

my file looks like this:

server=/iot.lan/10.20.10.1

server=/home.lan/192.168.1.1

server=/guest.lan/172.16.0.1

server=/10.20.10.in-addr.arpa/10.20.10.1

server=/1.168.192.in-addr.arpa/192.168.1.1

server=/0.16.172.in-addr.arpa/172.16.0.1