Anyone here switched hosts before?

thumbometer · 2005-02-26, 11:32 PM

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?

Hostive.com · 2005-02-26, 11:37 PM

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

drizzt · 2005-02-26, 11:38 PM

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

thumbometer · 2005-02-26, 11:52 PM

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?

Hostive.com · 2005-02-26, 11:58 PM

Quote:

Originally Posted by thumbometer

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

drizzt · 2005-02-27, 12:06 AM

Quote:

Originally Posted by thumbometer

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?

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

zack2004 · 2005-02-27, 12:09 AM

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|

drizzt · 2005-02-27, 12:12 AM

Quote:

Originally Posted by zack2004

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

twintone · 2005-02-27, 12:15 AM

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

SinSational · 2005-02-27, 12:17 AM

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.

twintone · 2005-02-27, 12:17 AM

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

thumbometer · 2005-02-27, 12:38 AM

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.

natalie · 2005-02-27, 12:39 AM

Quote:

Originally Posted by SinSational

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.

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)

SirMoby · 2005-02-27, 01:27 AM

Quote:

Originally Posted by SinSational

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.

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.

Greenguy · 2005-02-27, 08:07 AM

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

dunkin · 2005-02-27, 08:57 AM

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

JS/Exploit-MhtRedir.ldr

chilihost · 2005-02-27, 06:56 PM

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

GeorgeTH · 2005-02-28, 08:47 PM

Quote:

Originally Posted by Greenguy

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

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).

SirMoby · 2005-03-01, 11:04 AM

Quote:

Originally Posted by Greenguy

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

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

terry · 2005-03-01, 11:14 AM

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.

DeniseAWC · 2005-03-01, 12:12 PM

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

Dave at web1host.net rules!

Greenguy · 2005-03-01, 02:34 PM

Quote:

Originally Posted by SirMoby

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

Maybe?

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.

GeorgeTH · 2005-03-01, 05:40 PM

Quote:

Originally Posted by DeniseAWC

Dave at web1host.net rules!

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)...

chilihost · 2005-03-01, 09:09 PM

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

RyuLion · 2005-03-01, 09:26 PM

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..

2005-02-26, 11:32 PM	#1
thumbometer Aw, Dad, you've done a lot of great things, but you're a very old man, and old people are useless Join Date: Feb 2005 Location: Ontario, Canada Posts: 23	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? __________________ Please Re-Read The Rules For Sig Files

2005-02-26, 11:52 PM	#4
thumbometer Aw, Dad, you've done a lot of great things, but you're a very old man, and old people are useless Join Date: Feb 2005 Location: Ontario, Canada Posts: 23	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? __________________ Please Re-Read The Rules For Sig Files

2005-02-27, 12:09 AM	#7
zack2004 Ahhh ... sweet pity. Where would my love life be without it? Join Date: Apr 2004 Location: New Jersey, USA Posts: 209	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\| __________________ Zack Free XXX Twat Porn Links Twat Porn Blog

2005-02-27, 12:15 AM	#9
twintone Heh Heh Heh! Lisa! Vampires are make believe, just like elves and gremlins and eskimos! Join Date: Jul 2004 Location: Wisconsin Posts: 77	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 __________________

2005-02-27, 12:17 AM	#11
twintone Heh Heh Heh! Lisa! Vampires are make believe, just like elves and gremlins and eskimos! Join Date: Jul 2004 Location: Wisconsin Posts: 77	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 __________________

2005-02-26, 11:37 PM	#2
Hostive.com Aw, Dad, you've done a lot of great things, but you're a very old man, and old people are useless Join Date: Dec 2004 Location: Ft. Collins, CO Posts: 24	In some cases it can take 24-48 hours. Good luck!

2005-02-26, 11:38 PM	#3
drizzt Rock stars ... is there anything they don't know? Join Date: Oct 2003 Location: PA Posts: 17	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

2005-02-27, 12:17 AM	#10
SinSational Shut up brain, or I'll stab you with a Q-tip! Join Date: Jan 2005 Location: Boston, MA Posts: 119	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.

2005-02-27, 12:38 AM	#12
thumbometer Aw, Dad, you've done a lot of great things, but you're a very old man, and old people are useless Join Date: Feb 2005 Location: Ontario, Canada Posts: 23	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. __________________ Please Re-Read The Rules For Sig Files

2005-02-27, 08:07 AM	#15
Greenguy The Original Greenguy (Est'd 1996) & AVN HOF Member - I Crop Pics For Thumbs In My Sleep Join Date: Feb 2003 Location: Blasdell, NY (shithole suburb south of Buffalo) Posts: 41,764	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 __________________ Promote POV Porn Cash By Building & Submitting Galleries to the Porn Luv Network

2005-02-27, 08:57 AM	#16
dunkin Just because I don't care doesn't mean I don't understand! Join Date: Feb 2004 Posts: 92	Got this virus from the link in your sig. Thumbometer.com. Whats that all about. JS/Exploit-MhtRedir.ldr __________________ Dunkins World - Accepting gallery submits & link trades.

2005-02-27, 06:56 PM	#17
chilihost Look at 'em. Watchin' my TV. Sittin on my couch. You better not be in my ass groove! Join Date: Aug 2003 Posts: 465	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 __________________ HunkMoney+BritishBucks+LatinoBucks=50+ gay sites!

2005-03-01, 11:14 AM	#20
terry You can now put whatever you want in this space :) Join Date: Apr 2004 Location: Montreal Posts: 5,883	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. __________________ Stop That 9 To 5 Go Green Grocery Store

2005-03-01, 12:12 PM	#21
DeniseAWC A woman is like beer. They look good, they smell good, and you'd step over your own mother just to get one! Join Date: Jul 2004 Location: The Cotswolds, UK Posts: 55	I moved hosts 11 months ago and saved a bundle while getting far superior service too! Dave at web1host.net rules! __________________ Denise www.adwebcash.com

2005-03-01, 09:09 PM	#24
chilihost Look at 'em. Watchin' my TV. Sittin on my couch. You better not be in my ass groove! Join Date: Aug 2003 Posts: 465	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 __________________ HunkMoney+BritishBucks+LatinoBucks=50+ gay sites!

2005-03-01, 09:26 PM	#25
RyuLion Are you sure you're an accredited and honored pornographer? Join Date: Dec 2003 Location: Miami Posts: 61	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.. __________________ CougarsinHeat.com 1:352 - Who's who