nsupdate/DNS mgmt tool
Kevin Darcy
kcd at daimlerchrysler.com
Mon Feb 5 22:05:58 UTC 2001
Yes, I've invented that wheel also :-)
In my case, I'm just using the CGI module for the frontend and wrapping
around "nsupdate" for the "middle tier". My reason for not using using the
Dynamic Update part of Net::DNS was because of all the scary disclaimers in
that module, but Michael Fuhrman posted recently in this list that those
disclaimers are probably obsolete. I'm planning to convert what I have to
Net::DNS Dynamic Update. In my copious free time, of course...
- Kevin
Ian Watts wrote:
> Listers,
>
> I am looking into the feasibility of making a robust medium/large-scale
> BACKEND dns management system using nsupdate with a web front end in order
> to be able to control all backend (internal network) DNS updates from a
> single entry point. There are over a dozen backend nameservers in the
> network in question. I have a relatively simple working prototype and
> suspect it's possible to create a tool that would have full error-checking
> and good security (remember, protected internal network). I am using
> mod_perl/Mason to program the web interface.
>
> Does anyone here have experience with such a thing or advice regarding the
> usability of nsupdate like this? Is there more complete nsupdate
> information available other than the man page?
>
> I want to avoid being forced to implement Lucent's QIP product for this
> purpose and think I might be able to make a more streamlined and far less
> expensive solution myself.
>
> I can provide more details of my prototype if that would be of interest.
>
> I welcome any comments.
>
> Regards,
>
> -- Ian Watts
More information about the bind-users
mailing list