Free binds software for linux

tinybind is an add-on library for the tinyxml XML parser that makes it easy to "bind" a C++ struct definition to an XML file format for easy serializing and deserializing. It supports nested structs and STL containers.

myqslBind manages multiple DNS/BIND (8 and 9) name servers. mysqlBind automates updates to multiple DNS servers, centralizes and stores all zone and resource records for sets of related name servers (ns0...nsN.yourisp.net), and even manages different name server sets from a single browser-based interface.
Unlimited master and slave name servers update their zone information via a job queue system that uses MySQL socket connections. Advanced operations can use mySQL replication clusters for high availability and redundancy.
Large ISPs and other organizations should note that they can easily add SQL functions to customize the program for their special needs.
It supports authentication via SSL Unix password login, SSL personal certificate, or IP-based access with multiple permission levels and individual record ownership.
It is also compatible with mysqlISP.
Enhancements:
- This release has changed to new RAD3 templates.
- These are for a new clean look with a two step action confirmation tab-based interface.
- Many bugs have been fixed.
- Errors in tool-tip documentation, most regarding SOA TTL explanations, have been fixed.

ypbind-mt is a multi-threaded implementation of a NIS binding daemon. ypbind-mt compiles and works on Linux with glibx 2.x (libc6).
It should work on every System with POSIX threads and glibc 2.x. ypbind-mt works under Linux with libc5 and linuxthreads 0.7.1, but this C library isnt really thread safe and shouldnt be used with threads.
Main features:
- Supports bindings to multiple domains.
- Supports /var/yp/binding/* file for Linux libc 4/5 and glibc 2.x.
- Supports a list of known secure NIS server (/etc/yp.conf)
- Binds to the server which answered as first if the old one is down.
- Check all 15 minuts, if the current server is really the fastest.
Enhancements:
- ypbind has now DBUS support to watch network status messages from NetworkManager (if NetworkManager is used).

Bind9 SNMP Subagent provides indexed BIND 9 statistics via SNMP output. Data, query, and graph templates are provided for Cacti.
Enhancements:
- The duplicate %CFG variable (both in the library and script) has been removed.
- This release supports BIND 9 views.
- There are major documentation updates.

Blahz-DNS is PHP/MySQL based DNS (BIND 9/tinydns) administration with support for primary and secondary zones, user authentication, User and Admin account types (with read-only versions), and restricted access for user accounts to certain primary and secondary zones.
Enhancements:
Bugfixes:
- Search and replace now places updated zones into the updated table
Additions:
- Added import functionality. Will allow you to import zone files
- This is done by performing a dig @< dnsserver > < domain > AXFR and then parsing that output and inserting values into the DB.
- Added Search UI mode. Allows traditional listing mode and Search mode.
Changes:
- Swapped position of Write Zones and Restart server buttons since the old order didnt makes sense as you have to write the zones before restarting the server.

web-nsupdate is a web-based dynamic DNS update utility.

The web-nsupdate package provides a simple, web-based facility for clients to send dynamic DNS updates. Clients are typically DHCP hosts, such as a Linux system acting as a gateway for residential broadband service.

The client sends a simple web request (such as with the wget(1) or lynx(1) commands) to the web-nsupdate service to register their host request.

This package has been tested on a server with the following Debian packages:

* bind9 (ver 9.2.4-1)
* apache2 (ver 2.0.54-5)
* php4 (ver 4.3.10-16)

BE ADVISED: Its a pain in the butt to configure BIND to do dynamic DNS. You are going to need to do that to make "web-nsupdate" work. These instructions describe that process, so follow carefully. I *strongly* urge you to review the dnssec-keygen(8) and nsupdate(8) man pages first, so you can get some idea of what we are trying to accomplish.

Installation Instructions:

1. Copy the "web-nsupdate" files to a location such as
"/usr/local/lib/web-nsupdate". It is OK to install somewhere else,
just adjust the following directions accordingly.

2. Generate a TSIG key that "web-nsupdate" will use to authenticate
itself to the DNS server.

SECURE THIS KEY! Do not leave readable copies around. This key can
be used to make changes to DNS records managed by "web-nsupdate".

Here are the steps to generate the key:

cd /usr/local/lib/web-nsupdate
/usr/sbin/dnssec-keygen -a HMAC-MD5 -b 512 -n HOST web-nsupdate
chmod 440 Kweb-nsupdate*
# Below, adjust "www-data" to the GID your web server runs under.
chgrp www-data Kweb-nsupdate*

3. Setup the "web-nsupdate" definitions file, starting with the provided
sample. This file needs to be secured, to protect the client passwords
from being revealed.

cd /usr/local/lib/web-nsupdate
cp nsupdate-defs.php.sample nsupdate-defs.php
chmod 640 nsupdate-defs.php
# Below, adjust "www-data" to the GID your web server runs under.
chgrp www-data nsupdate-defs.php
vi nsupdate-defs.php

4. Verify that "nsupdate.php" has the correct path to the "nsupdate-defs.php"
file.

vi nsupdate.php
# Check the require_once() statement near the top.

5. Symlink the update script into your web site.

# Below, adjust "/var/www/nsupdate.php" to a location in your web server.
ln -s /usr/local/lib/web-nsupdate/nsupdate.php /var/www/nsupdate.php

At this point, the "web-nsupdate" front-end is configured. Now to
configure the nameserver back-end.

6. Assuming you dont already have a place for nameserver keys, create
a new file called "named.keys" that contains the TSIG key that
"web-nsupdate" will use. The file will look something like:

key web-nsupdate {
algorithm HMAC-MD5;
secret "jzzoMR4ocgZGq5pQho2Pr5r9DDHT4lWK8QO09cpvVtpvHqaUdzktBs1DHCslpPR8PwXU3ni8zjST/5FxEwg44Q==";
};

Replace the "secret" value show above with the key in the
"Kweb-nsupdate.+157+nnnnn.private" file you generated in step 2.

7. Install the "named.keys" file to the directory where your "named.conf"
resides. This file needs to be secured, to protect your namesever
from unauthorized updates.

If your "named.conf" directory is "/etc/bind", do:

# Below, adjust /etc/bind to directory where named.conf lives.
mv named.keys /etc/bind/named.keys
chmod 400 /etc/bind/named.keys
# Below, adjust "bind:bind" to the UID:GID your nameserver runs under.
chown bind:bind /etc/bind/named.keys

8. Add a line to your "named.conf" that says:

include "named.keys";

9. Modify your "named.conf" to list each host that web-nsupdate will
be updating. If, for example, you want to allow dynamic updates
from hosts "host1.example.com" and "host2.example.com", then modify
the "example.com" stanza in "named.conf" and add two lines:

zone "example.com" {
type master;
.
.
.
# add the lines below, one per host in thie zone
update-policy {
grant web-nsupdate. name host1.example.com. A;
grant web-nsupdate. name host2.example.com. A;
};
};

10. Test the update capability. Point your web browser to the installed
"nsupdate.php" script. This should bring up a form for manual
entry. Submit your entry, and verify the update was successful.