Dynamic DNS Services Update Scripts

Get the WebProNews Newsletter:

[ Business]

Strangely enough, I never had any need for a dynamic DNS service until this week. In retrospect, it really does seem odd that I’ve never needed such a service before now, but so be it.

My problem this week was that I wanted to set up a Kerio Mail Server in my office as a demo. My router could redirect the various ports I’d need, but I wanted to be able to send it real mail from the outside world, and although my cable assigned ip stays constant for months or even years, I needed a domain to send to.

Well, that’s easy. Visit http://www.dyndns.org, sign up for a free account, and it’s done. I assigned my current cable dynamic ip address to the hostname I chose, and now “xyz.dyndns.info” points to my cable modem.

In my case, I could have stopped there. The only time the dynamic ip changes is when I change routers. While that is something I do fairly frequently in the course of testing things, I certainly didn’t need to do it during the run of this demo, and even if I did, I could pop back to dyndns.org and update myself.

But what if I needed this for a longer term or if my dynamic ip address were more dynamic than it is now? Well, there are hundreds and hundreds of clients that will update dynamic dns services. Many home-use routers even have a client built into them (though the services warn against using these because most update too often for no reason).

Well, as usual, I don’t want to use someone else’s code. I’d rather understand how the thing works and do it myself. I might use someone else’s code after that, but almost always I want to get my own hands dirty first.

So, first problem: how to find the current ip address? If you are behind a firewall, there may be some way to get the device or computer to tell you. It might be as simple as an “ifconfig eth1″ if you are using a Linux router. But I change firewalls frequently, so I can’t depend on that.

There are places on the net that can help. For example, you can use http://checkip.dyndns.org/. At the command line,

lynx --dump http://checkip.dyndns.org/ > myip

will put your current ip into “myip”. That’s handy, and I’ll use that in the Perl script later in this article, but what if you don’t want to depend on things like that? If you have your own server hosted somewhere, you can use it to find out. It’s not hard to write a Perl server that listens for connections on a certain port and just logs the connecting machines ip, but you don’t even need to go that far if you have a web server. On a machine behind the firewall, have a script that does something like this every now and then:

lynx --dump http://yourserver.com/whatsmyip.html?564312 > /dev/null

The “whatsmyip.html” doesn’t exist, and the extra “?563412″ is just a number you make up. These accesses will be logged, so on the server we’ll find these in our access_log: - - [18/Sep/2004:10:01:01 +0000] "GET /whatsmyip.html?564312 HTTP/1
.0" 404 2240 "-" "Lynx/2.8.5dev.7 libwww-FM/2.14 SSL-MM/1.4.1 OpenSSL/0.9.7" - - [18/Sep/2004:11:01:01 +0000] "GET /whatsmyip.html?564312 HTTP/1
.0" 404 2240 "-" "Lynx/2.8.5dev.7 libwww-FM/2.14 SSL-MM/1.4.1 OpenSSL/0.9.7" - - [18/Sep/2004:12:01:01 +0000] "GET /whatsmyip.html?564312 HTTP/1
.0" 404 2240 "-" "Lynx/2.8.5dev.7 libwww-FM/2.14 SSL-MM/1.4.1 OpenSSL/0.9.7" - - [18/Sep/2004:13:01:16 +0000] "GET /whatsmyip.html?564312 HTTP/1
.0" 404 2240 "-" "Lynx/2.8.5dev.7 libwww-FM/2.14 SSL-MM/1.4.1 OpenSSL/0.9.7" - - [18/Sep/2004:14:01:01 +0000] "GET /whatsmyip.html?564312 HTTP/1
.0" 404 2240 "-" "Lynx/2.8.5dev.7 libwww-FM/2.14 SSL-MM/1.4.1 OpenSSL/0.9.7"

A simple shell script can extract “” which is what we need to know. That script could continue on to update the dynamic dns service.

So how do you update the service? Every service has their own method, but we’ll just look at dyndns.org. You can find the full details at http://www.dyndns.org/developers/, but the short version is that it updates by accessing a web page. You could do this with a shell script and lynx, but I’ll show a sample Perl program here. There are some rules we have to observe if we don’t want them to cancel our free account for abuse. First, they don’t want us to use the “checkip” more often than every 10 minutes. Second, if the ip hasn’t changed, we shouldn’t update more often than once every 28 days. Finally, if we get a problem response, we shouldn’t try again until we know why the problem happened.

These rules are complicated enough that we’ll probably screw up our code at least a few times, so dyndns.org provides test accounts you can work against. The code below uses such an account, so is safe for you to play with. It is intended to be run from cron at regular intervals, but it makes sure that it doesn’t run more often.

use LWP::UserAgent;
use HTTP::Request;
use HTTP::Response;
chdir("/root/dyndns") or die "can't chdir /root/dyndns $!";
# Try to get a lock just in case we got called again
# this isn't 100% foolproof but is good enough for this purpose
flock(O, 2) ; #block here
if (-e "badstatus") {
&nbsp logit("badstatus\n");
&nbsp myexit(0);
# Don't check more often than every ten minutes.
# We call this with cron, but this just makes sure
chomp $last;
close F;
if ($checkip) {
&nbsp while ($last > $now) {
&nbsp&nbsp printf "sleeping %0.2d\n",($last - $now);
&nbsp&nbsp sleep ($last - $now);
&nbsp&nbsp $now=time();
&nbsp }
&nbsp open(F,">currenttime");
&nbsp print F $now;
&nbsp close F;
&nbsp $what="http://checkip.dyndns.org/";
&nbsp $ua=LWP::UserAgent->new();
&nbsp $ua->agent("APL Perl/1.0");
&nbsp $req=HTTP::Request->new(GET=>$what);
&nbsp $response=$ua->request($req);
&nbsp if ($response->is_error() ) {
&nbsp&nbsp logit("Couldn't get $what");
&nbsp&nbsp myexit(0);
&nbsp } else {
&nbsp&nbsp $currentip=$response->content();
&nbsp&nbsp $currentip=~ s/.*Current IP Address: *//;
&nbsp&nbsp $currentip=~ s/..body.*//;
&nbsp&nbsp chomp $currentip;
&nbsp&nbsp open(F,"currentip");
&nbsp&nbsp $lastip=<F>;close F;
&nbsp&nbsp chomp $lastip;
&nbsp&nbsp open(F,">currentip");
&nbsp&nbsp print F "$currentip\n";
&nbsp&nbsp close F;
&nbsp }
$lastup=<F>;close F;
chomp $lastup;
$days=($now - $lastup)/(3600 * 24);
if ($days >= 28 or $lastip != $currentip or $debug) {
&nbsp&nbsp logit("update $days $lastip $currentip\n");
&nbsp &nbsp $what="http://members.dyndns.org/nic/update?system=dyndns&hostname=test.dynd
&nbsp&nbsp $ua=LWP::UserAgent->new();
&nbsp&nbsp $ua->agent("APL Perl/1.0");
&nbsp&nbsp $req=HTTP::Request->new(GET=>$what);
&nbsp&nbsp $req->authorization_basic('test', 'test');
&nbsp&nbsp $response=$ua->request($req);
# Lynx equivalent is
# lynx --dump -auth youraccount:yourpass "http://members.dyndns.org/nic/update?system=dyndns&hostname=yourhost.dyndns.info&myip=$currentip"
&nbsp&nbsp if ($response->is_error() ) {
&nbsp&nbsp&nbsp print "Error \n";
&nbsp&nbsp&nbsp myexit(0);
&nbsp&nbsp } else {
&nbsp&nbsp&nbsp $status=$response->content();
&nbsp&nbsp&nbsp print "$status\n";
&nbsp&nbsp&nbsp open(F,">lastupdate");
&nbsp&nbsp&nbsp print F $now;close F;
&nbsp&nbsp&nbsp myexit(0) if ($status =~ /good/ or $status =~ /nochg/);
&nbsp&nbsp&nbsp logit("Dyndns says $status\n");
&nbsp&nbsp&nbsp myexit(0);
&nbsp&nbsp }

sub myexit {
&nbsp&nbsp $a=shift;
&nbsp&nbsp flock(O, 8);
&nbsp&nbsp close O;
&nbsp&nbsp exit $a;

sub logit {
&nbsp&nbsp $a=shift;
&nbsp&nbsp print $a;

*Originally published at APLawrence.com

A.P. Lawrence provides SCO Unix and Linux consulting services http://www.pcunix.com

Dynamic DNS Services Update Scripts
Comments Off
Top Rated White Papers and Resources

Comments are closed.

  • Join for Access to Our Exclusive Web Tools
  • Sidebar Top
  • Sidebar Middle
  • Sign Up For The Free Newsletter
  • Sidebar Bottom