What issues will arise when installing Windows 2000 Active Directory into an environment with an existing Linux-based DNS and DHCP server (corp.com), which is NOT going to go away? I plan to delegate a DNS child domain with the same name as my Windows 2000 Forest Root (ad.corp.com), and I am wondering about DHCP leases (which DNS server will DHCP report to - Linux or Win2k. And how will I set up a Reverse Lookup zone for my Win2k DNS entries?
Also, all machines currently have DHCP leases recorded in the corp.com DNS zone. What will happen when those machines are upgraded to Windows 2000 and they boot up first to get a DHCP lease? Will they get their old one (it will not have expired, and the machine name will be the same)? If so, how do I get the "old" entry out of the Linux DNS zone table and into the Win2k AD-integrated DNS zone? (Phew - a lot of questions!)
Whew -- rapid fire questions. If you are going to delegate a subdomain in DNS for Windows 2000, it would be best for you if you make an Active Directory Integrated DNS zone on the Windows 2000 Domain Controllers. It is the easiest to manage, most flexible and most secure method for Windows 2000 machines. With a Windows 2000 domain, you will need to make sure that whatever DNS server system you decide to use, it will correctly support dynamic updates. I believe that there is Linux DNS server software that does. You will need to check that with yours. If the DNS in Windows 2000 and the client machines are Windows 2000 Professional reverse lookup zones won?t be a problem, as the machines will create their own PTR records. Non-Windows 2000 clients will not dynamically create either record.
As far as DHCP goes, the Windows 2000 machines by default will update their A and PTR records with the correct information from the DHCP leased address. This can be turned off if it presents a problem, but in most cases it is a huge benefit. As far as getting the records out of the Linux DNS zone, they will have to be manually removed. If you elect to use Windows 2000 DNS with your AD, then manually removal from Linux will be about all you need to do.
Dig Deeper on Windows systems and network management
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.