bind, Microsoft Active Directory, Exchange and Magic Pixie Dust

[Martin McCormick]

	One of the latest things I am hearing is that "You must have a
Microsoft DNS" in order for the Microsoft Exchange package to work
correctly.

	We presently delegate an active directory zone on the site in
question and am trying to get all the clients to point their resolvers
at our bind master DNS.  This does appear to work properly for
everything else.

	Those of us closest to DNS on our site would ultimately like
to use the solution in Chapter 16 of DNS and Bind, 4TH Edition so that
no Microsoft DNS is used at all and the AD controllers are allowed to
update bind.

	My own experience with that approach is that it works
perfectly as long as one makes sure all the controllers can update all
the special AD zones, but I don't have an honest example of what
Microsoft Exchange does or doesn't need so I can't argue intelligently
one way or the other and I certainly don't want to recommend a
harmful course of action since people tend not to listen even more
than they already don't listen when we give them good information.:-)

	Can anyone describe a failure mode in Microsoft Exchange that
is actually caused by not using a MS DNS?

	Thank you greatly.

Martin McCormick WB5AGZ  Stillwater, OK 
OSU Information Technology Division Network Operations Group