Package: dhcp3-server
Version: 3.0.3-5
Severity: wishlist
Hello!
For more than a week I'm fighting with DHCP-DNS update
in our local network. We have Windows machines, *Linux
and *BSD ones. On *Linux I mostly have pump as DHCP
client (for reasons not to be disclosed here I prefer
pump, udhcpc and dhcpcd to dhcp3-client). I hacked pump
to provide DHCP FQDN option, but without any success
due to dhcp3-server deficiency.
We have 2 DHCP servers
(dhcp3/ddns-update-style=interim), several DNS servers
and several domains (forward zones). Some clients must
request an IP and register A RR in _specific_ zone (i.e.
non-default for their IP subnet). I prefer to configure
fqdn/domainname/zone _at client_ and rely burden of
updating A RRs to DHCP daemon.
At first glance, client sends DHCP FQDN option and can
request a server to register A RR, using FQDN Flags
field.
Problem is that ISC's software ignores client's claim
for zone, WRT forward (A RR) updates.
citing `man dhcpd.conf`:
It will use its own domain name for the
client, just as in the ad-hoc update scheme. It will then update both
the A and PTR record, using the name that it chose for the client.
http://www.ietf.org/internet-drafts/draft-ietf-dhc-fqdn-option-11.txt:
the Client FQDN
option, which can be used by DHCP clients and servers to exchange
information about the client's fully-qualified domain name for an
address and who has the responsibility for updating the DNS with the
associated A and PTR RRs.
...
A client can choose to delegate the responsibility for updating the
FQDN to IP address mapping for the FQDN and address(es) used by the
client to the server.
...
there is a possibility that the DHCP server is configured to
complete or replace a domain name that the client sends,
...
(And unfortunately, this is the case with dhcp3-server,
which ignores/overrides client's intentions).
...
The server MAY be configured to use the name supplied in the client's
Client FQDN option, or it MAY be configured to modify the supplied
name, or substitute a different name.
I'd like this to be [at least] configurable. I can make
a patch for the "use the name supplied by client"
feature (e.g. honor-fqdn-domain), if anybody in Debian
is interested in this...
P.S. After failure with pump against dhcp3-server, I
tried more "native" dhcp3-client with all combination
of relevant options, without success too, as the
problem is in server, as described above.
--
WBR,
xrgtn
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (990, 'testing'), (500, 'oldstable'), (500, 'unstable'), (500,
'stable'), (1, 'experimental')
Architecture: i386 (i586)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.4.32-grsec
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Versions of packages dhcp3-server depends on:
ii debconf [debconf-2.0] 1.4.66 Debian configuration management sy
ii debianutils 2.15.2 Miscellaneous utilities specific t
ii dhcp3-common 3.0.3-5 Common files used by all the dhcp3
ii libc6 2.3.5-8 GNU C Library: Shared libraries an
dhcp3-server recommends no packages.
-- debconf information excluded
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
