Re: [cobalt-developers] DNS BUG in All Cobalt Products [missing feature]

[Chris Adams <cmadams@xxxxxxxxxx>]

Once upon a time, Barry Titmarsh <barry@xxxxxxxxxxxxxx> said:
> At 13:54 27/02/00 -0600, you wrote:
> 
> >Wrong.  It looks like the RaQ1 didn't allow this, but the I know the RaQ3
> >allows you to add multiple NS records for a domain (I don't know right
> >off about the RaQ2).
> Okay I have Qube2 here and is dont allow me to add the second NS record via 
> the Web front end,  I also have a RaQ2 here and that dont allow me to do it 
> either ? and My RaQ3 is the same,

Wrong again.  For example, on a RaQ3, all you have to do is modify the
SOA record for a domain.  It does only allow to put one more server in
there though.  On a RaQ2, you Add a Secondary Nameserver (NS) Record
(and you can add as many as you like).  I don't know anything about the
Qube series.

> So If you know how to add the second NS record without editing the 
> pri.domain.x.y.z Zone files directly and to only use the Web Front end then 
> please tell me. Thanks.

See above.

> It is a requirement to have
> 
> IN      NS      pri.dns.net.
> IN      NS      sec.dns.net.
> 
> as is the requirement to have more than one MX record. which you can add 
> via the WEB GUI Front end.

It is _recommended_ that you have this, but not _required_.

> So how do you get your two NS record into your Zone file then ?
> 
> [NS1.hiwaay.net]
> @                       12H IN SOA      ns1 hostmaster (
>                                          2000021800      ; serial
>                                          1H              ; refresh
>                                          5M              ; retry
>                                          2W              ; expiry
>                                          12H )           ; minimum
> 
>                          12H IN NS       ns1
>                          12H IN NS       ns2

That zone is not on a RaQ at all.  Our primary DNS servers are all
Digital Alpha servers.  A RaQ couldn't handle the load of our DNS.  We
have over 3400 zones, answering an average of over 70 requests per
second (that's a 24 hour average, so the peak is much higher).  The (in
memory) cache on one of our servers is almost 200MB, and it hasn't been
running a week yet even.  We only use the RaQs to enter DNS for domains
that are hosted on RaQs.

We don't put multiple NS entries into the zones on our RaQs, however.
But nobody queries the RaQs for DNS here; we list our Alpha servers with
Network Solutions and all requests go there.  The Alpha servers are all
setup as slaves of the RaQs.  You don't have to list the servers in the
NS records of the zone file.

> entries see the relevant RFC's and the DNS & Bind books  Also RIPE and RA 
> require this.

It is a recommended thing, but again, not required.  Now, domain
registries require you to have two servers listed that are authoritative
for a domain.  They _don't_ have to be listed in an NS records however.
If you configure a server as a slave and it gets a successful load of
the zone, it will be authoritative.

> The fact this feature in not included will stop me getting any more Cobalt 
> products for this company.

If you can't use the Cobalt interface for doing this, then maybe you
shouldn't buy any more Cobalts.
-- 
Chris Adams <cmadams@xxxxxxxxxx>
Systems and Network Administrator - HiWAAY Information Services
I don't speak for anybody but myself - that's enough trouble.