headers
Brandon Philips | 11 Apr 2005 18:46
Favicon

Re: [Maintain-dev] Import scripts and i18n

Yves-Alexis,

> I'm new on this list, and I dont know if it's the right place to write.
> (if it's not, please forward me to the correct one)

You might be better served by the general maintain list, and I have
cc'ed that list also.  So you can pick up with the thread there if it
takes off.

http://lists.osuosl.org/mailman/listinfo/maintain

> I'm planning to deploy Maintain in the University of Rennes 1, France,
> to manage DNS and DHCP.
> I have two questions about features that could be useful in Maintain:
> 
> - import scripts for dhcp, dns and zone configurations

Oregon State University made the transition to Maintain long ago from a
very customized system.  As such we don't have any scripts for importing
existing DNS data.  Purdue University has scripts that may work, and
they are on the maintain mailing list, and hang out in #maintain on
irc.freenode.net.

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

> - internationalization
(Continue reading)

Permalink | Reply | 8 comments |
headers
Brandon Philips | 11 Apr 2005 19:07
Favicon

Re: How to do reverse dns

Greg,

Sorry for the long delay, I started writing the email last week, but
forgot to send.

> I haven't seen a good explanation of how to set up in-addr.arpa zones.  Do I
> just create the appropriate in-addr.arpas, and then when hosts get defined,
> they will automatically associate themselves with the right reverse zones?
> Each host belongs to a domain (which I assume to be the "forward" domain) but
> there's no place to tell it which reverse domain it goes into.  Hopefully it
> just does the right thing.  I'll be testing to see what actually happens if
> the in-addr.arpas are in a different admin zone.

For hosts the in-addr.arpas should not be necessary, tinydns
automagically creates the reverse pointer record.

http://tinyurl.com/3td8a

> Speaking of reverses, does maintain support CNAME-type reverses, like you
> would use to split up reverse dns into chunks that are not /16 or /24?
> Example:  My home site looks like this:
> 218.172.225.69.in-addr.arpa. 7200 IN    CNAME
> 218.216.172.225.69.in-addr.arpa.
> 218.216.172.225.69.in-addr.arpa. 21600 IN PTR   neko-base.nekodojo.org.
> 216.172.225.69.in-addr.arpa. 21600 IN   NS      ns2.nekodojo.org.
> 216.172.225.69.in-addr.arpa. 21600 IN   NS      ns1.nekodojo.org.
> 
> How would I tell Maintain that the data should be placed into
> d.0.c.b.a.in-addr.arpa instead of the standard
> d.c.b.a.in-addr.arpa?
(Continue reading)

Permalink | Reply | 2 comments |
headers
Greg Connor | 11 Apr 2005 20:13
Picon
Favicon

Re: How to do reverse dns

On Mon, 11 Apr 2005, Brandon Philips wrote:

> Greg,
>
> Sorry for the long delay, I started writing the email last week, but
> forgot to send.

Thanks for the reply.  Here's a quick followup...

> > I haven't seen a good explanation of how to set up in-addr.arpa zones.  Do I
> > just create the appropriate in-addr.arpas, and then when hosts get defined,
> > they will automatically associate themselves with the right reverse zones?

> For hosts the in-addr.arpas should not be necessary, tinydns
> automagically creates the reverse pointer record.
>
> http://tinyurl.com/3td8a

OK, sounds good.  I found out that the PTR records were being automatically
generated, but I created the in-addr.arpa domains in the Domain: Create
section because I wanted them to have SOA records as well.  (SOAs are needed
in order to transfer the zones to a BIND server.)

> > Speaking of reverses, does maintain support CNAME-type reverses, like you
> > would use to split up reverse dns into chunks that are not /16 or /24?
> >
> > How would I tell Maintain that the data should be placed into
> > d.0.c.b.a.in-addr.arpa instead of the standard
> > d.c.b.a.in-addr.arpa?
>
(Continue reading)

Permalink | Reply | 1 comment |
headers
Keith Rinaldo | 12 Apr 2005 00:52
Favicon

RE: How to do reverse dns

>For hosts the in-addr.arpas should not be necessary, tinydns
automagically creates the reverse pointer record.
>http://tinyurl.com/3td8a 

Brandon, is it possible/feasible to use Maintain in a pure BIND setting?
I'd like the ability to control creation of in-addr.arpa zones --
utilizing mainly auto creation of records when A records are created,
but to be able to change records if necessary.  If you're relying on the
functionality of tinydns to dynamically create the PTR records, is your
code / database not storing these zones / records?

Thanks. 

---
Keith Rinaldo
Network Security Administrator
University of Nevada, Reno
keithr <at> unr.edu

-----Original Message-----
From: maintain-bounces <at> lists.osuosl.org
[mailto:maintain-bounces <at> lists.osuosl.org] On Behalf Of Brandon Philips
Sent: Monday, April 11, 2005 10:07 AM
To: Greg Connor
Cc: maintain <at> lists.osuosl.org
Subject: Re: [Maintain] How to do reverse dns

Greg,

Sorry for the long delay, I started writing the email last week, but
(Continue reading)

Permalink | Reply | 1 comment |
headers
Brandon Philips | 12 Apr 2005 00:58
Favicon

Re: How to do reverse dns

Keith,

> Brandon, is it possible/feasible to use Maintain in a pure BIND setting?

Absolutely, Purdue is working on a script to create BIND zone files.  I
don't have the latest (or working) copy of their code, so you may want
to ping Sabian* in #maintain on irc.freenode.net.

> I'd like the ability to control creation of in-addr.arpa zones --
> utilizing mainly auto creation of records when A records are created,
> but to be able to change records if necessary.  If you're relying on the
> functionality of tinydns to dynamically create the PTR records, is your
> code / database not storing these zones / records?

The database stores the information necessary to create the reverse zone
(in-addr.arpa) in BIND, that is the IP address and the hostname.  We
just take advantage of the fact that the reverse PTR record is created
automatically when using the "host" syntax in Tinydns.

-Brandon

> -----Original Message-----
> From: maintain-bounces <at> lists.osuosl.org
> [mailto:maintain-bounces <at> lists.osuosl.org] On Behalf Of Brandon Philips
> Sent: Monday, April 11, 2005 10:07 AM
> To: Greg Connor
> Cc: maintain <at> lists.osuosl.org
> Subject: Re: [Maintain] How to do reverse dns
> 
> Greg,
(Continue reading)

Permalink | Reply | 0 comments |
headers
Keith Rinaldo | 12 Apr 2005 01:20
Favicon

RE: How to do reverse dns

Brandon, thanks for the quick response.

>Absolutely, Purdue is working on a script to create BIND zone files.  I
don't have the latest (or working)
>copy of their code, so you may want to ping Sabian* in #maintain on
irc.freenode.net.

Is this going to be an official part of Maintain when it's done or a
branch / plug-in / add-on type thing?  Maintain vs. Purdue Maintain?  :)
I actually have some PHP code that generates BIND zones (forward and
reverse) from a MySQL database that I wrote a few years back for out own
home-grown DHCP/DNS management system.  I abandoned the project when I
changed jobs, but I still have the code and it works.

>The database stores the information necessary to create the reverse
zone (in-addr.arpa) in BIND,
>that is the IP address and the hostname.  We just take advantage of the
fact that the reverse PTR
>record is created automatically when using the "host" syntax in
Tinydns.

Any current or planned support for dynamic DNS?  For instance, I'm
looking into using Maintain (in case I haven't mentioned this to you
already in another thread) in a forced-host-registration kind of setup.
Right now it's a decision between Southwestern's NetReg system and
Maintain, which I only recently discovered.  A registered host can be
given a "host" entry in the dhcpd.conf file (which is what I assume
you're doing...) and possibly be allowed to do dnynamic DNS registration
when it comes online.  Many of our zones will have static A <-> PTR
mappings, but a few zones would benefit from the ability to let the
(Continue reading)

Permalink | Reply | 3 comments |
headers
Yves-Alexis Perez | 12 Apr 2005 09:26
Picon
Picon

Re: [Maintain-dev] Import scripts and i18n

On Mon, 2005-04-11 at 09:46 -0700, Brandon Philips wrote:
> > I'm planning to deploy Maintain in the University of Rennes 1, France,
> > to manage DNS and DHCP.
> > I have two questions about features that could be useful in Maintain:
> > 
> > - import scripts for dhcp, dns and zone configurations
> 
> Oregon State University made the transition to Maintain long ago from a
> very customized system.  As such we don't have any scripts for importing
> existing DNS data.  Purdue University has scripts that may work, and
> they are on the maintain mailing list, and hang out in #maintain on
> irc.freenode.net.

Yes, I've already asked on #maintain and I've got some scripts from
sabiancrash (I think). But i was thinking about standard scripts
released with maintain.

> 
> 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.

> 
> > - internationalization
> 
> Internationalization is not currently planned, but if you undertook such
> an effort I would be willing to help with debugging, merging changes,
(Continue reading)

Permalink | Reply | 5 comments |
headers
Nathan Butcher | 12 Apr 2005 09:58
Picon

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


>  
>
>>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. :(

>>>- internationalization
>>>      
>>>
>>Internationalization is not currently planned, but if you undertook such
>>an effort I would be willing to help with debugging, merging changes,
>>and of course maintaining the patches once they were in a proper state
>>to go into the tree.
>>    
>>
(Continue reading)

Permalink | Reply | 4 comments |
headers
Yves-Alexis Perez | 12 Apr 2005 11:05
Picon
Picon

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

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 :/
> 
> 
> 
> >>>- internationalization
> >>>      
> >>>
> >>Internationalization is not currently planned, but if you undertook such
(Continue reading)

Permalink | Reply | 3 comments |
headers
Leslie Arvin | 12 Apr 2005 23:06
Picon
Favicon

Purdue Bind<->Maintain Import and Export Scripts

I'm afraid a student member of Purdue University's Maintain project team
has jumped the gun and released Purdue code which has not been fully
tested and confirmed to work correctly.  Therefore, I want to make sure
that those who have copies of either the Purdue scripts to import Bind
data files into the Maintain database, or the scripts to export the
Maintain database into a Bind-readable format are aware that the code
is without warranty or guarantees that it will perform as desired or
intended.  Neither the authors nor Purdue University are responsible
for any consequences of the use of this software, and, unfortunately,
we cannot promise the released code is free of copyright issues.

We of Purdue's Maintain project team intend to ask Purdue University
for permission to give our code to Oregon State as part of the Maintain
development project, and we believe we can present an excellent case to
do so.  We hope for licensing terms such that the code is freely
distributable with a simple acknowledgement to Purdue for their
contribution.  However, we have not yet received official approval
from Purdue University of our proposed licensing terms.  We are bound
by the rules of our university and must abide by the guidelines set
by the Purdue department responsible for software distribution.

We sincerely apologize for the inconvenience.

Meanwhile, if you have questions about our scripts or could benefit from our
experience, please feel free to ask for our help.

-- Leslie Arvin
    arvin <at> purdue.edu, Office: MATH B-060D, Phone: 765-496-3971
    Systems Administrator, ITI-Networks
    Purdue University, Information Technology at Purdue
(Continue reading)

Permalink | Reply | 2 comments |

Gmane