Tech Geeks: Why does it take 2 days to switch when changing nameservers? - GoFuckYourself.com

DearAbby · 09-10-2003, 03:51 PM

Isnt there like some button you could push and have things switched faster?

Why does it take up to 48 for things to settle when changing nameservers?

j3ff · 09-10-2003, 03:54 PM

the time for the info to spread around the world's dns's

synchronization and all that bullshit.

MichaelP · 09-10-2003, 03:55 PM

It is the time it takes for all ISPs to resolve the domains to the new IP or nameserver.... Usually they refresh their databases once a day during night.

That's what I heard..

chuk · 09-10-2003, 03:55 PM

The internet only has something like 13 root servers, so it takes a while for dns to propagate through these.

DearAbby · 09-10-2003, 03:56 PM

Fabuleux · 09-10-2003, 03:58 PM

Quote:

Originally posted by DearAbby

I want it faster.

Azathoth · 09-10-2003, 04:00 PM

Quote:

Originally posted by Fabuleux

I want it faster.

You can make it faster if you change the TTL
( time to live ) value on the SOA ( start of
authority ) record on your domain at least 48
hours before you want to move your domain.

Make it something like 2 hours rather than the
default of 2 days. This means that other name
servers will only cache your DNS info for upto
2 hours rather than 2 days

Can also depend on your registrar but the
above will help the dns propagate through
nameservers throughout the world quicker.

rowan · 09-10-2003, 04:01 PM

If you change a DNS record without 'preparing' then usually it will take at least 24 hours for 99% of the people to change over to the new IP. (some will continue accessing the old one MONTHS after you change it - you can't help them

)

Each DNS record has a time-to-live field, which defines the maximum length that it should be cached by an intermediate DNS cache (or end host such as a surfers computer). Most DNS setups seem to have a TTL between 24-48 hours usually. If you don't reduce this TTL field prior to changing the IP, then everywhere will cache it as per normal. The trick is to reduce the TTL to something small (like 120 seconds) at least a couple of days prior to changing the IP... so in theory, the old cached record with the old IP should only live a maximum of 2 minutes. You'll see surfers accessing the new server pretty much immediately.

If you are actually redelegating (changing the DNS servers that your domain points to) then that's an added delay, since the root servers do not update in real-time.

If you move from one host to another and you have both an IP and DNS server change then you're looking at 48+ hours for everything to propagate out properly. If the old host is able to point to the new IP then it should be a lot less painful.

Jakke PNG · 09-10-2003, 04:04 PM

Quote:

Originally posted by chuk
The internet only has something like 13 root servers, so it takes a while for dns to propagate through these.

I want one of these to run my tgp off.

beemk · 09-10-2003, 04:07 PM

Quote:

Originally posted by TeenGodFather

I want one of these to run my tgp off.

ill sell you one for $10. paypal me to [email protected]

EscortBiz · 09-10-2003, 04:08 PM

because its part of the patriot act

Fabuleux · 09-10-2003, 04:11 PM

Azathoth and Rowan, thank you for the info, it's completely clear to me

Giving my host a phone call tomorrow.

Thanks.

09-10-2003, 03:51 PM	#1
DearAbby Confirmed User Join Date: Nov 2002 Location: NoCal Posts: 979	Tech Geeks: Why does it take 2 days to switch when changing nameservers? Isnt there like some button you could push and have things switched faster? Why does it take up to 48 for things to settle when changing nameservers?

09-10-2003, 03:54 PM	#2
j3ff Confirmed User Join Date: Jun 2003 Location: Quebec city Posts: 690	the time for the info to spread around the world's dns's synchronization and all that bullshit. __________________ Can A Paysite Pluggin NOT Be A Simple Pluggin? Downloadable MPEG, WMV and DiVX -- UPDATED DAILY! www.itsyourporn.com

09-10-2003, 04:08 PM	#11
EscortBiz Fuck Checks, CASH only! Join Date: May 2002 Location: New York City Posts: 19,422	because its part of the patriot act __________________ Spanking, Medical Fetish, Sleeping, Strap-on Anal Lesbians, Girls Fucking Guys, Handjob site REAL HOT, Shemales, Anal and Ass Licking sites 100% Real EXCLUSIVE with amazing retention, ccbill payouts, lots of content FREE FTP HOSTING Promote the largest and oldest member paid escort site, Converts 10 times better then any dating site, CCBill payouts ICQ# 158802076

09-10-2003, 04:11 PM	#12
Fabuleux Confirmed User Join Date: May 2003 Location: The Netherlands Posts: 2,543	Azathoth and Rowan, thank you for the info, it's completely clear to me Giving my host a phone call tomorrow. Thanks. __________________

09-10-2003, 03:55 PM	#3
MichaelP Registered User Industry Role: Join Date: Aug 2003 Location: QWEBEC Corporate Office Posts: 7,124	It is the time it takes for all ISPs to resolve the domains to the new IP or nameserver.... Usually they refresh their databases once a day during night. That's what I heard..

09-10-2003, 03:55 PM	#4
chuk Confirmed User Join Date: Mar 2003 Location: WI Posts: 682	The internet only has something like 13 root servers, so it takes a while for dns to propagate through these.

09-10-2003, 03:56 PM	#5
DearAbby Confirmed User Join Date: Nov 2002 Location: NoCal Posts: 979

09-10-2003, 04:01 PM	#8
rowan Too lazy to set a custom title Join Date: Mar 2002 Location: Australia Posts: 17,393	If you change a DNS record without 'preparing' then usually it will take at least 24 hours for 99% of the people to change over to the new IP. (some will continue accessing the old one MONTHS after you change it - you can't help them ) Each DNS record has a time-to-live field, which defines the maximum length that it should be cached by an intermediate DNS cache (or end host such as a surfers computer). Most DNS setups seem to have a TTL between 24-48 hours usually. If you don't reduce this TTL field prior to changing the IP, then everywhere will cache it as per normal. The trick is to reduce the TTL to something small (like 120 seconds) at least a couple of days prior to changing the IP... so in theory, the old cached record with the old IP should only live a maximum of 2 minutes. You'll see surfers accessing the new server pretty much immediately. If you are actually redelegating (changing the DNS servers that your domain points to) then that's an added delay, since the root servers do not update in real-time. If you move from one host to another and you have both an IP and DNS server change then you're looking at 48+ hours for everything to propagate out properly. If the old host is able to point to the new IP then it should be a lot less painful.