IPv6 dhcp leases not registered in forwarder
-
I recently "upgraded" my 500Mbs home connection to an 100Mbs business class connection just to get a static ipv6 PD. Yay!, no more dynamic PD bulshit…
I'm using dnsmasq (unbound is restarting too often for my taste), and i have both Register DHCP leases in DNS forwarder and Register DHCP static mappings in DNS forwarder checked.
Nevertheless the ipv6 dhcp leases are not registering in dns. There are no problems with static leases (v4 or v6) and ipv4 dhcp leases.I'm running pfsense 2.2.6 amd64. My ISP is assigning a static ipv4 and a /56 PD through a pppoe connection.
The forwarder is set to listen on all interfaces and all settings are checked except Resolve DHCP mappings first, Query DNS servers sequentially and Strict Interface Binding.
Dhcpv6 server is set to serve a ::50-ffff pool out of a /64, Time format change checked, Domain name and Domain search list completed with example.biz, everything else default. The RA is set to managed with Use same settings as DHCPv6 server checked.Any thoughts?
Later edit:
Forgot to mention the following advanced settings in forwarder:
domain=example.biz
local=/example.biz/
expand-hosts
bogus-priv
localise-queries -
Ok, after some digging i've found this post https://forum.pfsense.org/index.php?topic=101143.0
It seems it's a limitation of either pfsense as a system or maybe it's components (isc dhcp, dnsmasq or unbound).
Either way, i came to the conclusion that the only way to register any ipv6 dhcp client in forwarder (or resolver ) is to define a static lease for it.
Now the obvious question….is this the intended behaviour in the IPv6 ecosystem? -
@Inq:
Now the obvious question….is this the intended behaviour in the IPv6 ecosystem?
Yes it is, by design… IPv6 DHCP clients do not send their host name to the DHCP server, only a DUID, consequently DHCP cannot populate unbound.
Ultimately DHCP client needs to use dynamic DNS to register itself in the DNS server once the lease has been obtained. This I'm afraid is more in the territory of an active directory deployment. -
Ok, so all i have to do is install bind or nsd and set dhcpv6 rfc2136 dyndns.
