4 ms·
The most interesting takeaway from this article is that, according to people who actually do the work, NetworkManager and systemd-resolved do get things right.
by bonzini 6y ago
The most interesting takeaway from this article is that, according to people who actually do the work, NetworkManager and systemd-resolved do get things right.
- liveoneggs 6y agoone reason resolv.conf is/was so sticky is that gethostbyname (and friends) is a libc thing and pretty low-level
- corty 6y agoProblem is, modern browsers do things differently yet again. So the insanity continues, just on different levels.
- liveoneggs 6y agobrowsers are operating systems in user space. They will continue to replace kernel parts.
- vetinari 6y agoTechnically, the existing dns resolving mechanism is a part of glibc, so it is userspace already.
- YarickR2 6y agoMostly right. Article never mentions /etc/hosts , which is still largely a thing, and works wonders in difficult cases ( and makes other difficult cases much worse to debug)
- vetinari 6y agoBecause /etc/hosts is not really part of the chain handled by resolver or nss-dns. It is handled by different nss module which usually has higher priority.
- kevinoid 6y agoI agree! As a non-expert, I've also had good luck with NetworkManager, but wouldn't recommend systemd-resolved yet if you use DNSSEC: https://github.com/systemd/systemd/issues/6490 https://github.com/systemd/systemd/issues/6490 (fixed in v248) https://github.com/systemd/systemd/issues/8451 https://github.com/systemd/systemd/issues/8451 https://github.com/systemd/systemd/issues/9867 https://github.com/systemd/systemd/issues/9867 https://github.com/systemd/systemd/issues/12388 https://github.com/systemd/systemd/issues/12388