26.07: kea2unbound stopped being dynamic?

[keyser]

I have observed a strange issue today. I'm configuring a basic IPv4 26.07 install from scratch, and need quite a lot of aliases that refers to internal registered DNS names.
So I have enabled the KEA option to register DHCP clients in DNS. I'm running Unbound as the DNS server for clients and pfSense itself and basic Unbound works as expected:

EXCEPT: No DHCP clients are registered in DNS dynamically. None of my clients are DNS resolvable until I restart Unbound.
Upon restart all existing DHCP leases then works as DNS registered. That includes leases that are no longer active. A reboot of the Firewall with no clients connected - thus no new/renew of DHCP leases - still has ALL existing leases DNS registered.....

I have not enabled Early DNS registration, only the normal one.

Is this a 26.07 bug, and how do I go about diagnosing what's happening?

[luckman212]

@keyser Not disputing what you're seeing there, but I just want to add my data point. I am also running 26.07 with a large number of static DHCP reservations in Kea across a few VLANs with different DNS suffixes.

The dynamic registration and resolution with Unbound seems to be working for me. I wonder if you've confirmed the DNS suffix that's actually getting sent to Unbound (via wireshark etc)

I've shot myself in the foot a number of times where pinging an unqualified host name was appending an unexpected suffix. Example, ping foo where foo becomes → foo.lan when what I actually meant was ping foo.iot

Just a thought.

[keyser]

@luckman212 Yeah, I checked that is not the case - and like I mentioned, they are all registered perfectly after an unbound restart, so the "work" has been done and the suffix is correct.

EDIT: I'm going to have to troubleshoot a bit more tomorrow

[luckman212]

Ah, I will test if I add a quick DHCP reservation without rebooting or restarting Unbound and see if it gets resolved "on the fly". I didn't test that.

[keyser]

@luckman212 It's not reservations I'm working with. Just dynamic DHCP clients that are supposed to become DNS registered "on the fly". They are not.
They become DNS registered once unbound restarts, regardless of they are long gone and not coming back. As long as the ephemeral lease they got at their connect time is still valid, it get's registered after restart.

EDIT: The last part is not necessarily a problem as the lease is still valid, but that no dynamic registrations work is a HUGE problem

[luckman212]

I just fired up an Ubuntu VM with a bridged network to my LAN.

Its hostname was abc123 - it grabbed an IP from the DHCP pool. I ran ping abc123 from my Mac and it resolved successfully. Not sure how my setup is different but I'm sure we'll figure it out.

[dennypage]

@luckman212 said in 26.07: kea2unbound stopped being dynamic?:

I just fired up an Ubuntu VM with a bridged network to my LAN.

Its hostname was abc123 - it grabbed an IP from the DHCP pool. I ran ping abc123 from my Mac and it resolved successfully.

Is your Ubuntu VM hosted on your Mac with Parallels?

[luckman212]

No it was a VM created by VirtualBuddy. I also just tested resolution from one of my Proxmox nodes on the LAN, and that was successful too.

[dennypage]

@luckman212 said in 26.07: kea2unbound stopped being dynamic?:

No it was a VM created by VirtualBuddy.

Hmm... had not heard of VirtualBuddy, but it may have the same "feature" that Parallels does of automatically registering the client hostname in the host.

[luckman212]

Yes I updated my comment above, I also tested from a completely separate Proxmox host (succeeded)