It could be a caching issue. Maybe your PC was using your router as a dns server and it cached that example.com didnt resolve. Or maybe your own PC cached it. I'm thinking your cell phone probably used another dns server. On your PC, you could've tried to speed it up with
ipconfig /flushdns to force it to query the dns again and hopefully get an authoritative answer.
It was a problem with Chrome caching the DNS. To fix:
chrome://net-internals/#dns and click "Clear host cache."
chrome://net-internals/#sockets and click "Close idle sockets," "Flush socket pools."
Source: https://superuser.com/q/203674/4390
|
|
|
|