Occasionally (every 4 or so hours) my router loses DNS connectivety
(or the ability to forward my dns inquires). This only seems to happen
when I am downloading torrents, so I assume it is related. I use
"uTorrent" as my client. I've experienced this same phenomenon on
three different types of routers now over the past year or so. It's
something I've battled with quite a few times.
If anyone else has experience with this specific problem (routers
+torrents=dead dns) I'd love to hear your thoughts! Am I just
overwhelming these puny cheapo $30 routers? I read something about the
router NAT tables getting overwhelmed then disrupting DNS, anyone have
more info about this? Will a better router solve my problems?
More Details:
- I'm not a complete moron (meaning: the router is plugged in & turned
on, etc etc!)
- On the router(s) I set port forwarding correctly for the torrent
software.
- This loss of DNS connectivety affects all LAN computers at the same
time, regardless of if they are wired or wireless.
- It happens every 1-10 hours randomly, usually when the router is
under a fair amount of stress (overheating???).
- All computers retain LAN and WAN conectivety; meaning I can still
connect to my shared folders & my torrents are still moving.
- Running NSLOOKUP from dos confirms there is no DNS connectivety.
- I cannot connect to the router via the browser when this is
hapenning
- I've experienced this on 3 different routers: a DLink WBR-1310
Wireless, a Gigafast WF719-CAPR Wireless, and some unknown 4 port
Dlink wired.
- Note: all three routers were "cheapo" models.
- Main computer is running Xp Home and the torrent software.
- I have tried both dynamic and static IPs and DNS settings on the Xp
Home machine.
- I have tried both Zonealarm and Sygate Firewalls. I dont use WinXP's
Firewall. I've tried disabling all firewalls completely.
- I have tried lowering the maximum amount of connections uTorrent can
make, down to 20.
Below are two similar (unsolved) posts I found on google:
http://tinyurl.com/2fqkpg
http://tinyurl.com/262m35
Any thoughts would be appreciated. I'd like to know exactly what's
happening here.