http://www.savagehost.com/dns-servers-name-propagation-how-long-does-it-take-and-why-i-see-some-old-version-of-my-site.html Just another WordPress weblog Tue, 02 Mar 2010 23:13:58 -0600 http://wordpress.org/?v=2.8 hourly 1 http://www.savagehost.com/dns-servers-name-propagation-how-long-does-it-take-and-why-i-see-some-old-version-of-my-site.html/comment-page-1#comment-3092 poebassm Mon, 06 Jul 2009 06:25:09 +0000 http://www.savagehost.com/dns-servers-name-propagation-how-long-does-it-take-and-why-i-see-some-old-version-of-my-site.html#comment-3092 ON your DNS server and on Your computer ... Open a DOS window and type IPCONFIG/FLUSHDNS . This will flush out the cached DNS information. ON your DNS server and on Your computer … Open a DOS window and type IPCONFIG/FLUSHDNS .
This will flush out the cached DNS information.

]]> http://www.savagehost.com/dns-servers-name-propagation-how-long-does-it-take-and-why-i-see-some-old-version-of-my-site.html/comment-page-1#comment-3091 Jamie W Mon, 06 Jul 2009 04:39:12 +0000 http://www.savagehost.com/dns-servers-name-propagation-how-long-does-it-take-and-why-i-see-some-old-version-of-my-site.html#comment-3091 It depends on how often your ISP changes there DNS tables. Try going out to a friends house, see if you can access your new site from there. it can take up to 48 hours for a site to propegate fully. It depends on how often your ISP changes there DNS tables. Try going out to a friends house, see if you can access your new site from there. it can take up to 48 hours for a site to propegate fully.

]]> http://www.savagehost.com/dns-servers-name-propagation-how-long-does-it-take-and-why-i-see-some-old-version-of-my-site.html/comment-page-1#comment-3090 127.0.0.1 Boy Mon, 06 Jul 2009 00:35:12 +0000 http://www.savagehost.com/dns-servers-name-propagation-how-long-does-it-take-and-why-i-see-some-old-version-of-my-site.html#comment-3090 Could be the site is cached on your computer or behind a server somewhere. Also, like the earlier poster mentioned it could be your host provider is just slower in updating key DNS parameters on the server. Post the link if it is OK and see if someone can see the difference..( you must let us know what to look for though) Could be the site is cached on your computer or behind a server somewhere.
Also, like the earlier poster mentioned it could be your host provider is just slower in updating key DNS parameters on the server. Post the link if it is OK and see if someone can see the difference..( you must let us know what to look for though)

]]> http://www.savagehost.com/dns-servers-name-propagation-how-long-does-it-take-and-why-i-see-some-old-version-of-my-site.html/comment-page-1#comment-3089 TechGuy Sun, 05 Jul 2009 21:40:23 +0000 http://www.savagehost.com/dns-servers-name-propagation-how-long-does-it-take-and-why-i-see-some-old-version-of-my-site.html#comment-3089 Make sure you are loading a new copy of the page. You may be loading cached data from your hard drive, clear out your Browser Cache first and then try again. If it has been two days you may want to contact your new host. DNS depends on several different things. You indicate you changed the "name servers". Do you mean you switched to a different hosting provider, or you changed the IP address of the website or you actually changed the name servers. If you changed the name servers, which commonly occurs when you switch hosting providers, a change like this could take from 48 to 72 hours. The following excerpt from a wikipedia article, the full url is below for your reference, is an excellent explanation of "DNS Propagation". ...changes to DNS do not always take effect immediately and globally. This is best explained with an example: If an administrator has set a TTL of 6 hours for the host www.wikipedia.org, and then changes the IP address to which www.wikipedia.org resolves at 12:01pm, the administrator must consider that a person who cached a response with the old IP address at 12:00noon will not consult the DNS server again until 6:00pm. The period between 12:01pm and 6:00pm in this example is called caching time, which is best defined as a period of time that begins when you make a change to a DNS record and ends after the maximum amount of time specified by the TTL expires. This essentially leads to an important logistical consideration when making changes to DNS: not everyone is necessarily seeing the same thing you're seeing. RFC 1537 helps to convey basic rules for how to set the TTL Make sure you are loading a new copy of the page. You may be loading cached data from your hard drive, clear out your Browser Cache first and then try again. If it has been two days you may want to contact your new host.
DNS depends on several different things. You indicate you changed the “name servers”. Do you mean you switched to a different hosting provider, or you changed the IP address of the website or you actually changed the name servers. If you changed the name servers, which commonly occurs when you switch hosting providers, a change like this could take from 48 to 72 hours. The following excerpt from a wikipedia article, the full url is below for your reference, is an excellent explanation of “DNS Propagation”.
…changes to DNS do not always take effect immediately and globally. This is best explained with an example: If an administrator has set a TTL of 6 hours for the host http://www.wikipedia.org, and then changes the IP address to which http://www.wikipedia.org resolves at 12:01pm, the administrator must consider that a person who cached a response with the old IP address at 12:00noon will not consult the DNS server again until 6:00pm. The period between 12:01pm and 6:00pm in this example is called caching time, which is best defined as a period of time that begins when you make a change to a DNS record and ends after the maximum amount of time specified by the TTL expires. This essentially leads to an important logistical consideration when making changes to DNS: not everyone is necessarily seeing the same thing you’re seeing. RFC 1537 helps to convey basic rules for how to set the TTL

]]>