Installed Fangtooth. Happy with it and like the new virtualization with incus. Went to set up AdGuard Home under Apps and was unable to deploy it, both as a Custom App and from the App market. Incus was binding dnsmasq to 53, preventing me from using it for AdGuard Home. Considered a custom compose…

If you believe it to be a bug, file using Smile icon on upper right in Fangtooth GUI. It’s Feedback / Report A Bug. If you don’t think Bug, use Feedback

Same issue with pihole. dnsmasq is bound to port :53. pihole cannot start.

make sure you report a bug if that’s the case otherwise it may not be identified

Did you change the incus dnsmasq to bind to 5354 and try again?

yes, it’s reported via smiley button :wink: I didn’t try the incus command.

Try the Incus command in the OP and you can use PiHole now.

I was playing around with incus this weekend and stumbled upon the same problem with blocky, another dns sinkhole like adhgaurd and pihole. On the incus forum someone suggested to edit /etc/systemd/resolv.conf in the container like this: [Resolve] DNS=8.8.8.8 1.1.1.1 DNSStubListener=no #FallbackDN…

Interestingly, pihole in dockge is still fine. This is bound to {host ip}:53 exclusively. It suggests that the pihole TrueNAS app is the real issue, not incus.

That’s correct, here’s incus binding port 53 to 10.x network on my fangtooth (shell>netstat -ant), leaving my truenas 192.x network port 53 available: tcp 0 0 10.108.165.1:53 0.0.0.0:* LISTEN Process listing for incus confirms this: dnsmasq --keep-in-foreground -…

Incus was binding to port 53 on the 10.x network on my Fangtooth installation too, but was listening on all interfaces, so it would not allow me to run an application in Docker that also wants to bind to 53 (in my case AdGuard Home). As noted in the original post, after switching incus to another p…

Local DNS on Fangtooth

Apps and Virtualization

vakulenchuk April 15, 2025, 11:52pm 13

Someone has raised a jira for this
https://ixsystems.atlassian.net/browse/NAS-135341

actually looks like this was known in beta
https://ixsystems.atlassian.net/browse/NAS-134397

Adguard unable to start after update

Topic		Replies	Views
PiHole - port 53 appears to be conflicting Apps and Virtualization SCALE , Networking	10	3911	May 3, 2026
Unable to Install pi-hole App TrueNAS General SCALE , Networking	4	480	September 4, 2025
Upgrade to Fangtooth dident go as planned TrueNAS General	16	703	April 26, 2025
Dumb question regarding Instances port 53 and pihole conflict TrueNAS General	10	2200	July 17, 2025
Error Setting Up Instances - [EFAULT] The DNS and DHCP service exited prematurely: exit status 2 Apps and Virtualization	10	1249	May 14, 2025

Local DNS on Fangtooth

Related topics