Hacker News Reader

Comment by throw0101a | Hacker News Reader

> The reason for seeing overcomplexity in systemd components is usually that you never considered the use cases of other people or proper server management

What use cases of "proper server management" does fucking with my resolv.conf(5) solve?

If I have a laptop I can perhaps see updating values per DHCP or IPv6 RAs, but once I set up a server up why the hell is it a link to /run? (I once had to use chattr +i because of brain dead "cleverness".)

In over thirty years of running Unix-y systems I never needed my resolv.conf "managed", so I have no idea why Ubuntu (for one) defaults to fiddling with it.

View on HN

> What use cases of "proper server management" does fucking with my resolv.conf(5) solve?

For one, it avoids telling all processes and their mothers the IP of the DNS resolvers they should query, but hands them 127.53 instead. If you then update your resolvers using systemd-resolved, for example because the network changes to a failover line, or because puppet pushes an updated catalog, or you want split DNS for a VPN (like, send *.corp.local to the internal DNS server or something), that is all pretty easy. There are more use cases on servers, but of course you most obviously benefit from this on laptops that roam between WIFIs with different upstream DNS server config.

> For one, it avoids telling all processes and their mothers the IP of the DNS resolvers they should query, but hands them 127.53 instead.

What "all process" are you referring to? What kind of software on Unix-y systems is not using gethostbyname(3) (or similiar)?

(And the context of this sub-thread is "server management", which I'm not sure how often has VPN running on it and doing things like split (horizon) DNS.)

Just one thing: why that resolver work *need to be" in systemd package ? Why we can't have few implementations, as it always have been, that do different jobs, with overlapping funcionalities ? Why we ever need some gigantic codebase guarded by corporations that we can't easily replace ? Codebase that is uncooperative with other implemantations. And developers.

And moust importantly: why they make everything more stupid and windows-like trash ?

And I assure you: what you described as "easy" is not true. I is just few basic usecases they baked in. And when you neeed something a bit more specific in some direction you are not allowed to have that.

Systemd is a trash, atm.

You should install an actual local resolver for this, not systemd.

Reply on news.ycombinator.com