aardvark-dns using port 53

[d-513]

Cannot start Pi-Hole when aardvark-dns is enabled, because it takes up port 53

[root@archserver containers]# netstat -plntu | grep 53
udp        0      0 10.89.0.1:53            0.0.0.0:*                           2617/aardvark-dns

when aardvark-dns is disabled, everything works, but you can't use dns to communicate between containers

Port is hardcoded https://github.com/containers/netavark/blob/4af309fb888d54238dc9028bcfe150425c687b02/src/dns/aardvark.rs#L93-L100

related containers/aardvark-dns#13
anyway to bypass this limitation?

[mheon]

Not at present. There is no way to specify that DNS should use a nonstandard port, so until we implement a NAT solution port 53 must be used. You can bind your DNS server to specific IPs (the machine’s public IPs) to avoid the ports bound by Aardvark.

…

On Sat, May 14, 2022 at 11:11 dada513 ***@***.***> wrote: Cannot start Pi-Hole when aardvark-dns is enabled, because it takes up port 53 ***@***.*** containers]# netstat -plntu | grep 53 udp 0 0 10.89.0.1:53 0.0.0.0:* 2617/aardvark-dns when aardvark-dns is disabled, everything works, but you can't use dns to communicate between containers Port is hardcoded https://github.com/containers/netavark/blob/4af309fb888d54238dc9028bcfe150425c687b02/src/dns/aardvark.rs#L93-L100 related containers/aardvark-dns#13 <containers/aardvark-dns#13> anyway to bypass this limitation? — Reply to this email directly, view it on GitHub <#14242>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB3AOCDU3Z2YRYJZACDWI3DVJ67DBANCNFSM5V5WDBRA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[d-513]

Not at present. There is no way to specify that DNS should use a nonstandard port, so until we implement a NAT solution port 53 must be used. You can bind your DNS server to specific IPs (the machine’s public IPs) to avoid the ports bound by Aardvark.

Thank you! This worked like a charm. For reference for anyone wondering, I published the port to the IP directly: "192.168.10.225:53:53/udp"

[ninjadev64]

Helped me as well, thanks!

[tysegall]

I know this issue is a bit old, but I had to remove the aardvark-dns package from Ubuntu in order to spin up pihole and unbound running on podman with a docker-compse.yml file. It's a bit of a special case, @mheon but I would say that it "just works" if I'm using legit docker versus podman. Would be nice if the port was configurable for Aardvark instead of being hardcoded.

[Luap99]

The port can be configured in containers.conf

[network]
dns_bind_port=5000 # or well whatever you like

[tysegall]

Thanks! That actually worked. I created /etc/containers/containers.conf with a custom port, reinstalled the aardvark-dns package, and I can now successfully start pihole and unbound as defined in the docker-compose.yaml file. Thank you @Luap99