Difference between revisions of "R4L/Services/Hosting/DNS/Caching"
(Created page with "== What is DNS Caching == When you visit a web site, your connection goes from your browser to your ISP, and from there through switches and finally to where the site is host...") |
|||
Line 3: | Line 3: | ||
When you visit a web site, your connection goes from your browser to your ISP, and from there through switches and finally to where the site is hosted. These servers and switches your connection goes through along the way save in cache memory where the services for your domain are. | When you visit a web site, your connection goes from your browser to your ISP, and from there through switches and finally to where the site is hosted. These servers and switches your connection goes through along the way save in cache memory where the services for your domain are. | ||
These servers will keep this saved information for a fixed period of time which can range from five minutes to potentially up to a week. The period of time DNS is cached should come from the TTL value given in the zone file for the domain. | These servers will keep this saved information for a fixed period of time which can range from five minutes to potentially up to a week. The period of time DNS is cached should come from the TTL value given in the zone file for the domain. | ||
− | + | <br /><br /> | |
== How DNS Caching can affect your updates == | == How DNS Caching can affect your updates == | ||
When you make a change in DNS for your domain, DNS caching can prevent your ability from seeing the update happen. DNS caching usually affects recent visitors to your site, but not most viewers. | When you make a change in DNS for your domain, DNS caching can prevent your ability from seeing the update happen. DNS caching usually affects recent visitors to your site, but not most viewers. | ||
+ | <br /><br /> | ||
== What you can do if you're experiencing DNS caching == | == What you can do if you're experiencing DNS caching == | ||
Line 13: | Line 14: | ||
The bad news is that there really isn't anything you can do in cases like this but wait. DNS caching is a practice that works very well most of the time, and helps improve performance on the Internet. The vast majority of your site's visitors will likely not be affected by this. | The bad news is that there really isn't anything you can do in cases like this but wait. DNS caching is a practice that works very well most of the time, and helps improve performance on the Internet. The vast majority of your site's visitors will likely not be affected by this. | ||
+ | <br /><br /> | ||
== Local DNS caching == | == Local DNS caching == |
Revision as of 12:42, 3 February 2015
What is DNS Caching
When you visit a web site, your connection goes from your browser to your ISP, and from there through switches and finally to where the site is hosted. These servers and switches your connection goes through along the way save in cache memory where the services for your domain are.
These servers will keep this saved information for a fixed period of time which can range from five minutes to potentially up to a week. The period of time DNS is cached should come from the TTL value given in the zone file for the domain.
How DNS Caching can affect your updates
When you make a change in DNS for your domain, DNS caching can prevent your ability from seeing the update happen. DNS caching usually affects recent visitors to your site, but not most viewers.
What you can do if you're experiencing DNS caching
You can try contacting your ISP to have them refresh their cached value. In our experience, most ISPs however will not do this for you.
The bad news is that there really isn't anything you can do in cases like this but wait. DNS caching is a practice that works very well most of the time, and helps improve performance on the Internet. The vast majority of your site's visitors will likely not be affected by this.
Local DNS caching
In some case, the caching happens locally. To learn how to clear your local DNS cache, go to this page.