Windows 2003 DNS migrate current DNS zones to Windows 2012 R2 DNS and set as secondary.
Made the ultimate mistake and left our primary AD sitting alone until yes, it failed. Now have recovered the AD server and stood up a 2012 R2 server and want to make it a secondary DNS and was wondering the quick and easiest way to do this. From what I read, when I brought the secondary up I thought it would see the Primary, but did not.
I have the server up in the current domain, IP set and DNS installed. Obviously nothing in DNS. I want migrate zones over from 2003 server, set it as secondary and test. Can someone help?
Regards
I have the server up in the current domain, IP set and DNS installed. Obviously nothing in DNS. I want migrate zones over from 2003 server, set it as secondary and test. Can someone help?
Regards
Robin CM
Is it AD integrated DNS? Is the new 2012 R2 server a DC?
ASKER
@robincm, meaning MS, yes. A DC at the moment no, that's what made me think why it was not seeing my current AD/DNS server.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
any particular choices I should make for secondary or other settings?
Depending on how you look at it, there is no such thing as a secondary DNS server. it's just a DNS server that replicates with your other DNS server.
ASKER
Just didn't know how it would gather info, since I'm getting, "A delegation for this DNS server cannot be created because the authoritative parent zone cannot be found ot it does not run Windows DNS server....etc" thought this meant it didn't see the current DNS.
ASKER
How do the zones populate? Automatically? Does it take time? I've got crazy connection problems to Exchange is why I'm adding and asking.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
thanks for your help!!
ASKER
robincm: can this second AD corrupt my current AD and Exchange?
You're not creating a second AD, just adding a second AD Domain Controller to your existing AD. That'll give you resilience in your existing AD and machines will talk to either of the two DCs (though check out FSMO roles that you have to relocate should you want to get rid of your original DC).