guys, I'm starting with pi-hole now, since I didn't have a good time with the local DNS feature using UDM Pro. My intention is to use Pi-hole (running in docker, in a LAN called DMZ(172.16.100.x)) focused on resolving the names of my homelab, which by the way, is divided into any LANs (not VLANS).
I've already managed to create a test domain called “midgard.home”, and a CNAME linked to this domain, called “sonar.midgard.home”.I can resolve both names, either on my local server, where the pi-hole is running, or any host in the same Broadcast domain to which the pi-hole belongs. Within UDM pro itself, I can resolve the names in the pi-hole
The problem:
My main PC is on a LAN called “work desk” (192.168.10.x). If I try to make a DNS request, it can be any domain, for the IP of the Pi-hole, I get no response. I run Netcat to validate the connection, and it's ok.
Can anyone shed some light on what might be causing this problem?
The query works from the client to Pi-hole and from Pi-hole back to the client? How are you validating with NC? (If you can include the exact commands you use and the exact output/responses you see that would be helpful.)
Can you show the output from dig or nslookup, including any errors or responses you get? Do you have any firewall rules in place and are you using vLANs?
Can you capture some of the traffic with tcpdump or Wireshark to show if any packets are being intentionally dropped?
Check for any rules blocking DNS requests between LANs. Also, ensure proper routing configuration to allow traffic from "work desk" LAN to reach the Pi-hole in the DMZ LAN. If Netcat shows a connection, DNS requests might be blocked by a firewall. Double-check firewall settings.