DDNS-Updates with nsupdate or compareable
kcd at daimlerchrysler.com
Tue Jan 21 20:02:31 UTC 2003
Falk Husemann wrote:
> Kevin Darcy <kcd at daimlerchrysler.com> wrote:
> > Just give the input file as the last parameter on the command line, or
> > pipe the commands to nsupdate.
> This is exactly my problem. How does such a file need to be layouted?
> I've seen some strange things (like an EOT in a File) around in the Web.
Look at the nsupdate man page. I can't imagine why an embedded EOT would be
necessary (except maybe on wintel).
> Another Thing is the IP-Question. Does anyone know how I can get it for
> a specific (ippp0 for example) Netword-Device?
Using what language/API/OS? In C on Unix, there are ways to step through
the interface list and look at the properties of each interface. The exact
specifics of the API may differ between flavors of Unix (AIX was
particularly painful, I seem to recall). As for other languages/APIs/OSes,
I wouldn't know...
> BTW: Is there a way to show my zone-file using nsupdate or any other
Remotely, you mean?
You can retrieve the *data* of your zone using utilities like "dig" or the
zone-transfer capabilities of the Net::DNS Perl module. "dig" will even
format that data in master-file format, by default, so it'll look like a
zonefile. Note that for zone transfers to work, you either need to have
zone-transfers unrestricted on the authoritative server, or you need an
"allow-transfer" clause in order to permit it.
*BUT*, this is just the *data* of the zone. It's not an exact copy of the
zone file. All of the comments, formatting (including any $INCLUDE or other
directives) will not be present in the zone-transfer data. If you want a
literal copy of the zone *file*, you'll have to resort to more generic,
non-DNS-specific methods like FTP, scp, NFS or whatever.
More information about the bind-users