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

DNS on Server 2012

Hi there, we were migrating an old SBS 2003 box over to a 2012 Standard server. The day after the data transferred the old one burnt out so we were un able to do a proper DCPROMO to remove the old server. I have gone through the whole DNS and removed all records of the old server but it still wont work as the DNS server. No errors etc. except the active directory looking to update. NSLOOKUP says unknown. What have I missed?
0
grovenetsupport
Asked:
grovenetsupport
  • 3
  • 2
  • 2
1 Solution
 
footechCommented:
It's unclear what all has been done.
Clients need to point to the 2012 server for their DNS.  The 2012 needs to have replicated the AD info from the old server before it went away (if not you either have to restore from backup or create a whole new domain).
You may have to reconfigure DHCP to hand out correct info.
If you didn't transfer FSMO roles, they'll need to be seized on the 2012 server.
You'll need to perform a metadata cleanup of the old SBS.
Not sure where you're seeing "Unknown" in nslookup, but it's likely you just need a PTR record for the 2012 server (perhaps you need to create the zone first).
In the DNS console, look at the properties of the server > Monitoring tab > select both tests and click Test Now (I'm assuming it's the same as earlier versions). You should have root hints or forwarders configured so that internet resolution works correctly.
0
 
grovenetsupportAuthor Commented:
FSMO roles had been moved ad I have checked they are all correct one thing we have noticed is if we change the PC name and put the new server in the host file it logs onto the domain
0
 
footechCommented:
OK, well, thanks for responding with info on one of my suggestions.  I'm not going to guess about the rest.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
DrDave242Commented:
You'll need to perform a metadata cleanup of the old SBS.
This one's likely the key. The new DC is probably trying to perform initial directory synchronization after a reboot because it still thinks there's another DC in the domain, and its DNS Server service won't start for quite some time if this synchronization can't be performed.

The metadata cleanup needs to be performed to remove the old DC (the SBS 2003 server) from Active Directory. The steps required for doing so are here.
0
 
grovenetsupportAuthor Commented:
Thanks for this but this has already been done when the server failed.
0
 
DrDave242Commented:
Is the DNS Server service running on the 2012 DC? If so, are clients configured to use it as their only DNS server?

No errors etc. except the active directory looking to update.
Can you post the exact error you're seeing here?
0
 
DrDave242Commented:
Footech should get a share of the points; he did mention a metadata cleanup first.
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

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