D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: danieljai on January 07, 2013, 11:52:27 AM
-
I've owned the 655 for 3 months. Recently the DNS keeps failing on me (some website suddenly throws a DNS error) requiring me to do a ipconfig /flushdns as often as 10seconds. This happens to both wireless and wired connections.
I'm from Canada using Teksavvy.
Tried using default teksavvy's dns servers, or google's 8.8.8.8, 8.8.4.4 with no success
Tried setting dns server on my computer with no help
Experience DNS errors to all device that is connected to the network.
Tried enable/disable DNS relay
Using Rev. B
Newest firmware according to the router GUI
any thoughts? :(
-
I am not sure whether you are saying you have a network DNS error or a corrupted DNS data packet. If you do a recursive ping, say for a 1000 pings to your DNS server do all requests look good.
-
Link>Welcome! (http://forums.dlink.com/index.php?topic=41537.0)
Link>What Firmware (http://forums.dlink.com/index.php?topic=47512.0) version is currently loaded? Found on routers web page under status.
What region are you located?
Are you wired or wireless connected to the router?
Has a Factory Reset been performed?
What ISP Service do you have? Cable or DSL?
What ISP Modem do you have? Stand Alone or built in router?
What ISP Modem make and model do you have?
If this modem has a built in router, it's best to bridge the modem. Having 2 routers on the same line can cause connection problems.
Double NAT (http://www.practicallynetworked.com/networking/fixing_double_nat.htm)
To tell if the modem is bridged or not, look at the routers web page, Status/Device Info/Wan Section, if there is a 192.168.0.# address in the WAN IP address field, then the modem is not bridged.
If the modem can't be bridged then see if the modem has a DMZ option and input the IP address the router gets from the modem and put that into the modems DMZ.
Check ISP MTU requirements, Cable is usually 1500, DSL is around 1492 down to 1472. Call the ISP and ask.
Some things to try: - Log into the routers web page at 192.168.0.1. Use IE, Opera or FF to manage the router.
Turn off ALL QoS (http://vonage.nmhoy.net/qos.html) or Disable Traffic Shaping (DIR only) GameFuel (DGL only and if ON.) options. Advanced/QoS or Gamefuel.
Turn off Advanced DNS Services if you have this option under Setup/Internet/Manual.
Turn on DNS Relay under Setup/Networking.
Setup DHCP reserved IP addresses for all devices ON the router. Setup/Networking. This ensures each devices gets its own IP address when turned on and connected, eliminates IP address conflicts and helps in troubleshooting.
Ensure devices are set to auto obtain an IP address.
Set Firewall settings to Endpoint Independent for TCP and UDP under Advanced/Firewall.
Enable uPnP and Multi-cast Streaming under Advanced/Networking. Disable uPnP for testing Port Forwarding rules.
Does this happen with all connected devices?
What browser are you using?
You can disable DNS Relay and manually input DNS server addresses into Setup/Internet/Manual. Save settings and reboot. You'll need to either reboot all the devices or /ipconfig flushdns.
-
pings are fine when it works. Then all of a suddenly random pages will show DNS unresolved. If i do a /flushdns it comes back up.
What region are you located? Canada
Are you wired or wireless connected to the router? Wired to router. Wireless also exhibit same behaviour
Has a Factory Reset been performed? Yes, quite a few times.
Hardware Version: B1 Firmware Version: 2.10NA
What ISP Modem do you have? Stand Alone or built in router? Standalone router, no dhcp.
What ISP Modem make and model do you have? DCM476
No double NAT. The modem didnt have NAT capabilities, the WAN address is my public IP
Traffic Shaping is off
Advanced DNS Services is off
Enable DNS Relay is on
All devices has their own IP, so no conflict
Firewall is Endpoint to endpoint
uPnP and Multi-cast Streaming are both on.
I've tried manually input DNS with 8.8.8.8 or rely on obtaining default DNS from my ISP. Still has same problem.
It seems like I have all the things you've mentioned still no luck... just got an unresolved DNS googling again... :(
-
Ping by address not by name.
-
does pinging DNS server address count? I also did 1000 ping 8.8.8.8 and 4% was timeout.
-
Try disabling SPI as a test.
-
Try disabling SPI as a test.
It was never enabled :(
-
Has the cable been swapped out between the ISP modem and router?
Does this happen if you directly connect to the ISP modem?
Was this working before updating to v2.10?
What browser are you using?
Try Opera or FF? If IE 8 or 9, set compatibility mode and test again.
Maybe someone can review your router settings with you using Link> teamviewer (http://www.teamviewer.com) if your interested. Its safe and secure.
-
Has the cable been swapped out between the ISP modem and router?
Does this happen if you directly connect to the ISP modem?
Was this working before updating to v2.10?
What browser are you using?
Try Opera or FF? If IE 8 or 9, set compatibility mode and test again.
Maybe someone can review your router settings with you using Link> teamviewer (http://www.teamviewer.com) if your interested. Its safe and secure.
No the cable modem has been the same nor switched out for the psat 3 months.
connection directly to the modem has been
I'm using chrome 23
who's "someone"?
-
Try Opera or FF? If IE 8 or 9, set compatibility mode and test again.
Would be me if you need me to review your router settings.
-
sure. What do I do? download and install teamviewer?
-
download and either RUN or Install it. It's a self contained program. Lets set this up tomorrow.
-
What is the DNS error you are getting? When it occurs, can you ping the domain? Does it return a different IP when you ping and the site isn't working compared to when it is working?
-
Any status on this?
I've got my 655 running with v2.10 at the moment.
I'm currently using manual DNS address entries and DNS Relay is OFF.
-
Sorry, flu took me down for almost a week. I'm still at work atm, shall we set this up in few hours tonight FurryNutz?
@Hard Harry, usually chrome gives me an error unable to resolve DNS. When this happens i cannot ping the domain name... it turns timeout. Also when this occurs, pinging to the router response time is not <1ms.
I've never tried pinging an external IP (instead of a domain name) when this error happens tho.
-
There you are. Hope your feeling better. Ya we can set this up for tonight. Send me a PM with teamviewers ID and PW. Please be wired to the router while we do this.
I'll be home by 5pm MST.
I have my 655 up and running on 2.10 right now and this is working for me:
http://forums.dlink.com/index.php?topic=52123.0 (http://forums.dlink.com/index.php?topic=52123.0)
-
@Fuzzy, sent you PM, did you receive it?
-
Got it.
Had a look see,
Set DNS back to default ISP DNS, DNS Relay is ON. SPI is OFF, NAT is End Point. Re-enabled Traffic Shaping and set for 1024Mb Uplink for his 512k ISP SPEED. QOS is disabled for now. Port Forwarding is being used.
Mentioned that a downloader he uses could play a part in this as it might seem to cause the DNS to fail more often.
I checked System Check and pings were successful for google and facebook and one LAN device.
Ask him to test settings for now, then also try using manual DNS IPs and turn OFF DSN Relay and test.
Test with and with out the downloader running.
Do a speedtest.net to verify your ISP Speeds. I should have done this with you. Sorry. ::)
Windows 8 firewall is enabled and told hiim that this could be disabled at some point as it's not needed.
Keep us posted.
-
So the links on my switch has been blinking like mad for about 30minutes now. Ima try turn SPI to ON and wait to see again...
-
Ok..it should settle down after 10-15 minutes...Mine does.
-
Actually just when I was about to hit the restart button, the switch lights went back to normal! yeah!!
-
so it's been several minutes...you can still try SPI ON..reboot and time it if you can.
-
turned SPI back on, switch lights going christmas again... so I should wait for 30ish minutes for it to calm down?
-
check at 10 and 15 minutes.
-
So after a few days of fixing. Problem still persist... its so bad even normal web browsing will cause the router to act up. And when that happens, I cant even ping the gateway.
Pinging 192.168.0.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
I am done spending more time fixing this router. Gonna look else were. Thanks for all your help though.
-
Good Luck.