Changing ip adress of domain ? - GoFuckYourself.com

Klen · 12-08-2007, 10:19 AM

Will it when ip adress on same server is changed for certain domain dns servers worldwide act like name server is changed and it will be requied to wait 24 hours for propagation or there wont be such effects(domain will work like nothing happened) ?

SmokeyTheBear · 12-08-2007, 10:23 AM

i would assume that there wouldnt be a delay as the nameservers haven't changed just the ip, but maybe i should drink coffee before answering this question

Shaze · 12-08-2007, 10:26 AM

If you change your server IP and DNS it takes awhile to propogate to the new domain until all the worldwide DNS servers update. Nowadays it's usually less than 24 hours to propogate. I'd say between 6-12 hours.

baddog · 12-08-2007, 10:32 AM

Pretty much depends on your registrar. Godaddy takes about 10 minutes, tops.

[ScreaM] · 12-08-2007, 10:33 AM

What baddog said.

SmokeyTheBear · 12-08-2007, 10:41 AM

Quote:

Originally Posted by baddog

Pretty much depends on your registrar. Godaddy takes about 10 minutes, tops.

i think he just means if the internal ip is swapped not the dns. although there still could be a delay, but in my experience ( i tried it the other day ) it happens instantly..

its wierd that you mention godaddy as being fast as everytime i have someone reg a godaddy domain it always takes ages for me to see it , but when i reg thru directnic the site is up before i can type it in.

baddog · 12-08-2007, 10:50 AM

Quote:

Originally Posted by SmokeyTheBear

its wierd that you mention godaddy as being fast as everytime i have someone reg a godaddy domain it always takes ages for me to see it , but when i reg thru directnic the site is up before i can type it in.

Maybe they don't like Canadians.

Vick! · 12-08-2007, 10:57 AM

I will surely take time. Why? Because the ISPs that already have cached your old IP are not going to update (their cache) before 24-48 hrs.

And to answer if it will effect how domain works .. it will effect, because many ISPs will be sending request to older IP/Server, and if you have removed the content, it will return blank page .. or some error page of domain is removed from the control panel.

So, its better to keep site on older server/IP for at least 2-3 days after moving to new one.

Klen · 12-08-2007, 11:16 AM

Quote:

Originally Posted by Vick!

I will surely take time. Why? Because the ISPs that already have cached your old IP are not going to update (their cache) before 24-48 hrs.

And to answer if it will effect how domain works .. it will effect, because many ISPs will be sending request to older IP/Server, and if you have removed the content, it will return blank page .. or some error page of domain is removed from the control panel.

So, its better to keep site on older server/IP for at least 2-3 days after moving to new one.

Not sure how that will work since i have whm where you have option of change ip adress and that's it,everything stay same,username,pass,content ,etc just ip adress change.

Vick! · 12-08-2007, 01:49 PM

Quote:

Originally Posted by KlenTelaris

Not sure how that will work since i have whm where you have option of change ip adress and that's it,everything stay same,username,pass,content ,etc just ip adress change.

I am not 100% sure, but I guess changing IP this way wont effect domain functionality ..

GrouchyAdmin · 12-08-2007, 01:52 PM

I really don't understand the question, it reads like a DVD instruction manual.

However, if you're hosting your own DNS, then changing the IP, updating the serial number, and HUPPing bind to notify it to reload the zone will begin the process. Globally, it depends what your TTL is set to, but anything using the nameserver you have as a primary will see it almost immediately, since it's notified of the new version.

I hope I confused you as much as that question confused me.

pornask · 12-08-2007, 02:01 PM

Quote:

Originally Posted by baddog

Maybe they don't like Canadians.

They don't. And I'm not even joking. Last night I've changed DNS settings for one of my domains (reg with GoDaddy) and now, 18 hours later, it's still not propagated for me here in Canada. I can tell from stats that the site works in other parts of the world, cause I have a tracking script that shows me which pages are visited by each unique visitor and in what order - so obviously it works for some, but on my end it's just a non existent domain atm. Pisses me off. We're always the last ones to get updated here

directfiesta · 12-08-2007, 02:10 PM

Quote:

Originally Posted by Vick!

I am not 100% sure, but I guess changing IP this way wont effect domain functionality ..

nameservers being the same, they will serve the new Ip.

On his local computer, he should flush the ip's so it doesn't look down.

the Shemp · 12-08-2007, 02:40 PM

Quote:

Originally Posted by pornask

They don't. And I'm not even joking. Last night I've changed DNS settings for one of my domains (reg with GoDaddy) and now, 18 hours later, it's still not propagated for me here in Canada. I can tell from stats that the site works in other parts of the world, cause I have a tracking script that shows me which pages are visited by each unique visitor and in what order - so obviously it works for some, but on my end it's just a non existent domain atm. Pisses me off. We're always the last ones to get updated here

you must be on shaw or rogers cable...

rowan · 12-08-2007, 04:36 PM

GrouchyAdmin hinted at what you need to do in order to have a near instant change: set the TTL low. The TTL (Time To Live) field controls how long a DNS record can be cached at an intermediate point (such as your ISP's DNS cache) before it is discarded and queried again from the DNS server(s) for that domain. This is why it takes so long for some people to see the changes, since something closer to them has cached the DNS record.

If you set your TTL to something low like 2 minutes well in advance (ie, at least 24-48 hours ahead of the IP change) then the majority of your surfers will switch over very quickly as the records are not cached for long. Don't forget to change the TTL back to a more reasonable level after the switch.

12-08-2007, 10:19 AM	#1
Klen Industry Role: Join Date: Aug 2006 Location: Little Vienna Posts: 32,235	Changing ip adress of domain ? Will it when ip adress on same server is changed for certain domain dns servers worldwide act like name server is changed and it will be requied to wait 24 hours for propagation or there wont be such effects(domain will work like nothing happened) ?

12-08-2007, 10:23 AM	#2
SmokeyTheBear ►SouthOfHeaven Join Date: Jun 2004 Location: PlanetEarth MyBoardRank: GerbilMaster My-Penis-Size: extralarge MyWeapon: Computer Posts: 28,609	i would assume that there wouldnt be a delay as the nameservers haven't changed just the ip, but maybe i should drink coffee before answering this question __________________ hatisblack at yahoo.com

12-08-2007, 10:26 AM	#3
Shaze Confirmed User Join Date: Oct 2003 Location: Cyberspace Posts: 2,662	If you change your server IP and DNS it takes awhile to propogate to the new domain until all the worldwide DNS servers update. Nowadays it's usually less than 24 hours to propogate. I'd say between 6-12 hours. __________________ Adult Search Engine Japanese Porn Thai Porn

12-08-2007, 10:57 AM	#8
Vick! Confirmed User Industry Role: Join Date: Nov 2005 Location: 20 00'24.00" N, 75 09'00.00 W Posts: 6,882	I will surely take time. Why? Because the ISPs that already have cached your old IP are not going to update (their cache) before 24-48 hrs. And to answer if it will effect how domain works .. it will effect, because many ISPs will be sending request to older IP/Server, and if you have removed the content, it will return blank page .. or some error page of domain is removed from the control panel. So, its better to keep site on older server/IP for at least 2-3 days after moving to new one. __________________ Affordable Quality Web Hosting Last edited by Vick!; 12-08-2007 at 10:59 AM..

12-08-2007, 01:52 PM	#11
GrouchyAdmin Now choke yourself! Industry Role: Join Date: Apr 2006 Posts: 12,085	I really don't understand the question, it reads like a DVD instruction manual. However, if you're hosting your own DNS, then changing the IP, updating the serial number, and HUPPing bind to notify it to reload the zone will begin the process. Globally, it depends what your TTL is set to, but anything using the nameserver you have as a primary will see it almost immediately, since it's notified of the new version. I hope I confused you as much as that question confused me. __________________ AIM: GrouchyGfy

12-08-2007, 10:32 AM	#4
baddog So Fucking Banned Industry Role: Join Date: Apr 2001 Location: the beach, SoCal Posts: 107,089	Pretty much depends on your registrar. Godaddy takes about 10 minutes, tops.

12-08-2007, 10:33 AM	#5
[ScreaM] Confirmed User Join Date: Jan 2005 Posts: 1,664	What baddog said.

12-08-2007, 04:36 PM	#15
rowan Too lazy to set a custom title Join Date: Mar 2002 Location: Australia Posts: 17,393	GrouchyAdmin hinted at what you need to do in order to have a near instant change: set the TTL low. The TTL (Time To Live) field controls how long a DNS record can be cached at an intermediate point (such as your ISP's DNS cache) before it is discarded and queried again from the DNS server(s) for that domain. This is why it takes so long for some people to see the changes, since something closer to them has cached the DNS record. If you set your TTL to something low like 2 minutes well in advance (ie, at least 24-48 hours ahead of the IP change) then the majority of your surfers will switch over very quickly as the records are not cached for long. Don't forget to change the TTL back to a more reasonable level after the switch.