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
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?
--
Be
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
dis
3 matches
Mail list logo