Hehe I hunkered down with nsupdate as well (funny what working with Linux will do for your ability to work with Linux) ;-P
I'm not versed in nsupdate yet, but it will definitely do what you need it to (as you've already found out by now). The even better news is that automation is probably just a step away, since it sounds like dhcpcd, pump, and dhclient all have similar functionality that can be used to help automate the process. If you're using dhcpcd, it should be as simple as either triggering a script from, or including the individual commands in this file: /etc/dhcpc/dhcpcd_e.exe That file (from my reading, needs testing) gets fired every time the IP changes, and not even at startup if the IP has not changed. Here are the contents by default (Slackware 8.1): #!/bin/sh echo "(dhcpcd) IP address changed to $1" | logger So ideally, all you'd have to do is add the appropriate nsupdate commands after that and feed it the $1 variable: #!/bin/sh echo "(dhcpcd) IP address changed to $1" | logger server srns1.superreal.net prereq yxdomain open2space.com update delete open2space.com update add open2space.com 900 in a $1 update add open2space.com 900 in mx 10 $1 server srns1.superreal.net prereq nxdomain www.open2space.com update add www.open2space.com 900 cname open2space.com Of course, if that code isn't working, don't use that, but you get the idea. In the event that $1 doesn't work, it appears (again, from reading, needs testing) that you should be able to toss in the shell variable IPADDR instead. Let me know which DHCP client your router is using, and I'll have a peek at getting it automated. Curtis. -----Original Message----- From: Shawn Grover [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 11, 2003 8:19 PM To: '[EMAIL PROTECTED]' Subject: (clug-talk) Dynamic DNS - Partial Success WHOOO HOOOOOOO!!!!! I'm starting to see the light at the end of the tunnel.... I hunkered down and studied up on NSUPDATE. I'm sure I don't have things quite right, but I was able to wipe my entries on the Superreal name server, and replace with with an IP of my choosing. Unfortunately, I was only expecting this change to affect MY DNS server - but nsupdate is smart enough to move up the slaves to the authoritative server, and make the change there. Here's the script I now have: ;-------------------- server srns1.superreal.net prereq yxdomain open2space.com update delete open2space.com update add open2space.com 900 in a 209.89.234.79 update add open2space.com 900 in mx 10 209.89.234.79 server srns1.superreal.net prereq nxdomain www.open2space.com update add www.open2space.com 900 cname open2space.com ;-------------------- this is stored in a file called o2supdate. I can run it via "nsupdate o2supdate" In my testing, I had the server lines pointing to my internal address, and picked some arbitrary internal IP for the update add lines. when I did an nslookup open2space.com - I got a response from the Telus name server with the IP had entered.... Now, I think I'm stuck in that period of time when name servers are getting updated. So I'll try the command again in an hour (my script was using a 15 minute TTL), and see how it goes. All that's left I think is to automate the script, and tie up loose ends on my own DNS server (return it to a caching server I think). Hope this helps someone out. Also, if anyone can offer suggestions on how to improve my script, I'm all ears.... Shawn
