Hacker News new | ask | show | jobs
by agwa 3437 days ago
Non-DNS resolution protocols like LLMNR are almost entirely irrelevant, particularly on servers. Even if you do need asynchronous LLMNR support, you do not need dbus and a particular process running as PID 1 to get it - applications can make LLMNR queries using an asynchronous library, just like many currently use an asynchronous DNS library.

The fact that systemd keeps making decisions like this that are architecturally dubious and lead to lock-in is most certainly grounds for criticism.
2 comments
noselasd 3437 days ago
When people enter a hostname into my application, I'm not particularly keen on implementing name resolving myself via DNS, LDAP, hosts file and so on in the application - It's absurd to suggest applications should make such a decision.

The current NSS system works nicely though, it just needs an async API.

link
natermer 3437 days ago
Nothing systemd has done is preventing anybody from using any asynchronous library they feel like.

It's providing local name resolution services. And for very good reasons.

By your logic things like NSS is useless as well because programs themselves can read ldap configuration files and /etc/resolv.conf on their own using libraries or whatever else they feel like using.

link