Re: invalid prefix

The one on line 40 -- Mark Andrews > On 12 Mar 2022, at 10:28, Michael Richardson wrote: > >  > I upgraded to 9.18 from 9.11 or something that was in debian nulleye. > > Mar 11 18:14:27 tilapia named[9206]: /etc/bind/named.conf.options:40: invalid > prefix, bits [64..71] must be zero > >

invalid prefix

I upgraded to 9.18 from 9.11 or something that was in debian nulleye. Mar 11 18:14:27 tilapia named[9206]: /etc/bind/named.conf.options:40: invalid prefix, bits [64..71] must be zero Alas, line 40 has multiple IPv6 prefixes on it: 40 dns64 2607:f0b0:f:0:::/96 { 41 clients {

NOTAUTH on dynamic update followed by approved update

We have been using nsupdate for some time without issue. We recently started seeing NOTAUTH failures in the named logs followed by successful adding/deleting messages. The records are getting created but there are times when we see several (NOTAUTH) errors before we finally get a successful

Re: named log gaps/pause

You don’t mention your query rates. By chance is syslog rate limiting the messages sent by querylog channel? From: bind-users on behalf of Speagle, Andy via bind-users Hey Folks, I'm seeing something really strange with 9.16.26 ... we're getting like 10min gaps in the logs sent to

named log gaps/pause

Hey Folks, I'm seeing something really strange with 9.16.26 ... we're getting like 10min gaps in the logs sent to syslog... the server seems to work just fine... it just stops logging for long periods of time. We're using rsyslog on el8 ... Our logging looks like this: logging { channel

Re: Problems with caching server that forwards to an internal split-brain authoritative server

On Thu, Mar 10, 2022 at 7:48 PM Mark Andrews wrote: > > To answer your question about what you are overlooking the answer is “DNSSEC”. Thank you for the detailed response Mark. -- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development