Sit down with the DNS admin and discuss the possibility of creating a new
delegated DNS zone off of the main DNS infrastructure. For example, if the
current DNS infrastructure owns the domain MySchool.edu, then you can setup
a new DNS zone that supports your Active Directory infrastructure such as
MyNewZone.MySchool.edu. MS clients can use the new zone for the dynamic
registrations and you can do either forwarding to your main DNS server for
those records that are not in your zone or do zone transfers.
Of course this the simple abridged version. There are a lot of white papers
out there on integrating AD DNS into a legacy DNS structure. I'm also new on
the DNS learning curve so I might have oversimplified.
Diane
-----Original Message-----
From: Windows 2000 [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 25, 2001 8:06 AM
To: Active Dir mailing list
Subject: [ActiveDir] DNS
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. Do I setup an internal DNS server and forward all of my
requests to the primary DNS server. If this is the case then all of my
clients just need to point to the internal DNS server and they will be able
to gain access to the AD network and to the internet? Is there any special
configuration I need to make to the internal DNS server? Is the campus DNS
server the authoratative DNS server?
Thanks for your help
Jason
List info: http://www.activedir.org/mail_list.htm
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
List info: http://www.activedir.org/mail_list.htm
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
