why is dhclient fqdn options processing & client_dns_update disabled (client->sent_options = 0L) ?

[Jason Vas Dias]

I'm the maintainer of the dhcp package at Red Hat,
and we've had a number of bugzillas about client
DDNS update not working in dhcp-3.0.1 .

This is because in dhcp-3.0.1rc9+, (now just dhcp-3.0.1) 
there is this line in dhclient.c, in make_request() @ line 1981:

   option_state_dereference(&client -> sent_options, MDL);

This line was not in dhclient prior to rc9. 

This sets client->sent_options to 0L, so when we get 
round to doing the DNS update, in client_dns_update, line 3072:

	/* If we didn't send an FQDN option, we certainly aren't going to
	   be doing an update. */
	if (!client -> sent_options)
		return ISC_R_SUCCESS;

So the client DNS forward update is completely disabled now,
regardless of any fqdn options setting. Is this intentional ? 

This has caused customers and myself much anguish playing around
with options trying to get client forward DNS updates working, and
all the existing docuementation suggests that client forward dns
updates should still work.

Can anyone explain why I should not re-enable client forward dns
updates by commenting out line 1981 in the Red Hat distribution ?