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
