Hi All,
Sorry for the subject tag. Not sure how to word the subject, but here is an explanation. We have a Windows2003 domain with 3 DCs and 2 DNS servers (Active Directory Integrated). When we upgraded our network to Windows2003 years ago, the DNS settings for both servers were configured to have the DNS Suffix For This Connection from the advanced TCP/IP settings set for computer1.xxxxxxx.org (not the real name). We have since fixed this by removing this entry and now dhcp clients see the correct dns zone (up to this point they would see computer1.xxxxxx.org as the connection specific dns suffix). I know DNS is working. I ran some dcdiag commands to confirm all tests passed. So, all appears to be good, but there is one weird folder inside the zone that appears to be not normal and i'm not sure exactly how this folder got placed here, but i'm guessing this has something to do with the way our DNS servers were initially configured. The folder I see is computer1. This folder has several (A) records with ip addresses pointing to computername.computer1.xxxxx.org. I'm not sure if I need to delete these records manually and let the client release/renew (we have our DHCP scope lease times set for 1 minute for a few days so our DHCP clients will renew their ip address) and this will recreate the record in the correct zone xxxxxxxx.org? Here is what our zone folder records look like:
_msdcs
_sites
_tcp
_udp
computer1 (this is where i'm seeing several host records)
DomainDnsZones
ForestDnsZones
- I also have a 2nd question/issue. On the 2nd DNS server (computer2.xxxxxx.org), I should be able to point the primary ip address to itself. But, whenever I do this and I do an nslookup, I get aCan't find server for address x.x.x.x Non-existent domain. Default Server: Unknown addrss: x.x.x.x
- If I change the primary ip address to point to the ip address of computer1 then there is no issue. Any thoughts on this?
Thanks for any suggestions!
Bob