Pieturli said:
Does the domain name get resolved at all? Open the command line and type in
ping escapistmagazine.com
See if it gives you back the IP. Note: when I tried it now, I wasn't getting any responses back, so you probably won't either but don't worry, as long as the domain gets resolved, ping shouldn't be a problem.
So, if you DON'T see it resolve the domain, then the problem is somewhere in the DNS. Since you said you've flushed the DNS cache, I assume that's your PC's - the modem/router might have its own cache. If that's the case, I'd actually suggest switching over your DNS to Google's one (8.8.8.8) or OpenDNS or something and see if that helps. Router DNS caches I've found to be an absolute pain if they don't work, as I had one in one occasion which persisted the chache throughout power cycling for some stupid reason. Thus trying to bypass it might be easier.
If you DO see the domain being resolved, then the issue is, most likely somewhere else. I'd suggest following that with
tracert escapistmagazine.com
which would trace the path to the website, i.e., will show you the route packets take when being sent off there. At some point they will probably be lost so this could give you a rough idea, e.g., do they even leave your ISP's network or not. Though, the problem is, that tracing is not always really reliable. A failure there could just be meaningless but at least it's a cheap test to see if your ISP is being honest (at least in this regard).
This should give you some sort of start - I (and others) can delve into more specifics if we rule out at least some areas.
One final question - you said you wrote this on your pone - is your phone on a mobile network or is it on the same network as your home PCs?