dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
1268
share rss forum feed


jjeeff

@verizon.net

DNS lookups slow in Dallas area?

Anyone else been having DNS lookups running really slow this week. Its been several days that my lookups time out about 10% of the time, and about 50% of the time they are just too slow.

I'm using the router address 192.168.1.1 for dns. All three of my machines (XP and Linux) are experiencing problems and I haven't made any changes to my config lately.

Are there any alternative dns addresses that I can use?

BTW, I saw an article on CNET that was written in Sept of 2006 that reported Verizon FiOS having the slowest DNS times of any major provider, 3 times slower on average than Comcast. Interesting. Verizon denies that in a response.


fernando
Premium
join:2004-03-12
Chino, CA
208.67.222.222
208.67.220.220

Put those in your router settings then reboot it.
Start
Run
Type cmd
ipconfig /flushdns


jjeeff

@verizon.net
Nice tip, Index1489. I told my linux machine to use those DNS servers and it's back to zipping through web sites. It wasn;t necassary to tell the router anything. I'll change my windoze settings next time i boot them.

Alphasite

join:2005-07-27
Plano, TX
I've rarely had a problem with DNS lookups in the Dallas area. I've always used the standard Verizon DNS servers (4.2.2.1, 4.2.2.2, 4.2.2.3).

I've never had a problem with lookups timing out unless there was a connectivity issue and that's not a DNS problem.

I wouldn't use the OpenDNS servers as I don't want DNS servers trying to autocorrect addresses or serving me ads when it can't find the address I enter.

JohnA
Premium
join:2003-09-16
Pittsburgh, PA

Those are not Verizon DNS servers. They belong to LEVEL3.

albyva

join:2002-10-16
Ashburn, VA


I recommend folks (who are savvy enough) to setup an internal DNS caching server. I did and got a response back on a dslreports.com query in 3/msecs. You can't beat that..

; > DiG 9.3.4 > @192.168.1.129 dslreports.com any
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER- opcode: QUERY, status: NOERROR, id: 48924
;; flags: qr rd ra; QUERY: 1, ANSWER: 8, AUTHORITY: 4, ADDITIONAL: 5

;; QUESTION SECTION:
;dslreports.com. IN ANY

;; ANSWER SECTION:
dslreports.com. 3597 IN TXT "v=spf1 mx -all"
dslreports.com. 3597 IN A 209.123.109.175
dslreports.com. 3597 IN MX 5 mail.dslreports.com.
dslreports.com. 3597 IN SOA ns0.easydns.com. admin.easydns.com. 1168884232 21600 7200 1209600 3600
dslreports.com. 3597 IN NS remote1.easydns.com.
dslreports.com. 3597 IN NS remote2.easydns.com.
dslreports.com. 3597 IN NS ns1.easydns.com.
dslreports.com. 3597 IN NS ns2.easydns.com.

;; AUTHORITY SECTION:
dslreports.com. 3597 IN NS ns2.easydns.com.
dslreports.com. 3597 IN NS remote1.easydns.com.
dslreports.com. 3597 IN NS remote2.easydns.com.
dslreports.com. 3597 IN NS ns1.easydns.com.

;; ADDITIONAL SECTION:
mail.dslreports.com. 3597 IN A 209.123.192.187
ns1.easydns.com. 172797 IN A 216.220.40.243
ns2.easydns.com. 172797 IN A 209.200.151.4
remote1.easydns.com. 172797 IN A 209.200.131.4
remote2.easydns.com. 172797 IN A 205.210.42.19

;; Query time: 3 msec
;; SERVER: 192.168.1.129#53(192.168.1.129)
;; WHEN: Thu Feb 15 11:04:35 2007
;; MSG SIZE rcvd: 366

Alphasite

join:2005-07-27
Plano, TX
reply to JohnA
Those are the servers that were listed as the proper DNS servers in the documentation I received.

I didn't say they belonged to Verizon, I said they were the standard Verizon DNS servers (meaning the DNS servers Verizon lists as the ones to use as DNS servers).

Alphasite

join:2005-07-27
Plano, TX

1 edit
BTW, standard in the Dallas area.

Other areas may have different standard DNS servers depending on the provider pre-Verizon.

albyva

join:2002-10-16
Ashburn, VA


Just to remark.. I only setup my own internal caching
server because Verizon's was taking forever to respond to
queries, making it appear as if my link was running slow.

And once my wife started fussing, I had to do something to
curb the buzzing in my ear.


smajchrz

join:2003-10-11
Chantilly, VA
reply to Alphasite
said by Alphasite:

BTW, standard in the Dallas area.

Other areas may have different standard DNS servers depending on the provider pre-Verizon.
What exactly does "pre-verizon" mean?

The appropriate Verizon DNS servers will show up in your router via DHCP which I believe are regionalized. Anything beyond those are not "standard".

Now there is nothing wrong with the ones you suggested to use, but they have no association to Verizon or its service. I would be curious as to what documentation you received that suggested otherwise.


fernando
Premium
join:2004-03-12
Chino, CA
reply to jjeeff
Well the reason for putting them in your router is so that you don't have to change the settings on every PC.

Alphasite

join:2005-07-27
Plano, TX
reply to smajchrz
said by smajchrz:

said by Alphasite:

BTW, standard in the Dallas area.

Other areas may have different standard DNS servers depending on the provider pre-Verizon.
What exactly does "pre-verizon" mean?

The appropriate Verizon DNS servers will show up in your router via DHCP which I believe are regionalized. Anything beyond those are not "standard".

Now there is nothing wrong with the ones you suggested to use, but they have no association to Verizon or its service. I would be curious as to what documentation you received that suggested otherwise.
By pre-Verizon I mean whatever you had before they became part of Verizon. Mine was originally GTE.

I've always had static IPs (both DSL and FiOS) and the DNS servers 4.2.2.1, 4.2.2.2, and 4.2.2.3 have always been listed as the ones to use in the email sent from Verizon after the order has been processed.


smajchrz

join:2003-10-11
Chantilly, VA
That makes a bit more sense now.

It also appears that GTE internet services was spun off prior to the merger with BA(Verizon) and became Genuity. Verizon declined to reabsorb it and was later acquired by Level3. This is why whois returns L3 as the owner. I also found a reference of Verizon having a services contract with Genuity at one point which might explain why they suggest using those ips for DNS.

By way of comparison, I have FIOS DHCP and get the following ips 71.242.0.12 and 71.252.0.12.

It is interesting that they would provide two (or more) different sets of ips depending if you are static or DHCP.


fernando
Premium
join:2004-03-12
Chino, CA
The DNS servers Verizon assigns you are based on location not if your on static dhcp or pppoe.


smajchrz

join:2003-10-11
Chantilly, VA
If you read Alphasite's message you will see that they sent an email with what DNS servers should be used with his static IP. Those are not localized DNS servers and are actually owned by L3.

However, they ones that I am assigned via DHCP are localized (more like regionalized).