Today I was migrated from web140 to web135. It seems that my Internet IP address listed in the Control Panel/DNS manager did not get properly mapped to this new server and I have been down since 10:00 A.M. DST. I have had a ticket opened since that time and can't seem to get it resolved. I can hit the Alternate URL at web135 by my domain name will not properly resolve. When I query ns1,ns2,ns3.discountasp.net with my domain name they all return the IP Address listed in the control panel but all http requests return the generic web page Unavailable. Any help would be appreciated.
If you read the original post you will see that I stated that I had a support ticket open on this issue from the time I received confirmation of the completed migration. After 6 hours of back and forth with first level technical support the problem was finally escalated and resolved with the following response. Subject web140: marinepartssource.com migration Hello, The IP address was not properly migrated to the new server. I have manually reinstalled the IP address on the server and tested your site. Sorry for the trouble. Thank you, Frank DiscountASP.NET is a Microsoft Gold Hosting Partner Team Foundation Server Hosting | ASP.NET Web Hosting Why so long for such a simple issue? Shouldn't this have been one of the first things tested and confirmed upon completion of the migration? I've been using DiscountASP.NET for a number of my clients over the last 4 years and have been very pleased with the infratructure and performance of your network. However, "Sorry for the trouble" isn't going to repair the damage done to MY reputation with this client. I informed the client that I would be requesting a single site migration option (approx. 30 min) in lieu of the server migration (4+ hrs.) scheduled for Wednesday the 14th in order to avoid the prolonged downtime. Instead, his site goes dark for 6 hrs. in the middle of business hours and I become the target of his wrath and held liable for lost revenue.
When reading your ticket it looks like the guys in support assumed that the unique IP was moved when it wasn't. I can understand why they would assume that, since moving the IP is part of the migration procedure, but you're right, they should have checked to verify rather than assuming. We dropped the troubleshooting ball there, and I'm sorry about that.
The problem is that the migration code didn't return any error. This problem is related to a bug (at least I think it is a bug) with Windows. You actually see the IP bound to the Interface but it won't ping nor respond. This happens once in a blue moon and its very hard to detect by the frontline support team. Again, we apologize for the trouble and we'll make sure to retrain our support team of this type of problem
