Hi all, I set up pi-hole on Windows 11 with Ubuntu docker on an N100 Mini PC. My router is using ASUS Merlin. I have tried to set up pi-hole as my DNS server for either WAN or LAN. For the WAN set up, which is not recommended, I just put the host static IP address 192.168.50.37 to WAN DNS server in Asus page. The strange thing is that I can't access many websites like Google, Twitter and Outlook following the WAN DNS server set up, but remaining some very limited access to websites like Reddit.
I see you've created an exception for the Beelink host to have no DNS redirection.
You should do the same for the Pi-hole instance or DNS queries will go loopty loop and will never get forwarded to upstream Internet.
And preferred is to only configure the Pi-hole IP in the LAN-->DHCP-->DNS router settings and default the WAN-->DNS setting to factory default:
The Beelink host is running Windows 11 with Ubuntu where the Pi-Hole is set up. So I think it means that no DNS redirection is for the Pi-Hole instance as well.
That's the LAN configuration I am using. Following the link you suggested, I add 'static domain_name_servers=127.0.0.1' to '/etc/dhcpcd.conf', but still no luck. When I have Pi-Hole IP in the WAN-->DNS section, I am not configuring 'Conditional Forwarding' and I can't still not access the internet.
The interesting thing is that, my previous setup of Pi-Hole instance is on the Docker Desktop app, and configuring Pi-Hole in my router works well with no issues at all. After switching to docker in Ubuntu, same configuration in router is not working any more.
Am guessing its most likely Windows own caching stub resolver thats responding instead.
I have no experience with the Linux subsystem in Windows so cant help you with that.
Maybe someone else can.
No worries. Thanks for your help. I can see similar information by nslookup -class=chaos -type=txt version.bind 172.22.9.64, where 172.22.9.64 is the local IP address of docker on my Windows host. I will try to figure out how to make it work via Windows, and hopefully, someone can provide me with more ideas on this issue.
You have enabled a feature labeled as DNS Director in your router.
According to its description from your screenshot, that would have your router intercept and redirect DNS traffic to a given target DNS server.
Your nslookup results would suggest that your current configuration forces DNS traffic through an unknown DNS server, presumably your router (which somewhat would contradict the description for Global Redirection: Router, provided port 53 is accessible).
The screenshot suggests that you could also try to provide a User defined DNS server instead.
You should try to do so, and then run some version.bind lookups to verify, e.g.
