[Networkmanager] dns-priority ignored
thaller at redhat.com
Fri Dec 16 10:15:31 UTC 2022
On Thu, 2022-12-15 at 12:34 +0100, Michael Traxler wrote:
> I use on many OpenSuse Tumbleweed machines two network cards with
> their own
> VLAN and their separate DHCP- and DNS-servers and have a common
> problem in all
> systems (over a longer time now).
> The order of the DNS-servers of the two VLANs in /etc/resolv.conf is
> and in the end is arbitrary.
> I tried everything from the manual, so changing the dns-priority to
> values, even using
> $ nmcli connection modify internal_VLAN ipv4.dns-priority -100
> and keeping the other interface at positive 100 doesn't change the
> that the resulting order of DNS-entries in /etc/resolv.conf is
> changing from
> restart to restart of the network
> for example by calling
> $ systemctl restart NetworkManager.service
> Is there something I overlooked in the manual?
> I don't see how I can reach the point, that the result is constant
> retrieved from the DHCP-servers.
> The only workaround for me:
> ipv4.ignore-auto-dns yes
> and setting the dns to a fixed string.
> Any hints?
Setting the dns-priority should be the way to go.
If it doesn't work, it's not clear why it would not.
Check the `level=TRACE` logs. See "DEBUGGING" in `man NetworkManager` .
More information about the Networkmanager