Re: [cobalt-users] DNS Problems

[Kris Dahl <kris@xxxxxxxxxxxxx>]

Oh man.  That sucks.  I was in the same boat about 4 months ago.  I was
trying to migrate from another DNS server to the Raq.

I chose, however, to bail on those original zone files 'cause I realized
that they were inconsistent and best and obviously not done correctly.

I wrote a script in PERL (it was based loosely upon a shell script that
someone gave me--which helped greatly in understanding what the records file
WAS) that help me automate the process of re-creating them so that the new
admins of the server could use the web interface.

Depending on how many records you have this may or may not be an option.
I'd be willing to dig up that script (spiff it up a little bit) and send it
to you.

The syntax of the records file isn't too difficult to use--you could
probably create a script that converts from you pri files to the records
file.  Then run the dns control panel interface that cobalt uses, hit save
changes and it will create the properly formatted, cobalt friendly pri
files.

The other work around would be that you don't HAVE to use the cobalt
interface.  It sucks.  The Raq2 is using standard stuff--in this case BIND.
If you are comfortable with admining your own DNS in the typical fashion and
are comfortable configuring bind, then you are in good shape.  Just bail on
the interface and be done with it.  That wasn't an option for me in the case
mentioned above because I wouldn't be adminning the DNS.

If you are thinking about going this route, I'd suggest picking up the DNS &
BIND book from O'reily and Associates.  Top notch!

-k

on 12/10/99 12:20 PM, lists at lists@xxxxxxxxxxxxx wrote:

> I didn't manual edit the pri files. I need to dump the records file and
> reload it with the pri files. How do I do this? I can't loose all the info
> in the pri files.
> 
> 
> At 11:50 AM 12/10/99 -0800, you wrote:
>> on 12/10/99 11:16 AM, lists at lists@xxxxxxxxxxxxx wrote:
>> 
>>> Anyone ever have this problem?
>>> 
>>> The cobalt Admin Control Panel doesn't display the same information that is
>>> in the pri.domain.com file.
>>> 
>>> If I do an nslookup of a domain, it says can't find domainname. Everything
>>> was working fine yesterday morning but today, dns is screwed. How do I get
>>> the control panel to be updated with the pri files and get things back up
>>> and running ?
>> 
>> Are you manually editing the pri.domain.com file?
>> 
>> This is one of the more asinine things that Cobalt has done.  Instead of
>> reading the pri.domain.com files and using that for the user interface, it
>> uses a file called records.  I believe that file is in /etc/named/ or /etc
>> 
>> This is basically a list of all the A records, MX records and ALIASES, and
>> reverse dns records that are in all of the pri. and in-address files.  After
>> you screw with your dns settings with the web interface (which is writing to
>> your records file), it runs a script that parses you records file and
>> converts it to the pri files, updated your named.conf and runs /sbin/ndc
>> reload.
>> 
>> If you run an 'save changes' from the web interface it will overwrite
>> everything in the pri. files (including any changes you've made).
>> 
>> Hope that clears it up.
>> 
>> -k
>> 
>> 
>> _______________________________________________
>> cobalt-users mailing list
>> cobalt-users@xxxxxxxxxxxxxxx
>> http://list.cobalt.com/mailman/listinfo/cobalt-users
>> 
> 
> _______________________________________________
> cobalt-users mailing list
> cobalt-users@xxxxxxxxxxxxxxx
> http://list.cobalt.com/mailman/listinfo/cobalt-users
>