2 ms·

> Domain name resolution behaviour should be program-controllable, not system-controllable This is pure insanity, of course, but i'm sure i'd be entertained by

by twic 5y ago

> Domain name resolution behaviour should be program-controllable, not system-controllable This is pure insanity, of course, but i'm sure i'd be entertained by you trying to justify it, if you're inclined.

nybble41 5y ago
Not the GP, but I would at least agree that the C library should not be handling domain name resolution or requiring any dynamically-loaded plugins. However, I am strongly opposed to having each application implement its own resolver and ignoring system settings. There should be a single system resolver where applications submit their requests. Something like the DBUS API presented by systemd-resolved, for example. Or the older NSCD protocol which permits out-of-process implementation of the NSS APIs, ostensibly for caching. systemd-resolved offers a nice compromise since, in addition to the rich DBUS API, it also acts as a recursive resolver on 127.0.0.53. So any applications that do implement their own resolution can be pointed there.