At 07:11 PM 3/15/00 -0800, you wrote:
> If the RaQ is acting as a nameserver for a domain, yes, it should have a > nameserver record pointing to it. Hmmm, well, the GUI is misleading. It labels the option as "Secondary Nameserver (NS) Record." So I should add a NS record to point at the raq, which is acting as a primary.
Since I don't usually use the RaQs DNS interface, I didn't realize what you meant. I presumed when you said you had only NS record, you meant in the zone file, not in the RaQ's web-based gui interface.
I really didn't know if the RaQ Interface creates a primary NS record by itself or not, so I went ahead and created an A record using the RaQ's web-based gui interface.
Then I clicked on "Save Changes to DNS Server".Guess what: The RaQ2 DOES NOT create a NS record. Even though it says secondary, I'd create one for each. I trust the book more than the Cobalt's web-page.
Of course if Cobalt's got any DNS gurus who read this list, I'd love to hear from them <smile>.
No, I don't have a copy of DNS & Bind. :)
This doesn't seem to be a DNS & Bind issue; it seems to be a cobalt interface issue <smile>.
I'm seriously thinking of setting myself up as an Amazon sales-affiliate, that way instead of saying "have you gotten a copy of "DNS & Bind" I can say: "click here to order your copy of "DNS & Bind" <smile>.
Jeff -- Jeff Lasman <jblists@xxxxxxxxxxxxx>