[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-developers] DNS BUG in All Cobalt Products  [missing feature]
- Subject: Re: [cobalt-developers] DNS BUG in All Cobalt Products  [missing feature]
 
- From: Barry Titmarsh <barry@xxxxxxxxxxxxxx>
 
- Date: Sun Feb 27 10:46:28 2000
 
At 09:50 27/02/00 -0800, you wrote:
At 09:11 AM 2/27/00 +0000, you wrote:
DNS SOA records do require to have more than ONE NS pointer record.
on all Cobalt products there is no way to add the second NS pointer 
record 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
Slight terminology problem, Barry.  The SOA record start at "titmarsh" and 
ends at the ")".  The NS records (and yes, you need more than one for 
robust name service) are called NS records.  I've got a light problem with 
you calling anything but PTR a pointer record; it makes things more 
confusing to me <wry grin>.
Er ?
I used that domain as an example taken from the cobalt that knows not how 
to make an additional NS record for the listed secondary in the TLD co.uk
and the other was taken from my regular DNS that has both NS pointers for 
the listed pri and sec dns' in the TLD co.uk
the point I was reporting was there is no way to add the secondary NS 
record to the SOA that the Cobalt dns web front end gui uses. so it only 
possible to make SOA records with one NS line
maybe I cut and paste no so accurate in the posted email its was just an 
example for the cobalt code guys to get to fix.  I have been DNS Hostmaster 
long enough to know bind x.x.x  inside out,  I run 4 ripe LIR Registries hi hi,
And the whole thing (which I think is what you mean when you refer to a 
DNS SOA record) is called a zone file.
Ok just a name there is still a BUG you cannot add a second NS entry to the 
SOA record or Zone file what ever you want to call it.
This needs to be fixed fast please else as an ISP I cannot use Cobalt 
boxes as DNS's as a result of this I have to withdraw 10 boxes from 
service and go back to my Old systems
And it's pretty easy to use the RaQs for DNS even though they have this 
problem.  Just don't use the gui interface.
We've been doing that quite successfully.
Well in our organization we cannot have badly setup DNS its a must to have 
the Zone file report all listed NS that are pointed to by the TLD
Jeff
--
Jeff Lasman <jblists@xxxxxxxxxxxxx>
Thanks Barry
_______________________________________________
cobalt-developers mailing list
cobalt-developers@xxxxxxxxxxxxxxx
http://list.cobalt.com/mailman/listinfo/cobalt-developers
----------------------------------------------------------------------------
Peering Committee               Nacamar GmBh PLC
                                P.O.Box 102262
                                63268 Dreieich / Germany
E-mail: peering@xxxxxxxxxxx     fon: +49-6103-916-0
www.nacamar.net                 fax: +49-6103-916-999
http://peering.nacamar.net.uk   Automated Peering Forms
----------------------------------------------------------------------------