D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: supraman on May 06, 2008, 10:39:32 AM
-
Hello, I tried searching but I couldn't find anything.
I am having a VERY annoying problem. I have OptOnline's Boost line so my speeds are 30/5 Mbps.
Latency and Bandwidth are fine. When I am directly connected to the cable modem, I am still pulling the same amount of data and I can ping certain IP's at the same speeds.
My problem 'seems' to be resolving DNS entries. I've tried using 192.168.0.1 from my PC as a DNS entry.
I've tried using OpenDNS IP's from my PC as DNS Entries, and I tried using the DNS's provided from my ISP on my PC.
I Can not change the DNS entries on the Router to an OpenDNS IP as there is someone in my house that gets a work VPN IP unable to connect.
Sorry if that seems confusing, but I will sum it up here.
With/Without Router = Bandwidth & Latency are the same
With Router - EVERY LINK I click on takes a 3-4 second pause before beginning to pull the data.
Without Router - EVERY LINK I click on begins pulling data immedietly.
I will post some information when I get home, with and without the router from HTTP Watch Basic.
But does anyone else have this similar problem.
I've also changed the WAN side speed to 100 Mbps instead of Gbps
These are ALL WIRED connections.
NO QoS enabled.
ISP = Optimum Online Boost 30/5
Cable Modem = Not sure of at the moment
****
Reading up on some other stuff. Going to try and mess with transmission rates. I believe I am using a Realtek Onboard Gb NIC.
Always forget to do the simple stuff because it usually always works out of the box.
-
Does the QoS page report your upstream properly?
-
I have the same problem, DNS takes ~5 seconds to resolve every time when I use the router as my DNS server with DNS relay.
When I query my ISP's DNS server directly, it is instantaneous.
The DNS relay returns the right results, it just takes a long time.
Anybody know what's going on?
-
I have similar problem with my newdir 655 purchase with 1.21 firmware.
The problem for me is, valid name return quickly, but if you ask for non-existing domain( for example, you type http://dfafa.fawfaw.cawea) it take like 1 min to return saying not found.
is there some config to change?
-
correct. its a dns problem. Some comcast dns servers are severely old or so bogged down, it takes time for them to query the dns entry.
You may want to try openDNS. Extremely fast dns server.
if your using your router. set its primary and secondary dns address to
208.67.222.222
208.67.220.220
you'll notice a difference.
-
correct. its a dns problem. Some comcast dns servers are severely old or so bogged down, it takes time for them to query the dns entry.
I am using Comcast, but their DNS servers are plenty fast if I query them directly. It's only when using the router's DNS relay that things are slow. That points to a problem with the router, not the DNS server.
-
DNS relay is going to cause DNS lookup down. You're adding extra work for the router to handle.
-
DNS relay is going to cause DNS lookup down. You're adding extra work for the router to handle.
DNS relay should not make DNS requests take 4+ seconds. The 5 year old router I replaced does DNS relay with no noticeable delay. Plus, I can set up my server to act as a caching DNS relay without introducing a delay.
This is clearly not correct behavior.
-
Hmm, there's something else going on there.
What happens id you don't use the ISP DNS's?
-
Hmm, there's something else going on there.
What happens id you don't use the ISP DNS's?
If I use the OpenDNS servers suggested earlier in the thread, DNS relay works effectively instantaneously. So the router is behaving differently when connecting to different DNS servers.
However, as I said, I am able to query Comcast's DNS servers directly and they respond quickly. The router should be able to work with Comcast's DNS servers without introducing a delay.
-
Ping the DNS servers. Look at the reply times.
-
Ping the DNS servers. Look at the reply times.
I'm telling you, the DNS servers respond just fine when I query them directly. It's only when accessing them through the router's DNS relay that there is a delay.
C:\>ping 68.87.69.146
Pinging 68.87.69.146 with 32 bytes of data:
Reply from 68.87.69.146: bytes=32 time=20ms TTL=57
Reply from 68.87.69.146: bytes=32 time=17ms TTL=57
Reply from 68.87.69.146: bytes=32 time=17ms TTL=57
Reply from 68.87.69.146: bytes=32 time=16ms TTL=57
Ping statistics for 68.87.69.146:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 20ms, Average = 17ms
-
Let him troubleshoot, will ya.
-
Odd though, how could a router cause lag in DNS resolution on just one set of specific DNS servers?
What kind of speeds are you supposed to be getting from you ISP?
-
Odd though, how could a router cause lag in DNS resolution on just one set of specific DNS servers?
What kind of speeds are you supposed to be getting from you ISP?
It's certainly odd, yes :)
I get 22 Mbps down/2 Mbps up (measured).
Digging deeper, it seems like the router actually isn't responding at all on the first or second try, when the DNS client retries for the third attempt, it finally gets an answer. The timeout is normally 2 seconds, which explains why the results always take ~4-5 seconds to come back - it's because the first two tries burn 2 seconds each. When the router's DNS relay finally does respond, it does so quickly.
I wonder if the first two queries are failing on their way out or on the way back in...
C:\>nslookup
DNS request timed out.
timeout was 2 seconds.
Default Server: UnKnown
Address: 192.168.1.1
> set timeout=1
> www.cnn.com
Server: UnKnown
Address: 192.168.1.1
DNS request timed out.
timeout was 1 seconds.
DNS request timed out.
timeout was 1 seconds.
Non-authoritative answer:
Name: www.cnn.com
Addresses: 157.166.226.25
157.166.226.26
157.166.224.25
157.166.224.26
> set timeout=20
> www.cnn.com
Server: UnKnown
Address: 192.168.1.1
DNS request timed out.
timeout was 20 seconds.
DNS request timed out.
timeout was 20 seconds.
Non-authoritative answer:
Name: www.cnn.com
Addresses: 157.166.226.26
157.166.224.25
157.166.224.26
157.166.226.25
> server 68.87.69.146
Default Server: cns.beaverton.or.bverton.comcast.net
Address: 68.87.69.146
> www.cnn.com
Server: cns.beaverton.or.bverton.comcast.net
Address: 68.87.69.146
Non-authoritative answer:
Name: www.cnn.com
Addresses: 157.166.224.26
157.166.226.25
157.166.226.26
157.166.224.25
-
Try this.
Swap the two DNS servers manually. Set the Primary as secondary and vise versa.
-
Try this.
Swap the two DNS servers manually. Set the Primary as secondary and vise versa.
Same result. :(
-
Weird.
I'd just use the OPENDNS ones for now. I'll see what I can dig up.
-Anyone else having problems like this?
-
Weird.
I'd just use the OPENDNS ones for now. I'll see what I can dig up.
The OpenDNS servers are no good, because if they don't find a name they return an OpenDNS web server address instead of "not found".
This interferes with my ability to access other computers in my home, because trying to connect to "MYCOMPUTERNAME" results in me being connected to OpenDNS.
-
I'll see what I can dig up.
BTW, I don't mean to sound ungrateful - thanks for trying!
-
Ahh,
Well then you want an internal DNS server anyway. Hopping your entire LAN DNS resolution outside then back in for name resolution is not the best.
Are you running a domain?
-
Ahh,
Well then you want an internal DNS server anyway. Hopping your entire LAN DNS resolution outside then back in for name resolution is not the best.
Are you running a domain?
No, if DNS resolutoin fails, NetBIOS name resolution kicks in. OpenDNS prevents NetBIOS resolution from having a chance to work.
-
LOL. yea your kinda stuck. What downgrading the firmware? Any effect?
-
I posted about something similar to this - Issues with 1.20 firmware (http://forums.dlink.com/index.php?topic=2547.0)
Going back to 1.11 solved it for me.
-
I posted about something similar to this - Issues with 1.20 firmware (http://forums.dlink.com/index.php?topic=2547.0)
Going back to 1.11 solved it for me.
PAgefault, does this work for you?
-
The OpenDNS servers are no good, because if they don't find a name they return an OpenDNS web server address instead of "not found".
This interferes with my ability to access other computers in my home, because trying to connect to "MYCOMPUTERNAME" results in me being connected to OpenDNS.
If you create an account with OpenDNS, they allow you to add internal names such as "MYCOMPUTERNAME", which when you try to look up via DNS will not resolve but will return it back to your NetBIOS to handle. See their step-by-step info here:
http://www.opendns.com/support/article/148
Sounds like you might be looking for that feature?
-
Sweet. I did not know that, I'm going to try it.
-
I am having the exact same problem. When I was using the 1.11 bios everything was working great. I switched to 1.21 with securespot enabled and I started seeing this 3-4 second delay on all web pages but my download speeds and ping time where unchanged. I thought maybe the securespot filtering system might have been overloaded and slowing me down, but I just switched to the OpenDNS servers and now my internet page responses are back to where they used to be. Oh, and I have Comcast as my internet provider. 15mb down and 1.5mb up. Like I said throughput is fine it's just navigating to a new page that is painfully slow!
-
If you create an account with OpenDNS, they allow you to add internal names such as "MYCOMPUTERNAME", which when you try to look up via DNS will not resolve but will return it back to your NetBIOS to handle. See their step-by-step info here:
http://www.opendns.com/support/article/148
Sounds like you might be looking for that feature?
That does make it better, but I still don't like the idea that OpenDNS will return a result for addresses that don't exist. I know that's a "feature" for them, but I really don't like it.
-
PAgefault, does this work for you?
I have to confess, I actually don't have a DIR-655...I have a DIR-825.
I suspect the software on the DIR-825 is almost identical to the DIR-655 software, the main difference is the second radio. It makes sense that the DIR-825 and the DIR-655 are having the same DNS issue.
Unfortunately, this means I have no older firmware to downgrade to.
-
Here guys.
http://forums.dlink.com/index.php?topic=2737.0