There is no native way to work around this in Windows. You can uncheck register this connection in DNS on the properties of the "external" NIC on that DC and that will solve this to an extent. I'm unclear why you need two NICs though - are the networks not routed?
Thanks, Brian Desmond [email protected] c - 312.731.3132 Active Directory, 4th Ed - http://www.briandesmond.com/ad4/ Microsoft MVP - https://mvp.support.microsoft.com/profile/Brian From: Cameron Cooper [mailto:[email protected]] Sent: Wednesday, March 11, 2009 1:01 PM To: NT System Admin Issues Subject: DNS Would like some help in resolving this... we have two different sites, our main office and our datacenter. We currently have a leased Point-2-Point T1 running from the datacenter to our main office. There is a DNS and DC at each of the sites, and the DC at our main office holds all of the FSMO roles. The DC and all other servers at the datacenter have two different NICs in them and two different subnets... ie 11.x and 10.x The DC at our main office has two NICS, one enabled and the other disabled. The DC at the datacenter has DNS setup on both NICs. When we try to resolve the IP of the DC at the datacenter from the DC at our main office, the IP that shows up is the external IP and not the internal IP. Which in turn is causing FRS and replication issues between the two sites. I'm trying to find a way to only show the internal IPs, of our datacenter, in DNS at our main office. Both DCs are Windows Server 2003 R2. The one at the datacenter is also our Exchange server (I know, you shouldn't run exchange on a DC) and is 32bit. The DC at our main site is 64bit. _______________________________ Cameron Cooper IT Director - CompTIA A+ Certified Aurico Reports, Inc Phone: 847-890-4021 Fax: 847-255-1896 [email protected]<mailto:[email protected]> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
