[Networkmanager] dns-mgr occasionally writes resolv.conf in the wrong order

Beniamino Galvani bgalvani at redhat.com
Tue Jun 27 14:40:29 UTC 2023

On Sat, Jun 24, 2023 at 03:30:32PM +0200, Bjørn Mork wrote:
> Sometimes I end up with a resolv.conf in the wrong order wrt routing
> defaults.  The DNS servers listed first do not belong to the ISP
> providing the default route.
> This causes severe DNS timeout isues because those servers either are
> unreachable or refuse recursive queries over the default route.
> I believe the problem started when I went from the Debian bullseye to
> the Debian bookwork version of NetworkManager. I.e from 1.30.6 to
> 1.42.4, but with some Debian patches if relevant.  I've been trying to
> reproduce it for a while, without being able to force it.  So I'm not
> exactly sure what the trigger is.

> [...]

> I don't exactly understand what this means, but it looks like
> NetworkManager considers all 8 DNS servers equal ("best")?  With both
> links having "priority=100, default-route=1".
> This does not reflect the actual priority, as shown above, where the
> wlan0 (ifindex=3) link has a lowe metric than the wwan0 (ifindex=29)
> link.
> Anyone have a clue why this happens?


please try a more recent minor release from the 1.42 series if you
can. I suspect this patch could fix your problem:


If not please file an issue on gitlab and attach a complete trace log
since the startup of the daemon.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.freedesktop.org/archives/networkmanager/attachments/20230627/dbbaf872/attachment.sig>

More information about the Networkmanager mailing list