Expected Behaviour:
Pi-hole should bind to port 53 on the local host so DNS traffic is routed through pi-hole
- Windows 11 - WSL 2
Actual Behaviour:
Replace this text with what is actually happening
This part would be helpful:
”Replace this text with what is actually happening”
From your debug log, these are the active interaces Pi-hole sees:
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[âś—] Failed to resolve log.aebn.net on lo (127.0.0.1)
[âś—] Failed to resolve log.aebn.net on lo (10.255.255.254)
[âś—] Failed to resolve log.aebn.net on eth0 (172.26.223.151)
[âś—] Failed to resolve log.aebn.net on flannel.1 (10.42.0.0)
[âś—] Failed to resolve log.aebn.net on cni0 (10.42.0.1)
[âś“] doubleclick.com is 142.250.69.238 via a remote, public DNS server (8.8.8.8)
But, you have told Pi-hole to listen here:
interface = "wifi0" ### CHANGED, default = "eth0"
The default configuration gave the same error which is why i changed it to try to see if another interface would work. This worked in wsl version 1 however i could not get the updates to the application until i migrated it to version 2.
What is happening is the port 53 is being used by wsl service and changing the default port removes the internal application dns failure but still does not resolve on the LAN by IP address as it did before. It causes an issue when trying to route all router traffic to pi-hole.
You should note that Windows isn't among Pi-hole's supported operating systems.
In general, Pi-hole's required ports must be free for Pi-hole to bind to, see also Prerequisites - Pi-hole documentation.
In your specific WSL setup, it would seem that WSL already binds port 53 to its own DNS process.
I am not familiar with WSL at all, but a quick Internet search suggests that you'd probably have to adjust your WSL's dnsProxy and/or dnsTunneling options to free port 53 for your Debian guest OS.
1 Like
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.