> I have a DNS server on campus that does not support DDNS. This is the
> primary DNS server and it is out of my control to make change to this
> server. Any good suggestions on how to design my AD site to support this
> DNS server.
Assusming your university domain is uni.edu and the primary DNS server you
are talking about is that for uni.edu, I would:
- Create a zone on the uni.edu DNS server called ad.uni.edu (say)
- Use a Windows 2000 DNS server as primary for the new ad.uni.edu zone
- Call you root Windows 2000 domain ad.uni.edu
Then add uni.edu as a UPN suffix and your users need not know about the
domain name...
Of course, DDNS is not mandatory so you /need/ not do anything (but I
would). Another possibility is to call your domain uni.edu and delegate the
_tcp, _msdcs, _udp etc. portions of the DNS tree as zones to a DDNS server.
[You need to do some manual configuration if you choose this route, though.]
List info: http://www.activedir.org/mail_list.htm
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
