• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1017
  • Last Modified:

Bare metal restore of 2008r2 AD and DNS broke

I had a server crash and I did a bare metal restore of the VM.  It was my primary DC and DNS.  Now it keeps failing with error

2092 "This server is the owner of the following FSMO role, but does not consider it valid."

error 2087 "Active Directory could not resolve the following DNS host name of the source domain controller to an IP address. This error prevents additions, deletions and changes in Active Directory from replicating between one or more domain controllers in the forest. Security groups, group policy, users and computers and their passwords will be inconsistent between domain controllers until this error is resolved, potentially affecting logon authentication and access to network resources.
"


How do I fix the AD and DNS from messing up again?  How do I make it think its ok?
0
Mark_c
Asked:
Mark_c
  • 2
1 Solution
 
Mike KlineCommented:
Did you have other DCs?   How did you do a bare metal restore on the VM?

If you have other DCs you can seize the roles to that one, cleanup the dead DC and then promote another one.

Thanks

Mike
0
 
Mark_cAuthor Commented:
The other DC running would keep killing it, I turned it off when the restore become live.  I used a Veeam backup of the DC.
0
 
SandeshdubeySenior Server EngineerCommented:
Checked the DNS setting on the Server it should point to itself.If the public ip address is added in the NIC DNS setting remove the same and add to DNS forwarders if required.If 127.0.0.1 is entered as dns remove the same and add ip address.

Chech NIC binding the Nic which is online and has ip details should be in first order.If multiple NIC are present then disabled the unrequired NIC.

Disabled the firewall, update the NIC driver if it is not updated,many time the NIC driver is outdated if you perform BMR with third party solution.

Make sure the system time on both DC are sync.Check AD sites and services, make sure no dead or non-exsiting DC.

I have also seen many cases if you perform the BMR by third party soultion the server goes in USN rollback state.Check the event log in Directory service for event id 2095 if has occured then you need to demote and promote the DC followed by metadata cleanup.Also if the server is FSMO role holder you need to seize the role on other server.

Please post the dcdiag /q and repadmin /replsum log to analyse further of both DC.
0
 
Mark_cAuthor Commented:
I just rebult them
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Python 3 Fundamentals

This course will teach participants about installing and configuring Python, syntax, importing, statements, types, strings, booleans, files, lists, tuples, comprehensions, functions, and classes.

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