AIX 4.3.3. DDNS

[donsri]

I am running AIX 4.3.3 on an IBM RS/6000 model F50. I have configured and activated both DHCP and DNS, both of which are working just fine. However, when I plug my laptop into the network and let the DHCP server give my laptop an IP address, the other machines on the network can't find my laptop by name like they can if I put an entry in the /etc/hosts file (or the named.data file) on the F50 (with the current laptop IP address). The solution appears to be DDNS (dynamic DNS) which, according to the AIX 4.3.3 manual, should update the DNS table whenever DHCP hands out an IP address. I have tried to configure DDNS according to the IBM manual, but I can't get it to work. Is there anyone who has done this that can give me some direction, or perhaps a sample of DHCP and DNS configuration files that use DDNS successfully? ANY help would be most appreciated!
Thanks,
Don

 

[aixqueen]

I found a few things that may be of assistance to you....Not an expert on this...
but maybe it will help. Or maybe someone else will respond.

http://techsupport.services.ibm.com...mode=9&documents=090605201414638&database=aix

================
CASE 6: DDNS and the nameserver configuration

File: /etc/dhcpsd.cnf

NOTE: This information does not contain the usual documentation found inside the /etc/dhcpsd.cnf file.

The following two lines of code should appear on one line.

updateDNS "/usr/sbin/dhcpaction '%s' '%s' '%s' '%s'
BOTH NONIM >>

This line must be uncommented in the /etc/dhcpsd.cnf file. The nameserver must support DDNS. At the time of this writing, AIX 4.1.4, AIX 4.2.0 and AIX 4.3.x are
the only operating systems that support DDNS. No other vendor's operating system supports DDNS with the exception of WindowsNT beta v4. This beta or test version
of WindowsNT may support DDNS.

Please perform the following steps for DHCP and DDNS.

In the /etc/dhcpsd.cnf file:

1.Uncomment the following line; it should appear as one line:

updateDNS "/usr/sbin/dhcpaction '%s' '%s' '%s' '%s'
PTR NONIM >>

The PTR means the pointer record will be updated. This is the default value. If you want to update the A record and the pointer record, you should change PTR to BOTH.

That line will read (the following two lines of code should appear on one line):

updateDNS "/usr/sbin/dhcpaction '%s' '%s' '%s' '%s'
BOTH NONIM >>

2.Change the /etc/named.boot file as follows:

primary domainname.com /etc/named.data dynamic controlled
primary in-addr.arpa /etc/named.rev dynamic controlled

The dynamic keyword is required for the named.rev line if the updateDNS line shows the PTR update. Since the updateDNS line shows BOTH NONIM, then the dynamic keyword is required for the named.data and named.rev lines in the /etc/named.boot file.

Add the keyword controlled to the dynamic lines, as it acts like secured and allows updates.

Refresh the named subsystem. Enter: refresh -s named

DDNS is documented in the online product documentation using the following search path:

List of Books
AIX System Management Guide: Communications and Networks
TCP/IP Name Resolution

EXAMPLE /etc/named.boot file:

primary ztrans.com /etc/named.data dynamic controlled
primary 0.0.127.in-addr.arpa /etc/named.local
primary 32.3.9.in-addr.arpa /etc/named.rev
cache . /etc/named.

--------------------
another users info:
IBM chose to ship both BIND4 and
BIND8 code with AIX 4.3.X, and what's worse is that as shipped the default is to run BIND4. Yech. You have to delete the named, named-ixfr and nsupdate links in /usr/sbin, then link the BIND8 commands back in their place.

As for the dhcpaction8 and dhcpremove8 scripts, make sure
the nsupdate commands buried in the scripts work out in
your shell. I had to massage the IBM provided scripts
a bit to get them to work. Especially the dhcpremove8
script, which was delivered almost completely broken. They
do contain text to the effect of "This script is intended
to be modified by the customer", so I suspect IBM expect
a bit of customization.

Be sure to check your reverse zone to make sure it can be
dynamically updated (zone file is writable, zone is defined
as dynamic in the named.conf), and that there is a zone for
each IP network being served out by your DHCP service.

#-)