News for hackers. Stuff that matters.

A comment on The Sisyphean Task of DNS Client Config on Linux. Parent comment

Re:The Sisyphean Task of DNS Client Config on Linux by js2 on Thursday April 15, 2021 @04:30PM (#26825737)
On macOS, you could do this trivially by creating /etc/resolver/internal with the name servers in it.

Linux should copy that.

[ Parent | on HN ]
Re:The Sisyphean Task of DNS Client Config on Linux by vetinari on Thursday April 15, 2021 @05:13PM (#26826174)
Systemd-resolved does much more than MacOS resolver. It can make the additional resolvers active conditional on whether the link is up, for example (think VPN). MacOS resolver can't do that.
[ Parent | on HN ]
Re:The Sisyphean Task of DNS Client Config on Linux by js2 on Friday April 16, 2021 @11:30AM (#26835100)
I thought tptacek was looking for something simpler than systemd-resolved. I was just pointing out the simplicity of /etc/resolver/<domain> on macOS that's been available since, I think, the first version of macOS. It's a nice feature.

In any case, on macOS, you use scutil to adjust resolvers when you change networking state as when bringing up a VPN.

[ Parent | on HN ]
Re:The Sisyphean Task of DNS Client Config on Linux by vetinari on Friday April 16, 2021 @12:06PM (#26835646)
Conceptually they are similar; one has config files in /etc/resolver/*, other in /etc/systemd/resolved.conf.d/*.conf; one has mDNSResponder process (yes, it is also unicast DNS resolver and cache, since 10.6, despite the name) and the other systemd-resolved. With systemd-resolved, you can achieve exactly the same thing as with MacOS resolver, for approximately the same cost.

With systemd-resolved, you don't have to adjust resolvers manually as links come up and down, NetworkManager's VPN connections play nice with it, while DNS resolver handling in Mac VPN software (including Wireguard and Tunnelblick) is a nuasance :(.

[ Parent | on HN ]