?
Solved

Moving from a Windows 2003 DNS server to a Windows 2012 R2 DNS server

Posted on 2015-01-06
7
Medium Priority
?
310 Views
Last Modified: 2015-01-07
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.
0
Comment
Question by:regsamp
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
  • 2
7 Comments
 
LVL 12

Accepted Solution

by:
David Paris Vicente earned 1000 total points
ID: 40533934
If I were you first of all choose the primary DNS server to act as a Global Catalog, then depromote the secondary DNS server from the domain.

Now for the windows 2k12 I used the Old IP of the secondary and promote this one to a DC with the  integrated DNS role, by this way and recicling the old secondary DNS server you don't need to modify the secondary dns server in all your clients manualy or by other means.

This is just a suggestion.

Hope it helps.

Regards
0
 

Author Comment

by:regsamp
ID: 40534042
Okay, let me think about doing it that way. I would just want to avoid any issues with using the old IP on the 2012 server.
0
 
LVL 12

Expert Comment

by:David Paris Vicente
ID: 40534059
After remove the Secondary DNS server clean all the metadata related with that DC, then you can follow my suggestion if you want.
0
Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

 
LVL 53

Assisted Solution

by:Will Szymkowski
Will Szymkowski earned 1000 total points
ID: 40534165
I would personally do the following...
- promote the 2012 DC into the environment (give it a new IP)
- setup the DNS GC etc
- ensure that replication is working accordingly (to all DC's in the environment)
- demote the 2003 DC (secondary)
- Once the DC has been successfully demoted, Power off the old 2003 DC
- 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)

Will.
0
 

Author Comment

by:regsamp
ID: 40534244
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)"
0
 
LVL 53

Expert Comment

by:Will Szymkowski
ID: 40534584
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.
0
 

Author Comment

by:regsamp
ID: 40534865
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.
0

Featured Post

Get 15 Days FREE Full-Featured Trial

Benefit from a mission critical IT monitoring with Monitis Premium or get it FREE for your entry level monitoring needs.
-Over 200,000 users
-More than 300,000 websites monitored
-Used in 197 countries
-Recommended by 98% of users

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article demonstrates probably the easiest way to configure domain-wide tier isolation within Active Directory. If you do not know tier isolation read https://technet.microsoft.com/en-us/windows-server-docs/security/securing-privileged-access/s…
Had a business requirement to store the mobile number in an environmental variable. This is just a quick article on how this was done.
In this Micro Tutorial viewers will learn how to restore single file or folder from Bare Metal backup image of their system. Tutorial shows how to restore files and folders from system backup. Often it is not needed to restore entire system when onl…
Sometimes it takes a new vantage point, apart from our everyday security practices, to truly see our Active Directory (AD) vulnerabilities. We get used to implementing the same techniques and checking the same areas for a breach. This pattern can re…
Suggested Courses

770 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question