ddns-hostname problems - DDNS updates not sent
daniel at pocock.com.au
Fri Jul 5 17:27:58 UTC 2013
On 05/07/13 19:20, Steven Carr wrote:
> You might want to send bugs to dhcp-bugs at isc.org
> (I so wish the ISC would publicise their bug tracking, equally git/hg
> source code repos would be good).
Thanks, I'm cc'ing dhcp-bugs
Have other people had problems with DHCPv6 like this? I found some
posts suggesting it works and others suggesting that it doesn't.
There was also some discussion in Ubuntu:
and it appears they pulled support for "fqdn.fqdn" in their default
I've just tried the dhcpd package from Debian unstable (4.2.4-6) and
that has the same problem
> On 5 July 2013 17:46, Daniel Pocock <daniel at pocock.com.au> wrote:
>> Package: isc-dhcp-server
>> Version: 4.2.2.dfsg.1-5+deb70u6
>> Severity: important
>> I've found that DDNS updates are only sent if ddns-hostname is
>> statically defined, e.g.
>> ddns-hostname "some-name";
>> Of course, this is not useful because dhcpd will then use the value
>> "some-name" as the hostname of every host and the real hostnames won't
>> be in DNS at all.
>> On the client side, I've tried many different permutations, for example,
>> the Debian default is to send
>> send host-name = gethostname();
>> but I've also tried commenting that out and using:
>> send fqdn.fqdn "hostname.example.org."
>> send fqdn.encoded on;
>> send fqdn.server-update off;
>> also request fqdn, dhcp6.fqdn;
>> but it doesn't make any difference.
>> On the server side, I tried various permutations as well:
>> - not setting ddns-hostname at all
>> ddns-hostname = pick (option fqdn.hostname, option host-name);
>> and various other things I've seen in examples, such as
>> option host-name = config-option server.ddns-hostname;
>> option server.ddns-domainname = config-option host-name;
>> dhcp-users mailing list
>> dhcp-users at lists.isc.org
> dhcp-users mailing list
> dhcp-users at lists.isc.org
More information about the dhcp-users