[dhcwg] ddns-update-style and dhcp renewal

bao <bao@gibbons.com> Fri, 19 April 2002 00:09 UTC

Received: from optimus.ietf.org (ietf.org [] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA26170 for <dhcwg-archive@odin.ietf.org>; Thu, 18 Apr 2002 20:09:59 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id UAA14034 for dhcwg-archive@odin.ietf.org; Thu, 18 Apr 2002 20:10:02 -0400 (EDT)
Received: from optimus.ietf.org (localhost []) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA13969; Thu, 18 Apr 2002 20:08:37 -0400 (EDT)
Received: from ietf.org (odin []) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA13942 for <dhcwg@ns.ietf.org>; Thu, 18 Apr 2002 20:08:35 -0400 (EDT)
Received: from flounder.gibbons.com (sdsl-66-80-7-162.dsl.sca.megapath.net []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA26112 for <dhcwg@ietf.org>; Thu, 18 Apr 2002 20:08:30 -0400 (EDT)
Received: from gibbons.com (sdsl-66-80-7-180.dsl.sca.megapath.net []) by flounder.gibbons.com (8.11.2/8.11.2) with ESMTP id g3J08Ve26013 for <dhcwg@ietf.org>; Thu, 18 Apr 2002 17:08:31 -0700
Message-ID: <3CBF5FBA.143DFE40@gibbons.com>
Date: Thu, 18 Apr 2002 17:07:22 -0700
From: bao <bao@gibbons.com>
X-Mailer: Mozilla 4.79 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Dhcp <dhcwg@ietf.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [dhcwg] ddns-update-style and dhcp renewal
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <dhcwg.ietf.org>
X-BeenThere: dhcwg@ietf.org
Content-Transfer-Encoding: 7bit

I followed the recommendation to use dhcp 3.01rc8. However, the config
file for this version is not the same as that of 2.0xx. It requires the
use of "ddns-update-style ...".

What are the options for this line??

Currently, I have "ddns-update-style interim". This allows dhcp to
start, however, it always complains in the log file about "Unable to add
forward map from client.domain.com to server_ip: timed_out".

The second problem i'm encountering is when a lease is going to be
expired soon, the client owning the release  requests for a renewal.
This does not work and so the client loses its IP eventually. The log
shows many DHCPREQUEST from client and DHCPACK from server.

Although dhcp documenation says it's a must to have rules allowing
broadcast packets (67 and 68) through the firewall, I don't have this
enable and other machines (mostly 98) have no problem. The client having
problem is an NT, while other NTs also work fine.

Thanks for any pointers

dhcwg mailing list