1

Hi all hope all is well.
I have a issue with my network. My primary DC went down. I seize all the FSMO roles to the secondary DC, but client PCs are not resolving DNS name. My secondary DC is configured as a DNS server and is also doing DHCP. Client PCs received IP address and DNS settings. Client PCs cannot access resources on my network. I have troubleshoot all DNS issue but problem still the same. I notice that my secondary still points to my primary DC.

Any help regarding my issue will be appreciated.

Thanks.

Eric

5 Spice ups
2

If the second DC is the only DNS server on the domain, you need to change its DNS IP to point to itself for the time being.

After you have done that, run dcdiag from a command prompt or PowerShell on the DC and identify errors if any.

3 Spice ups
3

As above check the clients are using the new DC for DNS

1 Spice up
4

As InkMaster noted, make sure the second DC has itself as the primary DNS server. Also check your DNS zone and get rid of any/all entries for the failed DC. Also make sure your DHCP Options on the second DC do not still have any entries for the failed DC.

After checking those things, be sure to do a flushdns on workstations and release/renew their DHCP leases

5

Thanks for your point.

I ran the dcdiag command. please find attached the error I receive

DCDiag_Error.txt (11.5 KB)