Don't get DHCPv6 static mappings to work with Unbound DNS

[skr]

Dear all,

in 23.1.6 I don't get DHCPv6 static mappings to work with Unbound DNS. DHCPv4 static mappings are working just fine.

On the roadmap there is an accomplishment in 21.7 named „IPv6 prefix DHCP lease registration in Unbound/Dnsmasq“. Is there still a bug related to it?

Sure this is not fully the same, but related. Since the WLAN privacy feature in Apple iOS, the hostname is always empty for me and DHCP registration does not work without static mappings. Please tell me, if I am somehow wrong about this.

Thanks for any help!

Regards
Sebastian

[skr]

Hi again,

managed to get it working within DNS meanwhile. Did not recognize the remark to add the IPv6 address suffix within the static DHCPv6 mapping. „If no IP address is given above, hostname will not be visible to DNS services with lease registration enabled.“

root@OPNsense:~ # host SebastiansiPad.guest
SebastiansiPad.guest has address 192.168.4.11
SebastiansiPad.guest has IPv6 address 2003:XXXX:XXXX:XXXX:1:1:1:2
root@OPNsense:~ #

Unfortunately the reporting does not seem to be prepared for dealing with IPv6 (dual-stack) hosts. Have a look at the attached screenshot. There is no reverse name resolution for IPv6 addresses as it seems.

Does anyone know a solution to get IPv4 and IPv6 addresses „joined“ (both resolved to hostname) within reporting?

Thanks and best regards,
Sebastian

[franco]

IPv6 DHCP name registration is faulty in itself so it never worked and probably never will.


Cheers,
Franco

[skr]

Hi,

thanks for your reply, Franco!

Does someone have any insights/outlook regarding my additional question?

Unfortunately the reporting does not seem to be prepared for dealing with IPv6 (dual-stack) hosts. Have a look at the attached screenshot. There is no reverse name resolution for IPv6 addresses as it seems.

Does anyone know a solution to get IPv4 and IPv6 addresses „joined“ (both resolved to hostname) within reporting?

Thanks and best regards,
Sebastian

[CJ]

IPv6 DHCP name registration is faulty in itself so it never worked and probably never will.


Cheers,
Franco

Can you elaborate some on what you mean by this?  I've been looking at migrating my setup to a dual stack but haven't made the jump yet.

[franco]

It's very simple: isc-dhcp software does not forward host names in IPv6 or does not even receive them from the clients.


Cheers,
Franco