Free dynamic dns update software for linux

dyndnsupdate is a tool for keeping dynamic DNS hosts up to date. It simply processes the URLs in dyndns.hosts config file (sends a HEAD request via HTTP). No biggie, but it works.
Put dyndns.hosts in /etc and run dyndnsupdate from an init-script. That way youll be sure that your dyndns hosts are up to date within minutes after rebooting and perhaps changing IP address.
On my Debian box Ive put dyndns.hosts in /etc and linked to dyndnsupdate from etc/rc2.d, like this:
ln -s /usr/bin/dyndnsupdate /etc/rc2.d/S91dyndnsupdate
That will make sure that dyndnsupdate is up and run when rebooting.
Furthermore, it can be encouraged to run dyndnsupdate as a cron-job as well, in case your server should be up for more than a month, since most dyndns providers requires you to update at least once a month.
This can be done by adding the following line to your crontab:
15 5 */25 * * dyndnsupdate -s
Thatll make cron run dyndnsupdate every 25 days at 5:15AM and -s makes the script output nothing (unless errors are encountered) so youll be rid of the annoying exit status mails from cron.
Enhancements:
- Added win32/ for windows builds with exerb.
- added win32/LICENSE
- added win32/README

dynamic window manager or dwm is a dynamic window manager for X11.
As founder and main developer of wmii I came to the conclusion that wmii is too clunky for my needs. I dont need so many funky features and all this hype about remote control through a 9P service, I only want to manage my windows in a simple, but dynamic way.
wmii never got finished because I listened to users, who proposed arbitrary ideas I considered useful. This resulted in an extreme CADT development model, which was a mistake. Thus the philosophy of dwm is simply to fit my needs (maybe yours as well). Thats it.
Main features:
- dwm has no Lua integration, no 9P support, no editable tagbars, no shell-based configuration, no remote control, and comes without any additional tools like printing the selection or warping the mouse.
- dwm is only a single binary, its source code is intended to never exceed 2000 SLOC.
- dwm is based on tagging and dynamic window management (however simpler than ion, wmii or larswm). It manages windows in tiling and floating modes. Either mode can be applied dynamically, depending on the application in use and the task performed.
- dwm doesnt distinguishes between layers, there is no floating or tiled layer. Wether the clients of currently selected tag are in tiled mode or not, you can re-arrange all clients on the fly. Popup- and fixed-size windows are treated floating, however.
- dwm is customized through editing its source code, that makes it extremely fast and secure - it does not process any input data which hasnt been known at compile time, except window title names and status text read from standard input. You dont have to learn Lua/sh/ruby or some weird configuration file format (like X resource files), beside C to customize it for your needs, you only have to learn C (at least editing header files).
- Because dwm is customized through editing its source code, its pointless to make binary packages of it. This keeps its userbase small and elitist. No novices asking stupid questions.
- dwm uses 1-pixel borders to provide the maximum of screen real estate to clients. Small titlebars are only drawn in front of unfocused clients.
- dwm reads from standard input to print arbitrary status text (like the date, load, battery charge). Thats much simpler than larsremote, wmiir and what not...
- It can be downloaded and distributed under the conditions of the MIT/X Consortium license.
- Optionally you can install dmenu to extend dwm with a wmii-alike menu.
Enhancements:
- This release contains certain major bugfixes, especially regarding banning/unbanning client windows.

Dynamic Imager provides a small product with which you can generate dynamic images given a text.
This enables you to rotate text in browsers that do not support that.
The DynamicImager product is a small utility product that uses PIL to generate images on the fly, given a few parameters, like the font to use, a text, a background color, etc.
This enables you to rotate texts in browsers that normally do not support that option, but you can do much more.
The product currently supports:
- font
- text
- fill color
- background color
- width
- height
- rotation in degrees
- x offset for text
- y offset for text
Enhancements:
- includes a demo with all features of the product

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.

Dynamic Copyright it! is an easy-to-install, easy-to-use PHP script that adds copyright notices to your images dynamically, meaning that the copyright notices are generated on the fly.
If you get tired of changing the copyright on your images from year to year, this tools makes it so you never have to. You can use the Dynamic Copyright It! script for your own benefit, or add it to your web site for additional functionality.
Main features:
- Dynamic Copyright It! is easy to install. Just unzip and upload, or if youre using it on a local server, just unzip!
- Choose your copyright text, the font size, even the color!
- Dynamic Copyright It! integrates the copyright notice right in the image, so its difficult to remove.
- Copyright notices are added to images on-the-fly, making it so you can easily integrate other scripts to alter the copyright text site-wide without having to edit all of your images manually.

Dynamic Probe Class Library (DPCL) is an object-based C++ class library that provides the necessary infrastructure to allow tool developers and sophisticated tool users to build parallel and serial tools through technology called dynamic instrumentation.
Dynamic Probe Class Library takes the basic components needed by tool developers and encapsulates them into C++ classes. Each of these classes provide the member functions necessary to interact and dynamically instrument a running application with software patches called probes.
Dynamic instrumentation provides the flexibility for tools to insert probes into applications as the application is running and only where it is needed.
Enhancements:
- This version is a minor update to DPCL that fixes a couple problems that have been reported since the v3.4.2 release

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.

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