[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [cobalt-users] Re: How to use .include file to add secondary dns



On Sat, May 25, 2002 at 05:05:26PM -0400, Steve Werby wrote:
> "josh" <josh@xxxxxxxxxxxxxxxxxx> wrote too much as usual:
> > To remove the capablity when it previously
[snip]
> 
> I don't have access to an XTR, otherwise I would test myself, but have you
> tried adding other nameservers either by separating them with a space or a
> comma?  It's possible the expected input method changed in the XTR.  I agree
> that if the functionality to add multiple secondaries isn't present in the
> XTR interface that oversight is something that should be brought to Sun's

So how do you bring anything to Sun's attention.

> attention so they can consider correcting that in a future PKG.  If a
> modification is required it'll probably be an addition of 2-4 lines of code,
> unless the data is written to a database before writing the zone files, in
> which case the modification will be more extensive.

I did try both commas and spaces and have had no luck.  I suspect
there might be some other way, as there are still some options whose
purpose is unknown to me. I have a box where I can allow zone
transfers from many domains -- it strikes me that if I wanted to use
this feature I might wish it to have a one to one relationship with my
secondaries.

There are two entries to add "secondary name service for domain" and
"secondary name service for network", which I believe I would use to
secondary DNS for someone else. Neither ask for the information that
would be required for an NS record and I couldn't find either from the
built in help (clicking on question marks) or reading the manual what
records they would create. I happen to really believe that the web
interface and documentation would be improved by stating what records
get generated. They have this for A, PTR, CNAME, and MX records. I
believe that the webface does allow unusually complex sub networking.

-- 
Josh Kuperman                       
josh@xxxxxxxxxxxxxxxxxx