Dumb question regarding Instances port 53 and pihole conflict

[Okedokey]

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.

[swc-phil]

Perhaps this would help:

Can create Instances on Fangoth

Yes adguard is your problem since incus also wants to use port 53 for DNS resolution, but you can change the incus port with a command. When I’m back from my lunch break I’ll see if I can find the forum post with the command Edit this is the command to change the incus dns port incus network set incusbr0 raw.dnsmasq="port=5354"

[LarsR]

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)

[PK1048]

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.

[Okedokey]

Thank you