I have a customer that has been experiencing name resolution issues. They have a Windows 2000 Active Directory with parent.com and child.parent.com domains. I made some changes that have fixed the problems for now by removing orphaned secondary DNS zones with no Primary and ensuring there are only AD-Integrated DNS zones. Also removed WINS from the environment.
Just not comfortable with how DNS is still setup, so have a few questions: 1. Presently, the DHCP scopes point clients to the parent.com DNS servers. Since all users and computers are in the child.parent.com domain, wouldn't the best practice be to point all DHCP clients to the child.parent.com domain DNS servers? Does it make a difference that these clients use the DNS servers in the root (parent) domain? 2. Presently, the child.parent.com forward lookup zone is housed in the root of the DNS - i.e. - there is a DNS Forward Lookup Zone setup just for this child domain. There is also a separate lookup zone for the parent.com domain. Shouldn't the child domain zone be listed under the parent.com domain zone? Does it make a difference? 3. There are a number of websites hosted in the DMZ, so there are a number of Forward Lookup Zones. If I move the DHCP scope to point to the child DNS servers, should I then move these website zones to the child DNS servers to ensure the best possible performance? Thanks for any help with this long-winded question! List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
