[pkg-dhcp-devel] Bug#715036: [ISC-Bugs #34096] Re: ddns-hostname problems - DDNS updates not sent

Daniel Pocock daniel at pocock.com.au
Wed Jul 10 15:56:59 UTC 2013


On 08/07/13 23:11, Shawn Routhier via RT wrote:
> The fqdn option seems to be working properly to me. I believe
> the problem in your configuration is the line for the server:
> send fqdn.server-update off;
> This should either be commented out, removed or the off changed to on;
I have this in the server:

ignore client-updates;

Doesn't that mean fqdn.server-update should be ignored?

All the examples I found also had

send fqdn.server-update off;

in the client config.

In any case, changing the value as you suggest does appear to help, but
it doesn't appear to be a complete solution, I had to do more:

I tried sending both host-name and fqdn.hostname from the client and
neither seems to be recognised by lines such as
ddns-hostname = option host-name;
ddns-hostname = option fqdn.hostname;

so those don't seem to work.

I've found that if I send a full FQDN in fqdn.fqdn and put this on the
server:

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

then it does work for me.  So I have a working solution, but it appears
to be very rigid.

Many existing clients (e.g. Debian and Ubuntu) just send the "host-name"
option so it would be really nice to see that working.  Should those
other permutations work, or is it only possible to use fqdn.fqdn?

>
> I believe but haven't tested that ddns-hostname is properly scoped
> so if you set it in a host record you can assign a name per host record.
I'm having problems getting IPv6 host records working.  Should I match
by MAC or by DUID or are both supported?  I've tried each of them and
the clients don't seem to match.


> I'm marking this ticket as rejected for now. If you try removing the
> sever-update
> field and there are still problems please try a more recent server to verify
> the
> problem and, if it still persists, you can re-open the ticket by replying to
> this mail.
>
> My testing was done with a 4.2.4 client and a 4.2.5 server. You also may choose
> to not include the complete domain name in the fqdn option and have the server
> append the domain.
>
> Shawn
>
> On Fri Jul 05 17:28:11 2013, daniel at pocock.com.au wrote:
>> 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:
>> https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1088682/
>>
>> and it appears they pulled support for "fqdn.fqdn" in their default
>> client install
>>
>> 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
>>>> https://lists.isc.org/mailman/listinfo/dhcp-users
>>> _______________________________________________
>>> dhcp-users mailing list
>>> dhcp-users at lists.isc.org
>>> https://lists.isc.org/mailman/listinfo/dhcp-users
>>



More information about the pkg-dhcp-devel mailing list