News for hackers. Stuff that matters.
Re:Systemd: Don’t fallback to Google NTP and DNS by falcolas on Thursday July 02, 2020 @10:26AM (#23713418)
Did you know that there are at least four different file locations that resolvers can be set in for systemd-resolved?

The defaults being in a commented-out section in one of these four locations (and in a file whose name does not match the linux standard of resolv.conf) is, frankly, not a big help in identifying what's really being used.

https://jlk.fjfi.cvut.cz/arch/manpages/man/systemd-resolved....

Re:Systemd: Don’t fallback to Google NTP and DNS by JdeBP on Thursday July 02, 2020 @04:54PM (#23717952)
Actually, it's five, or even six. systemd doco is bad at including /usr/local/ .

You are pointing to the wrong manual page, incidentally. It's resolved.conf(5). This fails to list /usr/local/lib/systemd/resolved.conf.d/ , which is scanned before /usr/lib/systemd/resolved.conf.d/ (and if configured /lib/systemd/resolved.conf.d/).

Re:Systemd: Don’t fallback to Google NTP and DNS by megous on Thursday July 02, 2020 @12:44PM (#23715137)
How do any of those 4 resolv.conf location variants change where the compiled-in fallback is configured/visible?

If user wants to know what's really being used for name resolution he should go to /etc/nsswtich.conf and /etc/hosts and /etc/resolv.conf as usual.

Re:Systemd: Don’t fallback to Google NTP and DNS by JdeBP on Thursday July 02, 2020 @05:11PM (#23718115)
If systemd-resolved is actually being used, /etc/resolv.conf will list only 127.0.0.53, and to find out what systemd-resolved itself is using one has to visit the resolved.conf configuration files, which is what falcolas is apparently talking about.

But then if one is using, say, dnscache or dnsmasq or MaraDNS or BIND or PowerDNS or any other such software, one has to do the same thing. /etc/resolv.conf will list simply 127.0.0.1 or some such, and one has to go further to the configuration files of those softwares to find out what they are using for resolution/forwarding.

DNS softwares having their own configuration files is normal. falcolas is apparently getting at the fact that systemd-resolved uses the same style of configuration as the other systemd programs do: files and drop-in directories in /etc/systemd, /run/systemd, /usr/local/lib/systemd, /usr/lib/systemd, and (if configured) /lib/systemd, meaning that one has to read all of this together.

Re:Systemd: Don’t fallback to Google NTP and DNS by megous on Thursday July 02, 2020 @06:36PM (#23718905)
It would be clearer if he linked to https://jlk.fjfi.cvut.cz/arch/manpages/man/resolved.conf.5.e... then.

Anyway, in default config, there will be only the file I mentioned. And whole this issue is about default configuration.

Re:Systemd: Don’t fallback to Google NTP and DNS by JdeBP on Thursday July 02, 2020 @07:20PM (#23719192)
Actually, no. The headlined issue is about what the fallback is when there is no file, or a file that doesn't specify a setting.
Re:Systemd: Don’t fallback to Google NTP and DNS by megous on Friday July 03, 2020 @12:30PM (#23725333)
There's always /etc/systemd/resolved.conf in default installation/build.
Re:Systemd: Don’t fallback to Google NTP and DNS by JdeBP on Sunday July 05, 2020 @03:46PM (#23741329)
... which does not specify a setting. As falcolas explained at the start. Have you caught up now?
Re:Systemd: Don’t fallback to Google NTP and DNS by djsumdog on Thursday July 02, 2020 @10:56AM (#23713892)
Wow. I never realized there was a DNS server listening at 127.0.0.53 on systemd based distros.
Re:Systemd: Don’t fallback to Google NTP and DNS by creeble on Thursday July 02, 2020 @12:00PM (#23714709)
Just try using a system on a "captive portal" wifi connection. You will soon learn "apt purge systemd-resolvd".