[2273] in linux-net channel archive
Re: NameD and Telnet
daemon@ATHENA.MIT.EDU (James G. Stallings II -- NetAdmin)
Thu Mar 28 11:15:59 1996
Date: Thu, 28 Mar 1996 09:39:18 +0600 (GMT+0600)
From: "James G. Stallings II -- NetAdmin" <zap@kraken.port-aransas.k12.tx.us>
To: John Burton <john@piper.gats.hampton.va.us>
Cc: ATPlack@scj.com, linux-admin@vger.rutgers.edu, linux-net@vger.rutgers.edu
In-Reply-To: <Pine.LNX.3.91.960326081215.7883A-100000@piper.gats.hampton.va.us>
On Tue, 26 Mar 1996, John Burton wrote:
> 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.
YEP-
I'm running the named straight out of the box that came with Slackware 3.0
>
> 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 ?
YEP-
I get quite a few 'lame delegations to '' from nameserver blah.blah.blah.blah'
Usually (95%?) my (offsite) secondary nameservice, operated by UTEXAS OTS.
(I used to blame them).
>
> > 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...
Almost certainly the problem.
Thanks all, for your many insightfull suggestions (and this probable
solution).
-James
<zap@kraken.port-aransas.k12.tx.us>
"Every Day, from here to there, funny things are everywhere."
-- The Late Dr. Seuss
