Nameserver IP change

[wurlocke]

We were asked to change the IPs on our nameservers and were told it was going to be a smooth transition to the new ones when it propagates. When it did, all domains just have "Apache is working normally". I've opened a ticket nearly 2 hours ago and I have yet to hear back from a tech. I've spoken to chat and phone support but still no update or fix on the problem.

Ticket #13460866. IT NEEDS TO GET RESOLVED NOW. Another downtime in a growing list of downtimes in the past 3 months. Makes our business look unreliable.

[JPC-Katrina]

I apologize for any inconvenience. Our techs are checking on this for you.

[the_ancient]

We were asked to change the IPs on our nameservers and were told it was going to be a smooth transition to the new ones when it propagates. When it did, all domains just have "Apache is working normally". I've opened a ticket nearly 2 hours ago and I have yet to hear back from a tech. I've spoken to chat and phone support but still no update or fix on the problem.

Ticket #13460866. IT NEEDS TO GET RESOLVED NOW. Another downtime in a growing list of downtimes in the past 3 months. Makes our business look unreliable.

Sounds like the ip for the vhosts got screwed up...

Why did you need to change IP's anyway?

[wurlocke]

We changed IPs on the nameservers because JPC migrated them. We needed to update the custom nameservers we were using to reflect the new set of IPs they gave us in the original notification ticket they sent us regarding the migration.

I had to wait over 2 hours for the ticket to be read and responded to when the action they needed to take only took them a minute or two. The issue has been resolved but I wish the response time was speedier.

[Main Street James]

We were asked to change the IPs on our nameservers and were told it was going to be a smooth transition to the new ones when it propagates. When it did, all domains just have "Apache is working normally". I've opened a ticket nearly 2 hours ago and I have yet to hear back from a tech. I've spoken to chat and phone support but still no update or fix on the problem.

Ticket #13460866. IT NEEDS TO GET RESOLVED NOW. Another downtime in a growing list of downtimes in the past 3 months. Makes our business look unreliable.

wurloke,
Your experience is exactly what we feared would happen when JPC wanted to move our VPS to another node. They didn't tell us that we needed to change IP's until the last moment even tough we asked if there was anything we needed to do related to the migration. They casually mentioned changing all the IP's in the ticket "Please confirm if you are fine with IP change so we can proceed with this further."

We did not approve moving to another node because we didn't want the uncertainty or the worries about when they might get around to a ticket related to the migration failing. JPC should treat every client's move/migration as if they were moving their own sites, but obviously they don't.

[JPC-Katrina]

wurlocke - Again, my apologies. We had an unusually high amount of tickets yesterday. Our techs are working as quickly as possible to help everyone prior to the holidays.

Main Street James - We do take all moves seriously. Your issue is being brought up with our techs to assure clients are fully aware of any changes required during a move.