[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 203
  • Last Modified:

Changing a DNS record that cannot be found.

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?
0
lupineres
Asked:
lupineres
1 Solution
 
mattedkCommented:
go to DC3, set the "Primary DNS Server" on the network card you are using now to "DNS Server 1"

Open a command prompt and type "Ipconfig /registerdns"
Wait some minutes, or 15.

Now change Primary DNS Server to "Dns Server 2"
Open a command prompt and type "Ipconfig /registerdns"
Wait some minutes, or 15.

Set it back to having Primary/Secondary DNS.

This will cause DC3 to update its dns records in the DNS servers.

Now try another nslookup and check if it hasnt changed to the correct _new_ ip address
0
 
Computer101Commented:
Forced accept.

Computer101
EE Admin
0

Featured Post

Important Lessons on Recovering from Petya

In their most recent webinar, Skyport Systems explores ways to isolate and protect critical databases to keep the core of your company safe from harm.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now