Resolve AD Server IP Problem
Posted on 2010-11-17
I have four DCs in my environment which is running Windows Server 2003. And each machine have two NICs, the first one for production (ie. 10.52.x.x) the second one is running on a Giga Network for running backup. (ie. 192.168.0.x).
Unfortunately, the DNS record will automatically add 192.168.0.x on it. Therefore, the client will resolve an 192.168.0.x instead of 10.52.x.x . This make an serious problem when the logon script mounting using the UNC path. For example, \\dc1\share.
Is there any method to avoid this happens again? I have tried manually delete the A record in DNS server, but it will automatically generate it later. Thanks.