Re: BIND-9.16.1 & KASP

> On 14 Apr 2020, at 04:54, Evan Hunt wrote: > > On Mon, Apr 13, 2020 at 02:22:53PM +0200, Mark Elkins wrote: >> Question - What are the "TYPE65534" records? What are they saying? I am >> using "DiG 9.16.1" so surprised it doesn't know. > > This is a mechanism named uses to keep track of the

Re: bind 9.16 vs. 9.14 tcp client connections

> I believe this problem should be fixed in 9.16.1: > > 5361. [bug] named might not accept new connections after > hitting tcp-clients quota. [GL #1643] > > However, we had two authoritative name servers running 9.16.1 which > stopped accepting new TCP connections

Re: BIND-9.16.1 & KASP

On Mon, Apr 13, 2020 at 02:22:53PM +0200, Mark Elkins wrote: > Question - What are the "TYPE65534" records? What are they saying? I am > using "DiG 9.16.1" so surprised it doesn't know. This is a mechanism named uses to keep track of the status of zone signing operations, so that if there's a

Re: bind 9.16 vs. 9.14 tcp client connections

Hello all, I believe this problem should be fixed in 9.16.1: 5361. [bug] named might not accept new connections after hitting tcp-clients quota. [GL #1643] However, we had two authoritative name servers running 9.16.1 which stopped accepting new TCP

Re: DHCPD - BIND DDNS: dnssec-keygen hmac-md5 removed

I would suggest: tsig-keygen your-key-name It does not need any options, the defaults are fine. -- Bob Harold On Fri, Apr 10, 2020 at 7:52 PM moo can via bind-users < bind-users@lists.isc.org> wrote: > Hello, > > For educational purpose I need to setup an DDNS between DCHPD and

BIND-9.16.1 & KASP

Hi all, I have been experimenting with BIND-9.16.1 & KASP. So far - it really looks great and it should greatly simplify DNSSEC for the masses. My named.conf entry:- dnssec-policy "ecdsa256-policy" {     dnskey-ttl 3600;     keys {     ksk lifetime unlimited algorithm ecdsa256;