On Sun, Aug 15, 2021 at 10:35:27PM +1000, raf wrote:
> But the real problem is that bind crashed, and dumped
> core, and couldn't start at all. There were a hectic
> few minutes there. :-) I deleted the coredump and the
> key files, and the .jnl files, restored backup
> zonefiles, updated the
On 8/15/21 9:07 AM, G.W. Haywood via bind-users wrote:
> Hi there,
>
> On Sun, 15 Aug 2021, Tim Daneliuk wrote:
>
>> I have a bind slave instance running on FreeBSD 13-STABLE. Periodically
>> (after
>> a few days of perfect operation), it loses its ability to resolve at
>> least some names -
Hi there,
On Sun, 15 Aug 2021, Tim Daneliuk wrote:
I have a bind slave instance running on FreeBSD 13-STABLE. Periodically (after
a few days of perfect operation), it loses its ability to resolve at
least some names - in this case, git.freebsd.org. ...
...
Aug 14 17:07:03 ozzie named[32292]:
raf via bind-users wrote:
>
> But that means that it applies to all of the zones in
> /etc/bind/named.conf.default-zones which is not helpful. It also applies
> to the zones in /etc/bind/zones.rfc1918 if that is included in
> /etc/bind/named.conf.local (which a comment there suggested). That's
Hi,
I've just upgraded my bind9 server to debian-11 which
has bind-9.16.15. I've been looking forward to this. I
had my local dnssec-policy ("annual") all ready to go.
But it didn't go well at all.
For the first few seconds, I thought it was great. I
uncommented my new config to enable DNSSEC
5 matches
Mail list logo
