getting not authoritative with some notifies - Solved

[Carl Byington]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On Sun, 2016-07-31 at 19:25 -0700, Dave Warren wrote:
> Or, separate your resolver and authoritative roles, in which case this
> won't be an issue. One should still monitor for zones for customers
> who have departed, obviously, but it's not likely to cause any
> operational issues.

Yes, I should have prefixed my comments with a note that this applies
mainly to users of some low end multi-tenant hosting solutions that (by
default) run both dns roles on the same box, and point /etc/resolv.conf
to localhost.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)

iEYEAREKAAYFAlefiKIACgkQL6j7milTFsFbiACfbGBeSfb5ukdSPG9Kgu+xIXWN
Gy4AniOZC3+vFQ1orNUkE/op/WmshsyG
=qmYk
-----END PGP SIGNATURE-----