News for hackers. Stuff that matters.

A comment on Systemd: Don’t fallback to Google NTP and DNS. Parent comment

Re:Systemd: Don’t fallback to Google NTP and DNS by manjalyc on Thursday July 02, 2020 @11:23AM (#23714277)
Universal practice is editing the resolv.conf file and then write-protecting it with.

  chattr +i /etc/resolv.conf
This always works, but certain applications NetworkManager have their own preferred way of doing things that I quite frankly do not care to learn.
[ Parent | on HN ]
Re:Systemd: Don’t fallback to Google NTP and DNS by kevin_nisbet on Thursday July 02, 2020 @11:34AM (#23714419)
I think it get's a bit harder than this, with newer systemd supporting name resolution over dbus. It's conceivable that some programs may move away from libc resolvers using resolv.conf and start querying the service directly over dbus.

I'm not sure I'm personally a fan, just saying it's something that might become more common based on my read of the systemd docs awhile back.

[ Parent | on HN ]
Re:Systemd: Don’t fallback to Google NTP and DNS by vetinari on Thursday July 02, 2020 @12:00PM (#23714715)
> with newer systemd supporting name resolution over dbus.

Not only that, with suitably configured nsswitch.conf, (e.g. with nss-resolve), you might find out that your /etc/resolv.conf is used only by apps that have their own resolver and ignore the glibc one.

[ Parent | on HN ]
Re:Systemd: Don’t fallback to Google NTP and DNS by manjalyc on Thursday July 02, 2020 @11:55AM (#23714666)
Ah, I didn't want to get into the stupidity and sysadmin nightmare of systemd-resolved, but rest-assured even with systemd-resolved active most users can simply manage their /etc/resolv.conf file and systemd-resolved should respect it. It gets trickier when you don't have a network manager program or are use dhcp, VPNs, etc.
[ Parent | on HN ]