Secondary Name Server definition...and apologies to certain p arties

[Adrian Stovall]

	Allow me to clarify.  I did not mean to imply that it is good
practice not to implement redundant nameservers (actually, I meant to write
"if the DNS is down, the site is probably down too", as opposed to the order
I wrote it).  
	I apologize for the cavalier-seeming attitude my words may have
represented, and I was not pointing to a specific course of action, although
I try to mention the preferred method first.  
	From the gist of the original post on this matter, I was assuming
that Seb wanted to know how he could get things going period, so I tried to
explain what the two _possible_ routes to achieving this are.  I also
misakenly sent this reply to you personally (this time I will post only to
the list), and I apologize profusely.
	Seb, the _correct_ way to implement a nameserver is to use seperate,
redundant machines.  I know that it's not always possible due to the varying
budgets of individuals, but that's something to take into account when
hosting a domain.
	

-----Original Message-----
From: Kevin Darcy [mailto:kcd at daimlerchrysler.com]
Sent: Tuesday, August 29, 2000 5:27 PM
To: 'bind-users at isc.org'
Subject: Re: Secondary Name Server definition



What an awfully selfish point of view: "I don't care if every nameserver in
the
world is constantly retrying their queries to my dead machine because I
didn't
bother providing any redundancy". I'd like to think that DNS isn't just a
protocol, but also a *community*. One of the community rules is that you
make
your nameservice *robust*. Otherwise you're just pissing in the pool.


- Kevin

Adrian Stovall wrote:

>         You can assign two IP addresses to your single machine (known as
IP
> aliasing, or virtual IP addressing).  If you have a reserved range of
IP's,
> I'm assuming that either a).  you plan on adding more machines to your
> network (in which case, I would advise you to set one aside as a secondary
> DNS server) or b). you plan on your web server also answering DNS
requests,
> in which case, redundant DNS machines won't matter...if the site's down,
the
> DNS is probably down too.
>
>         In situation a, IP aliasing doesn't make much sense, in situation
b,
> it won't be any worse than if your web server crashes.
>
>         What operating system are you planning on using?  That little bit
of
> info will go a long way towards my giving a more informative answer.
>
> -----Original Message-----
> From: Kevin Darcy [mailto:kcd at daimlerchrysler.com]
> Sent: Tuesday, August 29, 2000 4:22 PM
> To: comp-protocols-dns-bind at moderators.isc.org
> Subject: Re: Secondary Name Server definition
>
> You should arrange for someone to be a slave for your domain. There are
> outfits
> that will do this for a fee.
>
> - Kevin
>
> Seb wrote:
>
> > Hello all
> > I have set up a server, I have reserved a range of IPs and I an going to
> get
> > my server plugged to the internet and when I want to register my domain
> > name, it ask me for a Primary Name Server which is the IP of my server,
> > until there that's cool but it also ask me for at least one Secondary
Name
> > Server, which can not be the same IP than the primary, I udnerstand
that,
> > but I don't know what to do...? I have one server only and it has one IP
> of
> > course so what should I put as a secondary name server ?
> > Thank you,
> > -Aur