Portal Home > Knowledgebase > Articles Database > Red Alert! ResellerZoom/HostingZoom Server Migration Problem!
Red Alert! ResellerZoom/HostingZoom Server Migration Problem!
| Posted by sc0rpi0n, 03-24-2007, 01:14 PM |
| Ok, they migrated this Richmon server to new DC. They informed me about the new IPs assigned to the new server, that I might need to make some changes to nameservers, A records, like that.
Problems appear when they did something called IP-forwarding from old IP to new one. In a sudden every visitor appears to be from the same IP 66.246.252.41. All the traffics are now originated from 66.246.252.41. Vbulletin is currently blocking member login due to its security measure against login bruteforce attack. Emails sent out are being rejected for no reason.
Worst of all, adsense guy has sent me a warning that there is suspicious clicks on my website. It is because all visitors are coming from same IP! It triggers the clickfraud screening.
This is insane, man. If my adsense were to be banned because of this, resellerzoom would have to pay. I'm really disappointed in a way that I asked them every day before the migration, and the only reply was "your server hasn't migrated yet." What a lousy company!
|
| Posted by sc0rpi0n, 03-24-2007, 01:22 PM |
| It appears to me that they forgot to update Richmon nameservers to new IPs. Therefore, every DNS record lookup will point to old IP. When clients access the old IP, they got forwarded by a cheap proxy server. Then every traffic was originated from the proxy's IP.
|
| Posted by EuroVPS/Director, 03-24-2007, 01:47 PM |
| they did something called IP-forwarding from old IP to new one.
I want to hear more about this, this is cool actually - maybe not for this kind of job but still nice
Details?
|
| Posted by IHSL, 03-24-2007, 02:20 PM |
| It's actually pretty boring, to be honest. Most all routers will have documentation for it. It can be done a bunch of ways: router level, server level, using a tcp proxy.
Simon
|
| Posted by sc0rpi0n, 03-24-2007, 11:13 PM |
| Can somebody verify that their nameservers point to old or new IPs?
ns1-richmond.nswebhost.com
ns2-richmond.nswebhost.com
I'm seeing they're pointing to 70.47.106.3, the old IP. But resellerzoom guy insisted that they're pointing to new IPs: 216.180.230.19, 216.180.230.20.
I'm in denial...
|
| Posted by sc0rpi0n, 03-24-2007, 11:20 PM |
| Please post your ping to
ns1-richmond.nswebhost.com
ns2-richmond.nswebhost.com
|
| Posted by nax9, 03-24-2007, 11:54 PM |
| They point to the new IPs on my end (the 216 range)
|
| Posted by xTiNcTion, 03-25-2007, 12:03 AM |
| same here, point to new ips (ping made from central america)
|
| Posted by Til, 03-25-2007, 04:16 AM |
| Pinging ns1-richmond.nswebhost.com [216.180.230.19] with 32 bytes of data:
Reply from 216.180.230.19: bytes=32 time=107ms TTL=54
Reply from 216.180.230.19: bytes=32 time=108ms TTL=54
Reply from 216.180.230.19: bytes=32 time=110ms TTL=54
Reply from 216.180.230.19: bytes=32 time=366ms TTL=54
Ping statistics for 216.180.230.19:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 107ms, Maximum = 366ms, Average = 172ms
|
| Posted by hfohrman, 03-25-2007, 04:44 AM |
| Target Name: ns1-richmond.nswebhost.com
IP: 70.47.106.3
From Sweden
|
| Posted by hfohrman, 03-25-2007, 04:46 AM |
| Ask them to check this page
http://www.dnsstuff.com/tools/lookup...ost.com&type=A
Hans
|
| Posted by hfohrman, 03-25-2007, 04:50 AM |
| Also here it indicates that something is very wrong with this name
http://www.dnsreport.com/tools/dnsre....nswebhost.com
Hans
|
| Posted by sc0rpi0n, 03-25-2007, 06:12 AM |
| Thank you guys for the pings.
Apparently, last time I checked through dnsstuff.com the names resolved to old IP. I don't think it's because of dns propagation, because dnsstuff.com tool doesn't cache any records, and it looks up live NS IPs directly from registrar.
Anyway, what they should have done in first place is update dns records in old nameservers to point to new IPs.
|
| Posted by Highland Web, 04-01-2007, 10:39 PM |
| I get 216.180.230.19 from northeast US.
|
| Posted by Highland Web, 04-01-2007, 10:41 PM |
| Whether DNSstuff does cache records is debateable. The way that the DNS for your new server is configured will certainly affect how quickly the new records are going to show up.
Last edited by Highland Web; 04-01-2007 at 10:44 PM.
|
| Posted by MicGoogle, 04-01-2007, 11:38 PM |
| Wow thast pretty bad if you did get banned, i would actually sue in that case
|
Add to Favourites 
Print this Article
Also Read
hello (Views: 767)
Shared Hosting
Shared Hosting
