How long for DNS servers to change?

[MichaelD]

I changed my webhosting company at about this time of day yesterday. How long does it take for the change to propagate (sp?) around the Intarweb?

Yes, I'm itchy. I'd like to get "this all done" (i.e. email addy changes) before returning to a busy workweek tomorrow.

 

[Fiveohhh]

I'd give it 48-36 hrs max, normally for me it takes about 12-24. Try using alertras spot check or post the name here to see if it resolves elsewhere

 

[daveshel]

I think more of it is bureaucratic lag time more than propagation time, but times I have done it it has taken a day and a half, two days.

 

[MichaelD]

Thanks guys. When I ping my domain, it resolves to my NEW hosts' IP, which is good, but the actual http:// Nameserver part doesn't resolve yet.

I will have patience.

 

[daveshel]

Originally posted by: MichaelD
Thanks guys. When I ping my domain, it resolves to my NEW hosts' IP, which is good, but the actual http:// Nameserver part doesn't resolve yet.

Now that is a propagation issue.

 

[MichaelD]

Hmm. Well, like you guys said; it's only been 24 hours. If by tomorrow I don't see anything, I'll contact my host.

 

[Fiveohhh]

If its pointing to the correct IP(but not resolving your account), its a hosting thing. Might want to contact them and see whats up.

 

[Abzstrak]

have seen it take 4-5 days before for worldwide propagation... it just takes time and you have to plan for it.

 

[Fiveohhh]

Originally posted by: Abzstrak
have seen it take 4-5 days before for worldwide propagation... it just takes time and you have to plan for it.

If hes pinging the domain name and its resolving to his new ip that would mean his nameservers are updated. Hes getting pointed to the right server, its his webserver thats not resolving the name request.

 

[MichaelD]

Well, I'm not as completely smart on this as I should be; but I understand the basics.

Still the same situation.

My new hosting's "user control panel" is in full effect; I can go in and manage my account, add emails, etc.

I just can't resolve it via HTTP or email. I will give it until tommorow. My email (thru the old host) is still working...but my old host IS THE REASON I changed hosts in the first place. Can U say "Sold our soul to Spammers?" :roll:

 

[Garion]

All these answers are generally correct, but there's one very important fact that's missing..

DNS is controlled by TTL's - Time To Lives. Each domain has a TTL that is used by DNS servers across the Internet. This TTL controls how long the DNS servers will cache information about your domain - What the authoritative DNS servers are, etc. If you set a one-week TTL (not uncommon) and move your domain it might take up to a week for the zone to expire in some DNS servers. The TTL is part of the DNS zone information and is something you can change. If you are planning on moving your domain, it's wise to set the TTL down loaw (~1 hour or so) a few weeks before you move, then set it back up once you've moved it to your new provider. Don't keep it low, as that adds undue load to your resolving DNS servers and the Internet as a whole

- G

 

[MichaelD]

Originally posted by: Garion
All these answers are generally correct, but there's one very important fact that's missing..

DNS is controlled by TTL's - Time To Lives. Each domain has a TTL that is used by DNS servers across the Internet. This TTL controls how long the DNS servers will cache information about your domain - What the authoritative DNS servers are, etc. If you set a one-week TTL (not uncommon) and move your domain it might take up to a week for the zone to expire in some DNS servers. The TTL is part of the DNS zone information and is something you can change. If you are planning on moving your domain, it's wise to set the TTL down loaw (~1 hour or so) a few weeks before you move, then set it back up once you've moved it to your new provider. Don't keep it low, as that adds undue load to your resolving DNS servers and the Internet as a whole

- G

Wow, that's really good information...I actually learned some of that in my MS course 2277 about a month ago. Too bad I didn't remember it.

I found a small glitch today...and it's my fault. :roll:

My domain name registration company and my webhosting company are different. Though my new hosting company had me up and running and resolving within 24 hours, I DIDN'T change my Nameservers with my Domain Registrar. :roll: Oooops. Did that tonight. We'll see what happens (if anything) by morning.

 

[Garion]

One note that I forgot. Each individual DNS record (i.e. www.foo.com) has a TTL associated with it, too. So you can set your host records to be cached on a DNS server for X amount of time. This is separate from your zone TTL. This one is useful if you're moving a server to a new IP. Set the TTL for the record down to a minute or two a day or so in advance, move it, then re-set the TTL back up to normal.

- G