[LUAU] Slow internet response with different nameservers
Maddog
maddog at heavymetalradio.net
Sun Jun 4 16:35:58 PDT 2006
Further testing from a Windoze box using pathping shows some interesting
results: (This should be prefaced by saying that I am on a RR connection but
nonetheless the results are interesting, especially when you consider the
number of hops and location of the Hawaiiantel servers.)
MD
>pathping ns1.lava.net
Tracing route to ns1.lava.net [64.65.64.17]
over a maximum of 30 hops:
0 broadcast [192.168.0.90]
1 192.168.0.1
2 10.102.96.1
3 gig2-1.oahuhikane-rtr1.hawaii.rr.com [24.25.224.117]
4 srp5-0.oahuhikili-gsr2.hawaii.rr.com [24.25.224.70]
5 srp5-0.oahuhimili-gsr1.hawaii.rr.com [24.25.224.65]
6 pop1-hon-P2-0.atdn.net [66.185.137.57]
7 bb2-hon-P0-0.atdn.net [66.185.137.50]
8 pop2-hon-P0-1.atdn.net [66.185.137.67]
9 pihana.atdn.net [66.185.137.78]
10 202.177.194.193
11 202.177.194.10
12 malasada.lava.net [64.65.64.17]
Computing statistics for 300 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 broadcast [192.168.0.90]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
2 6ms 0/ 100 = 0% 0/ 100 = 0% 10.102.96.1
0/ 100 = 0% |
3 7ms 0/ 100 = 0% 0/ 100 = 0%
gig2-1.oahuhikane-rtr1.hawaii.rr.c
om [24.25.224.117]
0/ 100 = 0% |
4 7ms 0/ 100 = 0% 0/ 100 = 0%
srp5-0.oahuhikili-gsr2.hawaii.rr.c
om [24.25.224.70]
0/ 100 = 0% |
5 8ms 1/ 100 = 1% 1/ 100 = 1%
srp5-0.oahuhimili-gsr1.hawaii.rr.c
om [24.25.224.65]
0/ 100 = 0% |
6 9ms 0/ 100 = 0% 0/ 100 = 0% pop1-hon-P2-0.atdn.net
[66.185.137
.57]
0/ 100 = 0% |
7 9ms 0/ 100 = 0% 0/ 100 = 0% bb2-hon-P0-0.atdn.net
[66.185.137.
50]
0/ 100 = 0% |
8 9ms 0/ 100 = 0% 0/ 100 = 0% pop2-hon-P0-1.atdn.net
[66.185.137
.67]
0/ 100 = 0% |
9 10ms 0/ 100 = 0% 0/ 100 = 0% pihana.atdn.net
[66.185.137.78]
0/ 100 = 0% |
10 9ms 1/ 100 = 1% 1/ 100 = 1% 202.177.194.193
0/ 100 = 0% |
11 9ms 0/ 100 = 0% 0/ 100 = 0% 202.177.194.10
0/ 100 = 0% |
12 11ms 0/ 100 = 0% 0/ 100 = 0% malasada.lava.net
[64.65.64.17]
Trace complete.
>pathping dns-pri-01.orange.rr.com
Tracing route to dns-pri-01.orange.rr.com [66.75.160.39]
over a maximum of 30 hops:
0 broadcast [192.168.0.90]
1 192.168.0.1
2 10.102.96.1
3 gig2-1.oahuhikane-rtr1.hawaii.rr.com [24.25.224.117]
4 srp5-0.oahuhikili-gsr2.hawaii.rr.com [24.25.224.70]
5 srp3-0.oahuhikili-gsr1.hawaii.rr.com [24.25.225.81]
6 so-0-1-3.lsanca1-rtr1.hawaii.rr.com [24.25.225.230]
7 POS1-0.ORNGCA4-GSR2.socal.rr.com [66.75.161.25]
8 GIG2-1.ORNGCA4-SWT2.socal.rr.com [66.75.161.5]
9 dns-pri-01.orange.rr.com [66.75.160.39]
Computing statistics for 225 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 broadcast [192.168.0.90]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
2 7ms 0/ 100 = 0% 0/ 100 = 0% 10.102.96.1
0/ 100 = 0% |
3 7ms 0/ 100 = 0% 0/ 100 = 0% gig2-1.oahuhikane-rtr1.ha
om [24.25.224.117]
0/ 100 = 0% |
4 8ms 0/ 100 = 0% 0/ 100 = 0% srp5-0.oahuhikili-gsr2.ha
om [24.25.224.70]
0/ 100 = 0% |
5 7ms 0/ 100 = 0% 0/ 100 = 0% srp3-0.oahuhikili-gsr1.ha
om [24.25.225.81]
0/ 100 = 0% |
6 81ms 0/ 100 = 0% 0/ 100 = 0% so-0-1-3.lsanca1-rtr1.haw
m [24.25.225.230]
0/ 100 = 0% |
7 84ms 0/ 100 = 0% 0/ 100 = 0% POS1-0.ORNGCA4-GSR2.socal
66.75.161.25]
0/ 100 = 0% |
8 84ms 0/ 100 = 0% 0/ 100 = 0% GIG2-1.ORNGCA4-SWT2.socal
66.75.161.5]
0/ 100 = 0% |
9 85ms 0/ 100 = 0% 0/ 100 = 0% dns-pri-01.orange.rr.com
0.39]
Trace complete.
>pathping hnlldnsdhcp.hawaiiantel.net
Tracing route to hnlldnsdhcp.hawaiiantel.net [72.235.80.4]
over a maximum of 30 hops:
0 broadcast [192.168.0.90]
1 192.168.0.1
2 10.102.96.1
3 gig2-1.oahuhikane-rtr1.hawaii.rr.com [24.25.224.117]
4 srp5-0.oahuhikili-gsr2.hawaii.rr.com [24.25.224.70]
5 so-0-1-1.tustca1-rtr1.hawaii.rr.com [24.25.224.254]
6 so-0-1-0-0.gar1.Tustin1.Level3.net [65.58.240.9]
7 so-7-0-0.mp1.Tustin1.Level3.net [4.68.125.153]
8 ae-0-0.bbr2.LosAngeles1.Level3.net [64.159.1.126]
9 ge-0-0-0-55.gar1.LosAngeles1.Level3.net [4.68.102.144]
10 sprint-level3-oc192.LosAngeles1.Level3.net [64.152.193.74]
11 sl-bb21-ana-4-0.sprintlink.net [144.232.8.95]
12 sl-bb22-ana-15-0.sprintlink.net [144.232.1.174]
13 sl-bb20-prl-10-1.sprintlink.net [144.232.8.157]
14 sl-gw2-prl-1-0.sprintlink.net [144.232.30.26]
15 * * *
Computing statistics for 375 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 broadcast [192.168.0.90]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
2 7ms 0/ 100 = 0% 0/ 100 = 0% 10.102.96.1
0/ 100 = 0% |
3 7ms 1/ 100 = 1% 1/ 100 = 1%
gig2-1.oahuhikane-rtr1.hawaii.rr.c
om [24.25.224.117]
0/ 100 = 0% |
4 8ms 0/ 100 = 0% 0/ 100 = 0%
srp5-0.oahuhikili-gsr2.hawaii.rr.c
om [24.25.224.70]
0/ 100 = 0% |
5 71ms 0/ 100 = 0% 0/ 100 = 0%
so-0-1-1.tustca1-rtr1.hawaii.rr.co
m [24.25.224.254]
0/ 100 = 0% |
6 84ms 0/ 100 = 0% 0/ 100 = 0%
so-0-1-0-0.gar1.Tustin1.Level3.net
[65.58.240.9]
0/ 100 = 0% |
7 85ms 0/ 100 = 0% 0/ 100 = 0%
so-7-0-0.mp1.Tustin1.Level3.net [4
.68.125.153]
0/ 100 = 0% |
8 84ms 0/ 100 = 0% 0/ 100 = 0%
ae-0-0.bbr2.LosAngeles1.Level3.net
[64.159.1.126]
0/ 100 = 0% |
9 83ms 0/ 100 = 0% 0/ 100 = 0%
ge-0-0-0-55.gar1.LosAngeles1.Level
3.net [4.68.102.144]
0/ 100 = 0% |
10 81ms 0/ 100 = 0% 0/ 100 = 0%
sprint-level3-oc192.LosAngeles1.Le
vel3.net [64.152.193.74]
0/ 100 = 0% |
11 82ms 1/ 100 = 1% 1/ 100 = 1% sl-bb21-ana-4-0.sprintlink.net
[14
4.232.8.95]
0/ 100 = 0% |
12 82ms 0/ 100 = 0% 0/ 100 = 0%
sl-bb22-ana-15-0.sprintlink.net [1
44.232.1.174]
0/ 100 = 0% |
13 137ms 0/ 100 = 0% 0/ 100 = 0%
sl-bb20-prl-10-1.sprintlink.net [1
44.232.8.157]
0/ 100 = 0% |
14 137ms 0/ 100 = 0% 0/ 100 = 0% sl-gw2-prl-1-0.sprintlink.net
[144
.232.30.26]
100/ 100 =100% |
15 --- 100/ 100 =100% 0/ 100 = 0% broadcast [0.0.0.0]
Trace complete.
----- Original Message -----
From: "Al Plant" <webmaster at hawaiidakine.com>
To: "LUAU" <luau at lists.hosef.org>
Sent: Sunday, June 04, 2006 9:21 AM
Subject: Re: [LUAU] Slow internet response with different nameservers
> Richard Z wrote:
>> rr.com has 4 dns server listed, dns4.rr.com, dns3.rr.com, dns2.rr.com
>> and dns1.rr.com. Unfortunately dns4 has very slow response time. In my
>> testing more than 3-4 seconds. Sometime even no response.
>>
>> When there are multiple dns servers, it is up to the dns client to
>> decide how/where to send the queries. Some would send to the first
>> one, wait for response, if no response then send to the second one.
>> Other clients would send queries to all servers at the same time and
>> use the first response. Others use round robin to choose which one to
>> send query first. Without doing some research, I suspect linux always
>> uses the first dns server which has the lowest response time in this
>> case. Windows clients probably query all servers and get the response
>> from the fastest server.
>>
>>
>>
>> On 6/3/06, David Imai <dimai at email.com> wrote:
>>
>>> > The RR servers are in Orange County CA and Oakland CA. The others
>>> are local.
>>>
>>> Even if this is the case, what is causing the slowness? Windows and Mac
>>> systems don't seem to suffer from the problem. Is it a problem with the
>>> way the nameservers are configured? or is it a problem with Linux or
>>> Ubuntu? I think if people who try to use Linux with RR experience this
>>> problem, they will probably blame Linux. HOSEF is planning to distribute
>>> desktop machines to people. It wouldn't be good if everyone who used RR
>>> ran into this problem. so what would be the best way to fix it before
>>> the user runs into it?
>>>
>>> --
>>> ___________________________________________________
>>> Play 100s of games for FREE! http://games.mail.com/
>>>
>>> _______________________________________________
>>> LUAU at lists.hosef.org mailing list
>>> http://lists.hosef.org/cgi-bin/mailman/listinfo/luau
>>>
>> _______________________________________________
>> LUAU at lists.hosef.org mailing list
>> http://lists.hosef.org/cgi-bin/mailman/listinfo/luau
>>
>>
>
> I just read where a misconfigured DNS server at an ISP can cause the
> delay. Could this be the case here if it's only the rr connected folos are
> affected?
>
> I tried a test using a FreeBSD box:
>
> if you run:
> dig soa rr.com | more
> you see a total dns response time of 154 ms from our noc.
>
> dig soa lava.net | more
> you see a total dns response time of 34 ms from our noc.
>
> If this is any indication the rr slowness of response looks like there end
> and not from your OS on the local box.
>
> Al Plant
>
> -- Webmaster- http://hawaiidakine.com Admin- http://freebsdinfo.org --
> Supporting Open Source Computing - - FreeBSD 6.* -- Debian Linux 3*
> "All that's really worth doing is what we do for others."- Lewis Carroll
>
> _______________________________________________
> LUAU at lists.hosef.org mailing list
> http://lists.hosef.org/cgi-bin/mailman/listinfo/luau
>
More information about the LUAU
mailing list