Search Again:

Re: Best setup for secondary?

From: Richard Johnson
Date: Thursday, March 6, 1997
Time: 11:48:00 pm

At 17:41 -0500 on 3/6/97, Jim Turney wrote:
> Is there any reason to think that there will be an impact on performance of
> our primary name server (on a 7100/80 also running AIMS as a secondary mail
> server and nothing else) if it also acts a as secondary name server (for
> different domains)?
>
> We use a 7200/90 only for our primary AIMS and our secondary name server
> for all our domains. It is more convenient to offer secondary name service
> (to another ISP who also uses QDNSPro) on our primary server than adding
> their domains to our list of secondaries.
>
> I'm just wondering if, on performance basis alone, it matters whether we
> service their secondaries on our primary or our secondary QDNSPro. thanks
> in advance...


We serve many domains as secondary off our QuickDNS Pro system (almost all
secondary, now). I haven't seen any performance difference between serving
as secondary, and serving as primary, but I also haven't bothered to look
for one because I can't see why one would exist. :-)

QuickDNS Pro is efficient enough that I see no noticeable impact from it on
a 7100/80 also running WebSTAR, FTPd, AIMS, and a horde of CGIs, whether it
is a primary or secondary. (FTPd is the hog, followed by WebSTAR.) This
server is the first resolver for ~100 internal machines, plus the
nameserver listed first in the whois record for our domains (meaning it
gets the majority of the outside queries for our domains).

Actually, how are you defining "primary" and "secondary"? In the usual
sense, a "primary" server is the one with the original zone data. A
"secondary" server is one that gets its zone data via zone transfers from
another (primary or secondary) server.

Some folks, on the other hand, refer to a "primary" server as the one
that's listed first in the whois record for the domain at the NIC. I just
refer to that as "the server listed first in the whois record". :-)

The server running QuickDNS Pro I referred to above is actually a
secondary, behind a primary server that's not even reachable from the
outside world. As we increase our visibility, and add domains, I expect to
eventually start seeing some load from QuickDNS. Eventually. But I can't
see how it would change if we were serving from QuickDNS as primary vs.
secondary.


Richard



Messages In This Thread:



Return to Digital Point Solutions' Home Page