zones question

[W Sanders]

> To promote a slave to master all you need to do is change the
	zone type from slave to master, remove the masters clause and 
	update the SOA MNAME (origin) to reflect the master.

BIND 9 wouldn't be picky about having the SOA MNAME match the name of
the server would it? I'm switching to a dual-master config and would
not want to have to edit my SOA's (I have 40,000 zones, growing by
about 50 per week.) I've never noticed BIND being picky about the MNAME
before.. Saw previous threads about DDNS using the MNAME, we're not
using that here.

It's kind of a tossup configuring two masters vs a master-slave:  I
provide web forwarding service for these 40K zones; about 30K of them
all have the same zone file and are held in memory (with no local zone
file) on the slave. We've had trouble with the slave dropping zones
with "no SOA found for <zone>" errors - named-xfer  works fine and "ndc
reload <zone>" always brings the zone back. It's almost like the
*master* is dropping the zone (because of the "no SOA found" on the
slave), or that since the zones are all the same they mass-expire
faster than the master-slave protocols can reload them. Anyway, I was
going to brute-force a solution by just rsync-ing the two masters
together.

Thanks,
-Wiley Sanders 
 Lafayette CA