Client domain in FQDN option

[Greg.Rabil at ins.com]

This looks like what I want, but I can't get this configuration to work.  Whenever I configure the following:

option server.ddns-hostname = option fqdn.hostname;
option server.ddns-domainname = option fqdn.domainname;

Then I see no DDNS updates happening at all on the server.  My packet captures show that FQDN Option 81 is configured with a value of 'client.test.com.' with the 'S' bit set ON.  The syslog output from the server indicates that no DDNS is even attempted.  I have configured 'ddns-update-style interim'.

Is there something else that I must configure to get this behavior?

Thanks,
Greg

From: dhcp-users-bounce at isc.org [mailto:dhcp-users-bounce at isc.org] On Behalf Of Denis Laventure
Sent: Saturday, October 11, 2008 11:22 AM
To: dhcp-users at isc.org
Subject: RE: Client domain in FQDN option

You might want to check http://marc.info/?l=dhcp-users&m=115410175622600&w=2

It works well for me.

Denis

De : dhcp-users-bounce at isc.org [mailto:dhcp-users-bounce at isc.org] De la part de Greg.Rabil at ins.com
Envoyé : 10 octobre 2008 17:20
À : dhcp-users at isc.org
Objet : Client domain in FQDN option

I have a question regarding the domain used for Dynamic DNS updates.  If I read the man page (and the code) correctly, it appears that the domain portion of the FQDN determined by the server is always taken from either the configured domain-name option (15) or the ddns-domain-name policy.  The hostname portion of the FQDN is derived from either the hostname option (12) supplied by the client or the leftmost label of the FQDN option (81).  That is, any domain provided by the client in the FQDN option (81) is essentially ignored by the server when performing the DDNS update.

1.  Is that correct?
2.  If so, that does _not_ violate section 4 of RFC 4702, as all references therein related to this are defined as MAY.  However, I was simply wondering if there was any plans to support additional behavior in the server to use the client's notion of the domain, or if there are any other workarounds that may be available.

Thanks,
Greg Rabil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20081013/d8c8c618/attachment.html>