RE: [cobalt-users] Configuring 2nd Raq for doing secondary DNS

["Rodolfo J. Paiz \(E-mail\)" <rpaiz@xxxxxxxxxxxxxx>]

> I was referring to settup up a secondary name server
> on a 2nd RAQ, not secondary dns for a domain. I'll try
> again and hopefully do a better job of explaining...

Actually, you explained it fine the first time. It's just that they are
the same answer.

By the way, please go check the archives for this; I know I've written
this answer at least four times personally in great detail and so have
others. The archive check will get you quicker answers, and because it's
there I'll also be more brief than usual here today:

* There is no such thing as a secondary name server. There are only name
servers. Therefore, you must enable BIND (the DNS server) on your second
RaQ for it to do DNS.

* You have one MASTER and one-or-more SLAVE servers for a domain. You
input the detailed records on the master, and all the rest are slaves.
In your case, the second RaQ is a slave for each domain.

* You tell clients to ask the PRIMARY nameserver first, then the
SECONDARY servers if this doesn't work. (Of course, clients ask whomever
they want, but this is the theory.) Your primary should be the faster
machine on the better network since it'll get the lion's share of the
requests. Usually the primary is also the master, but since they all
have the same info it (usually) doesn't matter. In your case, you tell
the registrar that RaQ-1 is the primary NS and that RaQ-2 is the
secondary NS for each domain.

* Bottom line: to make your RaQ-2 a "secondary name server" you merely
input the detailed records into RaQ-1 (the master and primary) and tell
the RaQ-2 to do slave DNS service FOR EACH DOMAIN.

Let us know if this is clear enough.

--
Rodolfo J. Paiz
rpaiz@xxxxxxxxxxxxxx <mailto:rpaiz@xxxxxxxxxxxxxx>