5 ms·
Hands down the most annoying defaults on Linux. Being an OS for nerds, I'm surprised NetworkManager doesn't handle for manual updates to resolv.conf
by kingo55 8y ago
Hands down the most annoying defaults on Linux.
Being an OS for nerds, I'm surprised NetworkManager doesn't handle for manual updates to resolv.conf
- peterwwillis 8y agoIf you manually change something, how is it supposed to handle it? Notify the user and ask them to accept the change? But NetworkManager changes the file based on each network. So it'd have to ask you every time you connected to any network. And what do you do until the user accepts the change? Default to nothing? That would break any headless box where resolv gets accidentally overwritten. The simple solution is, make your manual overrides through NetworkManager, or don't use it.
- subway 8y agoNM doesn't always change resolv.conf. This entirely depends on the dns backend. If it's set to use dnsmasq, systemd-resolved or unbound as a dns backend, it never touches the file, instead passing nameservers in to the stub resolver dynamically. https://wiki.gnome.org/Projects/NetworkManager/DNS https://wiki.gnome.org/Projects/NetworkManager/DNS
- the_why_of_y 8y agoNetworkManager generates resolv.conf from the information associated with an arbitrary number of network connections. Which, or how many, of these N network connections should manual updates be mapped to? Edit: now I notice a sibling comment already asked almost the same question, but it was greyed out.