Re: Workaround needed for TSIG Zone Transfer

Hi Rick, even while I should be destroying message (Sensitivity: Internal.) message, I am rather going to respond… Our colleague Tony Finch written nsnotifyd: https://dotat.at/prog/nsnotifyd/ Run this somewhere close to the proprietary server and configure it to send valid notifies to named.

Re: Workaround needed for TSIG Zone Transfer

There is no workaround that I can think of. As an aside I’d be specifying the key in the primaries clause rather than server clause. -- Mark Andrews > On 10 Jun 2023, at 07:52, Frey, Rick E via bind-users > wrote: > >  > I’ve got a case where using BIND (v9.16.41) as a secondary to a

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