mirror of
https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git
synced 2026-03-13 17:30:36 +01:00
With systemd-resolved, NetworkManager considers `/etc/resolv.conf` unmanaged. This breaks hostname lookups in a subtle way: when a new connection comes online, NM will initiate the hostname lookup *before* propagating DNS updates to systemd-resolved, which of course will cause the request to fail. And because NM doesn't update `/etc/resolv.conf`, it doesn't emit a `CONFIG_CHANGED` signal which would've restarted the lookup. Fix this by emitting a signal also when using a caching DNS plugin. https://bugzilla.redhat.com/show_bug.cgi?id=1933863 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/770 |
||
|---|---|---|
| .. | ||
| nm-dns-dnsmasq.c | ||
| nm-dns-dnsmasq.h | ||
| nm-dns-manager.c | ||
| nm-dns-manager.h | ||
| nm-dns-plugin.c | ||
| nm-dns-plugin.h | ||
| nm-dns-systemd-resolved.c | ||
| nm-dns-systemd-resolved.h | ||
| nm-dns-unbound.c | ||
| nm-dns-unbound.h | ||