| 1 |
On Tuesday 24 March 2015 06:52:58 Mick wrote: |
| 2 |
|
| 3 |
> Next time your router starts playing up, use nslookup and perhaps dig to |
| 4 |
> query your router's DNS repeater, your ISPs resolvers and any other 3rd |
| 5 |
> party DNS servers; e.g. openDNS, Google, or a DNS server from here: |
| 6 |
> |
| 7 |
> http://www.circleid.com/posts/20110407_top_public_dns_resolvers_compared/ |
| 8 |
> |
| 9 |
> so that you can draw comparisons to help you determine where the problem |
| 10 |
> lies. If it is your router, you can ask your ISP to replace it. |
| 11 |
> |
| 12 |
> If the ISP is not cooperating could perhaps run your own local DNS |
| 13 |
> resolver? |
| 14 |
|
| 15 |
I do that here. Dnsmasq runs on a little box on the LAN and speeds up the |
| 16 |
whole Internet experience. It didn't help though when my router started |
| 17 |
misbehaving, as it still had to forward some queries and the router sat on |
| 18 |
those. |
| 19 |
|
| 20 |
It was simple enough to reboot the router, once I'd found that was needed. |
| 21 |
|
| 22 |
-- |
| 23 |
Rgds |
| 24 |
Peter. |
Archives