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) ?
-
-
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 questionhatisblack at yahoo.com -
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.Comment
-
Pretty much depends on your registrar. Godaddy takes about 10 minutes, tops.Comment
-
What baddog said.Comment
-
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.hatisblack at yahoo.comComment
-
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.Last edited by Vick!; 12-08-2007, 08:59 AM.Comment
-
Comment
-
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.Comment
-
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
Comment
-
Comment
-
you must be on shaw or rogers cable...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 hereComment
-
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.Comment
AIM: GrouchyGfy
Comment