Migrating whole domain to another IP scope
We are planning migration process to new network structure (from collapsed-core to building blocks) and every server is going to have new ip address.
I am worrying little bit about moving domain controllers. Easiest way would be probably to make new scope as new site and move one by one over, but we need to do whole project as cut off, so everything should be moved to new IP addressing at once.
We have few hours acceptable downtime, but is there anything special I should know in changing IP addresses on domain controllers?
We have 2 domain controllers in 10.10.0.0/24 and will be moved to 10.32.0.0/13.
I'll be thankful for any useful advice.
Who is Participating?
Experts Exchange Solution brought to you by
"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.
Make sure DNS is set to listen on all addresses.
Make sure IP configuration gets set correctly.
Make sure all domain members are able to reach the servers to resolve DNS. (Change IP configuration on machines with static addresses, change DHCP scope options and make sure machines get the new options, make sure any firewalls will allow DNS traffic, etc.)
Experts Exchange Solution brought to you by
Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.
Start your 7-day free trialIt's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
From novice to tech pro — start learning today.
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.
Experts Exchange Solution brought to you by
you should update each other's record since it won't know that each other changed
for example, ServerA will show the old IP of ServerB so you need to update ServerB's address in ServerA DNS else it won't know ServerB changed its address. Same thing the other way with ServerB's DNS record of ServerA. if you don't update those records, they won't find each other and replication will fail.
also make sure to update sites and services so that the site has the new subnet