On Sun, Nov 21, 2021 at 06:51:13PM +0100, Sten Carlsen wrote:
! As far as I am aware - and what I have always done - the normal
| thing to do is to use a hints file. Lately the hints are built-in,
| so nothing is really needed.
Ah. Well, I have here a named.conf.sample file that comes with the
As far as I am aware - and what I have always done - the normal thing to do is
to use a hints file. Lately the hints are built-in, so nothing is really needed.
One question that comes to mind:
What happens if the slaved root zones are not up to date /not correct? might
that be the cause?
--
Hija,
I finally found the cause of the error! As soon as I stop slaving
the root-zones and instead use the (configured or compiled-in)
hint-file, the error stops.
The actual error-condition (zone is not loaded) then becomes
obvious, because this RFC-5011 action happens very early, before
any
On Mon, Nov 15, 2021 at 09:14:19AM +0100, Ondřej Surý wrote:
! > On 15. 11. 2021, at 3:41, Peter wrote:
! >
! > Wondering
!
> On 15. 11. 2021, at 3:41, Peter wrote:
>
> Wondering
> * WHAT is broken?
> * Why does it happen only to me?
We can’t really help you if you don’t share any details of your installation
and configuration (hint: You can use `named-checkconf -px` to scrub the
configuration).
So far, you shared
Hi all,
I continuousely happen to see this message:
> local0.warn named[2291]:
> dnssec: warning: managed-keys-zone: Failed to create fetch for DNSKEY update
I see it on different nameservers, at different sites, with and
without views, with and without IPv6, and I see it every time when
named
6 matches
Mail list logo