3 ms·
Do you mind sharing some? I would need some real examples to show to the team.
by zx8080 4y ago
Do you mind sharing some? I would need some real examples to show to the team.
- shrubble 4y agoThe above, of course. The DNS related issues seen (have they now been resolved?) where it takes over the DNS resolver functions and refuses to honor what you have put in e.g. /etc/resolv.conf ; a web search for "systemd breaks normal dns resolv.conf" will give you a lot of results ; unsure if this is now fully fixed. Strange things with LXC based VMs moved/migrated between hosts, even if an offline move; I think in 1 case I just ended up creating a new VM from scratch; then rsync'ing everything over from the host node into the VM's directory.
- Karellen 4y agoI thought that having the network subsystem manage resolv.conf dynamically had been pretty standard since well before systemd came along. e.g. Most DHCP clients have done that since... well, probably since DHCP was invented. See, for example: https://wiki.debian.org/resolv.conf https://wiki.debian.org/resolv.conf If you want a static resolv.conf, but you're not using a completely static network config and have some kind of dynamic network management daemon, be that `dhclient`, or `NetworkManager`, or `systemd-resolved`, you've always needed to explicitly configure it to leave resolv.conf alone. Not sure how this is a systemd issue?
- panick21_ 4y agoThe DNS issue here seems like you just wanted to use DNS like you had before despite the OS changing. That isn't really a bug, just a change in how the OS operates. If you don't want that, you can disable that feature.
- 3np 4y agoWhich services are enabled by default is up to each distribution. In you case I'm guessing it might be systemd-resolved or systemd-resolvconf, if not NetworkManager. Just disable what you don't want. In terms of problematic default services, I'd look at GNOME. systemd is just the medium.