The following files have been placed in this directory e:\fromindia\pmr03703 ,
               254587      A          03-13-01   08:17  dhcpcd.exe
               303239      A          03-13-01   08:17  nsupdate.exe
 Both the files are at os2warp99 level. The nsupdate.exe has been modified
 for this pmr. The dhcpcd.exe has the sysroute of defect 41355 (aurora43,
 aurora). The files may be installed as follows,
      (a) Take the backup of files dhcpcd.exe and nsupdate.exe in the directory
      \mptn\bin
      (b) Copy the given files in that directory.
      (c) For checking the working of '-k' option the following steps may
      be followed,
         (1) Create the private key for the client from client machine by
         executing the following command,
         nsupdate -g -kc:\dhcpcd\ddns.dat -hclient11 -din.ibm.com -pns-updates
         This should create the key in ddns.dat in the directory c:\dhcpcd for
         the host client11 in the domain in.ibm.com. A sound is usually heard
         when the keys are generated. Please check the file for the key after
         executing the command.
         (2) Please make the following modifications in the dhcpcd.cfg ,
            (i)  option 12 client11     # hostname
            (ii)  updateDNSA "nsupdate -kc:\dhcpcd\ddns.dat -h%s -d%s -s"d;a;*;a;a;%s;s;%s;3110400;q" -q"
         (3) Now start the client, after the client gets the IP address it registers
         it with the nameserver and another sound may be heard at this time.
         (4) (i) To check whether the address is registered with the nameserver,
            nslookup - <IP address of nameserver>
            and enter fully qualified domain name(check11.in.ibm.com) at the prompt
            The name server should give the IP address of the client.
             (ii) check nsupdate.log for ,
                  (a) Should have received updateDNS A record template.
                  (b) Should have accessed name server (IP address is usually present)
                  (c) DDNSxxxUpdate...succeeded (necessary). If DDNSSignUpdate has
                  failed with -11(authentication failure )then newly generate the keys and try again.
DESCRIPTION :

  Previously the nsupdate agent when it receives packets through AFOS2 socket
  from DHCP client did not check for -k option (but it does this when executed from
  command prompt). When spawned from dhcp client it just used ETC variable
  to access the ddns.dat file. The code has been changed so that it does check
  for -k option in the updateDNS A template packet it receives from DHCP client.




