Chrome gets stuck on "server DNS address could not be found" if I tried to access a domain while connecting

This happens to me quite a lot, and I'd like to know if there's a way to prevent it or a better way to fix it than restarting my computer. The circumstances are very different to existing questions like “DNS server address couldn't be found” for some websites; it goes like this:

1. I tu on my computer (Windows 8.1) and inteet router (which is either a 3G mobile router that I'm waking up from sleep, or a normal wireless router and modem that isn't on all the time because I'm in a country where there isn't power all the time)
2. I connect to the inteet, see the "connected" icon show and open a web page...

3. ...however, I sometimes misjudge it slightly, and try to access a web page a second or two before the router has completely finished starting itself up. It gives this message in Chrome:

   This site can’t be reached

   some.domain.com’s server DNS address could not be found.

   DNS_PROBE_FINISHED_NXDOMAIN

   ...with "reload" and "details" buttons, neither of which do anything.

   This is fine, it's presumably because I attempted to access a web page before the router/modem hadn't yet fully connected to the inteet.

4. The problem is, it then gets stuck for this domain:

   • Any attempt to access this domain then gives the same error, even after I'm fully connected and can access any other site
   • Other domains work fine, and this domain works fine in other browsers (e.g. Firefox)
   • Closing and re-opening Chrome doesn't fix it
   • Toggling whether the domain uses https or www. doesn't make any difference

For example, just now, I tried to open a web page slightly too early, and Chrome's DNS got stuck. I'm writing and posting this question in Chrome, in a different tab, and it's working fine. I still can't open that other web page in Chrome, but I can in Firefox.

It's like it only tries once, caches the result, and won't retry even if I use the "reload" button on the error page. Sometimes the domain works after a long period of time (30 mins?)

Is there any simple way to make it retry the DNS that is more convenient than rebooting the computer or waiting a long time?

Recent Questions...