Discussion Locked

UNIX DNS or plain'ol Win2K DNS...??

0 helpful
1 reply
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have an AD question should someone have the time to answer. Orders have been pushed down from mount high to install active directory for login support to the end user. We will start with a clean and pristine install of 2 brand-new HP 6000 servers.As I get my people logging into the new AD domain I will start to bring in other domains into AD. The setup of AD DNS however is a bit fuzzy. The existing DNS is a Unix AIX box which I converted to BIND 8.2.X to support the SRV record for dynamic updating. Now that it is done, how do I set up Win2K DC's i have running AD DNS service to point to the AIX box for Dynamic updates? And should I have my clients resolve to the AIX box or the AD domain controllers for DNS resolution? Also, should I just use Win2K's AD's DNS for the resolution for my internal domain and leave the AIX box for external resolution only? I would be glad to RTFM but the books I have read for these past months do not detail this setup very well. Any help you can provide,links, or other books on the subject that you recommend will be helpful. Thanks!

1 reply

by duskos

I am not joking, but reading about DNS in Windows 2000 Help can be very helpfull. Other resources are of course microsoft.com/technet and training manuals.

I would definitely go for Windows 2000 DNS.
Reasons:
1. Active Directory integrated zones. If you have more AD sites etc, any change, anywhere is automatically updated on all DNS's hosting that zone. With standard primary/secondary zones, you can only make change on primary zone, then replicate to secondaries.

2. Integration with DHCP and WINS.

3. You can still connect your UNIX DNS zone to AD integrated zone as normal standard secondary zone.

Now, about internal and external DNS's. Yes, you should definitely have separate DNS servers for Internet and for Intranet.

To which DNS to point your clients? Depends on network. You can define two or more DNS's. Have clients connect first to the closest DNS. If you are using DHCP for client configuration, it shouldn't be difficult at all.

This discussion is closed to new replies.