Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[saldlink]

I recently bought a DIR-825 and I find that when the DNS relay feature is turned on, Windows clients seem to have problems querying DNS. The first thing it looks like Windows tries to do is a reverse lookup on the DNS server itself. This seems to fail. In fact, it looks like I get two errors (timeouts) and then finally a response to the actual query. The output suggests a name of "UnKnown" for the DNS server. This seems to add an unacceptable delay to general web access where the browser often sits there resolving names.

Linux seems to tackle it differently by saying the name is 192.168.0.1 and the address is 192.168.0.1#53 and I don't encounter the issue on my Linux PCs.

Anyone know what the issue is, or a suitable workaround? I have read on other forums that in order to effectively disable the DNS relay, one also has to disable the auto bandwidth test. I have also hit this bug where the initial LAN clients don't get their addresses. Since I have some devices always on, this is an issue for me also.

What, in general, does the DNS relay add? Is it able to dynamically add local clients to the DNS table and perform name resolution for them?

[funchords]

I recently bought a DIR-825 and I find that when the DNS relay feature is turned on, Windows clients seem to have problems querying DNS. The first thing it looks like Windows tries to do is a reverse lookup on the DNS server itself. This seems to fail. In fact, it looks like I get two errors (timeouts) and then finally a response to the actual query. The output suggests a name of "UnKnown" for the DNS server. This seems to add an unacceptable delay to general web access where the browser often sits there resolving names.

Is that using NSLOOKUP?  If so, that's an effect of NSLOOKUP.  It does report the RDNS of the DNS server before it outputs the DNS output of the query. 

Anyone know what the issue is, or a suitable workaround? I have read on other forums that in order to effectively disable the DNS relay, one also has to disable the auto bandwidth test. I have also hit this bug where the initial LAN clients don't get their addresses. Since I have some devices always on, this is an issue for me also.

Despite all of the reports made to date, D-Link still can't reproduce the issue and so nobody is working on it!  See http://forums.dlink.com/index.php?topic=2737.0  -- and please add to the volume. 

What, in general, does the DNS relay add? Is it able to dynamically add local clients to the DNS table and perform name resolution for them?

I do think that some of the website limiting and logging capabilities might require DNS Relay.  I don't use those features.  With DNS relay, you only need to configure one thing if you want to change your DNS setting for your entire network.  Beyond that, if it's supposed to provide some value-added feature, it's lost on me.  As implemented, it adds a 15-20 second delay to anything that results in a failed query along the way.

One workaround is to use OpenDNS -- since even their failed queries resolve to an IP address, you'll never see a delay.   This has other side-effects, however, such as the lack of being able to fail-over to other methods like WINS or mDNS.

[saldlink]

Thanks for the reply funchords. Yes, the issue is with nslookup on Windows. I started trying to manually query using nslookup as I was experiencing what seemed to be slowdowns when initially loading websites. It seemed the browser would 'hang' while looking up addresses, and then proceed quickly once the DNS address was cached up.

I too, like yourself, don't use the website limiting/logging features, so I might try by turning DNS relay off and see if that improves things.

I tried both the D-Link and the Linksys routers, and in my home, the D-Link was consistently faster (Wi-Fi LAN performance), so I would like to stick with it.