Active Directory requires Microsoft DNS?

Mon Sep 20 14:51:57 UTC 2010

Our Corporate Overlords run DNS on a mixed environment of Windows and
Other (mostly other).  Back when we were still a small company, we moved
our DNS from BIND to Windows for ease of administration.  It CAN be
done, but it's a huge PITA since AD does things in DNS that aren't
standard (and in fact, violate it willfully and knowingly to make MS
Kerberos bits happy).  I had my Unix servers acting as secondary servers
to serve their clients off the AD primary servers, and that worked just
fine.  Windows Server 2003 and later are extremely stable and we've had
no issues with them taking over DNS duties (I've long since just pointed
all my Unix boxes at the Windows servers for DNS since the Windows
servers have been so stable and reliable).

Jamie

-----Original Message-----
From: Tom Mikelson [mailto:tmikelson at gmail.com] 
Sent: Monday, September 20, 2010 10:05 AM
To: nanog at nanog.org
Subject: Active Directory requires Microsoft DNS?

Presently our organization utilizes BIND for DNS services, with the
Networking team administering.  We are now being told by the Systems
team
that they will be responsible for DNS services and that it will be
changed
over to the Microsoft DNS service run on domain controllers.  The reason
given is that the Active Directory implementation requires the Microsoft
DNS
service and dynamic DNS.  Not being a Microsoft administrator I do not
know
the veracity of these claims.  Anyone out there had any experiences with
a
situation like this?  I am a bit leery of changing something that is
already
working.