[2256] in linux-net channel archive
Re: NameD and Telnet
daemon@ATHENA.MIT.EDU (John Burton)
Tue Mar 26 08:34:42 1996
Date: Tue, 26 Mar 1996 08:27:12 -0500 (EST)
From: John Burton <john@piper.gats.hampton.va.us>
To: "James G. Stallings II -- NetAdmin" <zap@kraken.port-aransas.k12.tx.us>
cc: ATPlack@scj.com, linux-admin@vger.rutgers.edu, linux-net@vger.rutgers.edu
In-Reply-To: <Pine.LNX.3.91.960325224547.20418D-100000@kraken.port-aransas.k12.tx.us>
On Mon, 25 Mar 1996, James G. Stallings II -- NetAdmin wrote:
>
> We have a flat class C network tied to a 56K leased line via a Cisco 2501
> Router. We run named on a 486DX100 (local bus/bus mastering fast SCSI II);
> it has 32 MB of RAM and 2GB HD. The disk is reasonably fast (its a
> Seagate Baracuda II). When we were running this machine as a dedicated
> nameserver (i.e. no user accounts, no extraneous processes), it ran the
> DNS so slowly that we were completely unable to connect until after
> several requests for nameservice had be made. Lynx would only work on
> any given "new" link after attempting to activate the link several
> times. Once the address was successfully acquired, it would remain
> cached and access to that site would become routinely quick.
>
Ummm...biggest question...what version of named/bind are you running...
I currently have a 486/33 8MB, ISA bus, 800MB IDE (not EIDE) running
as primary DNS for 4 domains which use 4 Class C networks. I had some
problems with earlier Beta versions of named (like the one that came
standard in Slackware 3.0), but after I upgraded to the current distributed
version, everything runs smoothly and quite fast...no response time problems.
Have you looked in your system log files (/var/log/syslog, /var/log/messages
to name a couple) to see if named is returning any error messages ?
> I found I was able to alleviate the problem somewhat by tweaking the SOA
> time-to-live and refresh rate for the machine running the nameserver.
> This caused the system to require only a few requests for a name before
> the server was able to retrieve and cache it. Once cached, with the TTLs
> on the local server optimised, things would crackle after the network had
> been on-line.
>
Those values shouldn't make much difference on the responsiveness of
*your* nameserver, they mainly modify the behaviour of other nameservers
that look to yours for information.
>
> I do think it interesting to observe the difference that the Sun netra
> makes, and to wonder if there is something incredibly "less than optimum"
> about the port of "named" for linux.
>
Ummm...the named I'm using for my Linux box is basically the standard
named/bind distribution that runs on a bunch of other platforms. I have
the same version running on an IBM RS/6000. No "porting" needed. If anything
named running on my Linux box is *more* responsive than the one running on
the RS/6000 (or the stock IBM named for that matter).
Sounds like you have a configuration problem (check your log files) or
you are running the stock (beta) named that came with Slackware and
possibly other distributions...
John
John Burton GATS, Inc.
j.c.burton@gats.hampton.va.us 28 Research Drive
j.c.burton@larc.nasa.gov Hampton, VA 23666
(804) 865-7491 (voice) (804) 865-1021 (fax)
