Zone not propogating to slaves

[Niall O'Reilly]

On Wed, 2008-11-19 at 19:36 -0800, Steve Koon wrote:
[ ... ] 
> Anyone know why I am getting this “not authoritative” message and no
> zone file on .118 all of a sudden?
[ ... ]
> This is the log message in the 69.25.129.118 slave
> 
> client 69.25.129.117#1304: received notify for zone
> 'manzanitavacation.com': not authoritative

	118 is telling you that it won't act on a notify from 117
	because ...

[ ... ]
> =[3]== named.conf for 69.25.129.118 Slave ======================
[ ... ]
> zone manzanitavacation.com. in {
> 
>             type slave;
> 
>         file "c:\windows\system32\dns\etc\named\zones
> \db.manzanitavacation.com.zone";
> 
>             masters { 69.25.129.119; };
> 
>             allow-notify {69.25.129.117;69.25.129.118; };
> 
> };

	... you've told it to accept only 119 as a master. 

	[Log message might better say this more plainly.]

	You have a few options.

     1.	Read the ARM and work out how to avoid sending useless
	NOTIFY messages, while keeping the useful ones.

     2.	Leave things the way they are, and live with noisy logs.

     3.	Allow one or other (but not both -- you need to avoid
        loops in your update-propagation graph!) slave to act
	as intermediate master for the other.

	Beir bua!
	/Niall