Re: [cobalt-developers] dns setup

[Jeff Lasman <jblists@xxxxxxxxxxxxx>]

Gerald waugh wrote:

> IMHO do not use the RaQ GUI to setup your named servers <RYE (or is it a
> (SCOTCH) grin>

A "wry grin" is shaped something like a "~".  It indicates I'm smiling
because I understand something I'd rather not be smiling about.

> unless you are willing to always edit the errors that the RaQ GUI
> inserts into the BIND records. Speaking from using the RaQ2 GUI, which
> will always break your reverse look-up, by conveniently writing a "/"
> instead of a "-" into your named.conf file!

I think I've said in many posts that the RaQ2 gui is NOT suitable for
managing DNS.  I apologize for not mentioning it every time.

> Plus will neglect to add
> $TTL <value> as the first line of the zone files, which will fill your
> log files with errors, when ever named initializes (starts, re-starts),
> not to mention the CPU - disk Access time required to write all the
> errors to the log file (/var/log/messages). Is The RaQ BroQe?

Maybe it is.  I don't recall this being a problem with the RaQ2 when I
had it.  Did an upgrade recently update Bind?  Probably, to eliminate a
security hole.  Perhaps they forgot to change the program that creates
the pri.* files; the old version of Bind didn't require the $TTL line.

> Maybe a
> little SUN will help! Is it time for a RE-CALL? Is it time for a
> CLASS-ACTION-LAW-SUIT? where is Ralph Nader?

Our running for president, as a matter of fact.  For the Green party.

> A system that promises so
> much, but delivers headaches, is QUESTIONABLE, at the least? I have
> spent more time and effort maintaining (correcting) the RaQ's errors
> than it takes to maintain the (few) troublesome issues with my NT
> servers.

It would seem then, that you should concentrate on NT servers, just as
I've learned to stay away from them because I can never seem to get the
things to work <wry grin>.  At the moment I'm trying to install W2K
Advanced Server.  I'm sure it's worth the money, if I can ever figure it
out <wry grin, again>.

> But, do create a secondary (slave in modern day terms) server... Your
> Master (primary)  .in-addr.arpa file must have entries for your
> nameservers (both Master and Slave), and, your Slave (secondary) must
> have entries in it's named.conf file to accept updates from the Master
> (primary).
> 
> There is no mystery about getting your nameservers registered in your
> ROOT TLD database, although it is never well explained!
> (1) get your nameserver records in order,
> (2) Go to your DOMAIN registrar (this is important)
>      There should be an interface whereby you can administer the name
> servers.
>      First ADD your nameservers as 3rd and 4th,
>      this being an exercise to see if they are accepted.
> (3) Then delete the primary (master) and secondary (slave) nameservers
> and make yours the
>     primary(master) and the secondary (slave)!

Aren't you know waying about the same as I've been saying for several
days now, that your nameservers must be registered with your registrar?

Jeff
-- 
Jeff Lasman <jblists@xxxxxxxxxxxxx>
nobaloney.net
P. O. Box 52672
Riverside, CA  92517
voice: (909) 787-8589  *  fax: (909) 782-0205