[Maintain] Re: [Maintain-dev] Import scripts and i18n

Leslie Arvin arvin at purdue.edu
Tue Apr 12 14:11:26 PDT 2005


Yves-Alexis Perez wrote:
> On Tue, 2005-04-12 at 16:58 +0900, Nathan Butcher wrote:
> 
>>>
>>>>If I had the time I would invest it in doing zone transfers from DNS
>>>>servers into Maintain using this:
>>>>
>>>>http://pear.php.net/package/Net_DNS
>>>>   
>>>>
>>>
>>>Well, i'll give it a try.
>>> 
>>
>>Sounds like a good idea. If there was a way I could capture some zone 
>>transfer output  and have a script turn it into a Maintain database all 
>>ready to go- that would be great.That way, it doesn't matter what 
>>DNS/DHCP management software you're moving away from, you could import 
>>all the data.
>>
>>....and making something like that sounds like a hell of a lot of work. :(
> 
> 
> Yes, but adding 10 000+ host into the maintain database is a lot of work
> too :/

10,000?  If only we had 10,000 hosts!  :-)  Try 100,000+ hosts and 177 master
domains.

The trouble with going straight from zone transfer output to maintain is parsing
the Bind file.  One of our network engineers says he tried to write a parser for
Bind a few years ago and gave up.

Pre-Maintain, we store our hostmaster data in multiple text files using a
subset of the Bind formatting rules.  These data files are what our import
script uses to import our current DNS setup into Maintain.  So files are
in a standard Bind format, but we don't have to deal with every possible
permutation one could get from zone transfer output.  This approach may
not work for everyone.

We have not yet tackled importing our DHCP into Maintain.

-- Leslie Arvin
    arvin at purdue.edu, Office: MATH B-060, Phone: 765-49-63971
    Systems Administrator, ITI-Networks
    Purdue University, Information Technology at Purdue


More information about the Maintain mailing list