Re: [SOLVED?] Re: BIND: managed-keys-zone: Unable to fetch DNSKEY set '.': timed out

[Jeremy Ardley <jeremy@ardley.org>]

On 14/3/23 06:34, Greg Wooledge wrote:
> On Tue, Mar 14, 2023 at 06:23:09AM +0800, Jeremy Ardley wrote:
> > FYI systed-resolved is the inbuilt debian caching DNS server which may be
> > enabled by default.
> It is NOT enabled by default.
>
> unicorn:~$ systemctl status systemd-resolved
> ● systemd-resolved.service - Network Name Resolution
>       Loaded: loaded (/lib/systemd/system/systemd-resolved.service; disabled; ve>
>       Active: inactive (dead)
>         Docs: man:systemd-resolved.service(8)
>               man:org.freedesktop.resolve1(5)
>               https://www.freedesktop.org/wiki/Software/systemd/writing-network->
>               https://www.freedesktop.org/wiki/Software/systemd/writing-resolver>

I replicated your test above and it seems your listing has been 
accidentally truncated...

jeremy@testldap:~$ systemctl status systemd-resolved
● systemd-resolved.service - Network Name Resolution
     Loaded: loaded (/lib/systemd/system/systemd-resolved.service; 
disabled; vendor preset: enabled)
     Active: inactive (dead)
       Docs: man:systemd-resolved.service(8)
             man:org.freedesktop.resolve1(5)
https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients

It would seem the debian default is enabled? See vendor preset below.

Loaded: loaded (/lib/systemd/system/systemd-resolved.service; disabled; 
vendor preset: enabled)

--
Jeremy
(Lists)