Workaround needed for TSIG Zone Transfer

I’ve got a case where using BIND (v9.16.41) as a secondary to a third party (commercial) primary nameserver. Using TSIG for the zone transfers. Have verified zone transfers and TSIG key using dig between hosts. BIND is configured to use TSIG for the primary server using server x.x.x.x { keys

Re: lame-servers: SERVFAIL unexpected RCODE resolving

The .org TLD nameservers point to ns1 – ns4.opensuse.org as the authoritative nameservers for openSUSE.org. Appears that while ns2 and and ns3.opensuse.org are working, ns1 and ns4.opensuse.org return SERVFAIL when querying for openSUSE.org records. Your first sample log entry for lists.opens

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 syslog.

Re: Bind suddenly starts responding clients with servfail

Recursive clients are lookups/clients on your nameserver on behalf of a query received. If you are seeing that your nameserver is running out of recursive clients after removing “all” traffic, it would indicate something is still querying your nameserver as BIND won’t spontaneously create recur