Jump to content

2 router


Hamburger
 Share

Recommended Posts

If you are pinging from your PC to your internal router, DNS does not come into the picture. Majority if not all home users do not need to resolve DNS within their internal network. You only need to resolve the DNS when you are trying to access external sites via domain names (mycarforum, yahoo ... etc).

 

High ping times could be due to a lot of factors. Is your router or server too busy to service your request? Is the network congested? Wireless does have a issue on this, esp when you are staying in a highly built up area as many people are transmitting using the default channel 6. You can download Netstumbler to detect the number of people using this channel.

 

For DNS settings, there is no need to download any 3rd party softwares to do it. As long as you know the IP addresses of the DNS servers, you can hardcode them into Windows. Or if you prefer to use dynamic IP assigned by your router, you can hardcode these addresses into your router. Most routers will allow you to specify a primary and secondary DNS address for use.

 

Actually it does affect. If you are like me and torrent a lot, the router is probably handling about 10,000 to about 16,000 simultaneous connections (inclusive of normal surfing alongside) Most of the time, you are using your own gateway as a relay DNS if you leave DNS settings as default. However the gateway is also burdened by having to serve as a conduit for all those simultaneous connections. I am seeing a chipset limitation here. My ping timings took a hit for sure. Once i designate another ip address as my primary DNS rather than using the relay DNS, my ping timings improved a hell lot.

 

Anyway, like i mentioned. i was doing an internal WLAN ping, client to access point. so if anyone experiences such an issue, no harm trying this out.

 

Also i feel it is a better idea for you to designate the DNS ip addresses in the gateway directly. it should override everything that is set at the client's side. Theoretically all that the WWAN sees your network is your gateway. Essentially 1x ip address. It is only with NAT that you manage to "share" your public ip address wiht all the domestic up addresses. So if the DNS setting is optimal for one of your client, it should be theoretically good for everyone in your WLAN.

Edited by Happily1986
↡ Advertisement
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...