US Telco Support > Verizon > Verizon Online DSL > DNS slowdown in Philly?

DNS slowdown in Philly?

No one else having DNS resolution slowdowns???

Here's some results:

quote:

---

; > DiG 9.2.4 > microsoft.com
[...]
;; Query time: 2892 msec

---

quote:

---

; > DiG 9.2.4 > nfl.com
[...]
;; Query time: 1192 msec

---

Woke up this morning and it was working fine. Got home this evening and it's back to 500+ms on the resolves. I can't believe no one else is having this problem in the Philly area.

-- HP

I did some more testing and it seems that EVERY Verizon DNS server is giving me responses > 500ms. WTF is going on??? I ssh'd into a server back east that uses the Pburgh DNS servers and it gets 20ms, if i use that DNS server i still get 500+ms responses. Anyone have any idea? My speeds are 190KB/sec on the download, and 40KB on the upload, so my line is just fine. I'm pinging about 11ms to my first hop too. I will check again in the morning to see if it is any better, but if anyone has any input on this let me know. I sure hope this isn't turning into another NYC event.

-- HP

reply to hp550c
Checked this morning and sometimes they were fine, but mostly they were 500ms+. I even checked at work (on a different host) and the Philly DNS servers were doing the same. Most times they were 500ms+, but ONE time during the day i was getting a few 20-70ms resolutions. Keep in mind that these aren't ping times, this is doing a 'dig @151.197.0.38' and 'dig @151.197.0.39'.

ANOTHER weird thing is that ANY dns server that i am trying it getting 300ms+ when doing a 'dig @serverip'. Yet from work I am getting great times on other DNS servers. Does ANYONE have any idea what is going on?

Thanks,
-- HP

reply to hp550c
It makes me feel like I am back on Comcast. I have no idea what is causing the problems.
--
FWD# 57817

reply to hp550c
Just updating this problem. It's still on-going. The mornings are mostly fine. DNS resolutions are in the 12-20ms range. As the day goes on and more people start using the net the DNS resolutions slow down (500ms+).

The weird thing is that no matter what DNS server i use (be it Pittsburgh, NY, Dallas, CA, etc) they are ALL resolving in the 500ms+ range. If i remote connect to my computer back in Pittsburgh, and do the exact same DNS resolution on those servers (other than the Philly DNS servers) they are fine. Which tells me that it might be something other than the DNS servers themselves, such as an overloaded router/switch or something. Another weird thing is my pings to the DNS servers are fine, about 15-20ms, even when the DNS resolves are high. So it's actually like a router is slowing down the DNS packets for some reason.

Jump in at any time for a discussion about this.

-- HP

i knew that there was something funny going on so its a
DNS problem or so u think.

I'm pretty sure it isn't so much a DNS issue, but rather a router that is getting hammered and is lowering the priority of the DNS packets (or something to that effect).

If it were a DNS server problem, the Philly DNS servers would be high, but others should be low. That isn't the case. When it's slow, they are ALL slow (Pittsburgh, VA, CA, TX).

Funny thing is, other traffic is just fine. Pings to other servers are great, and when i do get an IP number, i can download at my 187K / sec. Yet DNS resolutions are still slow.

-- HP

reply to hp550c
I've managed to track the problem down to a router in Philly...here's why:

When i do a regular dig on _ANY_ DNS server (Verizon's, or any other ISP's) during peak times i will get high DNS resolution times quite often (sometimes i will get good results (200ms).

BUT

When i do a dig with the +tcp option (which sends TCP packets instead of UDP packets) i get excellent results EVERY TIME.

This tells me that there is a router in Philly which is not liking the UDP packets that much. I sure hope some Verizon network engineers read this and check into it. This has been an on-going problem for over a month now.

-- HP

Ok I give up what is the "dig" command?

Sorry. 'dig' is a linux command which does a DNS lookup on the DNS server you specify. Among other things, it tells you how long it took to do the DNS resolution.

-- HP

Thanks I am running "win_doze"

reply to hp550c
Anybody ever figue out WTH is going on or a way around this crap. Yesterday around 8pm DNS request timeouts were crazy.
--
Area Code & Exchange Lookup

I'm having problems in Wisconsin, slow.
I think it's probably with their upgrade maintence work they are doing.

West Sacramento, CA, Atlanta, GA, Hilliard, OH, Detroit, MI, Newark, NJ, Kernersville, NC, Hartford, CT, Hayward, CA, Sterling, VA, Indianapolis, IN, Los Angeles, CA, and Manassas, VA

Network Maintenance throughout the month of March

Verizon Online will be conducting a series of network enhancements throughout the month of March in the following areas: Dallas, TX; Tampa, FL; Clearwater, FL; and Fort Wayne, IN. This maintenance is scheduled from 12:00 A.M. to 6 A.M. daily (including weekends). We are also conducting maintenance in Sun Prairie, WI. The maintenance is schedule to occur daily (24X7) in this location. The network maintenance could lead to a temporary interruption of your Verizon Online DSL Service.

reply to hp550c
Same problem on Long Island. Some sites are ok some take a long time. Yahoo is slow, Even google at times.

reply to hp550c
I too am feeling the affects of this slowdown, my download and upload speeds have be practically slashed by more than half!

Down - 56 KB/s
Up - 22 KB/s

By the way, I'm on the 1.5/384 package and am in the Philly area.

Not just Philly. I have same problem in MA. Dig shows query times of >500 ms using UDP but 30-40 ms using TCP. DNS sometimes takes seconds to resolve. Anybody know what is going on here?

reply to Metal Sandbag
The funny thing is, my nntp D/L speeds are right up at 1.5+ Mb/s when the regular WEB stuff is at ~50-200 Kb/s (which is where it is right now.

Go to their system status page and they have "Nothing to report" regarding any DSL problems {-- BS!
--
Never raise your hands to your children, it leaves your groin unprotected.

reply to hp550c
Yeah, I'm not sure if they "patched" some routers and somehow screwed up UDP traffic or what happened. Obviously TCP is OK, and UDP is messed up. Just hope they fix whatever the problem is soon. This has been going on for well over a month now in the Philly area.

-- HP