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

[Chris Adams <cmadams@xxxxxxxxxx>]

Once upon a time, Barry Titmarsh <barry@xxxxxxxxxxxxxx> said:
> DNS SOA records do require to have more than ONE NS pointer record.

No they don't.  They should, but they don't have to.

> on all Cobalt products there is no way to add the second NS pointer record 

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).

> You can only add an A record which creates the SOA with only ONE NS pointer 
> record. so with Bind 8.2 how does the DNS server inform its secondaries 
> there has been an update .  Well is cant because the SOA does not know 
> about any other NS's in the domain

Having the master inform the slaves is a nice thing, but not a
requirement.  The slaves will still automatically load the updated zone
after a bit (up to three hours), or you can manually force the slave to
reload.  That's the way everybody did it prior to BIND 8 (and the way
lots of people still do it).  And since the RaQ1 and RaQ2 only run BIND
4, they won't do notifies anyway.
-- 
Chris Adams <cmadams@xxxxxxxxxx>
Systems and Network Administrator - HiWAAY Information Services
I don't speak for anybody but myself - that's enough trouble.