Its doable to have bind be your DNS for AD it just takes some work and planing. The primary thing is make sure dynamic DNS works properly.
The big catches there are making sure you have the right Service entries and ensuring dynamic DNS works correctly. By the way neither of theism are AD specific requirements they actually stem from the RFCs that describe LDAP 3 and the RFCs which describe TLS and Kerberos V which the LDAP 3 RFC's reference. Essentially AD is Microsoft's implementation of LDAP 3 and since Windows server 2008 its very RFC compliant with some Microsoft windows specific optimizations and automation 



-- Sent from my HP Pre3


On Jan 9, 2014 21:38, Jeremy Wellner <[log in to unmask]> wrote:

That's a resounding stay the course and I don't mind that one bit.  It's been rock solid and I've been happy with it.

So as a secondary question, we are planning on adding Active Directory in to our network and I know that it is very particular about it's DNS.  Will AD be happy with being given a delegate domain to have as it's sandbox or does that throw my BIND install out the window?

Thank you all for the advise!! :)