Need help with this issue.

Had to restart the AD/DNS main box, as the hardware died, but now it seems DNS is not being picked up, I’ve run the following test and I get Del FAIL. Any ideas?

DCDIAG /TEST:DNS /v /e

437c274f-922e-4656-a126-e69dd1a03828-dns_error.png

5 Spice ups

See if this post helps. It talks about needing to do some cleanup.

I’ve already checked that link @jrp78 but thank you.

@jayparker9836

Give us some more details about how the main box died and how you rebuilt it. Did you restore from a backup or rebuild from scratch? Did the server hold your FSMO roles?

Box holding the VMs AD/DNS died.

We got an identical box, so it was only the steps of moving the disks identical to the new box, so the RAID show all the disks, so no configuration need it to do.

I can see all VMs and we can access them but for some reason when computers boot don’t seem to be able to ping to some servers by IP or name.

The DNS Server holds all the FSMO Roles.

Does the new server have all the proper static IP information configured on its NIC?

Yes

Have you looked at the event viewer logs on the DC to see if there any glaring errors in the application and/or system log?

Also, have you run a full DCDIAG for any clues?

dcdiag /e /c /v /q > c:\dcdiag.txt

HI @jayparker9836 ​,

I re-run the DCDIAG again but this time I saved it to a file, looking at the text file I noticed all my delegations were failing because it seem someone who created the DNS original it created a double delegation on the server 'mydomain.local.mydomain.local’, after finding the issue in DNS I re-run the test again and all Delegations passed. Got a few Warn and a Fail on Dyn & RReg section, I just need to g through the report again.

Thank you for your assistance.

a2cb1e66-8866-4605-b22b-6456c9e0e928-dns_error.png

2 Spice ups

Nice work :+1:

Hi, I’ve got the exact same issue. Can you be more verbose about where you found the doubled fqdn? Ive looked at every a record Ns record and srv record and I’m just not seeing it.