[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] Re: How to use .include file to add secondary dns
- Subject: Re: [cobalt-users] Re: How to use .include file to add secondary dns
- From: "Steve Werby" <steve-lists@xxxxxxxxxxxx>
- Date: Fri May 24 21:52:01 2002
- List-id: Mailing list for users to share thoughts on Sun Cobalt products. <cobalt-users.list.cobalt.com>
"josh" <josh@xxxxxxxxxxxxxxxxxx> wrote:
> > Josh,
> >
> > Having just one primary and one secondary nameserver is perfectly
fine --
>
> No it's not. See the post I sent just before this one.
Josh, it really depends on the domain and how it's being used. You
referenced RFC 2182 which states that 2 nameservers are required, but it may
be beneficial to have more than 2 nameservers. IMO, there is little benefit
for the average RaQ admin to implement 3+ nameservers and that can be
burdensome to implement and manage, at least for the typical RaQ admin who
has a single box at his/her disposal (or multiple boxes on the same
network). You may be the exception to the rule - it really depends on how
your domains are being used and what the cost of all nameservers being
inaccessible is. As long as both nameservers are in separate physical
locations with different connectivity the likelihood that both will be
unreachable at the same time is pretty low. Unfortunately, a large
percentage of RaQ admins either have a secondary nameserver listed which is
either not actively maintained, does not exist, is on the same network as
the primary or is <shudder> on the same machine as the primary (which means
there really is no secondary). My opinion is based on several years
experience consulting for RaQ owners and observing discussions on the Cobalt
lists. <slight rant>It would be nice if these folks would just setup 2
nameservers properly. And implement solid backup/recovery solutions and
security plans *before* they find out the hard way that they need
them.</slight rant> Obviously, if a domain needed to be highly available,
say because it does large volumes of ecommerce, having 3+ nameservers is
probably advisable. As long as they're located on separate networks in
different geographical areas it's mathematically very unlikely all 3 would
ever be inaccessible at the same time. I'm not trying to get involved in a
holy war - I just wanted to make some observations. My 2 cents.
--
Steve Werby
President, Befriend Internet Services LLC
http://www.befriend.com/