Re: systemd.resolved problems
On Fri, Mar 25, 2022 at 06:51:55AM +0800, Jeremy Ardley wrote:
> Is there any compelling reason to use systemd.resolved over ordinary DNS ?
> If not, why was it inflicted on debian?
It's disabled by default. It's there if you wish to try it, but out of
the box, it does absolutely nothing except sit there taking up space.
There's really no such thing as "ordinary DNS", though. Each nameserver
is implemented by some developer or team of developers, and is supposed
to conform to the various RFCs that define how DNS work. It's up to
you whether you want to run a local nameserver, and if so, to select
which one, and to configure it according to your needs.
systemd-resolved is just one of many available caching nameservers. If
it works for you, that's fantastic. If it doesn't, then you can try
something else.
If you don't run a local nameserver, then you will most likely receive
the IP address(es) of someone else's nameservers via DHCP, and you'll
use those instead. Either that, or you will manually type in the
addresses of some nameservers.
Reply to: