NB : The mydns project appears to be dead, and a new project has (sort of) taken its place (mydns-ng). With this in mind, the module discussed here should be considered of VERY limited use.
First of all, you need to go here so you have an idea of what this is about.
This is a perl module written to help manage a mydns based server.
The idea was to provide a simple and clean interface, which also means that there aren’t a lot of additional or optional things enabled or supported.
Still, this should get you by if you need to do a lot of bulk management duties.
note – this project was pretty much abandoned ones I put together my own dnsadmin system to manage bind rather than mydns. This isn’t to say bind is better than mydns, but rather that the environment I deployed these in preferred bind.
here is the pod2html output for the module :
here is the module itself :
canary is a network inventory and monitoring system. Originally designed to track interfaces and configuration on core/edge network routers, it has been expanded to have a flexible monitoring system and to manage/display graphs using rrdtool.
The web interface is deployed using the Mite framework, and the monitoring servers are written in perl utilizing POE.
iphive is an inventory management system for IPv4 addresses.
Consider a network with more than one /24 IP block present, and a need to divide that into smaller blocks for allocating to for arbitrary uses. In our use case we will assume that you want to divide that /24 into /29 blocks. Obviously being able to track which of those /29 blocks are in use and what they are being used for is helpful. This system allows you to do this.
iphive uses a mysql database to keep track of the supernets, blocks, and addresses. The web interface is based on the Mite web framework and also contains an auditing tool meant to be run directly on a command line. The auditing tool uses SNMP queries against a user-defined set of routers to check for routes and confirm IP usage on a network and the blocks sizes actually used.