Preparing to migrate server to new POP, with IP change while also using external DNS cluster?

[InTheWoods]

In the coming week or so we need to migrate from a location that is closing to our own infrastructure located elsewhere. This move will unfortunately require IP renumbering.

The good news is, we containerize our DA servers so if needing to migrate to different hardware, etc it's much simpler to migrate the VM. This part isn't a problem or a concern. That's the easy part, moving the data.

Once the migration completes, and the VM that was once located at IP 1.2.3.4 is now at IP 4.5.6.7, what steps do I need to perform within to minimize downtime to the customers? Additionally, we have separate DA servers for NS1 and another one for NS2, which I believe is worth a mention since it may be considered a non-standard (but supported) setup.

Thank you.

 

[Active8]

Once the migration completes, and the VM that was once located at IP 1.2.3.4 is now at IP 4.5.6.7, what steps do I need to perform within to minimize downtime to the customers?

Ip swap ?

cd /usr/local/directadmin/scripts
./ipswap.sh 1.1.1.1 2.2.2.2  # ./ipswap.sh old_ip new_ip

Restart all services for the changes to take effect:
systemctl restart

 

[Richard G]

You might need to update the SPF records with the new ip too. Probably with a perl -pi command or something like that.
Because as far as I know the ipswap script does not cover that.

 

[InTheWoods]

Ip swap ?

cd /usr/local/directadmin/scripts
./ipswap.sh 1.1.1.1 2.2.2.2  # ./ipswap.sh old_ip new_ip

Restart all services for the changes to take effect:
systemctl restart

Just to confirm, this needs to be completed only on the server that is being migrated or also on each of the NS servers in the multi-server setup for DNS?

 

[Richard G]

or also on each of the NS servers in the multi-server setup for DNS?

After migration also on the multi server NS servers. However, it could cause odd issues if you keep them running during migration. I would disable multi-server DNS connections before migration on the old server first.

And right after migration and changing the ip's to new ip's, then use the DNS command to update the multi-server setup command on each migrated server:
echo "action=rewrite&value=named" >> /usr/local/directadmin/data/task.queue
this way they will get the new ip's automatically, and when ready, activate the multi-server DNS connection again.