Container dns configuration with dnsmasq running on different port

Incus
1

Hello,

I have an incus bridge incusbr0 with a dnsmasq configured to run on port 5353 using:

raw.dnsmasq: port=5353

My problem is the resolver configuration inside containers doesn’t receives the port from the dhcp.

For the moment I do it manually by launching

resolvectl dns eth0 [ipv6address]:5353

But obviously it doesn’t survive any reboot :slight_smile:

I tried to specifying a name server with the syntax ipv4:port and/or [ipv6]:port into dns.nameservers but it seems that property expects only an IP address.

Does a mechanism to workaround that situation exists ?

Thanks in advance

2

As far as I know, the DHCP protocol does not let you specify a port in the dns-nameserver field, neither does the IPv6 RDNSS field.