Problem using Google DNS

[Freakazoid]

I've had my RT-AC68U for about two years now, and I've used Merlin's firmware, as well as Google's DNS since day one with zero problems until now. Since last week, I've had occasional DNS issues crop up on all of my devices. It comes and goes in less than a minute, and affects any site it pleases.

I've run through several troubleshooting options such as flushing the DNS cache, rolling back firmware, rebooting the router, even doing a factory reset before simply trying to connect to DNS server automatically. That seems to solve the issue, as it hasn't popped up in the last 24 hours.

I would like to continue to use Google's DNS, as it's faster than my ISP's for things like the Playstation Network. This is a bit baffling to me, because it just started happening out of the blue, and I haven't seen anyone else complain about having similar issues lately.

 

[thelonelycoder]

Your nearest google server may have issues.
Anyway, read this:

Google's DNS server information page:

Note, however, that because nameservers geolocate according to the resolver's IP address rather than the user's, Google Public DNS has the same limitations as other open DNS services: that is, the server to which a user is referred might be farther away than one to which a local DNS provider would have referred. This could cause a slower browsing experience for certain sites

 

[CaptainSTX]

I've had my RT-AC68U for about two years now, and I've used Merlin's firmware, as well as Google's DNS since day one with zero problems until now. Since last week, I've had occasional DNS issues crop up on all of my devices. It comes and goes in less than a minute, and affects any site it pleases.

I've run through several troubleshooting options such as flushing the DNS cache, rolling back firmware, rebooting the router, even doing a factory reset before simply trying to connect to DNS server automatically. That seems to solve the issue, as it hasn't popped up in the last 24 hours.

I would like to continue to use Google's DNS, as it's faster than my ISP's for things like the Playstation Network. This is a bit baffling to me, because it just started happening out of the blue, and I haven't seen anyone else complain about having similar issues lately.

1. From the command line run an ipconfig /all and confirm what your DNS server is

2. If you are selecting your DNS servers using your router select another DNS server other than Google for your number 2 choice.

3. Run a ping plotter to your number 1 DNS choice for an extended period and see what it shows.

 

[Freakazoid]

1. From the command line run an ipconfig /all and confirm what your DNS server is

2. If you are selecting your DNS servers using your router select another DNS server other than Google for your number 2 choice.

3. Run a ping plotter to your number 1 DNS choice for an extended period and see what it shows.

I've been pinging 8.8.8.8 for several minutes now, and got 'Request timed out' for just one line so far. I'm using whatever DNS my ISP uses, and I typically set that up in the router. Like I said, things have been fine since I set it to connect to DNS server automatically.

 

[Freakazoid]

I've been monitoring pings for the past few hours from my router, modem, Yahoo.com, and Google's 8.8.8.8 address that you suggested. I see nothing weird coming from the router or modem, but I get an occasional 'Request timed out' message in the lines for Yahoo and 8.8.8.8, and some random spikes in 'time=__ms'. The timed outs seem to happen about as often as the issues that would pop up when the router was set to Google DNS, and don't seem to happen at the same time between the two. Strange.

edit: Ok, after spending more time using my ISP's DNS, it seems like the problem might still be happening. Not as often, and it seems to resolve itself quicker.