The issue I am facing:
Local subnet, works no problem.
Non-local subnets and VLANs are not appearing in the queries. However, public internet resolution seems to be fine, but local resolution which should be forwarded to BIND does not work on a non-local subnet. I see no queries coming from any subnet/VLAN that are not local.
Details about my system:
I have a pair of rasppi that run both BIND9 on port 60053 and then pihole is the client DNS servers. DHCP is handled by a UDM-Pro.
I forward requests to BIND using custom forwarders:
10.0.0.43#60053
10.0.0.45#60053
I have Permit all origins set under interface settings since requests come from various subnets.
There are no active firewalls in line or on the rasppi.
Core v6.2.2
FTL v6.3.3
Web interface v6.3
The local domain is set to lan on pihole.
The actual local domain is a subdomain of a publicly routable root domain. All of this is maintained in BIND and should return in the forward.
This configuration had worked for years.
What I have changed since installing Pi-hole:
General Ubuntu updates and pihole updates. Minor updates, was already on 6.
Things I’ve tried so far:
Toggling the Permit all orgins to None, restarting FTL and then toggling it back and restarting FTL.
Moving back and forth between a local subnet and non-local for testing.
Connectivity to the pihole (even the admin portal) is accessible from a non-local subnet via IP.
A packet capture from the laptop doing the testing can see dns requests and responses coming from the pihole IPs.
An NSLOOKUP from the local subnet:
C:\Windows\System32>nslookup
Default Server: pi.hole
Address: 10.0.0.43
An NSLOOKUP from the non-local subnet:
C:\Windows\System32>nslookup
Default Server: UnKnown
Address: 10.0.0.43
I’ve tried a repair and a complete uninstall/reinstall.