IPv6 DNS Servers and IPv6 Leases page empty

Started by BP9906, September 02, 2023, 02:31:11 PM

Previous topic - Next topic
Hello,
New guy here so bear with me.
I setup Opnsense about a month ago and things are going well overall.
I am using nextdns CLI with DNSMasq because nextdns CLI is my resolver with DNS masq for local resolution.

I have DHCPv6 set to track interface because it was easy.  My ISP gateway hands out a /64 prefix and so it just works.  I did however enable the "Allow manual adjustment of DHCPv6 and Router Advertisements" on the LAN interface.  This is because I dont want to hand out the OpnSense local IPv6 address for DNS resolution.  As a result the DHCP leases page doesnt show anything active anymore, yet IPv6 assignments are working properly.
Is this expected behavior?

In case you're wondering:
The reason I dont want IPv6 handing out my local IPv6 DNS server address is because nextdns CLI doesnt properly name the host coming from IPv6 address that sent the DNS request. With all the DNS requests coming in via IPv4, nextDNS properly names the device and I'm able to use profile conditions to route Mac addresses to different profiles.

Thank you for your kind thoughts and feedback.

If you allow manual adjustment of DHCPv6 and Router Advertisements and want to use DHCPv6 (which isn't strictly required btw.), you have to specify an address range in the DHCPv6 server settings and set RAs to managed or assisted.

Cheers
Maurice
OPNsense virtual machine images
OPNsense aarch64 firmware repository

Commercial support & engineering available. PM for details (en / de).

This is a known issue fixed in 27.3.3, maybe even in 27.3.2 for some users (not for me, I needed .3)

Thank you both for replies.  I have RA set to Assisted.

9axque was right that the 23.7 now shows the leases.  Its better than it was.

Not sure if this is what Maurice was referring to, but the leases show as status "offline" but state is active.

I'm guessing that the Assisted mode is assuming stateless so its sort of an ambiguous who has what address.

I think I'll have to look at DHCPv6 config.  I see my ISP assigns me a prefix with /64 so that looks good.  DHCPv6 might be the way to go long term.