[Maintain] Active Directory, non-Master Domains, and SOA's for Fun and Profit

[Ryan Dorman]

Hi guys-

     I asked this in the chat room but there didn't seem to be anyone  
around.. so i'll post it here and see if anyone has an insight...

     We are using maintain for A records and trying to integrate  
Active Directory into the mix.  I have hard-coded delegations for the  
Active Directory SRV zones in the tinydns configs so that the dynamic  
stuff that MS needs goes to the domain controllers but the A records  
stay in Bind/Maintain.
Its all groovy for our top level domain millersville.edu.  It does  
NOT work for a subdomain we are tryign to setup as  
labs.millersville.edu.  The data seems to make it to our BIND 9  
client-facing server but if i do a "dig _tcp.labs.millersville.edu"  
for example I get a SERVFAIL.   The only difference between the top  
level and labs is that  i set up labs.millersville.edu as a domain  
rather then a master domain with a SOA.  This is not Maintain's  
fault, I realize we are doing some funky business here. So... I need  
to temporarily migrate all the hosts in labs.millersville.edu (about  
1,200) into something else so i can delete labs.millersville.edu in  
Maintain and recreate it as a master domain.  The button you click on  
to do that says 'Dangerous" next to it  (in the Batch/Bulk Host  
Update Screen).  I was wondering if you coudl shed some light on  
that, or offer a different/better suggestion, I'd rather not hose all  
of the data entry we've done.

Thanks in advance!

Ryan Dorman, CCNA
Network Communications Specialist
Millersville University
717.871.5883
Ryan.Dorman at millersville.edu