Free dns update software for linux

popdns is a small daemon that aims at simplifying the use of DHCP-configured machines by allowing them to dynamically update their DNS entry using (nearly) any POP3-capable e-mail tool.

After having configured a new e-mail source (with the POP3 protocol), users are authenticated using their system password and popdns automatically updates the specified (or implied) DNS entry with the IP address of the connecting machine.

popdns makes all DNS modifications with plugins. The plugins are external programs (scripts or compiled programs) simply launched with the following arguments:

plugin ipaddress name [ name ... ]

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.

UpdateIP application is used to update a machine ip for the JumpGate service (similar to dynamic DNS, for keeping track of machine IPs).

You must have an active account on http://jump.x2studios.com to use this software.

You can sign up for a free week. A year subscription costs $12.

To use the script edit the settings in the top half of the updateip file (use vi or pico or whatever you want).

To add updateip as a scheduled task add it to your crontab, the following crontab will update every helf hour:

01,31 * * * * perl /Path To Script/updateip s

dnsutl package is a collection tools to make administering DNS easier. These include:
dns-rev
Take the forward DNS mapping and generate the reverse mapping. This is useful for producing a self-consistent DNS configuration.
dns-ethers
By using a bogus record type, you can keep the MAC address with the IP address, and generate the /etc/ethers file.
dns-hosts
Take the forward DNS mapping and generate the /etc/hosts file.
dns-bootp
Using the MAC and IP information, you can generate the /etc/bootptab file.
dns-ng
Take the forward DNS mapping and generate the /etc/netgroup file.
dns- bootparams
Using the MAC and IP information, you can generate the Sun /etc/bootparams file.
dns-boot- check
Check your named(8) configuration for self- consistency.
dns-hosts-import
Turn your /etc/hosts file into a DNS forward map, as a first step to configuring your DNS server.
dns-dhcp
Using the MAC and IP information, you can generate the /etc/dhcp.conf file.
All of these programs are both faster than shell scripts, and more robust when faced with all the peculiar semantics of DNS resource files. They even understand the $include directive.
dnsutl runs on almost any flavor of UNIX. The source distribution is self configuring using a GNU Autoconf generated configure script.
Enhancements:
- A bug has been fixed in the SRRF parser, so it more closely follows RFC 1035.
- A bug has been fixed in the name server (ns) record validation.

DNSDusty is my answer to the above problems that I saw in existing web-based DNS management tools.

All updates to DNS are done through the dynamic DNS interface, using signed updates. There is no external database. It simply does a zone transfer when it needs to get a listing of records.

It has worked well for me so far on my home DHCP/DNS server, which uses the ISC BIND and DHCP server. It has very basic functionality at this point. You can add records one at a time, and can delete them via checkboxes.

Installation:

DNSDusty comes set up to be installed according to the Debian packaging guidelines. The sources also come with an EPM listfile. If you have the EPM program installed (see http://www.easysw.com), then you should be able to package the software by running:

% epm -v -f native dnsdusty

Once you generate the package, install it with your OSs installation tool.

Youll then need to modify the config file, which is by default at etc/dnsdusty/dnsdusty.conf.

The config file should only be writable by root, and only readable by the user that your webserver runs as. Since it contains the key to allow updates to your webserver, make sure that you secure it well, unless you want the world to be able to update your server.

PowerDNS daemon Nameserver is a advanced, modern and high performance authoritative-only nameserver.
It is written from scratch and conforms to all relevant DNS standards documents. Furthermore, PowerDNS interfaces with almost any database.
The PowerDNS Nameserver utilizes, a flexible backend architecture can access DNS information from any data source. This includes file formats, Bind zone files, relational databases or LDAP directories.
If you have specific needs for your DNS infrastructure then you can use the Backend Developers Kit to write the glue between PowerDNS and your data or logic.
There is one master database that is replicated to two slave databases. The slave databases are read-only and are updated immediately when the master database changes.
For sites that do not yet have an existing database infrastructure we recommend the MySQL database. MySQL is very easy to setup and handles replication well.
If your nameservers are located on different physical networks then you immediately take advantage of the distributed nature of DNS. Questions will be load balanced on your array of servers. If a server is down then one of the other servers is queried.
PowerDNS is by default configured to serve all information directly from a database, which results in unmatched maintainability of your DNS information.
PowerDNS has developed a complete suite of technologies surrounding Internet Naming and email. Internet Naming is at the core of all online activities and is involved in each and every transaction on the net. Email remains the killer application of the Internet.
Enhancements:
- This release fixes many issues, unifies the PowerDNS Recursor and Authoritative DNS infrastructure (reducing code size by 2,000 lines), significantly improves the "BIND" compatibility mode (making real life zone loading up to 30 times faster than the original BIND), addresses many corner cases, reworks the TCP backend for improved stability, and makes 64 bit packages available.

Tired of clicking the reload button? Page Update Checker (aka PUC -- pronounced "Puke" is a FireFox extension that automatically checks to see if web pages have changed.

How to Use:

Once installed, you will be able to right-click on any page in Firefox and select "Monitor for Updates". The PUC options will open up and you can select how often you would like PUC to download the webpage and see if it has changed. To return to the options menu later, select "Tools" -> "Page Update Checker Options..."

Click the homepage link to find the PUC Wiki and share your Update Checkers!

DHCP-DNS update DNS servers according to DHCP requests.

This version is an upgrade of the real v0.52 version. It only includes support for servers that manage several domains (multiple domain name). It is no longer a need to tell the name of the domain the DNS server administrates.

One just tells the path to your dhcpd.conf file and the perl script manages alone to find the domain names (option domain-name).

A problem could occur when puting a host from a LAN to another. This problem does not come from the perl script, but from the DHCP server: in old DHCP servers, the implementation does not totally respect the RFC2131 that specifies that to release a lease, the client must provide its UID and its current IP address.

Older DHCP servers were releasing leases only according to UIDs, and were investigating IP addresses only if no lease for the UID had been found. This problem is solved since the version 2.0pl2.

However, it is very easy to patch an old server to make it compliant, and thats what has been done in the version 2.0b1pl6 version available on this site.