|
I know something about this. Sounds like you're talking about your home wifi and a problem with your router. And that an apparent dns issue is being resolved by rebooting your router.
DNS is internet address resolution. The rough idea is to translate the text names of internet addresses into a numeric ip address. Its a distributed system, lots of moving parts, but generally it works well.
Roughly it works like this: when you make a request to the internet your computer checks its dns cache, if it believes it has the address already it will uses that, otherwise network request goes to your wifi router, if router cache can't serve your request then router sends request to your providers dns server, etc...
What is probably happening in your case is that your router has a s**t-a** implementation of dns and is crashing.
I've run into a bunch of routers whose internal dns code is rife with bugs and errors. The routers worked fine with some old slow devices but can't handle cases exposed by newer devices and software.
There are a set of belkins that whose dns will crash if you use them with ipads. There are some other old routers that would crash if you gave them too many dns queries in a row. Is stunning to me that this is so difficult to get right. Its been more than 10 years and companies still struggle with this.
Chrome and IE browsers do DNS prefetching as part of page load, they speculatively scan each page and query dns for all urls. This can mean 400-1000 dns queries within a few ms and that causes crappy routers to crash their dns.
Your first solution is to check if there are updates to your router software. If nothing or it it doesn't fix then buy a better router. Probably any modern unit will be good. I have been really happy with mikrotik but I've heard some people think the setup is difficult.
|