Well, I don't really have the time, nor interest to clarify, the link Kopper posted
seems pretty good, it does a better job then I could on that
https://isc.sans.edu/forums/diary/Syste ... DNS/22516/
>>
I particularly like where OpenBSD is going with pledge(), which is even able to restrict ability of daemons to do things like file I/O. Maybe systemd is such a large beast that something like it couldn't be implemented there, and if that's the case I would suggest to simply steer clear of it.
Myself, I do use the google dns, I have no problem with it, and it is not just a systemd thing, I use it on my
OpenBsd server, and also on a
Minix 3 server,
neither of which is systemd, I also use it on the Debian 7 server, that is pre-systemd, so it is not systemd either.
If Debian , says
It's available, but not implemented by default.
I would take their word for it, obviously it would be rather foolish to try to lie, and say anything other then the truth, because surely someone would/ will check to confirm it.
Beyond the scope of the topic, but just saying, my reasons for not wanting to use a systemd system have nothing at all to do with this, and there is no point in going into a long list of details to clarify on that.
How ever I would like to add, in any case systemd or not, any Unix like OS, BSD, Linux what ever, one should have the ability to be able to go over all of the "default" settings and configurations, to make sure they are set as desired, if they do not know enough to do that, then they should either take the time to study and learn, or find a tech that they trust, and pay them to do it for them.
It is not wise to just take every bodies word for it, and assume the default setting are what you need or want.
Kristijonas >>Excellent answer Garry Ricketson
Thank you, that is nice, it is pretty rare anyone says that to me,... any way, also most of the more experienced Debian users here on this forum,ones that are actually using Debian 9 and systemd , most are pretty reliable , trustworthy,... again if some one claims something, and it is not true, some body will spot it and call them on it pretty quickly, being wrong by mistake , is not the same as delibrately misleading some one.
==== edit ====
from the "bug report link:
https://bugs.debian.org/cgi-bin/bugrepo ... bug=761658
This default is not used as long as a resolver has been configured by
the system administrator or provided by DHCP, and I see no value in
allocating development time to break cases which currently work by
removing support for a default.
Since the Google resolvers are a very reliable widely anycasted service
which third parties are encouraged to use they actually look like a sane
fail-safe default, hence I am closing this bug.
It is simple enough , to make sure the google dns is not used, make sure the
"/etc/resolv.conf" has something else configured.
Code: Select all
/etc/resolv.conf. This setting is
hence only used if no other DNS server information is known.
The rest of the "bug report", looks more like just a troll and arguments so
I did not read all of it.