Re: [SLE] named dns
From: Carlos E. R. (robin1.listas_at_tiscali.es)
Date: 05/30/05
- Previous message: Scott Leighton: "Re: [SLE] Weird Video Problems"
- In reply to: Randall R Schulz: "Re: [SLE] named dns"
- Next in thread: Per Jessen: "Re: [SLE] named dns"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 30 May 2005 04:14:32 +0200 (CEST) To: SLE <suse-linux-e@suse.com>
The Sunday 2005-05-29 at 14:16 -0700, Randall R Schulz wrote:
> Many ISPs provide more than one name server. Does your ISP provide more
> than one name server (address)? If so, is it possible you've
> misconfigured the primary, forcing each request to time out once (on
> the primary server) and then fail over to the secondary where they
> succeed?
Possible. But I don't think so. If the first DNS fails timing out, my own
DNS will time out as well, or at least, take much longer than three
seconds. I know, in some cases it takes perhaps ten seconds till it
complains.
Remember: modem is slow. Providers are slow.
I can try using the root servers and see if it is faster.
[...]
Offline:
Host nxsecure.org not found: 2(SERVFAIL)
Received 30 bytes from 192.168.100.2#53 in 164 ms
Online:
Trying "nxsecure.org"
...
Received 113 bytes from 192.168.100.2#53 in 1344 ms
Trying "nxsecure.org"
...
Received 91 bytes from 192.168.100.2#53 in 313 ms
Trying "nxsecure.org"
...
Received 129 bytes from 192.168.100.2#53 in 302 ms
Notice it's got to make three seeks, making a total of 1.959 seconds, a
bit faster than using my forwarders the other day. Second time (cached):
Received 113 bytes from 192.168.100.2#53 in 57 ms
Received 91 bytes from 192.168.100.2#53 in 43 ms
Received 129 bytes from 192.168.100.2#53 in 45 ms
I reenable my forwarders, and reload named. First time:
Received 129 bytes from 192.168.100.2#53 in 2540 ms
Received 91 bytes from 192.168.100.2#53 in 339 ms
Received 145 bytes from 192.168.100.2#53 in 342 ms
That's a total of 3.2", slower than asking the root servers; second
time (cached):
Received 129 bytes from 192.168.100.2#53 in 45 ms
Received 91 bytes from 192.168.100.2#53 in 30 ms
Received 145 bytes from 192.168.100.2#53 in 45 ms
Ok, I'll try again; I dissable my forwarders a second time, reload named,
and retry:
cer@nimrodel:~> time host -v nxsecure.org
Received 113 bytes from 192.168.100.2#53 in 3543 ms
Received 91 bytes from 192.168.100.2#53 in 291 ms
Received 129 bytes from 192.168.100.2#53 in 300 ms
real 0m4.176s -- and the sum of the above values is 4.134", it
matches what the comand "time" said.
You see... four seconds, from the root servers. I didn't try again with
forwarders enabled, because my connection went down (1 minute timeout).
Times longer than two seconds for a lookup are very normal, at least in my
part of the world, when using a modem.
--
Cheers,
Carlos Robinson
--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@suse.com
- Previous message: Scott Leighton: "Re: [SLE] Weird Video Problems"
- In reply to: Randall R Schulz: "Re: [SLE] named dns"
- Next in thread: Per Jessen: "Re: [SLE] named dns"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
