D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: Lycan on June 29, 2009, 03:55:08 PM
-
Trying to get an idea of the number of people that were able to resolve lock ups by disabling DNS relay.
-
Not sure if this counts but turning of DNS Relay did fix a Call of Duty 4 game issue I was having.
Basically with DNS Relay turned on whenever I would launch the game it would take at least 30
or more seconds to load it. I just turned it off and now the game loads instantly like it used to
under my old router.
EDIT: Okay this is odd or maybe I'm just not understanding something. I have DNS Relay turned off now and have manually put in the DNS servers on my LAN computers. But when my wireless computers connect to the network they act like DNS Relay is turned on. At this point if i remove the DNS server addresses from my LAN computers they still connect but not to the DNS servers I manually entered. When I check the routers network page DNS Relay is in fact turned off. Is this normal behavior or am I missing something here?
Rift
-
Considering the number of people in the freezing thread said that it worked for them, I am kind of surprised by the results of this poll.
Maybe freezes and stuff. All I know is that I ran on 1.11 with an uptime of over a month. I couldn't get more than 3-4 days on 1.31 with dns relay enabled.
-
So anyone have any idea if what I wrote in my Edit is normal behavior? Is DNS Relay turning back on somehow even how its not checked off in the router options, or am I just missing something?
-
Considering the number of people in the freezing thread said that it worked for them, I am kind of surprised by the results of this poll.
Maybe freezes and stuff. All I know is that I ran on 1.11 with an uptime of over a month. I couldn't get more than 3-4 days on 1.31 with dns relay enabled.
DNS relay enabled, disabled makes no difference here: no crashes and an uptime of three weeks (since upgrading to 1.32beta)
-
1.32 beta02 NA after disabling DNS Relay and automatic Update DIR655 Rocks! 3 weeks of continuos work without any issue!!
-
I've been running version 1.2x (I forget which beta) for quite some time now.
However, I've got DNS relay disabled, as well as DHCP server, since I've got a linux box in my network handling DHCP, which also services DNS requests from network clients (rather than the '655), the DHCP/DNS server also bypasses the '655 by using a list of static DNS servers provided by my ISP.
The router only goes down when we lose power (in its current configuration).
Note that the seeming insanity of the setup was brought on by the need for gigabit router (the 655), -AND- working reliable DNS services (which I now have regardless of the network gateway device).
Before I gave up on using the 655 as a DHCP & DNS server, I experienced intermittent problems on various machines (windows, linux, and macs) in various ways, with DNS relay on -AND- off, though the problems would vary from sluggish-ness to failed resolves for things which CLEARLY shouldn't have failed, and some other strange behaviors.
Though, I suspect -PART- of the problem was the fact that the DHCP server on the 655 (when sending out DNS addresses to hosts as part of the DHCP message) would give out the address of 0.0.0.0 in addition to its own (or my static WAN-Side DNS server depending on the state of the DHCP relay setting). And as far as I could tell (not being a network expert by profession) this caused machines to intermittently be _VERY_ confused when they tried to ask 0.0.0.0 for a DNS resolve (I don't think they're SUPPOSED to be able to do so, but I suspect some were anyway).
Of course I could be mistaken about it handing out 0.0.0.0 as a valid DNS server through DHCP messages when DNS relay was on, though I don't think so. I am however *CERTAIN* that it did when DNS relay was off, it would mindlessly send both the primary static DNS address from the WAN port -AND- the secondary address without checking to see if they made any kind of sense first.
I'm happy with my current setup, though I also want to contribute to making the (otherwise very nice) router actually usable as a router by itself, without having to reverse engineer the thing's behavior. :)
-HazardX
-
Sorry to sound like a Novice , but I have been facing problems with DNS but I am not sure whether it is relevant to this topic. I use my Dir 655 purely for WebSurfing needs. However from time to time I am encountering problems such as all of a sudden my webpages stop opening. This lasts for a minute or so and then voil everything is normal. However the point to note here is that torrents work beautifully all the time with no interrupts any time. I am sure it is a DNS problem. Is it because of the router or my ISP provider ? Please help. I am using F/W version 1.21 !
-
Sorry to sound like a Novice , but I have been facing problems with DNS but I am not sure whether it is relevant to this topic. I use my Dir 655 purely for WebSurfing needs. However from time to time I am encountering problems such as all of a sudden my webpages stop opening. This lasts for a minute or so and then voil everything is normal. However the point to note here is that torrents work beautifully all the time with no interrupts any time. I am sure it is a DNS problem. Is it because of the router or my ISP provider ? Please help. I am using F/W version 1.21 !
So back in 1.21 there was an issue that was referred to as "DNS slowdown" where randomly it would take a while for sites to load. This was fixed in 1.22B05 and then the fix was later introduced officially in 1.31.
However, something seems to be wrong with the fix, because now instead of a slowdown, the router just freezes. If I were you, I would stick with 1.21 and disable DNS relay. That should solve the issue you are seeing.
-
Since upgrading to the 1.3x series firmware the 655 will lock up between one and three days. Prior to the 1.3x series I ran 1.21, and up time would be for at least a month usually much more. DNS Relay was ENABLED.
Each time I try a different firmware version I first set the router to its default, upgrade, and then manually input all the settings again. While these steps are tedious it allows me to make sure that I am not making any mistakes or over looking anything that could cause or help the problem. (After the unit locks up I try an older saved settings file just to verify that I have the same behavior.)
I have just upgraded to 1.32 (non-beta), and have disabled DNS relay. In three days to a week I can have a rough guess if DNS Relay makes any difference. I have also tried upgrading the router with different web browsers to verify there were not issues from that direction.
One thing I do want to point out is that when DNS Relay is disabled, after a period of time, 0.0.0.0 starts showing up multiple times below the current DNS server addresses. So far I have seen up to three sets of 0.0.0.0 under the current DNS server addresses. This appears when I run ipconfig /all. (Vista x64 SP1).
-
One thing I do want to point out is that when DNS Relay is disabled, after a period of time, 0.0.0.0 starts showing up multiple times below the current DNS server addresses. So far I have seen up to three sets of 0.0.0.0 under the current DNS server addresses. This appears when I run ipconfig /all. (Vista x64 SP1).
This mirrors what I recall seeing, and what I suspect as being problematic with linux boxes and Apple's OSX.
Though in itself, having 0.0.0.0 show up in host's DNS resolver config is COMPLETELY unrelated to the use DNS relay (or not) setting in the router. DNS relay should only (from the internal side) result in sending the router's IP (Versus whatever the ISP tells the router its DNS IPs are) directly. The 0.0.0.0 thing appears to me to be a strangely configured DHCP server (on the router).
-
Disabling DNS Relay worked for me... I have been using 1.31 for over a month since I setup my 655 and have been dealing wth it locking up every evening. Since disabling it, I've been up continuously for 5 days straight without any issues.
Kicking myself because I know better than to use the latest REV of ANYTHING... Guess I was just too excited to have my 655... :-\
-
After three days the router is still up but the DNS on my computer is starting to show more odd IP addresses. At one point my computers IP 192.168.30.150 was also listed, though that is currently not the case. The computer was restarted one hour prior to this screen shot.
(http://img132.imageshack.us/img132/8032/dnst.jpg)
-
I made it just over four days before freezing with 1.32NA and DNS Relay enabled.
I've disabled DNS relay... we'll see how that goes.
-
The router still has not crashed with DNS relay disabled, but it really has been to short of a time period to tell. However the DNS info keeps getting weirder and longer. The image below is 1min after startup after an ipconfig /flushdns command, followed by a release and a renew command. The 203 servers are the correct DNS servers. The same DNS information is appearing on multiple computers. (Three to be exact, 1 vista sp 1 x64, 1 vista sp 1 x86, and 1 xp sp3. All different brand network adapters.
(http://img27.imageshack.us/img27/7564/ipconfiginfo.jpg)
Any ideas? When in relay is enabled could the router be getting stuck searching for DNS information then pages time out?
-
disabling dns resolves the lock up, but it still has problems of resetting and stuff like that.
I would like DNS on because its an awesome thing to have but right now its currently disabled.
With DNS disabled, it lasts about a week until a reboot is required to function normally.
I have to do a reboot because my internet slows down, and when i try to log into the router, it barely responds.
-
Dlink, any ideas on the multiple DNS numbers?
-
No thats weird. I've never seen anything like that before.
Is it only 1 Pc on your network thats doing that?
-
All three PC's on the network are doing it, and are showing the same numbers.
I just double checked to verify that all the machines do have the same thing happening.
ONE Vista x64 SP1 machine 802.11n connection
ONE Vista x32 SP1 machine 802.11g connection
ONE XP x32 SP3 machine 802.11g connection
I have not tried a wired connection yet, but I will shortly. As of this moment the list has expanded to 18 different DNS numbers up from the 14 that were posted in the last screen shot.
-
Thats so crazy.
I'd RMA that router.
-
I voted yes because I couldn't make it 16 hours and so far it's been 24 and counting - we'll see how the long term results end up.
Background: Was running rock solid on 1.21, updated to 1.32NA (NA="no answer?") in an attempt to resolve another issue. The router would broadcast OK but not answer/respond to any wired or wireless requests the next morning.
-
I voted yes because I couldn't make it 16 hours and so far it's been 24 and counting - we'll see how the long term results end up.
Background: Was running rock solid on 1.21, updated to 1.32NA (NA="no answer?") in an attempt to resolve another issue. The router would broadcast OK but not answer/respond to any wired or wireless requests the next morning.
hahaha!! the NA = no answer
oh wow. thats funny. haha it actually flows.... no answer to "what the heck is wrong with my dir-655"
or "im having problems with my dir-655, any help?" (no answer...)
hopefully dlink can fix this issue with the dir-655 soon, i would like to use ALL of its functions properly again.
-
Thats so crazy.
I'd RMA that router.
I would, but unfortunately I am outside the US at the moment. I am teaching English abroad and took the router with me so I could have wireless. I will not be back in the States until after the warranty expires.
As far as I can tell having all the numbers doesn't really cause a major problem. This only happens when DNS relay is disabled, but for me with DNS relay disabled the router is appearing to be stable. I am going to try manually setting the DNS numbers on the router so see if that prevents it from accumulating the excess IP's. At the same time I will try doing that with both DNS relay enabled and disabled.
-
HMM
I wonder if the odd ip's are ISP related.
-
HMM
I wonder if the odd ip's are ISP related.
There is a chance. Any way to figure that out? Reseting the router does remove the excess IP until it starts accumulating again.
-
Can Dlink already reproduce this issue? Among those polled >50% has experienced issues with DNS relay.
As this feature is not really that important, I suggest that the option should at least be disabled by default in the next firmware if it is not fixed.
-
Can Dlink already reproduce this issue? Among those polled >50% has experienced issues with DNS relay.
As this feature is not really that important, I suggest that the option should at least be disabled by default in the next firmware if it is not fixed.
So far, I don't think they have been able to reproduce it.
-
So far, I don't think they have been able to reproduce it.
I wonder if any of them have taken the Router Home with them and have tried to run it on a standard broadband connection with at least one other computer hooked up. Doing it in a lab is all fine and good, but lab vs real world could show differences. Just wondering.
The accumulation of DNS entries is odd. One of them points to Stillwater, mn to a telecom company. That is just odd. Perhaps the thing is just searching for ANY DNS that it can find. Those it can grab it adds maybe. At least if none is set in the router? I have not had any issues with the DNS relay, I have had other issues with the router not doing what it should be.
-
So far, I don't think they have been able to reproduce it.
... but they could have level II support contact someone who's reported the problem and get some log / configuration dumps. The general purpose of these forums is to 1. Cut down on customer support calls by giving users a discussion resource, and 2. For technical support to monitor for issues...
-
... but they could have level II support contact someone who's reported the problem and get some log / configuration dumps. The general purpose of these forums is to 1. Cut down on customer support calls by giving users a discussion resource, and 2. For technical support to monitor for issues...
I agree a 100%. This issue has been going on for a while.
http://forums.dlink.com/index.php?topic=5281.0
First post about this was May 1st.
-
Also me after 2/3 day the router lock ups and no more connection are permitted. I must reset the router and all come back in order.
So i try to disable dns relay, but after no internet connection on web. After enable it again and i can surf the web again....why ?
Or i must put primary and secondary DNS in "Dynamic IP (DHCP) Internet Connection Type" ??
Thank
-
I upgraded from 1.21 because I was tired of some random dhcp issues but other than power outages the thing was rock solid and never locked up on the internet connection.
Installed 1.32na and four days later hard lock, router still lit like normail but couldn't access it. I disabled dns relay but today had some odd issues where the router couldn't get a dns server to use, tried renewing and nothing, two reboots it finally worked. Now maybe my ISP (twc) was having some issues today but I miss 1.21.
-
Also me after 2/3 day the router lock ups and no more connection are permitted. I must reset the router and all come back in order.
So i try to disable dns relay, but after no internet connection on web. After enable it again and i can surf the web again....why ?
Or i must put primary and secondary DNS in "Dynamic IP (DHCP) Internet Connection Type" ??
Thank
You need to restart your computers after you turn of DNS relay.
Then the computers will get the DNS IPs from your ISP automatically.
-
Just over ten days now with DNS Relay disabled, no problems so far.
I made it just over four days before freezing with 1.32NA and DNS Relay enabled.
I've disabled DNS relay... we'll see how that goes.
-
Add me to the list of people that has to disable DNS Relay to resolve the lockout.
-
I have a A2 and a A3...
The A2 has the lockup problem on 1.32NA....
I will try disabling the DNS relay...
if that doesn't fix it, I'll reconfigure the A3 unit to see if it's any better than the A2...
(the A3 is just another wireless access point in the other side of my house...)
1.21 was rock solid... my wife works from home and I'm her IT support...
WHY DID I UPGRADE!!! ARGH!!!
-
I'm running 1.32na with hardware version A4. I'm trying tofigure out why the "enable dns relay" checkbox is checked but faded out so I can't actually uncheck it. Does anyone else have this problem? I'd really like to go longer than 3 days before having to unplug this thing every time.
-
I'm running 1.32na with hardware version A4. I'm trying tofigure out why the "enable dns relay" checkbox is checked but faded out so I can't actually uncheck it. Does anyone else have this problem? I'd really like to go longer than 3 days before having to unplug this thing every time.
I think if you have securespot or advanced dns enabled, you can't disable it.
-
Ah yes...disabling "Enable Advanced DNS Service " in the Internet Setup brought back the "Enable DNS Relay" thanks man! Now lets see how long this thing goes before it hangs again...will update!
-
I voted yes. Hopefully they resolve this issue in the next update (assuming there is one).
-
the next firmware will be like 5 years from now cause they are slow in reacting and lisytening to us people who own dlink products... like the dir-655
-
I have no idea what DNS Relay is, but I sure know what DIR-655 lockup is! I am on my third D-Link DIR-655 via the RMA process. This one arrived the middle of July, 2009. It worked fine until August 10th. It locked up and I noticed the Status LED was on solid - not blinking as it is supposed to. A power of and back on got it going. It locked up again this morning - Aug 15, 2009 with the same indications. I called D-Link to report the problem. They were going to send me router #4, but thought better of it. Now I have to call their super duper specialist on Monday to find out what they're going to do. The router arrived with hardware version A4 and firmware version 1.21. I did not change anything, just loaded my saved configuration and let it run. This is supposed to be a great router. I like the features but I am glad I have a Belkin router as a backup!
-
20 days now with DNS Relay disabled, no problems.
Just over ten days now with DNS Relay disabled, no problems so far.
-
I disabled DNS Relay a few months ago and this white puppy of mine works like a charm now! No problems at all. Before that... freezed after 3-5 days every time. Even the admin page didn't load up.
So yes... it defenitely worked for me.
-
still have lock up issues both on my wireless laptop and my PC via hard line. any more advise.
I have reflashed the FW--tried starting over with the set up--same old problems.
-
still have lock up issues both on my wireless laptop and my PC via hard line. any more advise.
I have reflashed the FW--tried starting over with the set up--same old problems.
So you disabled DNS relay? Can you describe your lockups?
-
yes it is off. it is pretty random. for example, It will work for say 5 to 15 minutes then lock for 2-5 minutes.
-
Disabling DNS does not help
Actually after that, browsing the net does not work, so I have to turn DNS back on.
Any sugestions?
-
Disabling DNS does not help
Actually after that, browsing the net does not work, so I have to turn DNS back on.
Any sugestions?
after you disable dns relay, you need to reset your connection to the router, otherwise you won't get internet.
-
yes it is off. it is pretty random. for example, It will work for say 5 to 15 minutes then lock for 2-5 minutes.
That might be something different, atleast the lockups most people see don't go away, unless you restart, not 2-5 minute things.
The issue is that after some period of a couple days, the router just freezes.
-
That's good to know, but I'm not sure how to fix it? It would freeze up once in a rare while with the 1.21
but after fw 1.32 upgrade it happens all the time. It also seems like it works well for 1/2 hour or so when I first
boot up the pc and then I start getting the lock-ups.
-
Mine is working beautifully after disabling DNS relay and manually entering my uplink speed in the QoS engine. Been connected for 11 days and haven't had to reboot. :)
-
Also me ....are 10 days without problem ;D ;D
Hispanico
-
Helped with the hard connection, but the wireless still locks up about every 24 hours requiring a reboot of the router.
I'm ready to take a hammer to the router. It worked fine until I foolishly upgraded the hardware.
-
It worked fine until I foolishly upgraded the hardware.
How'd you upgrade the hardware? ???
-
Disabling DNS, for me, only prolongs the usefulness by a few days. The performance gets worse after about 3-4 days of normal usage, and although at day 10 I can still access the router configuration page, the performance is awful until I power cycle the router. Disabling DNS has a seemingly slower effect on performance degradation, but it's definitely not a fix for the 1.3x firmware performance problem I have.
-
Disabling DNS, for me, only prolongs the usefulness by a few days. The performance gets worse after about 3-4 days of normal usage, and although at day 10 I can still access the router configuration page, the performance is awful until I power cycle the router. Disabling DNS has a seemingly slower effect on performance degradation, but it's definitely not a fix for the 1.3x firmware performance problem I have.
is it a performance problem or a freeze?
-
On June 29th Lycan, who is as a "tech-engineer", started this thread. It's August 27th, two months later, and a lot of people have confirmed that they have seen router hangs when DNS relay is enabled.
My question is when will D-Link fix the problem? DNS relay is part of a widely used open source package that is generally very reliable, so I don't understand why there isn't a beta firmware release that fixes the problem by now.
-
Please do something about it! I had 1.21 for long time and never restarted the router. After upgrade to 1.32NA (clean upgrade) I have to restart it 1-3 times a day (I and my wife work from home).
P.S. I disabled DNS relay, NTP update.
Please help!!!
-
is it a performance problem or a freeze?
Performance so far. However, the performance decline is so frustrating that I may not be giving it enough time to freeze completely. This week I made it to 1 day 17 hours before performance was unacceptable, but it also was not at the very poor performance it typically reaches and I did not give it a chance to get very poor since I'm back on my routine of rebooting when performance begins to decline instead of waiting until it's practically unusable.
I need to describe this very carefully so it's properly understood. I did not allow the performance to get as bad as it has when the router becomes inaccessible, and my reason is that because it progressed more slowly, I had to deal with poor performance for many days (rather than a quick downward spiral over a period of 12-36 hours and rebooting) and I eventually couldn't cope with it any longer. Again, performance was well below normal, but it had not yet reached the 10% chance of having a webpage load as before; it was at about 50-60% chance of having a webpage load but I was dealing with having to refresh pages for many days and I couldn't bear dealing with it any longer since the performance problem obviously had not gone away. If I had the patience to wait until what probably would have been 25 days of uptime (with 22 days of declining performance) until I reached that common 10% success rate, I would be able to check if the router had frozen...it's painfully frustrating to know how to restore performance so easily yet force myself to suffer through an awful internet experience. I'm surprised I made it to day 10 instead of rebooting at day 3, when it first became problematic.
To reiterate, I did not have any performance or lockup problems with firmware 1.21 with DNS relay enabled and although disabling DNS relay appears to have helped, I believe that it's a partial fix for the symptom rather than a fix for the problem. It still feels like a memory leak since I only made it to 1 day 17 hours this round despite DNS relay being disabled.
-
Performance so far. However, the performance decline is so frustrating that I may not be giving it enough time to freeze completely. This week I made it to 1 day 17 hours before performance was unacceptable, but it also was not at the very poor performance it typically reaches and I did not give it a chance to get very poor since I'm back on my routine of rebooting when performance begins to decline instead of waiting until it's practically unusable.
I need to describe this very carefully so it's properly understood. I did not allow the performance to get as bad as it has when the router becomes inaccessible, and my reason is that because it progressed more slowly, I had to deal with poor performance for many days (rather than a quick downward spiral over a period of 12-36 hours and rebooting) and I eventually couldn't cope with it any longer. Again, performance was well below normal, but it had not yet reached the 10% chance of having a webpage load as before; it was at about 50-60% chance of having a webpage load but I was dealing with having to refresh pages for many days and I couldn't bear dealing with it any longer since the performance problem obviously had not gone away. If I had the patience to wait until what probably would have been 25 days of uptime (with 22 days of declining performance) until I reached that common 10% success rate, I would be able to check if the router had frozen...it's painfully frustrating to know how to restore performance so easily yet force myself to suffer through an awful internet experience. I'm surprised I made it to day 10 instead of rebooting at day 3, when it first became problematic.
To reiterate, I did not have any performance or lockup problems with firmware 1.21 with DNS relay enabled and although disabling DNS relay appears to have helped, I believe that it's a partial fix for the symptom rather than a fix for the problem. It still feels like a memory leak since I only made it to 1 day 17 hours this round despite DNS relay being disabled.
You may try disabling QoS entirely. If it works after that I recommend you to try some online speed testing of dslreport or speedtest for at different times in a day to figure out if the problem lies with unstable upstream speed. At least that was my problem with my unstable DSL line until I fixed it with my ISP.
-
I've had the worst problems ever with the DIR-655 after I upgraded from 1.11 (WAS PERFECT) to 1.31 - 1.32 - now with DNS Relay disabled and the IPs from the router revoked. It's running fine, but not as good as 1.11 stable, mediocre at best. Last time I dump any money into D-Link or recommend them to friends, family and any business associates. Unless they send me a working unit or they eventually fix the problem.
-
Can you be more specific about what's not as good as 1.11, mediocre as best?
-
So far so good! I have been looking for a cure to my problem now for over two weeks. I did not receive very good troubleshooting from dlink support over the phone. I have 3 wireless PC's and a hard wired desktop all running vista and a PS3. I could not go more then 5 minutes and it was done.
-
I have been having a problem with Net-Flix. I can stream a movie for about 30-40 minutes then suddenly the connection drops and I can no longer access any configure options. Unfortunately disabling DNS relay did nothing to solve the problem.
-
You may try disabling QoS entirely. If it works after that I recommend you to try some online speed testing of dslreport or speedtest for at different times in a day to figure out if the problem lies with unstable upstream speed. At least that was my problem with my unstable DSL line until I fixed it with my ISP.
No difference with QoS off. I've also tried having SPI disabled. My speeds, when tested, have been a reliable 30+ mbit down and 2mbit up for a couple of years since the ISP bumped up my service.
-
***update so disabling DNS relay has decreased the amount of times it drops off. It does seem to be only when the hardwired computer is running I get this problem any Ideas?
-
My 655 would lock-up at least daily, but with dns-relay disabled I've been up for almost three weeks.
What's interesting is that we don't seem to missing out on whatever dns-relay was providing. Perhaps, the first web page loads a little slower, but I could be imagining that.
-
DIR-655 A4 1.32NA.
Disabling DNS relay cured the lockups, but after a few days, I think I checked enable "advanced DNS service" and then unchecked it after the system locked up again. The enable DNS relay must have been automatically selected, because the router was routinely locking up again. I disabled DNS relay and things are good again. I hope they can fix this soon.
-
Can you be more specific about what's not as good as 1.11, mediocre as best?
Sure, for one, in 1.11 I was able to get an avg rate of 281Mbit's, when I upgraded to 1.32 it has a REALLY hard time getting past 170Mbit's. Nothing has changed except for the firmware. Two, N connections like to reset themselves every 3-4 hours at random. Three, router locks up every 24-36 hours - if it does not lock after 24 hours, then browsing the net is very slow until it locks up, or I power cycle it. Overall, browsing the web feels a little sluggish, DNS Relay off, for the obvious reasons.
-
I'm also having issues with my DIR-655 after upgrading to 1.32NA
Every couple days it things slow to a crawl or fail outright and I cannot access the router's config page to restart it so I have to pull the power. I will turn off the DNS Relay to see if that helps. (I'll have to manually configure OpenDNS into every machine on my network, which sucks.)
I sincerely hope this gets fixed soon. I went out on a limb and bought a premium router for a reason. Right now, I'm wishing I had my old DI-624 back... :(
-
I sincerely hope this gets fixed soon. I went out on a limb and bought a premium router for a reason. Right now, I'm wishing I had my old DI-624 back... :(
Unfortunately, this has been going on for over 4 months (for me anyways, longer for others), if a fix was coming, it would have came. :'(
-
same here, 1.32 is bad, a very bad step for me to upgrade from 1.11
My internet get slow to connect to every page after 24 hours.
Have to reset router. >:( >:( >:(
-
Not sure but it may help to know what hardware versions are having problems.
Myself, I have A3 and 1.32 is totally solid for me.
-
Not sure but it may help to know what hardware versions are having problems.
Myself, I have A3 and 1.32 is totally solid for me.
A3 here also, but I had to disable DNS relay to get everything working properly.
-
didn't do it! but disabling WISH did though!
-
i was skeptical, but i've had 9+ days without lockups since disabling DNS relay.
-
Is this a memory leak issue with DNS or a physical memory limitation with the new Kernel? With any DNS cache algorithm, you should be aging DNS entries and pruning that cache frequently. This is especially true when you have limited memory, like on these little routers.
So, to me this looks like some fundamental issue with memory management on the box. This is especially true if by disabling the DNS relay, it does not clear up the issues for everyone.
My guess is that there is a general memory problem, and DNS is the largest consumer of available user/system memory.
TheWitness
-
Is this a memory leak issue with DNS or a physical memory limitation with the new Kernel? With any DNS cache algorithm, you should be aging DNS entries and pruning that cache frequently. This is especially true when you have limited memory, like on these little routers.
So, to me this looks like some fundamental issue with memory management on the box. This is especially true if by disabling the DNS relay, it does not clear up the issues for everyone.
My guess is that there is a general memory problem, and DNS is the largest consumer of available user/system memory.
TheWitness
Firmware 1.21 had an issue with DNS Relay that was referred to as "DNS Slowdown" (you can do a search). This was fixed in a beta firmware 1.22B05 and rolled into 1.31. It would be interesting to see what the original problem is and what the fix was.
-
yea, very familiar. if i had the source, i would fix it too.
-
I have A4 hardware and 1.22 FW. Was regularly having drops. 109 days without a lockup and still counting since disabling DNS relay. Was only change I made, so absolutely no doubt that this fixed the lockups.
-
I am having this issue with hardware A4 and 1.21. I tried disabling DNS relay and the internet actually stopped working completely. Had to re-enable it to get back on. Has anyone else had this issue? My ISP is comcast.
-
I am having this issue with hardware A4 and 1.21. I tried disabling DNS relay and the internet actually stopped working completely. Had to re-enable it to get back on. Has anyone else had this issue? My ISP is comcast.
You have to disable and re-enable your network connection, or just restart.
-
I am having this issue with hardware A4 and 1.21. I tried disabling DNS relay and the internet actually stopped working completely. Had to re-enable it to get back on. Has anyone else had this issue? My ISP is comcast.
If you use a static IP, you'll have to manually set the DNS addresses displayed on the router's status page in your OS settings. If you just use DHCP, restart the connection like the guy above me said.
-
thanks guys. that did the trick. i will now add my name to the list of people waiting to see if this resolves the issue. confused as to why this is an issue on 1.21 firmware that's been around since November. Shouldn't 1.21 be rock solid?
-
thanks guys. that did the trick. i will now add my name to the list of people waiting to see if this resolves the issue. confused as to why this is an issue on 1.21 firmware that's been around since November. Shouldn't 1.21 be rock solid?
You would think. Glad to hear it worked. :)
-
thanks guys. that did the trick. i will now add my name to the list of people waiting to see if this resolves the issue. confused as to why this is an issue on 1.21 firmware that's been around since November. Shouldn't 1.21 be rock solid?
Are you seeing freezing or something else? If you do a search for "DNS Slowdown", there was an issue with 1.21 that some people saw (including myself) where DNS resolution would start taking a really long time. This was fixed in 1.22B05 and then subsequently released in 1.31+. Disabling DNS relay was also a fix for that issue.
-
does DNS relay = Advanced DNS?
my router locks up randomly at least once a month, sometimes once every three days.
i know its the router b/c my surfing starts to simply not work, and when i try to go to 192.168.0.1 i can't. power cycle the router and all is fixed.
any solutions?
-
does DNS relay = Advanced DNS?
my router locks up randomly at least once a month, sometimes once every three days.
i know its the router b/c my surfing starts to simply not work, and when i try to go to 192.168.0.1 i can't. power cycle the router and all is fixed.
any solutions?
No, DNS relay is on the network page. You need to disable advanced DNS and securespot and then disable DNS relay.
-
I disabled DNS relay last night and have still experienced the issue with momentary lock ups. The connection is restored almost instantly, but still annoying nonetheless.
Question: I'm on hardware A4 with 1.21. Most people in this thread who have seen the issue and say disabling DNS relay solved it seem to have upgraded to 1.31 or 1.32. Should I try upgrading to 1.32 and then disabling DNS relay to see if it resolves the issue? I just bought this router yesterday, so I'm not really concerned about not being able to downgrade since I can just go return the thing.
I'm grateful for all input. Thanks.
-
I disabled DNS relay last night and have still experienced the issue with momentary lock ups. The connection is restored almost instantly, but still annoying nonetheless.
Question: I'm on hardware A4 with 1.21. Most people in this thread who have seen the issue and say disabling DNS relay solved it seem to have upgraded to 1.31 or 1.32. Should I try upgrading to 1.32 and then disabling DNS relay to see if it resolves the issue? I just bought this router yesterday, so I'm not really concerned about not being able to downgrade since I can just go return the thing.
I'm grateful for all input. Thanks.
I say upgrade it. 1.32 is better than 1.21 once you disable DNS relay. All of my problems with this router are gone.
-
Well my router has been going for 7 days straight with DNS Relay off instead of around 2 to 4 days when it's on. I'm on 1.32NA. No more out of resources problem till now. Hope it will continue to be so.
-
I would recommend first trying 1.22b05 before making the leap to 1.32. Once you go to 1.3x series, you cannot go back to 1.2x series and many are reporting problems with 1.32. If 1.22 works for you, then there is no need to risk going any further.
-
please release a new firmware already! >:(
-
I went ahead and bit the bullet and upgraded to 1.32NA with DNS relay disabled. So far (about 18 hours), so good. Was able to play on xbox live last night for over an hour with no drops or lag. We'll see what happens!
-
No, DNS relay is on the network page. You need to disable advanced DNS and securespot and then disable DNS relay.
securespot was already disabled. i had to disable advanced dns just to be able to disable dns relay.
this is unacceptable... the router should not lockup from users simply using it as its intended. is dlink aware of this and if so, are they going to issue a fw fix?
-
securespot was already disabled. i had to disable advanced dns just to be able to disable dns relay.
this is unacceptable... the router should not lockup from users simply using it as its intended. is dlink aware of this and if so, are they going to issue a fw fix?
Check a couple pages back. They know about it but can't reproduce it.
-
they should come to my house, i mean, it reproduces like rabbits here.
the lockup seems to be port 80 related... http traffic dies, but skype, email, etc... continue.
i got a crazy email from dlink, talking about upnp and the like:
From the email it seems the router is locking up.
The following are possibilities why your router is locking up:
A large amount of traffic may lock the router up. Disable any broadcast protocols or unused protocols such as NetBEUI and IPX/SPX on the computer.
Disable UPnP(TM) if not being used on both your computer (ME or XP) and on the router (Tools - Misc).
Check the log on your router. Is it showing a large amount of traffic? If coming from 1 IP address, you may want to use the IP Filter to block that user.
Check the log settings and uncheck some of the items the router will report.
Check your firewall and virtual server settings on the router. Too many may degrade performance of the router.
Upgrade firmware at http://support.dlink.com/downloads. If you have the latest version, flash it again.
Perform a hard reset on the router and reconfigure. With the unit powered on, use a paperclip and hold down the reset button for 10-15 seconds. Release and wait about 20 seconds. DO NOT power off while holding the reset button.
If the router continues to lock up, especially more than once a day, then it would be best if you interact with a live technician to resolve the issue.
is any of that meaningful?
-
yes.
have been running about 2 weeks now and no lock ups. with dns relay on it will lock up within 3days or so.
-
Well, I posted in another thread, so I'll just cross link to here:
http://forums.dlink.com/index.php?topic=6547.msg50262#msg50262
I voted for "what is DNS relay". Did I miss the instructions on how to disable DNS relay? I looked at the first post / page in this thread and didn't see anything. I also looked at the FAQ ( http://www.dlink.com/support/faq/?prod_id=3383&question=DIR-655 ) and didn't see anything there either?? I'm at work and not near my DIR655, so maybe it's just an obvious button in the web GUI I'll look at tonight then...
And I have to fully agree that this is completely unacceptable. The 1.21 firmware that came with the router worked like a champ -- the the effect that I didn't even consider the DLINK at all in my day to day networking. It worked like a switch. You just plug it in and leave it alone and it blends into the background. I'm not normally one to "fix what ain't broke", but with a company like DLINK who has such a great reputation, and this router which got such great reviews, I would NEVER have expected such a colossal failure in firmware. I mean, this is a networking company; This is a router; It's what DLINK does! How can they break something so intrinsic and fundamental -- and besides, it's only software, so fix it or at the very least, let me revert back to the 1.2x version! ???
-
I voted for "what is DNS relay". Did I miss the instructions on how to disable DNS relay? I looked at the first post / page in this thread and didn't see anything. I also looked at the FAQ ( http://www.dlink.com/support/faq/?prod_id=3383&question=DIR-655 ) and didn't see anything there either?? I'm at work and not near my DIR655, so maybe it's just an obvious button in the web GUI I'll look at tonight then...
Setup > network settings > uncheck "Enable DNS Relay" and save. If you get your IP automatically, you'll have to restart your connection to the router for it to work. If you use a static IP, you'll have to manually input the DNS addresses on the router's status page.
-
I must be doing something wrong or stupid because if I uncheck the Setup > Network Settings > Enable DNS Relay checkbox (http://192.168.1.1/Basic/Network.shtml), then I can't get out to the internet.
I have a static IP, and I have the DNS configured here:
Setup > Internet > Manual Configuration > Static IP Address Internet Connection Type (http://192.168.1.1/Basic/WAN.shtml)
Even Status > Device Info (http://192.168.1.1/Status/Device_Info.shtml) shows the right setup
Connection Type : Static IP
QoS Engine : Inactive
Cable Status : Connected
DNS Status : Online
Network Status : Established
Connection Up Time : 0 Day 0 Hour 01 Min 08 Sec
MAC Address : 00:21:91:......
IP Address : 75.147.180.77
Subnet Mask : 255.255.255.252
Default Gateway : 75.147.180.78
Primary DNS Server : 208.67.222.222
Secondary DNS Server : 208.67.220.220
Advanced DNS : Disabled
You say to "manually input the DNS address on the router's status page", but I don't see anywhere to do that (that doesn't already have the DNS entries filled in above)?
I've tried soft-rebooting via the web GUI. I've tried to unplug the router. I've tried to renew my networking on my PCs/servers and I can't ping any domain name. However I *can* ping by IP, so networking is alive. (and of course that makes some sense as we're talking DNS here which is failing me)
I have Hardware A4 : Firmware Version: 1.32NA if that matters.
-
I must be doing something wrong or stupid because if I uncheck the Setup > Network Settings > Enable DNS Relay checkbox (http://192.168.1.1/Basic/Network.shtml), then I can't get out to the internet.
I have a static IP, and I have the DNS configured here:
Setup > Internet > Manual Configuration > Static IP Address Internet Connection Type (http://192.168.1.1/Basic/WAN.shtml)
Even Status > Device Info (http://192.168.1.1/Status/Device_Info.shtml) shows the right setup
Connection Type : Static IP
QoS Engine : Inactive
Cable Status : Connected
DNS Status : Online
Network Status : Established
Connection Up Time : 0 Day 0 Hour 01 Min 08 Sec
MAC Address : 00:21:91:......
IP Address : 75.147.180.77
Subnet Mask : 255.255.255.252
Default Gateway : 75.147.180.78
Primary DNS Server : 208.67.222.222
Secondary DNS Server : 208.67.220.220
Advanced DNS : Disabled
You say to "manually input the DNS address on the router's status page", but I don't see anywhere to do that (that doesn't already have the DNS entries filled in above)?
I've tried soft-rebooting via the web GUI. I've tried to unplug the router. I've tried to renew my networking on my PCs/servers and I can't ping any domain name. However I *can* ping by IP, so networking is alive. (and of course that makes some sense as we're talking DNS here which is failing me)
I have Hardware A4 : Firmware Version: 1.32NA if that matters.
Oh, I meant if you have a static IP on your computer that accesses the router then you'd have to manually input the DNS addresses from your router into the network settings on your computer. The router should automatically get the DNS addresses from your ISP (and it looks like it did). Sorry about the confusion.
-
I dsiabled my DNS relay, but I found that I had to manually enter my ISP's dns setting (which is displayed on the rotuers status tab), very easy to to.
I have a torrent program seeding a bunch of files, and after about 3 hours, it would lock up. Usually the torrent would still be uploading, but I could not access my router and browse the internet.
Turned off the DNS relay, and my fileserver has been seeding for 3 days straight now, haha.
thanks!
-
Oh, I meant if you have a static IP on your computer that accesses the router then you'd have to manually input the DNS addresses from your router into the network settings on your computer. The router should automatically get the DNS addresses from your ISP (and it looks like it did). Sorry about the confusion.
So.... then why can't I access the internet (via domain names) with DNS relay off, if my settings appear correct? Is there somewhere else I need to update DNS (such as on EACH PC connected to the router -- that seems like a PITA when I have about a dozen machines that go through this DLINK). Or is there some other router GUI page that needs attention?
I'm half tempted to just go back to the store, buy another DIR655 (which will come with 1.21 on it) and return this 1.32 one in its place. This is ridiculous that I can't even downgrade, until they figure this out -- I really don't understand that part at all.
-
Oh wait! Okay, my bad. I've been using my Ubuntu server/Gnome to hit the DLINK router web GUI and test connections. What you said reminded me that I have it manually set to static 192.168.1.100 (not just an assigned DHCP lease, although not sure why I set it up static when assigning via the DLINK would have been sufficient I think) and my /etc/resolv.conf was set to :o
nameserver 192.168.1.1So I changed it to this 8)
nameserver 192.168.1.1
nameserver 208.67.222.222
nameserver 208.67.222.220
nameserver 4.2.2.1
For those that don't know, 4.2.2.1 is some old DNS server (owned by Level 3) that's been around for as long as I can remember. If you ever are unsure of a DNS IP, you can always count on that one. Even if DLINK gets this DNS relay issue (or whatever is the problem) resolved, I think I will keep my resolv.conf file like that anyways come to think of it -- can't hurt to have multiple DNS entries in there right. ;)
Is there any harm/slowdown in putting 192.168.1.1 (my router) as a DNS with this relay turned off? Like, will my packets have to timeout or anything before they hit the 208.* ones? I'm not noticing anything significant so far.
Then I fired up my Windows7 notebook, did this:
cmd
ipconfig /release
ipconfig /renew
Now both are working fine. :)
I will let this run and report back. Usually it runs all day from this point (11am) till about 8pm or so without incident. I think it's related to the fact that I'm on it all day (ssh/IMAPS/SMTP), whereas when I come home after work, I tend to watch TV and be with family, so it's not in use as much. Perhaps a clue in there? Maybe some kind of timeout for inactivity or something?
-
So.... then why can't I access the internet (via domain names) with DNS relay off, if my settings appear correct? Is there somewhere else I need to update DNS (such as on EACH PC connected to the router -- that seems like a PITA when I have about a dozen machines that go through this DLINK). Or is there some other router GUI page that needs attention?
I'm half tempted to just go back to the store, buy another DIR655 (which will come with 1.21 on it) and return this 1.32 one in its place. This is ridiculous that I can't even downgrade, until they figure this out -- I really don't understand that part at all.
What I meant is if the computers are connected with DHCP, their connection to the router will need to be restarted.
-
I will let this run and report back. Usually it runs all day from this point (11am) till about 8pm or so without incident. I think it's related to the fact that I'm on it all day (ssh/IMAPS/SMTP), whereas when I come home after work, I tend to watch TV and be with family, so it's not in use as much. Perhaps a clue in there? Maybe some kind of timeout for inactivity or something?
Well, it's been 24 hours of uptime now as it's 11am again and I'm off to work. Doing my usual check my internet connectivity (and hard-reset the DLINK router). But shockingly today I was able to ping out to any domain name I could think of. Woo Hoo!
So... how do I change my Poll vote from "what's DNS relay?" to "Yes!" ?
-
router has been up for 15 days since disabling DNS relay.
-
Damnit! I spoke too soon and jinxed myself. It's 12:30p and I'm at work and can no longer get my email or ssh to my home server as of right now (was fine till now). I can't even ping the IP. UGH! This sucks.
What's worse is that it seems to have taken out my Vonage phone too. The interesting thing with that is the way I have it setup is like so (purposely so that this kind of thing couldn't/shouldn't happen, where I lose my SIP/VoIP phone service):
______ Vonage (gets a 10.10.* from modem from Comcast)
|
wall ---- cable modem ----|
| _______ Server (192.168.1.100)
|------ DLINK (static IP) ------|
|_______ Notebooks, etc. (DHCP)
Yesterday and every other day for the past week or more, when DNS relay was enabled and the router S.T.B., Vonage was fine. Perhaps this is coincidence, but it sure is curious.
I was able to SMS txt my g.f. and have her pull the plug (since I couldn't phone home or drive there myself), and then everything started working again (server AND vonage). WTF!?
So... how do I change my poll vote from "what's DNS relay?" to "No!!!!!!" ?
I think I'll just execute plan B... time to buy a new DIR-655 (with v1.21 on it) and return this one. I've learned my lesson not to fix what isn't broke, that's for sure. I have neither the time nor patience for this bull$hit!
-
Running for 2 weeks now and no more issues. Thank GOODNESS!!!
TheWitness
-
My lockups seemed to have stopped but I dont know why. It could have been because I moved, in which case the environment changed, even though this new area has more AP's around, or it's because I had a talk with one of the room mates, who now doesn't have 15 torrents going at once, or if it's because I decided to leave the network unencrypted.
-
I have been playing around with this router for 2 months. (note: I have worked as a network admin for 15+ years) I have upgraded to version 1.32 of the firmware to alleviate some issues only to get the dreaded lockup issue. The router locks up once a day at least. I have tried a myriad of the things listed in this forum including disabling DNS relay. Nothing solves the issue. I'm not looking for help at this point. This is a buyer beware post. If you're looking to buy a router you would do well to steer clear of DLINK. This was my first and last purchase of a DLINK product. The current state of the product is unacceptable.
-
well, two weeks since i disabled DNS relay and advanced dns and so far no lockups.
i use a cable modem with comcast btw.
dlink has really dropped the ball on this. the newer fw and/or features must be to blame. it used to be rock solid.
when are they gonna get this fixed?
-
We have gathered enough information about this issue. This thread is no longer needed.
I am going to lock this thread, if anyone feels i have done this in error please PM me.
-Lycan.