IP Migration Guide

[Daniel]

Hello!

I am in the process of creating a document outlining the steps needed to migrate your server and related sites to the new IPs you have been assigned.

This is still in the preliminary stages (sorry for not getting this done sooner!) and will be undergoing a lot of changes in the meantime.

I would appreciate any feedback on additions that you want, or changes that need to be made.

Version History:

v0.1: Initial Public Release. cPanel section is mostly done (awaiting more suggestions on what needs to be added), along with the initial steps for Plesk and Directadmin.

v0.2: Separated Guides into control panel specific guides for easier reference. Plesk mostly completed. Awaiting comments. Still working on Directadmin which should be released shortly.

v0.3: Added the Directadmin guide to the mix.

v0.4: Added a note about changing nameservers at your registrar. Make sure to get that document as well.

[JohnQM]

Hello,

My VPS does not use any control panel. Is there a guide with all steps which has to be followed?

Thx
John

[Daniel]

Hello,

My VPS does not use any control panel. Is there a guide with all steps which has to be followed?

Thx
John
John,

Due to the number of setups you could be running the migration for yourself is really up to you. If you need some general steps for what you need to do I can put those in the document.

Hope that helps.

[ricardo]

Only as a comment

In our server we have only one control panel (in my case cPanel), it is not usefull to have a mess of diferent control panel.

[Daniel]

Only as a comment

In our server we have only one control panel (in my case cPanel), it is not usefull to have a mess of diferent control panel.
I thought about this. Once I get a good start on the other two (hopefully some time this morning), I believe I will go ahead and seperate these out to their repective control panels for easier reference for everyone.

[peersignal]

Would it be possible for a guide created for those with DirectAdmin installed?

[Daniel]

Of course! I was trying to get the Directadmin one done today, however things got really busy so I couldn't get to it. I will hopefully have it up tomorrow.

[Daniel]

peersignal,

This has been added now :D

[Fred]

thanks for this guide.

I did check the cpanel one and it's great.

[dexus]

I did everithing according to this manual for cPanel, and after DNS propagation, I went again to IP Migration page to complete migration, and after I clicked to "Complete Migration", it fixed httpd.conf, and succesefully restarted it, but that is not all, like it should be done according to manual...

There is another step left, that is not mentioned in the manual...


Ip Migration is complete! To complete the change-over to the new ip addresses, you will need to:

* Remove the old ips from this system.
* Update your system startup scripts reflect the new main ip address. On redhat system, this can be generally by done by editing /etc/sysconfig/network-scripts/ifcfg-eth0. On FreeBSD system this can be done by editing /etc/rc.conf.
* After the main ip address has been changed, you will need to to change the Main Shared Virtual Host Ip in the Server Setup.
* If you have set a different main ip for your resllers, you will need to change them in the Reseller Center.


After completing the above, please click here to finish the change-over


What about this?

- How should I remove IP's, when I go to page "WHM > Show or Delete Current IP Addresses" it just give me a list of IP's, and I can't delete them
- We changed main shared IP at the begining, so that should be fine
- I don't think we should change "ifcfg" files, because we did that at the begining of the manual at little bit different way.
- I don't have resellers on that VPS so I don't care about this part

So what should that last step do, and can I click to continue on this last step without removing old IP's?

[Atomm]

Daniel,

How about adding a guide to changing your name servers with little to no impact to propagation?

TTL is your friend..... :)

[dexus]

That is mentioned in the guide, but that is not realy important, because there will be no down time anyway, so speed of propagation is irrelevant.

[Daniel]

dexus,

Send a ticket into support when you are ready remove the IPs. We'll remove them which will fix all networking related files. At that point you can just rebuild the IP Pool and those IPs should not be there. Make sure that all of your accounts are off the old IPs before doing this.

Hope that helps!

[Daniel]

Atomm,

Propagation really should not matter in this case. You have the IPs still routing to your servers, so whether or not the TTL is set to 5 minutes or a week does not matter. You can keep your IPs until December 1st, which is well enough time to have them propagate. As long as you don't remove those old IPs before propagation is complete, your nameservers should still respond. There may be small tiny issues because of this not being like this, however it should not cause your sites to go down.

I didn't see this as a needed step personally, unless you wait until the last day or two.

[dexus]

Ok, I understand that, but should I click this link on the last step, or just ignore that.

This link that I should click should run:
https://myserver:2087/scripts2/ipmigrate9

So should I click this and then contact support or just ignore this and contact support?

Thanks

[Daniel]

Sorry!

Send in a ticket and get those IPs removed (make sure we get the cPanel license changed over too), then click that button to finish it up.

[Daniel]

I have added a new attachment in regards to some tickets that have come in as of late. This is a very initial guide detailing what needs to be done at your registrar. Be sure to grab this if you haven't updated your nameservers at your registrar yet.

Please contribute as well!

[StingRay]

My experience so far.

I'm using Cpanel.

0. Update name server at registrar, done .... ding ding ding, oops my hyperspin alert goes off, should have shut that off first. VPS support kindly emails me and says nothing is wrong. Which is correct.... for the moment... however had this been an unintentional DNS failure, we would have had a DNS propagation flame out and no one listening to the SOS.

1. Rebuild IP pool, no problem

2. Edit DNS, needs to be more specific, which DNS zone? It seems obvious to me that it aught to be the domain you use as the main domain on the server, but clarity would probably help. Maybe adding into that sentence that it is the nameserver domain zone file you are to edit.

3. Networking Setup -> Nameserver Ips.
Ok this annoyed me, I think the guide needs to be clearer that you need to WAIT for cpanel to grab the updated whois data before you can change this. I went and changed my nameserver with the registrar then thought I could proceed with the rest of the guide, not realizing Cpanel doesn't seem to grab un-cached data. I asked support if there was a way to make cpanel behave but if there is, they are being quiet about it.

4. Change main IP, no problem. But what is going on with the "You will need to change the main ethernet device", first ifconfig wasn't in my path, had to "locate" it first :(
Then I'm wondering why on earth I have to change this and to what? It wasn't until I had a very close look that i spotted, way down the list, the new IP's and that they were on venet0:6 and 7 and CPanel still said venet0:0

I've never had to change this so I makes me nervous. :eek:


5. reseller IPs - Luckily they are all ok, I can skip this bit.

6. Ip Migration Wiz. After putting in the two new ip's it lists every domain on the server! How to proceed with changing JUST the domains that are attached to the bad ips? No idea. I forge ahead by deleting the new ip from those enties, leaving them blank. Hit continue .. warning about it can't be reversed blah blah, I'm scared, click continue.

"Merging httpd.conf ....Warning: cannot migrate ip address [*.*.*.*]" etc etc
Oh great, those are the ips to the domains i didn't want changed...
Ahh apache is restarting... and it restarted ok, but now no websites work. doh!

Oh wait.. a continue button.. ok, click.
"Migration has been completed.. hooray, but do my web sites come up? No such luck.

Time to call support :(


Aha support found that is messed up one number of my IP's used a 0 instead of a 4 etc.
So easy enough to fix at the registrar, but i have already done a IP migration with the Wrong Ip. I think i'm up the creek...

[Daniel]

Hi Stingray,

Thanks for your comments! Sorry for the late reply, been a busy week thus far:


2. Edit DNS, needs to be more specific, which DNS zone? It seems obvious to me that it aught to be the domain you use as the main domain on the server, but clarity would probably help. Maybe adding into that sentence that it is the nameserver domain zone file you are to edit.


I had thought that I put this in there, but I guess I did not. Thanks for catching this!


3. Networking Setup -> Nameserver Ips.
Ok this annoyed me, I think the guide needs to be clearer that you need to WAIT for cpanel to grab the updated whois data before you can change this. I went and changed my nameserver with the registrar then thought I could proceed with the rest of the guide, not realizing Cpanel doesn't seem to grab un-cached data. I asked support if there was a way to make cpanel behave but if there is, they are being quiet about it.


You can go into Tweak Settings and tell cPanel to not use the WHOIS data when doing this so you can remove them. I thought I had added this as well, but again I guess I missed this. Again, thanks for the catch.


Then I'm wondering why on earth I have to change this and to what? It wasn't until I had a very close look that i spotted, way down the list, the new IP's and that they were on venet0:6 and 7 and CPanel still said venet0:0


Agreed, I need to clarify this a bit. WHM checks your ethernet device to make sure it matches up with your "Main Shared IP Address." If these don't match, it can cause the dreadful "IP Problem!" email at midnight.


So easy enough to fix at the registrar, but i have already done a IP migration with the Wrong Ip. I think i'm up the creek...

I hope the techs got you all good to go now.

I'll be looking at this and hopefully will push out another revision today or tomorrow.

[StingRay]

Techs, umm not entirely helpful, but that does allow me to learn more.

The IP migration wizard does two things that I am aware of.
1. Adds a second IP to your httpd.conf virtual host areas, for each domain affected.
2. Changes the DNS zone file for each affected domain.

So to fix my mistake I had to:
1. go into httpd.conf and do a find and replace to fix the IPs.
2. Edit each zone file manually via WHM... or go in through terminal and edit them there, which could be faster if I had a script to do it, ie using sed and grep, however I'm not familiar enough with those programs to write the script myself.

If editing each zone file in the terminal , you need to at some point restart bind to make it all take effect. WHM reloads/restarts automatically after each edit.


I have completed my migration, I clicked on the migration wizard and it removed the old ip's from httpd.conf

I haven't told support yet to remove the old IP's yet though because I want to wait until the weekend in case anything else goes wrong.



Oh also, regarding the Nameserver IPs not showing up right away, I wonder if that was because I had put in the wrong IP at the registrar and once the correct one was in it showed up.. right away. I'm not certain at this point, but that could have been the case.

[Atomm]

I guess I am a bit confused. Can you clarify?

About 75% of my websites are on the old IP's.

Let's say I change my Nameservers at my Registrar and change the IP's for the sites on the old IP's to the new IP's.

Now, a Cached DNS server out in the wild would point a request to the old DNS and old IP's, which my DNS and Sites are no longer on. Sure, the IP's are still on my box, but DNS and Apache think the sites are on the new IP's.

Wouldn't this cause the requested page to fail until propagation has updated the remote DNS server?

-----

While typing this, I decided it would be better if I RTFG.... :-)

Right there on the guide it states:

change the TTL from 14400 (default) to something like 900. This will speed up the time nameservers around the world will remove their cached result and update their cache.

However, this should be put in as the first step along with instructions to wait 48 hours before continuing. (I know 14400 = 4 Hours, but you know how these things work) If you have already changed your NS and IP's before changing the TTL, it does no good as a cached DNS server doesn't know to check back quicker anyway.

I know I'm being picky, but I run PPC to some of my sites and 4+ hours of downtime due to cached DNS records can cost me money.

[Daniel]

Atomm,

Nothing should fail as long as you keep your old IPs until propagation is finished.

Keep in mind that although cached DNS records may keep pointing people to your old nameserver IPs, the DNS requests are still coming to your server. That is all that matters. Just because your nameservers are on old IPs does not mean that the old IP will be given for your site.

I hope that makes sense. The reason that you wantto use the IP Migration Manager is so that your sites are able to be viewed on two IPs, both the old AND new IPs, until propagation is complete.

Does that make sense?

[daniel522]

I have a plan RESELLER PLESK and use these DNS:

ns1.pvpsplesk.com, A, 204.157.9.195
ns2.pvpsplesk.com, A, 204.157.9.196


I must do something for the change of IPs that you announced?


thank´s,

Daniel

[Fred]

Hi,

Just to be sure:
When using the ip migration wizards: I change the old ip to the new one.
BUT: does the old IP continue to be in the httpd.conf during the 48hours period ??

Thanks for your infos :)
Fred

[Fred]

Another question:

What will happen with:
nameserver 204.157.6.3

In my resolv.conf.

Also, i noted that rwhois.defenderhosting.com doesn't work.
root@X [~]# whois 74.200.X.X
[Querying whois.arin.net]
[Redirected to rwhois.defenderhosting.com:4321]
[Querying rwhois.defenderhosting.com]
[Unable to connect to remote host]
root@X [~]#

[Daniel]

I have a plan RESELLER PLESK and use these DNS:

ns1.pvpsplesk.com, A, 204.157.9.195
ns2.pvpsplesk.com, A, 204.157.9.196


I must do something for the change of IPs that you announced?


thank´s,

Daniel
Hello,

Since you're using our nameservers, you shouldn't need to worry about anything. We will add your new IPs to your account (if you haven't gotten them already for some reason), and you'll need to change your site's IPs from Plesk.

Hope that helps!

[Daniel]

Hi,

Just to be sure:
When using the ip migration wizards: I change the old ip to the new one.
BUT: does the old IP continue to be in the httpd.conf during the 48hours period ??

Thanks for your infos :)
Fred
That would be correct. It lets you access the site on both IPs until you tell it that the DNS is done propagating, then it takes the old IP off of httpd.conf for that domain.

[Daniel]

Another question:

What will happen with:
nameserver 204.157.6.3

In my resolv.conf.

Also, i noted that rwhois.defenderhosting.com doesn't work.
root@X [~]# whois 74.200.X.X
[Querying whois.arin.net]
[Redirected to rwhois.defenderhosting.com:4321]
[Querying rwhois.defenderhosting.com]
[Unable to connect to remote host]
root@X [~]#
Replace that IP with 205.234.103.204.

Regarding the rwhois server, I'll look into this and let you know shortly.

[Daniel]

Another question:

What will happen with:
nameserver 204.157.6.3

In my resolv.conf.

Also, i noted that rwhois.defenderhosting.com doesn't work.
root@X [~]# whois 74.200.X.X
[Querying whois.arin.net]
[Redirected to rwhois.defenderhosting.com:4321]
[Querying rwhois.defenderhosting.com]
[Unable to connect to remote host]
root@X [~]#
Fred,

Can you try the whois again? Things seem to be working fine here. Using an external server:

[root@X:~]# whois 74.200.80.3
[Querying whois.arin.net]
[Redirected to rwhois.defenderhosting.com:4321]
[Querying rwhois.defenderhosting.com]
[rwhois.defenderhosting.com]
%rwhois V-1.5:0010b4:00 rwhois.defenderhosting.com (jrwhois.p5 V-0.6.0)
network:Class-Name:network
network:Auth-Area:74.200.64.0/19
network:ID:1254641667/32
network:Handle:DTG-74-200-80-3
network:Description:DTG-74-200-80-3
-------CUT OUT SOME--------
network:Handle:DEFENDER-4
network:IP-Network:74.200.64.0/19
network:IP-Network-Block:74.200.64.0 - 74.200.95.255

%ok searched for 74.200.80.3/32 1254641667 and found 2 records
[root@X:~]#

[Fred]

aaah must be the firewall then ... I'll look into it next week :)

I'm trying from a server here at work and it's working...

Sorry for this then :)

thank you daniel.

[bpeikes]

How about a real example? It would make it much clearer. For example:
Let's say you have the following domains all hosted in cpanel:
peikes.com
doodle.com
rintintin.com

All hosted at the IP numbers which are being removed, with the registrar godaddy.com. They are all currently set up to use the nameservers NS1.PEIKES.COM and NS2.PEIKES.COM.

Give explicit steps telling us exactly what to do. Are my DNS servers already running on the new IP numbers? If I update the IP numbers for NS1 and NS2 with my registrar, should I immediately update the ip numbers in DNS for the peikes.com domain on cpanel? How about the other domains?

You folks should really be working with us more closely to make sure that nothing goes down. This is a HUGE hassle. The pdf that you put together does not inspire any confidence. Were they read over by anyone? They're not even dated.

[paulcook]

A question on the server's "main" IP address. I don't use any of the panels. I've changed my DNS for my domain to point to the new IP, that's fine -- the website works well. However, the IP address that my server is using for OUTGOING connections (ssh or, more importantly, SMTP) is still the old IP. This might cause some of my outgoing email to be flagged as spam, as I use SPF to restrict the class of servers allowed to send email.

So my question is: how do I change the IP address with which the server makes outgoing connections? I see there is a /etc/sysconfig/network-scripts/ifcfg-venet0:* entry for each bound IP; how do I choose the preferred one?

Thanks,
Paul

PS. My domain is thornhill.co.za

[Robert]

If you need to change the main outbound IP, you need to contact support. It will result in a small amount of downtime. They need to change Virtuozzo's configuration file to reorder the IP. If you try to do it, Virtuozzo will ignore the changes.

If you're done with the old IP, just ask support to remove the old one. :)

[dario]

I did migration to new IP two weeks ago and everything went fine from PVPS side. But I’m having problem with my domain registrar. From some reason my NS1 is still resolving to old IP. It’s domain registrar problem, I think, and only my NS2 is pointing to correct IP address.
My questions are:

Am I going to be fine with only one correct NS record (NS2) until this is resolved?

What do I put in resolve.conf ? (just double checking before I change anything)

Dario

[sjs]

This has NOT been a smooth migration for me.

* The Plesk IP Migration Guide is missing important information (ticket CGI-52816-971).

* Apache does not seem to handle subdomains properly after restarting following the migration (ticket ADY-84400-487).

* Support seems to be swamped. I submitted the first ticket over two hours ago and have not received a response other than the auto responder. I submitted the second ticket over an hour ago with "URGENT" in the title, and have received only a single sentence "We are looking into the issue at this time" in response to repeated queries.

And to add insult to injury, I just received the important migration email reminding me to migrate my IP addresses and that "This is the SIXTH and final notice that you will receive!" :)

[Daniel]

I did migration to new IP two weeks ago and everything went fine from PVPS side. But I’m having problem with my domain registrar. From some reason my NS1 is still resolving to old IP. It’s domain registrar problem, I think, and only my NS2 is pointing to correct IP address.
My questions are:

Am I going to be fine with only one correct NS record (NS2) until this is resolved?

What do I put in resolve.conf ? (just double checking before I change anything)

Dario
dario,

Regarding your domain registrar issue, send in a ticket so that we can confirm whether or not it is. If it is we'll let you know.

Regarding resolv.conf, you can replace 204.157.6.3 with 205.234.103.204.

[Daniel]

This has NOT been a smooth migration for me.

* The Plesk IP Migration Guide is missing important information (ticket CGI-52816-971).

* Apache does not seem to handle subdomains properly after restarting following the migration (ticket ADY-84400-487).

* Support seems to be swamped. I submitted the first ticket over two hours ago and have not received a response other than the auto responder. I submitted the second ticket over an hour ago with "URGENT" in the title, and have received only a single sentence "We are looking into the issue at this time" in response to repeated queries.

And to add insult to injury, I just received the important migration email reminding me to migrate my IP addresses and that "This is the SIXTH and final notice that you will receive!" :)
sjs,

Sorry to hear you haven't had a smooth migration. Like I said, I need feedback to improve the guides. I barely got any so I assumed all was OK.

I do not see every ticket that comes through unfortunately.

Regarding us being swamped, our official reply time is 24 hours. While we try to make all replies in under 1-4 hours, we can't always. Especially with a widespread issue like this, support response times are going to be delayed.

If it is urgent, please put URGENT in the ticket subject.

[sjs]

Hi Daniel,

This documentation issue I ran into was this: after rereading the IP addresses in Plesk, you need to manually add a client to the new addresses before they are available to the domains. The docs probably should mention this. Also, some indications of whether to edit the additional A records (or just let Plesk handle it when you selected the new IP address for the domain) would have been helpful.

As for the response times: I understand your guidelines and that you try to get to tickets as quickly as possible (and I should note that Graham was able to fix the problems in about an hour and a half).

With the migration, though, you effectively moved the support burden to the customer, I guess I expected a little bit more backup when I ran into a problem that resulted in downtime.

[DavidP]

This has NOT been a smooth migration for me.

* The Plesk IP Migration Guide is missing important information (ticket CGI-52816-971).

* Apache does not seem to handle subdomains properly after restarting following the migration (ticket ADY-84400-487).

* Support seems to be swamped. I submitted the first ticket over two hours ago and have not received a response other than the auto responder. I submitted the second ticket over an hour ago with "URGENT" in the title, and have received only a single sentence "We are looking into the issue at this time" in response to repeated queries.

And to add insult to injury, I just received the important migration email reminding me to migrate my IP addresses and that "This is the SIXTH and final notice that you will receive!" :)

I've noticed that when sending out the IP Migration notices, the support load for the day actually DOUBLES for 2-4 days, and yes, that does slow us down a bit as we aren't fully staffed to handle multiple days of a double-normal support load. With that in mind, we still need to send reminders, and many customers still have taken no action to move off of the old IPs.

I will be expecting a heavy support load on Monday, December 3rd, along with higher than normal response times, though the responses will still be well within our promised 24 hour response window. I do strongly recommend that our customers not wait until this weekend to make these changes. Those who act early and ask us to remove the IPs from their systems today/tomorrow/friday will likely find all the issues that this migration will cause now, and can work with support to get them fixed now, before our response times are further delayed.

To those of you waiting for the secondary nameserver IP, I have good news! Our engineering staff has provided us with the secondary nameserver IP, and I will be sending that out to customers shortly. For those of you on our Linux-based virtuozzo VPSes, I will be replacing the old secondary IP where it occurs with the new nameserver IP, as well as providing you with that IP.

I do apologize that our support responses are suffering a delay today, and I can assure you that I have brought in additional technicians to better handle today's support load. I will be sure to staff as heavily Monday as possible to handle any emergencies that arise when these IP blocks stop routing, and will personally be working with my technicians on the helpdesk to make sure that this goes as smoothly as possible for all of our customers.

Please remember that the best way to deal with this is to move off of the IPs BEFORE this weekend. This will help you avoid unnecessary delays and handle the move in the most graceful manner possible.

[Aeronautic]

The "Alternate Main Ethernet Device" issue is very poorly documented. I've never run the ifconfig command before so reading the results was a steep learning curve.

I hope I got this right - I had to read all the way up and all the way down several times to (hopefully) verify which IP the VenetX:X address applied to - they are not on the same line and I've got a bunch of IPs.

It seems to be Device is Above IP - and the IP is Main Shared Virtual Host IP, yes? (on cPanel Linux).

And I agree with the earlier comment that each version of the guide should also be dated (file names too) so we could be sure our local copy of the PDF was the most recent.

[Aeronautic]

You may want to sticky this since it was not clear from the GoDaddy "help" docs.

1) Login to GoDaddy
2) Domains > My Domains
3) Select a domain (or THE domain) you use as a name server
4) Look down in the far left hand corner of the page for "Host Summary"
5) You should see at least NS1 and NS2 and "edit" and "delete" links
6) Keep track of your choices here - you need them later!
7) Edit each by adding your new IP

That should do it - I found the changes live in minutes.

[Aeronautic]

I know the support folks are under water at the moment, but wanted to get this out there to see if others who have finished the process noticed this, or if this is simply a non-issue, or related to problems others noticed where cPanel, on server re-boot, reverted to the old IPs.

So I'm passed the IP Migration Wizard step as of last night - all my domains are living on the old and new IPs as far as cPanel/WHM is concerned. Name server at registrar updated, all (fingers crossed) resolving okay so far.

This morning reading through the first scripts/upcp cron job log since the above steps I spotted this line (I know this is not a server re-boot) :

Running Cleanups...Found hostname to be HOST.MYHOST.XXX, which resolves to OLDIP

Is that resolution to the old IP due to it reading some outside cached table? It defaulting to the first listed resolution on my server?

Or is it broken per my earlier point about the issues others had?

Much to my surprise everything is running okay right now - even my ISP, just overnight, is resolving right to the new IP for each domain and name server.

Another one for the FAQ: If you have all your domains on a single shared IP now, but you have been allocated (due to your hosting plan) several IPs, despite what the IP Migration Wizard step in the Guide will ask you (to enter all your new IPs), you can simply add the new Main Shared IP Address you have selected and move all from one IP to a single new IP if you wish to keep them on a single IP.

[Daniel]

Really quickly as I'm bogged down with tickets right now (though this came to my email so I read it)... check your /etc/hosts file.

Does that still have the old IP for your hostname?

[Aeronautic]

Does that still have the old IP for your hostname?

OLDIP host
127.0.0.1 localhost
NEWIP host.mydomain.tld

[Aeronautic]

Support asked me to flesh this out so others would know about it - they are buried as Daniel mentioned above.

I've taken the specifics for my VPS out but this should be clear enough.

So SSH into your server and check, and if needed, correct, the following in "/etc/hosts"

If after the "IP Migration Wizard" step in the Migration Guide, you check your /etc/hosts file and find:


0.0.0.0 cpanel.template
OLDIPHERE host
127.0.0.1 localhost
NEWIPHERE host.MYDOMAIN.TLD


You need to change it (Pico, perhaps) to:


NEWIPHERE host
127.0.0.1 localhost
NEWIPHERE host.MYDOMAIN.TLD


NOTE: MYDOMAIN.TLD = your actual domain, not that text string.
OLDIPHERE = your old IP address, not that text string
NEWIPHERE = if after reading the two lines above you don't know what this is perhaps you ought not be touching this.* ;)

* One additional thought about NEWIPHERE - that is the IP you selected for your host, of course. In my case also the new Main Shared Virtual Host IP.

** In case you are wondering where the first line about cPanel went (0.0.0.0 cpanel.template):

That entry should not be needed. It is added on the VPS build but is not needed for the VPS to work correctly (as you can see it says template).

So the omission above is not a typo.

Hope this is helpful!

[D3F]

With the migration, though, you effectively moved the support burden to the customer, I guess I expected a little bit more backup when I ran into a problem that resulted in downtime.

I agree 100%. I'll reserve my comments about the pattern service has taken here, but let's say its nearly on par with iPower at this point.