Anyone here switched hosts before?
 

Was hosting with a buddy of mine off a reseller account he has. Was a shared IP, knew that, but they don't allow adult sites, didn't know that (booo).

Is there ANYTHING worse than switching hosts? I actually think that moving the information is not too bad, I can probably get that done in like a day or less. However, on this new host I've been waiting for like EVER for my DNS entry to resolve. Shouldn't this take just a couple hours at most? What's the worst case scenario I'm looking at here? |cry|

In some cases it can take 24-48 hours. Good luck!

Brent,

There are things that could be done to reduce the time to update the dns, but generally it takes between 24-72 hours to update.

And yes, migrating hosts can be a very trying experience at times.

Drizzt
http://www.powerstorm.net

Ahhhh, that was my greatest fear. It's funny. These days someone could probably deploy another Internet in 24-48 hours, but we can't even get a DNS record to resolve, hehe. Is Forrest Gump running these entries back and forth or something?

Lol

It does seem crazy at times doesn't it? Again though, there were some things that coul dhave helped your situation prior to the move though. Like setting the TTL on the DNS lower.

Drizzt
http://www.powerstorm.net

The main dns servers on the net refresh in about 30 minutes. The problem is the cache at the ISP dns servers which is why it takes 24-72 hours. Sometime in the future the service providers will join the rest of us in the 21st century |pcwins|

I'm not going to hold my breath on that one. LOL

Drizzt
http://www.powerstorm.net

If the domain is the same domain in your sig, then your new host didn't setup the domain correctly. This is pretty ugly.


; <<>> DiG 9.2.1 <<>> +trace THUMBOMETER.COM
;; global options: printcmd
. 150482 IN NS E.ROOT-SERVERS.NET.
. 150482 IN NS D.ROOT-SERVERS.NET.
. 150482 IN NS A.ROOT-SERVERS.NET.
. 150482 IN NS H.ROOT-SERVERS.NET.
. 150482 IN NS C.ROOT-SERVERS.NET.
. 150482 IN NS G.ROOT-SERVERS.NET.
. 150482 IN NS F.ROOT-SERVERS.NET.
. 150482 IN NS B.ROOT-SERVERS.NET.
. 150482 IN NS J.ROOT-SERVERS.NET.
. 150482 IN NS K.ROOT-SERVERS.NET.
. 150482 IN NS L.ROOT-SERVERS.NET.
. 150482 IN NS M.ROOT-SERVERS.NET.
. 150482 IN NS I.ROOT-SERVERS.NET.
;; Received 436 bytes from 24.196.64.39#53(24.196.64.39) in 83 ms

COM. 172800 IN NS K.GTLD-SERVERS.NET.
COM. 172800 IN NS L.GTLD-SERVERS.NET.
COM. 172800 IN NS M.GTLD-SERVERS.NET.
COM. 172800 IN NS A.GTLD-SERVERS.NET.
COM. 172800 IN NS B.GTLD-SERVERS.NET.
COM. 172800 IN NS C.GTLD-SERVERS.NET.
COM. 172800 IN NS D.GTLD-SERVERS.NET.
COM. 172800 IN NS E.GTLD-SERVERS.NET.
COM. 172800 IN NS F.GTLD-SERVERS.NET.
COM. 172800 IN NS G.GTLD-SERVERS.NET.
COM. 172800 IN NS H.GTLD-SERVERS.NET.
COM. 172800 IN NS I.GTLD-SERVERS.NET.
COM. 172800 IN NS J.GTLD-SERVERS.NET.
;; Received 505 bytes from 192.203.230.10#53(E.ROOT-SERVERS.NET) in 77 ms

THUMBOMETER.COM. 172800 IN NS ns1.selectedsex.COM.
THUMBOMETER.COM. 172800 IN NS ns2.selectedsex.COM.
;; Received 113 bytes from 192.52.178.30#53(K.GTLD-SERVERS.NET) in 140 ms

THUMBOMETER.COM. 154880 IN NS ns1.selectedsex.COM.
THUMBOMETER.COM. 154880 IN NS ns2.selectedsex.COM.
;; Received 113 bytes from 66.230.167.185#53(ns1.selectedsex.COM) in 47 ms

THUMBOMETER.COM. 154880 IN NS ns2.selectedsex.COM.
THUMBOMETER.COM. 154880 IN NS ns1.selectedsex.COM.
;; Received 113 bytes from 66.230.167.185#53(ns1.selectedsex.COM) in 51 ms

THUMBOMETER.COM. 154880 IN NS ns2.selectedsex.COM.
THUMBOMETER.COM. 154880 IN NS ns1.selectedsex.COM.
;; Received 113 bytes from 66.230.167.186#53(ns2.selectedsex.COM) in 42 ms

THUMBOMETER.COM. 154880 IN NS ns1.selectedsex.COM.
THUMBOMETER.COM. 154880 IN NS ns2.selectedsex.COM.
;; Received 113 bytes from 66.230.167.186#53(ns2.selectedsex.COM) in 45 ms

THUMBOMETER.COM. 154880 IN NS ns2.selectedsex.COM.
THUMBOMETER.COM. 154880 IN NS ns1.selectedsex.COM.
;; Received 113 bytes from 66.230.167.185#53(ns1.selectedsex.COM) in 49 ms

THUMBOMETER.COM. 154880 IN NS ns2.selectedsex.COM.
THUMBOMETER.COM. 154880 IN NS ns1.selectedsex.COM.
;; Received 113 bytes from 66.230.167.186#53(ns2.selectedsex.COM) in 39 ms

THUMBOMETER.COM. 154880 IN NS ns1.selectedsex.COM.
THUMBOMETER.COM. 154880 IN NS ns2.selectedsex.COM.
;; Received 113 bytes from 66.230.167.186#53(ns2.selectedsex.COM) in 43 ms

THUMBOMETER.COM. 154880 IN NS ns1.selectedsex.COM.
THUMBOMETER.COM. 154880 IN NS ns2.selectedsex.COM.
;; Received 113 bytes from 66.230.167.185#53(ns1.selectedsex.COM) in 49 ms

THUMBOMETER.COM. 154879 IN NS ns2.selectedsex.COM.
THUMBOMETER.COM. 154879 IN NS ns1.selectedsex.COM.
;; Received 113 bytes from 66.230.167.185#53(ns1.selectedsex.COM) in 45 ms

THUMBOMETER.COM. 154879 IN NS ns2.selectedsex.COM.
THUMBOMETER.COM. 154879 IN NS ns1.selectedsex.COM.
;; Received 113 bytes from 66.230.167.186#53(ns2.selectedsex.COM) in 44 ms

THUMBOMETER.COM. 154879 IN NS ns2.selectedsex.COM.
THUMBOMETER.COM. 154879 IN NS ns1.selectedsex.COM.
;; Received 113 bytes from 66.230.167.186#53(ns2.selectedsex.COM) in 41 ms

THUMBOMETER.COM. 154878 IN NS ns2.selectedsex.COM.
THUMBOMETER.COM. 154878 IN NS ns1.selectedsex.COM.
;; Received 113 bytes from 66.230.167.185#53(ns1.selectedsex.COM) in 50 ms

THUMBOMETER.COM. 154878 IN NS ns1.selectedsex.COM.
THUMBOMETER.COM. 154878 IN NS ns2.selectedsex.COM.
;; Received 113 bytes from 66.230.167.186#53(ns2.selectedsex.COM) in 40 ms

THUMBOMETER.COM. 154878 IN NS ns1.selectedsex.COM.
THUMBOMETER.COM. 154878 IN NS ns2.selectedsex.COM.
;; Received 113 bytes from 66.230.167.185#53(ns1.selectedsex.COM) in 46 ms

THUMBOMETER.COM. 154878 IN NS ns2.selectedsex.COM.
THUMBOMETER.COM. 154878 IN NS ns1.selectedsex.COM.
;; Received 113 bytes from 66.230.167.185#53(ns1.selectedsex.COM) in 48 ms

THUMBOMETER.COM. 154878 IN NS ns1.selectedsex.COM.
THUMBOMETER.COM. 154878 IN NS ns2.selectedsex.COM.
;; Received 113 bytes from 66.230.167.186#53(ns2.selectedsex.COM) in 39 ms

THUMBOMETER.COM. 154878 IN NS ns1.selectedsex.COM.
THUMBOMETER.COM. 154878 IN NS ns2.selectedsex.COM.
;; Received 113 bytes from 66.230.167.185#53(ns1.selectedsex.COM) in 47 ms

THUMBOMETER.COM. 154878 IN NS ns1.selectedsex.COM.
THUMBOMETER.COM. 154878 IN NS ns2.selectedsex.COM.
;; Received 113 bytes from 66.230.167.185#53(ns1.selectedsex.COM) in 46 ms

THUMBOMETER.COM. 154877 IN NS ns1.selectedsex.COM.
THUMBOMETER.COM. 154877 IN NS ns2.selectedsex.COM.
;; Received 113 bytes from 66.230.167.185#53(ns1.selectedsex.COM) in 46 ms

THUMBOMETER.COM. 154877 IN NS ns1.selectedsex.COM.
THUMBOMETER.COM. 154877 IN NS ns2.selectedsex.COM.
;; Received 113 bytes from 66.230.167.185#53(ns1.selectedsex.COM) in 45 ms

THUMBOMETER.COM. 154877 IN NS ns1.selectedsex.COM.
THUMBOMETER.COM. 154877 IN NS ns2.selectedsex.COM.
;; Received 113 bytes from 66.230.167.185#53(ns1.selectedsex.COM) in 46 ms

THUMBOMETER.COM. 154877 IN NS ns2.selectedsex.COM.
THUMBOMETER.COM. 154877 IN NS ns1.selectedsex.COM.
;; Received 113 bytes from 66.230.167.185#53(ns1.selectedsex.COM) in 44 ms

THUMBOMETER.COM. 154877 IN NS ns1.selectedsex.COM.
THUMBOMETER.COM. 154877 IN NS ns2.selectedsex.COM.
;; Received 113 bytes from 66.230.167.186#53(ns2.selectedsex.COM) in 45 ms

THUMBOMETER.COM. 154877 IN NS ns1.selectedsex.COM.
THUMBOMETER.COM. 154877 IN NS ns2.selectedsex.COM.
;; Received 113 bytes from 66.230.167.185#53(ns1.selectedsex.COM) in 47 ms

THUMBOMETER.COM. 154877 IN NS ns1.selectedsex.COM.
THUMBOMETER.COM. 154877 IN NS ns2.selectedsex.COM.
;; Received 113 bytes from 66.230.167.185#53(ns1.selectedsex.COM) in 45 ms

THUMBOMETER.COM. 154877 IN NS ns2.selectedsex.COM.
THUMBOMETER.COM. 154877 IN NS ns1.selectedsex.COM.
;; Received 113 bytes from 66.230.167.185#53(ns1.selectedsex.COM) in 45 ms

THUMBOMETER.COM. 154877 IN NS ns2.selectedsex.COM.
THUMBOMETER.COM. 154877 IN NS ns1.selectedsex.COM.
;; Received 113 bytes from 66.230.167.186#53(ns2.selectedsex.COM) in 40 ms

THUMBOMETER.COM. 154877 IN NS ns2.selectedsex.COM.
THUMBOMETER.COM. 154877 IN NS ns1.selectedsex.COM.
;; Received 113 bytes from 66.230.167.186#53(ns2.selectedsex.COM) in 40 ms

THUMBOMETER.COM. 154877 IN NS ns1.selectedsex.COM.
THUMBOMETER.COM. 154877 IN NS ns2.selectedsex.COM.
;; Received 113 bytes from 66.230.167.186#53(ns2.selectedsex.COM) in 39 ms

THUMBOMETER.COM. 154877 IN NS ns1.selectedsex.COM.
THUMBOMETER.COM. 154877 IN NS ns2.selectedsex.COM.
dig: Too many lookups

it's actually pretty easy to switch hosts as long as it is planned out. just put up "down for maintenance" on your old host while DNS bounces back and forth. i have had DNS switch in less than 5 minutes with godaddy. of course it bounced back and forth for a few hours.

A domain setup correctly would look something like this.


; <<>> DiG 9.2.1 <<>> +trace hosthead.com
;; global options: printcmd
. 150266 IN NS E.ROOT-SERVERS.NET.
. 150266 IN NS D.ROOT-SERVERS.NET.
. 150266 IN NS A.ROOT-SERVERS.NET.
. 150266 IN NS H.ROOT-SERVERS.NET.
. 150266 IN NS C.ROOT-SERVERS.NET.
. 150266 IN NS G.ROOT-SERVERS.NET.
. 150266 IN NS F.ROOT-SERVERS.NET.
. 150266 IN NS B.ROOT-SERVERS.NET.
. 150266 IN NS J.ROOT-SERVERS.NET.
. 150266 IN NS K.ROOT-SERVERS.NET.
. 150266 IN NS L.ROOT-SERVERS.NET.
. 150266 IN NS M.ROOT-SERVERS.NET.
. 150266 IN NS I.ROOT-SERVERS.NET.
;; Received 436 bytes from 24.196.64.39#53(24.196.64.39) in 29 ms

com. 172800 IN NS A.GTLD-SERVERS.NET.
com. 172800 IN NS B.GTLD-SERVERS.NET.
com. 172800 IN NS C.GTLD-SERVERS.NET.
com. 172800 IN NS D.GTLD-SERVERS.NET.
com. 172800 IN NS E.GTLD-SERVERS.NET.
com. 172800 IN NS F.GTLD-SERVERS.NET.
com. 172800 IN NS G.GTLD-SERVERS.NET.
com. 172800 IN NS H.GTLD-SERVERS.NET.
com. 172800 IN NS I.GTLD-SERVERS.NET.
com. 172800 IN NS J.GTLD-SERVERS.NET.
com. 172800 IN NS K.GTLD-SERVERS.NET.
com. 172800 IN NS L.GTLD-SERVERS.NET.
com. 172800 IN NS M.GTLD-SERVERS.NET.
;; Received 502 bytes from 192.203.230.10#53(E.ROOT-SERVERS.NET) in 76 ms

hosthead.com. 172800 IN NS ns1.hosthead.com.
hosthead.com. 172800 IN NS ns2.hosthead.com.
;; Received 98 bytes from 192.5.6.30#53(A.GTLD-SERVERS.NET) in 69 ms

hosthead.com. 3600 IN A 8.9.32.46
hosthead.com. 3600 IN NS ns2.hosthead.com.
hosthead.com. 3600 IN NS ns1.hosthead.com.
;; Received 114 bytes from 8.9.32.45#53(ns1.hosthead.com) in 44 ms

Thanks TwinTone, does look ugly right now. I've been using DNSReport.com to check out the status and I saw that the glue was still listed as my old host for most of the day, but that seems cleared up now. So maybe it's just a matter of clearing up a little more. I'll sleep on it and hopefully will have it all resolved by morning.

um I don't think thats a good idea if you have free sites submitted on the domain. You will have them deleted and possibly get blacklisted. Its best to leave the old stuff up at the old host until the dns has finished bouncing around. (unless I have taken your post the wrong way lol)

Godaddy or any place should update within minutes of you changing but that has nothing to do with other people being able to find your site. Comcast seems to have a 72 hour cache so they won't look to update on thier end for a long time.

The best thing to do is copy the data, make sure your scripts work, change the DNS and don't make any changes for 72 hours. Your new sites need to be exact duplicates of your old until the DNS cache is cleared every where and you don't have full control over that.

You could use htaccess to redirect everything form the old host to the new one until the dns propagates - I think this is all you have to do:

Redirect / http://66.115.135.176/

(of course replacing your IP with the one I have i there)

This way, at least you're not 404'ing & loosing all your traffic :)

Got this virus from the link in your sig. Thumbometer.com.
Whats that all about.

JS/Exploit-MhtRedir.ldr

Yes, you can switch hosts and have it resolving properly around the world in less than 30 minutes, its easy! All you have to do is use Advanced DNS or Total DNS at your registrar (godaddy, enom resellers and many others offer this service for free) or use zoneedit to keep total control over your DNS. That way when you switch hosts, all you have to do is update the IP addresses of your A & MX records, and since this is not a change to your nameservers (ns1/ns2) you don't have to worry about the DNS replication 72 hour cycle.

cheers,
Luke

|thumb Exactly what I wanted to say!

Even as a newbie I got to learn this little trick quickly...
Before I used to put a meta-refresh to numeric IP on all pages - but that gets you blacklisted with everybody running scanner scripts (eg. LL and TGP submissions).

Didn't you black list once for doing exaclty that?

I think I would rather have my teeth knocked out than deal with switching hosts.. I have always had bad experiences.
For example, I am currently moving my paysites from Swiftwill and I asked them for a root dump of my mysql database .. easy enough I thought, but apparently not the case. Even though it is my server I am not allowed to request a root dump, nor am I allowed shell access ... sound fishy to you? I bet it is. I have never had a problem with them till now.. whats up with that?

Anyway good luck on the server move thumbometer.

I moved hosts 11 months ago and saved a bundle while getting far superior service too!

Dave at web1host.net rules!

Maybe? :D

Think of it this way - they're gonna get blacklisted anyway for the 404's - that's a given.

This way, at least they keep some of the traffic & the sites are open & when we run the Link Bot, we do try to look for things like this & then hold off on removing the sites.

If my memory doesn't fail me completely I had been with them some years ago (2000-2001?) and I was always happy - until one day I was hit with a huge overage bill (a single link from a japanese site, which I didn't catch quick enough - I always thought that a good host should consider sending a short alert about unusual traffic spikes)...

you know part of the job of the hosting company is making sure they help you out with your initial setup and move....It seems from these posts that there are a lot of hosts out there that do not believe in top notch service like I do!

cheers,
Luke

It's really a pain, but if you have to do it, the sooner the better..
The more scripts you have running the worst the nightmare will be..O, and CCBill and your other processors will have to config again..

So Thumbometer, what exactly is the trojan JS/Exploit-MhtRedir.ldr attached to your site, Thumbometer

I am curious since no one else here has inquired about it.

I didn't read this whole thread so excuse me if someone mentioned this before. Can't you just add additional name servers (the ones for your new server), get everything setup on the new server and then remove the old name servers once everything is setup?

Damn, thanks for the heads-up on that, much appreciated!

Juergen, I've checked your last several bills for tropicheat.com when you left Web1Host July of 2002. There were no extra charges of any kind and you cancelled for July on June 23rd 2002. If there was any kind of excess bandwidth used in May or June, you weren't billed for anything.

|huh

1 question while we are on the subject, i just had to change servers, not hosts, and things went pretty smooth, but i am having a problem accessing autogallery pro, the script moved fine and is running, but i can't log in. I have done the password reset the tell you to do i.e. upload password.cgi to the root of the script and it reset it, but it still won't let me in?? any suggestions??

George has retired from this business -AND more importantly - this thread is from March of '05. Nice work. |thumb

mmmmm, I need to start looking at the dates of posts :D

Yikes...someone really dusted off an old thread |loony|