When trying to start an Instance it complains that my pihole app is bound to port 53, which Instances needs evidently:
Can I simply go into the pihole app and change its DNS port without any issues? Or do I need to do something else?
Thank you.
Perhaps this would help:
According to a video from STH showcasing the new incus system, this is only required if one is using the incus bridge. If you create and use your own bridge, at least according to the video, this is not required (i did not test it myself)
You need to leave Pi-Hole on port 53 if you expect other DNS clients to find and use it.
I have run into this, with Incus wanting port 53. I suspect (but I have not had time to actually do this fix) I can get Incus to only bind to port 53 on certain interfaces and leave port 53 open for Pi-Hole on the public interfaces. Once I get it working I will post how I do it.
1 Like
Thank you
Sorry for the delay, I finally had time to tackle this today.
- Ensure that Instances (Incus) is not using the same IP address that you want to use for Pi-Hole.
Instances -> Configuration -> Global Settings, Incus will run a DNS server on port 53 on the configured default global networks.
- When you deploy the Pi-Hole App you need to specify three separate networks (address and port) for HTTP user interface, HTTPS user interface, and DNS service. Use a different IP address for Pi-Hole than you used for Instances.
After doing the above, Pi-Hole started just fine and bound only to my LAN on port 53. Technically, it was a Docker proxy that bound to the ports for HTTP/HTTPS/DNS and proxies the traffic to Pi-Hole.
xxx% sudo netstat -apn | grep LISTEN | grep docker-pr
tcp 0 0 192.168.32.37:53 0.0.0.0:* LISTEN 2131748/docker-prox
tcp 0 0 192.168.32.37:30020 0.0.0.0:* LISTEN 517825/docker-proxy
tcp 0 0 192.168.32.37:20720 0.0.0.0:* LISTEN 2131778/docker-prox
xxx%