Change IP on DA Legacy

[modem]

Good afternoon. My host informed me last week that by the end of the month I'll be required to change the IP on my server from what had been assigned for about 8 years to a new one.

I'm looking at a couple options and wanted to get input from everyone here.

1.) Pay for DA under the new license model and simply setup a new host and move client data over (I am on CentOS 7 and this is the last server...)

2.) Change IP on the existing DA legacy codebase as well as add the IP to CentOS7 and have it go live there. This option would buy me more time as I consider DA's new model and other control panels. But... I'm looking at possible adverse affects with this option. I do not have physical access to the server. I'm wondering how best I approach changing it's IP without losing total access to the server and all client data.

 

[Richard G]

First of all you need to have SSH access, if you got that then you're half way.
There is an option to swap ip's easily withing DA so that is not the biggest issue. Also mass change DNS records for nameserver ip's and SPF records will also not be a biggy normally.

However, be sure to ask your host if that new ip also does work on the legacy license. As internal licenses might be limited to a certain ip pool so I don't really understand why he needs to give you a new ip, but well... nothing much to do about it I guess.

But again, be sure the new ip is accepted on the current lifetime license.

 

[modem]

First of all you need to have SSH access, if you got that then you're half way.
There is an option to swap ip's easily withing DA so that is not the biggest issue. Also mass change DNS records for nameserver ip's and SPF records will also not be a biggy normally.

However, be sure to ask your host if that new ip also does work on the legacy license. As internal licenses might be limited to a certain ip pool so I don't really understand why he needs to give you a new ip, but well... nothing much to do about it I guess.

But again, be sure the new ip is accepted on the current lifetime license.

Thanks for the reply. I do have SSH access without any issue there.

I do want to pass along I was able to get the new IP connected to eth1. My initial main concern was being able to do that without losing permanent connectivity to the remote server. Thankfully WebMin made that part easy on ensuring the network interface was working properly.

DA support did give me info on the ip update script which ran and after Name Servers were updated for those needing it at registrars, it appears everything is working at the moment. Just looking for post update tweaks.

 

[modem]

Just as a followup, while websites are working on the new IP, I've discovered an issue that may be related to IONOS hosting, or may not be. I'm really unsure. Anyway, the reason for the IP change is IONOS is mandating it. They stated as of Feb 26th the old IP would expire and the new IP would automatically take affect via DHCP (reservation). Obviously to prevent this from seriously messing up and possibly permanently disconnecting me, I decided to get it taken care of in advance.

So I initially setup a secondary interface (eth1) to DHCP but it never picked up the new IP. I ended up configuring a new eth1 interface and statically assigning it. The new IP pings just fine, I can SSH into the server with it, so I went ahead and started getting name servers and related DNS items changed to the new IP. All of that was successful.

When I ran ifconfig (see below) it showed eth1 with the new IP didn't have any receiving or transmitting traffic crossing that interface. Rather it appears all traffic is crossing the old interface of eth0.

Now, this is where I'm confused. Have I misconfigured something on CentOS.... OR.... with IONOS's virtual machine setup, do they only recognize eth0 on their bare metal / hypervisor side? I can only have a theory that come the 26th when the old IP is released and the new one is supposed to be DHCP assigned, it would do that on the eth0 interface?

If so, since I have my eth1 interface already configured with the new IP that could potentially create a conflict and take me offline. With that thinking, I set eth1 to NOT start a boot, even though it's up now. **IF** this theory is correct then when eth0 picks up the new IP and if I lose access to the server due to a conflict, I can reboot the server via the IONOS control panel which should take eth1 offline and keep eth0 online.

That's only a theory. I simply don't want to lose access to the server with the few amount of client sites I have (and my own email at the moment). I only share this because I'm unsure if I have a genuine misconfiguration or if IONOS does it way differently.


eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet <OLD IP> netmask 255.255.255.255 broadcast <OLD BROADCAST>
inet6 2607:f1c0:833:5400::64:c016 prefixlen 64 scopeid 0x0<global>
inet6 fe80::529a:4cff:fe73:fbc2 prefixlen 64 scopeid 0x20<link>
ether 50:9a:4c:73:fb:c2 txqueuelen 1000 (Ethernet)
RX packets 20663 bytes 2366479 (2.2 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 34746 bytes 15289221 (14.5 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 16

eth1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet <NEW IP> netmask 255.255.255.0 broadcast <NEW BROADCAST>
ether 50:9a:4c:73:fb:c3 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 17

 

[Richard G]

do they only recognize eth0 on their bare metal / hypervisor side?

Thanks for the explanation about the requirement to change the ip.

An ip reservation in DHCP is mostly done on MAC address, so that is almost certainly the reason that the ip is not given out automatically to your eth1.
When I compare both then I see that eth1 ends on c3 while eth0 ends on c2 so that is a difference there.

This is not part of a DA functionality. DA just looks on which ip it has to run, can be configured in the directadmin.conf file.

So most likely if you would set eth0 to dhcp it should get the new ip, however, eth1 should not be active then otherwise you would indeed have an ip conflict.
You have to keep that in mind if you don't want to loose access.

Best is to talk to IONOS support about this or if they would be prepared to change their dhcp reservation to your eth1 or if you just can set your eht0 to dhcp and disable eth1.