getting not authoritative with some notifies - Solved

Matus UHLAR - fantomas uhlar at
Tue Aug 2 09:47:18 UTC 2016

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

On 01.08.16 10:37, Carl Byington wrote:
>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.

in such a small system it shouldn't happen often that someone migrates
domain off your server.

However you can avoid this issue by running either multiple dns servers,
bind instances or views, recursive-only on and authoritative on
public IP.
Matus UHLAR - fantomas, uhlar at ;
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
I just got lost in thought. It was unfamiliar territory. 

More information about the bind-users mailing list