Re: [cobalt-developers] Order of records in /etc/named/records

[Daniel Foster <daniel@xxxxxxxx>]

> > From looking at the way /usr/admserv/cgi-bin/.cobalt/dns/index.cgi
> > does things, I think the order of records in /etc/named/records isn't
> > relevant. I don't have a non-production RaQ3 to test things on, so a
> > bit of feedback here would be nice <smile>.
> 
> You are correct, the order does not seem to matter. The dns cgi can parse
> records properly no matter where they are located.

For anyone trawling through the archives, I can now confirm this - the
order of records in records (at least on a RaQ3) doesn't matter.

> > The reason being, if order doesn't matter, I could simply add any DNS
> > records I wanted to the end of the file, which would be much simpler
> > than having to put them at some point in the middle of the file.
> 
> Yes, you could do that very easily. Just append the new records to
> /etc/named/records , then restart named just by reloading
> /usr/admserv/cgi-bin/.cobalt/dns/index.cgi . In Perl you would just do:
> 
> system "/usr/admserv/cgi-bin/.cobalt/dns/index.cgi";

Yep, John's got this one right again - thanks John!

-- 

Daniel Foster - daniel@xxxxxxxx