Brangwyn, I have been without CP since 12:30AM EST. It appears that for some dumb reason, given the IP reorganization, I decided to check which IP my CP was resolving to. Now I wish I had not.
I looked in the E.Manager and it had (216.157.135.110). Okay, so I performed a couple of tracert's and noticed the IP address flipping back and forth between two different IP addresses (216.157.135.110 & 216.157.129.181) like it was in the middle of propagation. I was STILL able to access the CP with NO problems. But I knew that something was wrong as it should only resolve to one IP, that is unless H-Sphere is split across servers which I don't believe to be the case. So I sent in a TT.
Matt jumped right on it, said there was a problem and corrected it right away. The correction, it seems, rendered my CP inaccessable. In the radio business (I used to be an announcer) a few seconds of dead air can seem like an eternity. Try 12+ hours without a CP. He indicated it could take 24 hours to propagate over the network. Makes sense to me, that is the usual but I have seen much, much, MUCH quicker local propagation than this.
A work around is to change the Base Reseller URL back to the default by logging in to the reseller CP -> Home - > Change URL -> [ Default ] button. This of course is a temporary fix until, well, I don't know when. But it WILL NOT help my customers because I do not want to give them the default URL.
So I did the workaround thing, and went in first to do support and second to check the E.Manager to find the IP of my CP. Come to find, its not even one of the two revolving IPs I mentioned above: cp.mydomain.com (216.157.130.51). So I can only presume that once propagation completes, the other two will be removed and this one will be left in their stead.
This may or may not be a problem that anyone else encounters. Then again, how many resellers are checking their CP IPs with pings/tracerts to see if they change?
