WFUtoUSC
Well-known member
- Joined
- Mar 17, 2011
- Messages
- 1,671
- Reaction score
- 110
ACCSports.com wrote an article about how ridiculous of a gaffe it was by media relations.
Psssh. Hope ACCSports enjoyed their WF credentials while they had them.
ACCSports.com wrote an article about how ridiculous of a gaffe it was by media relations.
ACCSports.com wrote an article about how ridiculous of a gaffe it was by media relations.
Dozens of readers will be appalled.
Still not working for me.
If it was just this one thing, it would be no big deal, but it seems like we have a couple of amateur hour gaffes a year.
Anybody remember the lack of concessions at some of the early football games this year?
ACCSports.com wrote an article about how ridiculous of a gaffe it was by media relations.
In all seriousness, it was working for me earlier on this computer and now it's not. Mobile isn't working either.
ACCSports.com wrote an article about how ridiculous of a gaffe it was by media relations.
Finally working for me today. Cleared my cache several times yesterday, never did work?
Not sure whose fault it is...word I heard was IMG, but I am 100% sure it was not media relations.
ACCSports.com wrote an article about how ridiculous of a gaffe it was by media relations.
For the record, it's usually not a web browser cache thing in this case or anything on your computer really, it's DNS caching. When you fail to renew a domain the hosting site alters the DNS record (what IP the domain resolves to) which is hosted on DNS servers all over the world. Eventually it'll filter down to all the ISP's and your computer will start resolving the new location. This is why some people were seeing the broken site and others were still seeing the Wake one for a while. Same happens in reverse.
Additionally many companies and ISPs have Edge Routers or what some call Internet Accelerators. They'll store web sites and pages and only check for reload if there are changes in page content or DNS records - otherwise they won't pull data from the internet they'll just serve up their cached data (saves money and bandwidth). Because DNS record updates are rare, many only check once a day.
Google's DNS servers are actually public. If your ISP sucks (or you suspect it sucks) you can always point to 8.8.8.8 and 8.8.4.4 as a gold standard of DNS. For most this is a manual update on their router, not an individual computer, assuming you want the change to apply everywhere on your network.
If it was just this one thing, it would be no big deal, but it seems like we have a couple of amateur hour gaffes a year.