dns2 named[23971]: client @0x7fa83ce341c0 192.168.15.1#37178/key gw-zones: received notify for zone 'ldev': TSIG 'gw-zones'
Seems I got it to work. Thanks Axel, and list. On Sun, May 26, 2019 at 4:37 PM Greg Rivers <gcr+bind-us...@tharned.org> wrote: > On Sunday, May 26, 2019 11:51:38 AM CDT Axel Rau wrote: > > > > > Am 26.05.2019 um 18:38 schrieb Rick Dicaire <kri...@gmail.com>: > > > > > A quick google search of "bind also-notify key" returns: > > > > > > https://kb.isc.org/docs/aa-00851 > > > https://kb.isc.org/docs/aa-00296 > > > > > > Looks like keys provide a means to differentiate views. > > > > ARM for bind 9.14.1 says on page 24: > > > > For example, a key may be specified for each server in the masters > statement in > > the definition of a slave zone; in this case, all SOA QUERY messages, > NOTIFY > > messages, and zone transfer requests (AXFR or IXFR) will be signed using > the > > specified key. Keys may also be specified in the also-notify statement > of a > > master or slave zone, causing NOTIFY messages to be signed using the > specified > > key. > > > So it does. Seems my knowledge of this was either outdated or just plain > wrong. Thanks for pointing this out. > > -- > Greg > > > _______________________________________________ > Please visit https://lists.isc.org/mailman/listinfo/bind-users to > unsubscribe from this list > > bind-users mailing list > bind-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/bind-users >
_______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
