<div>
Forced accept.<br />
<br />
Computer101<br />
EE Admin
</div>


<div>
<div class="content wysiwyg-content">
I have three Windows Server 2003 that are domain controllers with active directory, only two of them have DNS service running.<br />
I started to experience replication problems when on of the network cards failed, and we did not replace it.<br />
<br />
I have tracked the problem to the following.<br />
when done a nslookup in DC1 about the name of DC3 he points to the damaged network card<br />
How can I fix it, when looking at the records in the DNS it displays everything as it should be, I already flushed the DNS of all the DCs.<br />
<br />
Any ideas on how to track the correct registry in the DNS?
</div>
</div>


I have three Windows Server 2003 that are domain controllers with active directory, only two of them have DNS service running.
I started to experience replication problems when on of the network cards failed, and we did not replace it.

I have tracked the problem to the following.
when done a nslookup in DC1 about the name of DC3 he points to the damaged network card
How can I fix it, when looking at the records in the DNS it displays everything as it should be, I already flushed the DNS of all the DCs.

Any ideas on how to track the correct registry in the DNS?

Changing a DNS record that cannot be found.

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).