I had the same issue this morning, but later it resolved itself.
I hadn't seen Jeff's message before, but it makes sense why one would work versus another. Every web site name (aka "domain") has a numeric address behind of it (very loosely like towns and zip codes- it's easier to remember, "York, PA" instead of "17406"). There is a domain name (i.e. Forest River Forums - Forest River Owners Community
) maps to a set of numbers (in this case, 220.127.116.11). The servers and hardware of the internet works off of these numbers whereas we people generally use the names.
Because it takes time for your computer, phone or tablet to do the translation (aka "name resolution") from name to number when you enter in Forest River Forums - Forest River Owners Community
, this name resolution gets cached in a variety of places (your phone/tablet/computer itself, the router that connects you to Verizon, Comcast or other Internet provider, their servers and beyond). It's to help things be "more quick".
The problem comes when you switch the IPs behind the scenes which is exactly what it sounds like Social Knowledge did - they likely moved servers. It takes a period of time for the switch to occur in each device that handles name resolutions. Sometimes it's a set period of time, "this *remembered* record expires in 2 hours from this point in time" and sometimes it's a rolling period of time, "this *remembered* record expires 2 hours after the last time that it was used". (The 2 hours part is even configurable- each device decides how long it should live.)
It's that rolling timeout that can be problematic. If it's not working for you on your phone and you keep trying, that 1 to 2 to 24 hours can keep getting extended.
What Jeff recommended earlier was to flush your DNS caching. The problem is, the command that he provided was specific to Microsoft Windows. You might try restarting your devices and see if it helps. Otherwise, you can also reset network settings- I'm just not sure what side effects that has:
Oh, and you Android users - I'm of ZERO help there. Here's a Google search that might help (the first Stack Overflow article seems to indicate that restarting may help you, too):