On 5/21/07, Patrick Doyle <wpdster@xxxxxxxxx> wrote:
I'm nowhere closer (as far as I can tell), but I've just enabled syslog to dump everything and I've noticed that when dhclient starts up, after it gets its IP address, it logs the following message: Unable to add forward map from <hostname> to <A.B.C.D>: timed out where <hostname> is the name I specified in the dhclient-eth0.conf (I've tried just the hostname, and the fully qualified hostname, with and with out the trailing period) and <A.B.C.D> is the IP address fetched from the DHCP server. From everything I've read, I believe that I should be able to enable this by adding the following lines to /etc/dhclient-eth0.conf: send fqdn.fqdn "<hostname>"; send fqdn.encoded off; # or, perhaps "on" send fqdn.server-update false; and I've tried send fqdn.no-client-update off;
continuing on after I must have hit the send key... The DHCP and DNS servers are both windows servers locked in a closet someplace. I would like to figure out what option I need to set on my FC6 boxes to enable dynamic updating of the DNS records on those servers. It works from the windows hosts (managed by our IT department), but I can't figure out why it doesn't work from my Linux hosts (managed by me). I presume that the "unable to add forward map...timed out" message is the result of dhclient attempting to make the DDNS update. I have no idea where that timeout is specified, otherwise I'd try doubling it to see if that makes a difference. I have no idea to which port it is attempting to connect (nor which protocol), otherwise I'd try changing that. I have seen references to DDNS updating things securely, but I have no idea where to plug in an "update" key into dhclient (nor do I even know what words to use to ask our IT department what update key they've programmed into all of the myriad windows PC's around the organization -- I suspect they have not, so I suspect I'm on the wrong track here). Any and all clues will be gratefully accepted. --wpd
