Local DNS on Fangtooth

Apps and Virtualization
, , ,
1

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 under Dockge using macvlan, using a separate NIC, etc, but ended up finding a much simpler solution:

incus network set incusbr0 raw.dnsmasq="port=5354"

I haven’t checked if this will survive a reboot or if I’ll need to configure that command to run every boot, but just a heads up for anyone running into the same issue.

Not sure if it’s a bug, but if there’s not a compelling reason for incus to bind to 53, might be better to set it to another port?

2

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

3

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

4

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

1 Like
5

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

6

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

7

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

8

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
#FallbackDNS=
#Domains=
#LLMNR=no
#MulticastDNS=no
#DNSSEC=no
#DNSOverTLS=no
#Cache=no-negative
#DNSStubListener=yes
#ReadEtcHosts=yes

I didn’t have time to try it myself and won’t be able to play around with incus for another 2 weeks. Maybe someone can try and report back if it’s working or not.

9

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.

2 Likes
10

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 --strict-order --bind-interfaces --except-interface=lo --pid-file= --no-ping --interface=incusbr0 --dhcp-rapid-commit --no-negcache --quiet-dhcp --quiet-dhcp6 --quiet-ra --listen-address=10.108.165.1 --dhcp-no-override --dhcp-authoritative --dhcp-leasefile=/var/lib/incus/networks/incusbr0/dnsmasq.leases --dhcp-hostsfile=/var/lib/incus/networks/incusbr0/dnsmasq.hosts --dhcp-range 10.108.165.2,10.108.165.254,1h --listen-address=fd42:88b7:2e94:81ab::1 --enable-ra --dhcp-range ::,constructor:incusbr0,ra-stateless,ra-names -s incus --interface-name _gateway.incus,incusbr0 -S /incus/ --conf-file=/var/lib/incus/networks/incusbr0/dnsmasq.raw -u nobody -g incus

11

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 port, I was able to start my AGH docker with it binding to port 53. My router does not allow me to specify a non-standard port for DNS, so this was my best option.