Are you sure? <br /> <br />Modems don´t cache anything. Routers only cache traffic data. <br /> <br />What may be the case is that you experienced DNS lag from moving your site. When moving hosts, the DNS (database that translates domain names into actual server adresses) gets updated and since DNS is a distributed system, it can take up to 48 hours before everyone ends at the new location.
adni18
Member
Yes, listen to our friend <b>craeonics </b> , he is always right! <br /> <br />Hey crae! :)
adni18
Member
Though, sometimes modems or routers are getting crazy. <br />A restart or the settings back to default and re-configuration is always a good solution, if you are facing problems.
clwoods
Member
Thanks, that is very interesting.Was it just a coincidence then that it was set right after rebooting or did the rebooting actually update the lag? :Happy
craeonics
Member
I think it´s a coincidence. But you never know. Like our resident mad Greek said, routers and modems can crash at times. Usually due to heat issues and/or too many connections at the same time (which is something you´ll only run into when using P2P apps). A reboot once in a while is always healthy. <br /> <br />If you´re moving your site and still see the old one, it´s usually one of these factors: <br />1. DNS lag of your ISP (as said, can be up to 48 hours) <br />2. DNS lag of Windows (Windows caches these things too, but it has never caused any problem for me) <br /> <br />If you´re updating your site and don´t see changes: <br />1. Browser cache <br />2. ISP (proxy) cache, meaning that your ISP caches frequently requested pages (if your ISP uses proxies, it´s time to switch) <br />3. Intranet proxy cache somewhere in your network. Usually pop up in big corporations with idiot system administrators. <br /> <br />Proxy caches fortunately are rare occasions, leftovers from when everyone was on dial-up. Although... Countless are the times where I´ve called a (government or big corp) client to tell them I updated their site and got the response "I don´t see any changes". After walking through the "empty your browser cache"-steps, I finally tell them to tell their sysop to remove site X from the proxy cache and lo and behold, they can suddenly see the changes.
Edited
clwoods
Member
That is a lot of information and I thank you very much. After reading it, I still do not know for sure which one of those things caused it, but I am glad it is fixed. The sites are current and running very well on our new serverl! :Happy
