When trying to start an Instance it complains that my pihole app is bound to port 53, which Instances needs evidently: [image] Can I simply go into the pihole app and change its DNS port without any issues? Or do I need to do something else? [image] Thank you.

Perhaps this would help: [image] Can create Instances on Fangoth Apps and Virtualization 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 …

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 …

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. [Screens…

When specifying the IP you used for PiHole, what determined the IP you selected? Just an available IP on your network? Do I then need to reserve that IP on my router (Dream Machine in this case) as a static IP? I’ve been asking this question in a couple different Discord forums, but is this the new…

The IP I used was the one the TrueNAS system was configured with. I did not try to bind to all IPv4 addresses (0.0.0.0) as there is another DNS service running that needs to bind to the internal Docker and Incus networks.

Apologies if this is very basic, I’m just trying to learn. Earlier you said: Ensure that Instances (Incus) is not using the same IP address that you want to use for Pi-Hole. How about in this case? How did you select this IP? If my server’s on 192.168.1.50, is 192.168.1.100 fair game if it’s ope…

[image] MillerWDJr: How did you select this IP? https://apps.truenas.com/managing-apps/installing-apps/#network-configuration might help for a start.

Thank you for sharing this! It solved my problem right before i was about to use the change the incus dns port. good lookin out my friend!

Dumb question regarding Instances port 53 and pihole conflict

TrueNAS General

swc-phil June 3, 2025, 1:40am 2

Perhaps this would help:

Topic		Replies	Views
Upgrade to Fangtooth dident go as planned TrueNAS General	16	693	April 26, 2025
Local DNS on Fangtooth Apps and Virtualization SCALE , Apps , Custom-Apps , Fangtooth	19	2012	November 14, 2025
Can create Instances on Fangoth Apps and Virtualization SCALE , Networking , Apps , Incus	8	655	July 15, 2025
Unable to Install pi-hole App TrueNAS General SCALE , Networking	4	457	September 4, 2025
Simplest DNS server Apps and Virtualization	25	785	December 15, 2025

Dumb question regarding Instances port 53 and pihole conflict

Related topics