Print

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

[twizeek]

I am working with a customer who has a DIR-825.  I have encountered nothing but headaches with its configuration (or lack thereof), but let me focus on the showstopper.

I found another thread on this topic, but no working solution was ever posted.  Specifically, the issue with DNS is that the local DNS suffix is being appended to all FQDNs (or sometimes the ISP's, its quite random).

I have tried resetting the router's configuration back to stock, no dice.  Per the other thread, tested with Advanced DNS Services and DNS Relay both on and off, no change.  I have manually set a local domain, with no change.

This appears to be a SERIOUS issue with the software.  It has completely soured me to D-link products, as decent QA testing should have caught this.  D-link is forcing their customers to beta test software for them, which is utterly unethical.

My current solution is simply to configure each PC on the customer's network with a valid DNS server; unfortunately, this is NOT an acceptable solution because any newly connected device must be manually configured, totally negating the purpose of DHCP.

While I'd like to see a solution posted here to help anyone else who may be encountering this problem, I will likely have the customer replace this steaming brick with an Asus WL-500g; a router of superior specifications, performance, and build quality.  I have sworn by D-link products for years in the SMB environment, but will seriously reconsider their products in future, due to this glaring quality control issue, along with several others I've recently encountered, not limited to CHEEEEAP internal components and shoddy construction.

[user11]

only happens when DNS relay is off, correct? you can set DNS server(s) manually in internet setup, this solves the DHCP, DNS handout issues seen in vista and 7, doesnt seem to affect xp clients tho. now you don't have to worry about DNS breaking while using DHCP...yay!

[bkspero]

only happens when DNS relay is off, correct?

I believe that the OP wrote that it happens with either DNS relay on or off.

"Per the other thread, tested with Advanced DNS Services and DNS Relay both on and off, no change.  I have manually set a local domain, with no change."

The OP is already on the way to the ultimate fix.

[user11]

I believe that the OP wrote that it happens with either DNS relay on or off.

"Per the other thread, tested with Advanced DNS Services and DNS Relay both on and off, no change.  I have manually set a local domain, with no change."

The OP is already on the way to the ultimate fix.

Have a look at his solution,

My current solution is simply to configure each PC on the customer's network with a valid DNS server; unfortunately, this is NOT an acceptable solution because any newly connected device must be manually configured, totally negating the purpose of DHCP.

I was merely solving the error in his approach. Many others could also benefit by it, so don't shoot the messenger...

[slavanaway]

Did this get resolved? I didn't see twizeek respond.

[lotacus]

You absolutly right.

I tried several things as well. On the DIR-825's setup page for the domain name it won't let me put a domain. Every time I try something like river.com river.local river.edu river.whatever it will spit an error saying that the domain is invalid. It will only let me put "river". What I guess is that it's hardcoded with .local since when I put in "river" windows shows the domain as river.local.

To furthar validate this claim, I connect to my PFSense server, or even to the the Windows Server DC and the FQDN will display properly.

If I set the domain on my dir-655 (which works!) and connect to the dir-655, I will get the FQDN as it's supposed to be.

So no, this issue will not be fixed until dlink decides it warrants fixing.

[bkspero]

Have a look at his solution,  I was merely solving the error in his approach. Many others could also benefit by it, so don't shoot the messenger...

Sorry User11 if my note came across as disrespectful of your intentions.  I did not mean to do that, but instead wanted to point out that he had tried that portion of the suggestion.  We all appreciate the effort that the user community is making to compensate for the shortcomings of dLink and this product.

[user11]

Sorry User11 if my note came across as disrespectful of your intentions.  I did not mean to do that, but instead wanted to point out that he had tried that portion of the suggestion.  We all appreciate the effort that the user community is making to compensate for the shortcomings of dLink and this product.

No worries, just wanted to point out a solution I had found concerning similar circumstances, however I don't work with nor have too much experience with local domains, so I may have hijacked the thread some, for that I apologise. D-link has been trying to address the DNS-relay problems, maybe they don't know about the broken functionality of DHCP when DNS-relay has been turned off which many have had to do for stability for some time now. Hopefully for the customer base and our sake they will notice these relative broken DNS features that can be fixed in an upcoming firmware release. How do we get their attention about it?

[twizeek]

You absolutly right.

I tried several things as well. On the DIR-825's setup page for the domain name it won't let me put a domain. Every time I try something like river.com river.local river.edu river.whatever it will spit an error saying that the domain is invalid. It will only let me put "river". What I guess is that it's hardcoded with .local since when I put in "river" windows shows the domain as river.local.

To furthar validate this claim, I connect to my PFSense server, or even to the the Windows Server DC and the FQDN will display properly.

If I set the domain on my dir-655 (which works!) and connect to the dir-655, I will get the FQDN as it's supposed to be.

So no, this issue will not be fixed until dlink decides it warrants fixing.

Unfortunately, DNS via WHS does not work either, even after trying your domain w/o '.local' trick.  The DNS server on the D-link still adds extra server information on to every link.  This is the case either via nslookup or through any application, on the server, and on each of the client PCs.

When I reconnected the customer's old router, then refreshed each client/the servers DHCP addresses, voila, the DNS problems are GONE! (The old router has an unrelated issue and still needs to be replaced.)

I've also come to find that manually setting the DNS servers, either manually or with WHS DHCP, breaks the WHS' ability to offer services.  WHS offers many of the services and features one would expect from a Windows Server 2003 network, but it does not actually create or operate a domain.  Everything is handled via proprietary software through a workgroup.  Remote access will suddenly cease to function, authentication intermittently doesn't work, and of course, I still have the original DNS issue.

I'm a little shocked as to why I should expect to tolerate such behaviors from a router my customer PAID for.  ESPECIALLY when the issue is CLEARLY the fault of the router.  Being told that D-link will simply ignore the issue seals the deal for me: I will never, in good faith, EVER purchase another D-link product again.

[user11]

for the record, what firmware revision on the 825 are you using?