Hmm...
Well, as an example.
We have two pairs of name servers. One pair runs one big zone with around
20,000 records, and does so without even breaking stride.
30525 root 0 0 2864 2864 788 S 0 0.0 1.1 13:17 named
That 1.1 is memory, the 0.0 is the CPU. 13 minutes of CPU in 70 days of
uptime
The other pair run about 15,000 zones, most of which are smallish (4 - 10
records ), and also do so without skipping a beat.
3867 root 2 0 15852K 7140K select 9:08 0.00% 0.00% named
10 minutes of CPU in 5 days of uptime, much higher, but these boxes arn't as
good.
OK, so I'm doing this at 3am, but you get the point
In fact, we get more load problems in the programs that create and update
the zones than we do with the nameserver :)
They arn't that big machines either, all intel of varying types.
Of course, they have a lot of memory, but they don't really need it.
Trust me when I say there's not much you can do under notmal circumstances
to load up a DNS server, provided you keep it happy with memory, and
bandwidth. named is a very tame program.
Adam
----- Original Message -----
From: Chuck Dale <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, May 09, 2000 7:10 PM
Subject: Re: [SLUG] DNS Limitations?
> > >Are there any limitations on the number of records for a domain?
> > >
> > >ie. Could I set up blah000001.domain.com through to
blah100000.domain.com?
> > >(100,000 hosts)
> >
> > IMHO, there aren't.. I've seen examples of bind configs for setups like
> > this, but not as many as 100000 hosts ;)
>
> Well it's rather likely there are more than 100,000 hosts on
> [A-J].root-servers.net, but then they may not run Bind..
>
> Would be interesting to know what the root servers run though.
>
> Chuck
> --
> SLUG - Sydney Linux Users Group Mailing List - http://www.slug.org.au
> To unsubscribe send email to [EMAIL PROTECTED] with
> unsubscribe in the text
>
--
SLUG - Sydney Linux Users Group Mailing List - http://www.slug.org.au
To unsubscribe send email to [EMAIL PROTECTED] with
unsubscribe in the text
