Changing the IP of A DC.

Technical Information
Technical Information used Ask the Experts™
on
I'm going to be giving a domain controller a new IP address.  what else do I need to change IP wise on the DC apart from the NIC Ip
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Top Rated Freelancer on MS Technologies
Awarded 2018
Distinguished Expert 2018
Commented:
Well, basically everything.

Internal DNS
DHCP
Wait for the DHCP to issue new IPs.
Old IPs "leased address" will be inaccessible to any resource since DNS will be "off" (because of the change).
That would be a mess...

But there are always ways to do it without Breaking your whole network.


step1. Instead of removing the old and adding the new...
Add another IP into the NIC (advanced properties, IP Settings Tab)
Add additional ip to NIC
2 Do the changes on DNS, DHCP an all other services... (DNS Internal, DHCP) any different IP on fixed servers that requires the "new IP" as DNS.
3 Wait until the lease time of the DHCP Expires  (7 or 10 days usually)
4 Monitor that you didn't break anything and double-checked the changes (during the all 7 to 10 days)... and
5 then you can remove the "old IP" safely without breaking anything
Thanks for the fast reply.


If I run ipconfig /flushdns wont the clear the DNS cache? ipconfig /registerdns will then register the new DNS.

with DHCP if I just amend scope and router address.

That should be OK right?
Jose Gabriel Ortega CastroTop Rated Freelancer on MS Technologies
Awarded 2018
Distinguished Expert 2018

Commented:
in a Domain infrastructure, the DHCP DNS should be your domain controllers. (best practice)

Please do not use 8.8.8.8 and 8.8.4.4 as your DNS in your network :) google doesn't know a thing about your internal servers.

So
Client Computer  Gets IP from DHCP and DNS should be the 192.168.0.1 for example, then you want to change it for 192.168.0.254.
you need to tell the client's computers that your new DNS would be 192.168.0.254 instead of 192.168.0.1 and send the traffic to 8.8.8.8 or 8.8.4.4 as "forwarder" and of course, allow port 53 accessible from the internal network to external so this "query forward" will take place.

If you run ipconfig /flushdns It will clear the DNS cache of the computer your run that ... but i won't update the IP on the NICs network wide :)
Acronis in Gartner 2019 MQ for datacenter backup

It is an honor to be featured in Gartner 2019 Magic Quadrant for Datacenter Backup and Recovery Solutions. Gartner’s MQ sets a high standard and earning a place on their grid is a great affirmation that Acronis is delivering on our mission to protect all data, apps, and systems.

apologies but you didn't provide an answer to my comment. I'm not going to use Google's DNS servers. Where moving office and the in house IT will be providing the DNS servers.
Jose Gabriel Ortega CastroTop Rated Freelancer on MS Technologies
Awarded 2018
Distinguished Expert 2018

Commented:
If I run ipconfig /flushdns wont the clear the DNS cache? ipconfig /registerdns will then register the new DNS.

ipconfig /flushdns => Clear the DNS CACHE on the computers (yes)
Ipconfig /registerdns => Will register the new IP into the DNS  (the way is CLIENT TO SERVER, not SERVER TO CLIENT)

Open in new window


with the DHCP change, you make sure that "SERVER TO CLIENT" is refreshed.

and if you want a new IP you'd have to run
ipconfig /release
ipconfig /renew

Open in new window


network-wide on each computer to get the new IP (on DNS)
and what I said related to the Googles DNS is that a lot of people use them internally like crazy.
OK great, thanks for your help
Jose Gabriel Ortega CastroTop Rated Freelancer on MS Technologies
Awarded 2018
Distinguished Expert 2018

Commented:
Well, the DNS servers on a domain environment should be the domain controllers and use external IPs DNS (like google) as forwarders.
You shouldn't use internal DNS as forwarders because it will break the flow to internet

Flow using an external DNS as the forwarder

The client computer asks Domain Controller if DC doesn't have the registry ask to external DNSs, get the answers and answers all the way back until the client's computer.

Flow using a DC DNS as the forwarder
The client computer asks Domain Controler if DC doesn't have the registry asked it will forward the query to the other DC or "ask to himself in an infinitive loop" and it won't work :)
"with the DHCP change, you make sure that "SERVER TO CLIENT" is refreshed."

How do I go about doing that? Just go into DNS and delete all the entries?

Do I need to change the IP address in DNS for the server? Or will it do it automatically?
Jose Gabriel Ortega CastroTop Rated Freelancer on MS Technologies
Awarded 2018
Distinguished Expert 2018

Commented:
How do I go about doing that? Just go into DNS and delete all the entries?
That's is not an option, you update DNS on the DHCP scope Options, not on the DNSs, the cons of that is that you will lose all connectivity with the network for a little time, (it could be done after hours, so you don't impact anybody), generally on the servers to have "manual" ip you'd need to go one by one updating to the new IP.

What I'd do is just to change the "DNS Settings" on the "Options of the scope" and wait 7 days", to monitor it and see that all will work flawlessly and without interruptions, if you want to do it immediately, you can do the change on the Options of the scope and then remove all entries on the DHCP leased IPs.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial