Auth server reports: resolver priming query complete

[Jim Popovitch]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Sun, 2019-07-28 at 02:14 +1000, Mark Andrews wrote:
> > On 28 Jul 2019, at 2:03 am, Jim Popovitch via bind-users <bind-users at lists.isc.org> wrote:
> > 
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA256
> > 
> > On Sun, 2019-07-28 at 01:36 +1000, Mark Andrews wrote:
> > > Authoritative servers lookup addresses of nameservers to send notify messages.
> > > If the names are not in the authoritative data it will iterate to find the address.
> > 
> > Thanks Mark. BTW, this is with v9.14.4.  Follow-up question:
> > 
> > I only see ns1 (master) logging the priming, ns2 doesn't.  ns2 is a
> > slave to ns1, but also a master to a 3rd party (e.g. also-notify,
> > notify-explict).  Shouldn't ns2 also be priming addresses of the non-
> > auth 3rd party?
> 
> If you have "notify explicit;” and also-notify then named will only
> send notify messages to the addresses listed in the also-notify clause
> so there is not need to iterate.  Priming only occurs when named actually
> iterates.

Should ns1 (master) be priming if it also has notify-explict and also-
notify statements.  The domain in question is the domain sending this
email.

- -Jim P.
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEE3RmV4WutJ2KyCS2zPcxbabkKGJ8FAl08esIACgkQPcxbabkK
GJ85/hAAt3QPtbto6SraqIa24pmYDf0gG/D2YBzjaEI7JkqpIJHabtDSt4FjueGs
gQpjgJ40ivs4sicd8KeX5OGMZcr3zerMXJrtVWg/XqlT1hi55ZwMEkEssikHiL2P
HYSmNCDRUuZpUuRyQEW2kGoaeTXU/21p0SJo5Q8UCG0D/ww8dTa9ACIJGMBkGCTk
KkNduOX+uG3qwSa22WEsewhyU9I7rAUd7W/PrF3nsMEshCuuom5O5zUfq2F5COyJ
ad0BJJSBBHfjgEj4ym1oxqRtUoh6M9eJU12GHp9gqhI6uRsTwxtYnwdThXfwvMqp
myIwnx4IdG+6gisfns1nPlsdrg6lXAKIZ3AzBKGiTSj5wMVRB3EVnDTs6C4B02pk
75i+/YOUFL5kmRJUUgIVKOqv4f3ePTM3KsglkCLRRRK+Zw/2JGui2vuekS/EO0la
DQ8xcFCf75CW3v84TMtiCK0O8yMwsxFJVfW0pyQwOWhU3jjniPEVZDIMs1Wgzryk
zjHq6Zi2U25ZXSHKHmYnQB97cMxSAPOikFeWuuZcKfaBhmaSOXKN7RJZdHxCxyu0
gh5k3qt0XaQj351sOm3kHLN1ZtHT2w+W+RZS+EcMu6nIUKPUDE9WNtk5P3Al/OkP
FELyyEzDwc1QkaGuqzlz6kXR7BGjR50dRcqwdSJfuFUcdTneVPs=
=pPMe
-----END PGP SIGNATURE-----