regsamp
asked on
Moving from a Windows 2003 DNS server to a Windows 2012 R2 DNS server
We have an old Windows 2003 server that acts as a secondary DNS and Global Catalog server. It is quie old and we have a new server with Windows 2012 R2 installed that we would like to be the new secondary DNS and Global Catalog server. We are trying to get the best steps on how to do this.
For example do we have promo the 2003 server down first and then add the 2012 server with the new features or will adding the 2012 with DNS first and then promoting the 2003 server down after this cause issues? Any assistance offered would be greatly appreciated.
For example do we have promo the 2003 server down first and then add the 2012 server with the new features or will adding the 2012 with DNS first and then promoting the 2003 server down after this cause issues? Any assistance offered would be greatly appreciated.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
After remove the Secondary DNS server clean all the metadata related with that DC, then you can follow my suggestion if you want.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
So the three DNS servers on a small one domain network for a few hours won't hurt anything and you think the last steps I quoted here are mainly for saving time so that the machines don't have to be manually changed to a new secondary DNS IP ?
" Add the IP of the old DC to the new 2012 DC (as a second IP, not a second NIC but a second IP)
- Allow DNS entries to update (ensure that you see 3 DNS IP's using nslookup domain.com)
- Remove the new IP address from the 2012 DC (leaving only the old 2003 IP on 2012 DNS server)
- Once the originaly IP has been removed use nslookup domain.com to ensure that only the 2 IP's are listed (original IP's)"
" Add the IP of the old DC to the new 2012 DC (as a second IP, not a second NIC but a second IP)
- Allow DNS entries to update (ensure that you see 3 DNS IP's using nslookup domain.com)
- Remove the new IP address from the 2012 DC (leaving only the old 2003 IP on 2012 DNS server)
- Once the originaly IP has been removed use nslookup domain.com to ensure that only the 2 IP's are listed (original IP's)"
That is correct. Really, if you wanted to use a new IP and all of your clients use dhcp just change the scope DNS options to add the new IP and remove the old one. Then clear the leases which will force the users to pull another lease.
Either way is safe. Having a 3rd DNS server really does nothing unless you are pointing to it for DNS.
If you are going to use the new IP you will need to update any staicly assinged DNS enteries i.e. servers etc.
Will.
Either way is safe. Having a 3rd DNS server really does nothing unless you are pointing to it for DNS.
If you are going to use the new IP you will need to update any staicly assinged DNS enteries i.e. servers etc.
Will.
ASKER
Okay, let me look into possibly going that route or even just manually changing things if the list is not to large to avoid any conflicts.
ASKER