Here is what I got from 3 of those digs Al, much different than your results
This cannot be an accurate measure because it doesn't take into
consideration, network traffic and other factors that may inhibit quick
responses. Note that RR is the fastest respone here. Also note that is goes
across the ocean to orange county.
MD
dig soa hawaii.rr.com | more
; <<>> DiG 9.3.1 <<>> soa hawaii.rr.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 42122
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
;; QUESTION SECTION:
;hawaii.rr.com. IN SOA
;; ANSWER SECTION:
hawaii.rr.com. 86395 IN SOA
dns-pri-01.orange.rr.com. help.socal.rr.com. 2006060200 3600 600
604800 86400
;; AUTHORITY SECTION:
hawaii.rr.com. 78718 IN NS dns-pri-01.orange.rr.com.
hawaii.rr.com. 78718 IN NS dns-sec-01.orange.rr.com.
;; ADDITIONAL SECTION:
dns-pri-01.orange.rr.com. 3600 IN A 66.75.160.39
dns-sec-01.orange.rr.com. 3600 IN A 66.75.160.38
;; Query time: 85 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Sun Jun 4 13:03:01 2006
;; MSG SIZE rcvd: 167
dig soa hawaiiantel.net | more
; <<>> DiG 9.3.1 <<>> soa hawaiiantel.net
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 28424
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
;; QUESTION SECTION:
;hawaiiantel.net. IN SOA
;; ANSWER SECTION:
hawaiiantel.net. 86400 IN SOA
HNLLDNSDHCP.hawaiiantel.net. dnsadmin.hawaiiantel.net. 595 3600 900
604800 600
;; AUTHORITY SECTION:
hawaiiantel.net. 24650 IN NS HNLLDNSDHCP.hawaiiantel.net.
hawaiiantel.net. 24650 IN NS WPHUDNSDHCP.hawaiiantel.net.
;; ADDITIONAL SECTION:
HNLLDNSDHCP.hawaiiantel.net. 80543 IN A 72.235.80.4
WPHUDNSDHCP.hawaiiantel.net. 80543 IN A 72.235.80.12
;; Query time: 156 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Sun Jun 4 13:04:15 2006
;; MSG SIZE rcvd: 162
dig soa lava.net | more
; <<>> DiG 9.3.1 <<>> soa lava.net
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37027
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 3
;; QUESTION SECTION:
;lava.net. IN SOA
;; ANSWER SECTION:
lava.net. 21600 IN SOA ns1.lava.net.
hostmaster.lava.net. 2006060200 7200 3600 604800 21600
;; AUTHORITY SECTION:
lava.net. 12549 IN NS ns2.lava.net.
lava.net. 12549 IN NS ns3.lava.net.
lava.net. 12549 IN NS ns01.backupdns.com.
lava.net. 12549 IN NS ns1.lava.net.
;; ADDITIONAL SECTION:
ns1.lava.net. 3480 IN A 64.65.64.17
ns3.lava.net. 73092 IN A 64.65.64.65
ns01.backupdns.com. 3834 IN A 199.242.242.199
;; Query time: 153 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Sun Jun 4 13:04:51 2006
;; MSG SIZE rcvd: 207
----- Original Message -----
From: "Al Plant" <[EMAIL PROTECTED]>
To: "LUAU" <luau@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 <[EMAIL PROTECTED]> 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@lists.hosef.org mailing list
http://lists.hosef.org/cgi-bin/mailman/listinfo/luau
_______________________________________________
LUAU@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@lists.hosef.org mailing list
http://lists.hosef.org/cgi-bin/mailman/listinfo/luau
