Child Item

Site Totals

61181 Questions Answered 267 Categories

DSL DNS lookup too slow and cause disconnection

I think it started around 02/24(last Tuesday). 3mb/768 connection suddently slows down and get disconnection all the time. However, ftp download is quick once connected. I saw dns lookup like this:
>nslookup www.yahoo.com
Server: dslrouter
Address: 192.168.1.1

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to dslrouter timed-out

>nslookup www.yahoo.com
Server: dslrouter
Address: 192.168.1.1

DNS request timed out.
timeout was 2 seconds.
Non-authoritative answer:
Name: www.yahoo.com.westell.com
Addresses: 63.251.179.13
8.15.7.117

-----

this actually makes VPN and web browsing slows like 14.4k moden. Any idea to fix this? thanks

Comments

Provider7

Have you tried flushing your Dns?

go to start, type cmd

next type ipconfig /flushdns

Reboot your computer and see if it makes a difference

One of verizon tech has done that with me already (flush dns). it is no joy. The problem is it is slow even dns lookup from westel 327w modem. From my observation, in average, it took 2-6 sec to for dns lookup. so it is extremely slow to open any web pages esp when it has lots of links in it. I do not see this is a line issue. for instance, it may take me 30 sec or refresh twice to get into mdsn.microsoft.com. However, I can download windows 7 dvd image with 350KB/sec once have ftp download session established. I wish some one can give me primary/secondary/cache dns servers in edision,NJ area and see if I can set them as my dns server not 192.168.1. I think some of dns farm behave badly. if that is router issue, download speed will suffer too.

Provider7

What if you did a system restore to before that date?

In order to verify if this an OS issue or not, I have wired connected to modem with Vista/XP/Ubuntu/opensolaris 11/08/solaris10upd6. They all have the same problem. It even time out by going to diag (ping / dns) from westel 327w modem. Monday, verizon tech said they want to open network ticket to trouble shooting for me as with 3Mb/768 is having a benchmaerk of 1100/15 kb/sec with speedtest.net tests. Yesterday, it looks like back to normal with 3MB/768. Today, the modem show 861/156 kb/sec and same slow dns lookup. download/upload speed are very inconsistent. same slow dns lookup. the download speed (ftp)once connected is nomral 80KB/sec for 768/128 speed. (but mine is supposed to be 3Mb/768kb.

linuxGeek-21401

Ever since my Westell 6100 was 'upgraded' by Verizon, DNS lookups take 20-? ? secinds. Reading web pages with external links usually result in freezing and ultimately disconnection. I know the firmware was changed because the web interface was completely different.

In addition, email downloads are agrevatingly slow, with 3-5 minutes required to download a half dozen text emails. I set up TCPcump and watched the transaction, the server was returning NOPs to keep the connection alive.

I reported this to verizon tech support, they said the upgrade had caused many issues, said they would send me a new CD ROM. I waited patiently for the ROM which showed up after 3 weeks, and was only the new user install disk, not the image as promised.

I have several machines on my network Linux, WinXP, and Mac, all behaving the same way. I have reasonable connectivity for web browsing, with downloads showing about 95 kbs, so I don't beleive there is a conndectivity issue.

Regards

-b

Provider7

If you had modified the original default settings before the update was made, you may have to go back in to the router and re-do them

linuxGeek-21401

All settings wre confirmed and re-entered per the verizon tech. The modem is configured to obtain an IP, GW, and DNS from the verizon.

Provider7

@linuxGeek-21401 wrote:
per the verizon tech.

Was this a tech on the phone or a tech dispatched to your your house?

Did they run a line test to your modem and share the results with you?

Our testers can usually see if there is an issue, although they sometimes seem reluctrant to dispatch a tech to your house, it would hurt to call and inquire.

CLS500

I have the exact same problem with my DSL line and the Westell 6100 modem- the link to the Internet works in no more than 25% of the time. I ended up using my neighbor's wireless network to come to these forums and look for a solution.

I noticed that while the DSL light on the modem is on, the Internet light blinks all the time and does not go into a steady state. DNS lookups either timeout or take forever to complete. I did enter the DNS servers in my Linksys router manually, but things don't really change.

I run Mac OS X 10.5.6 and noticed in the system log thousands of error messages referring to "defective DNS relay" at 71.250.0.14 and 68.237.161.14, which were the supplied DNS settings; all 3 computers in the house report the same problem with DNS.

Based on the above, I don't think the problem is the DSL line itself, but rather what has been changed on Verizon's end.

Any suggestions?

Provider7

There have been instances in Long Island where the Routers in our Central office are at full capacity. When this occurs the traffic becomes congested, .leading to slower rates. Next time you call into repair ask them to escalate your trouble and request being placed on a different router in the office. It's worth a try...

CLS500

Calling Tech Support was a waste of time, despite their genuine efforts to help me out. The problem is that they treat all customers like idiots and ignore any suggestion that perhaps there is a problem on the VZ end. The suggestion to look into the router was met with sarcasm and ignored by 2 reps.

I switched the modem into bridge mode. My Linksys router complains most of the time that it was unable to obtain and IP address from the PPPoE server. When it does, the connection does not stay on for a very long time and it tends to drop randomly for no apparent reason at all. Also, I seem to bounce between 2 sets of IP addresses- one on a 93.xxx.xxx.xxx network and another one of 73.xxx.xxx.xxx. Using my Mac without the router yields the same results where it is close to impossible to obtain an IP address or keep it long enough.

I am very frustrated and have decided to go back to Comcast Cable.

Child Item