asked on

New DC Moving to Different Branch

Looking for some advice on the proper way to accomplish this. I have a remote branch that does not currently have a DC. I would ideally like to bring up a Server 2012 DC and DNS server at our HQ branch (different subnet) and ship the server to the remote branch. I will be placing the new DC within the "remote branch" site in AD Sites and Services when I install AD and DNS on the server at our HQ branch.

Here are my concerns:

- I will be changing the static IP of the server to reflect the remote site's subnet prior to shipping. I need to make sure that this DNS server can still communicate and replicate DNS and AD with other DC's and DNS servers on our network (6 total sites).

- I need to make sure that all DNS records are updated manually in DNS prior to bring the new server online at the remote branch. Any advise on this?

Any other concerns that I should look out for?

Thanks!

Mike Kline

When you boot the machine at the new site it will register its new IP address or you can put in the new IP and restart the netlogon service before you turn it off and box it up and it will register its new IP/SRV records in DNS.

Are you going to have a site link between HQ and this remote site?

Thanks

Mike

rbsd176

ASKER

Thanks Mike. We already have a site link configured. Long story, but this branch had a DC/DNS server that was tombstoned (already cleaned metadata, removed from DNS, etc.) and a series of unfortunate events prevented that server from communicating with other DNS servers (had to forcefully demote, couldn't reach other DNS servers because there was no DNS server at the branch). The site was due for hardware refresh anyways so we decided to move forward with a new server. I'm hoping to have it mostly configured before we ship it to the remote branch.

Mike Kline

Your plan is sound; just make sure the communication/link issues you had in the past with that site don't hit you again.

Thanks

Mike

Jaihunt

Make sure your Primary,Secondary DNS pointing to your HQ site DC. Also Move the server object to HQ site from the Remote site and check KCC is creating the connections based on the site link configuration. Monitor the replication of the server to avoid issues.

rbsd176

ASKER

Wouldn't I point DNS on a DNS server to itself?

Jaihunt

No point it to other DC so that it will advertise to other DNS by registering IP. Once everything working as expected like replication, connection object creation. you can change it to point to itself.

rbsd176

ASKER

Got it, thanks.

ASKER CERTIFIED SOLUTION

Sandesh Dubey

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial