If Azure's suggestion didn't solve it, you can use the nslookup command to help troubleshoot the problem. Click on Start -> Run -> cmd to start a command prompt, then type in...
nslookup - <your DNS IP address here>
...and press enter. You'll get a ">" prompt. Type in a domain at the prompt to test whether the DNS server you're querying returns a response. Here's an example...
C:\>nslookup - 208.67.222.222
Default Server: resolver1.opendns.com
Address: 208.67.222.222
> google.com
Server: resolver1.opendns.com
Address: 208.67.222.222
Non-authoritative answer:
Name: google.com
Addresses: 74.125.155.103, 74.125.155.104, 74.125.155.99, 74.125.155.147
74.125.155.106, 74.125.155.105
>
Type "exit" at the prompt when done. Do this when you're having the internet problem. If you don't get a successful query from your current DNS server, then try one from Azure's post. By using two DNS servers your results should tell you if you have a global problem with DNS or if it's just limited to one server.
But if power-cycling your router fixes the issue temporarily, I'm guessing it's on the way out. I had to power-cycle my old Linksys router once in a while to keep the 'net flowing. Check for firmware updates and make sure it's not overheating...
|