@webdawg said in KEA DHCP missing "Register DHCP leases in DNS Resolver...": Is 2.8.0 community working with KEA and DNS Resolver? Yes, I am on 2.8.0, and KEA now works well with DNS resolver. The DNS server now resolves client.mydomain.xx for leases received via KEA DHCP server.

Configure DNS-over-TLS to prevent the ISP from eavesdropping the entire LAN's (including unbound's) DNS lookups. The documentation has a config recipe.

@marcg Thanks I have switched to ISC, will remain there till they figure out the issues with KEA

I figured this out. Our tailscale config included a floating firewall rule that blocked tcp/443 on the sync interface. I removed the rule and everything syncs now.

@luckman212 Testing the latest version, with syslog:kea-dhcp4 output. Working perfectly, so far. Logs are being sent to my syslog server. Thanks @luckman212

@Gertjan thank you!

it seems same issue of: https://forum.netgate.com/topic/197667/update-2-7-2-to-2-8-0-dynamic-dns-not-working-with-cloudflare/17 which I found later on

@viragomann Thanks. I knew it was a default IP address -- that's the first time I've ever seen a name put to it though. I'll double-check when I get home tonight. But I thought I did have it in the trunk.

@0x44 Router interfaces don't typically 'change' (i.e., unplug/replug, link up/down) that regularly. In order to have Wi-Fi even, you'd need to somehow get an AP on at least the same management broadcast domain as the LAN interface without directly connecting it... because how else would you expect to be able to connect to and manage it? Directly connecting a network host like a PC or a server to a router interface is a somewhat unsual setup. @SteveITS's advice to connect a switch to the LAN interface—and then properly test connectivity of any/all devices that will connect to the switch, plus assess overall network stability with that topology—is the right advice.

watching

Hi, after some testing, it seams that is now working with the "TFTP Server" Option under "Other DHCP Options". But just with the new Release 25.07 with Release 24.11 its not working. You just need the enter the 3CX Provisionen URL in the Field, without any special Character like ' or ''

@SteveITS Thanks; I believe I found the root cause... the mmc in my 4200 was dying and is now dead, replaced by a nvme..

@Gertjan o/ Hey, sorry for the lack of replies, I was on a vacation. Upgrading to 25.07 seems to have fixed the issue. After upgrade, I can see the dynamically assigned DHCP leases under the "Leases" menu: [image: 1755260165183-590d93cd-a189-42d8-be3c-953b70eb0395-image.png] I guess this is solved now.

@Gertjan I suspect that can be a change in the MV configurarion on proxmox. It's weird, I mean, i change a parameter on mv configuration (Static ram vs balloning) but changes in proxmox needs shutdown and start again, are not applied until shutdown. For now i'm testing and checking every 2-3 hours and now it's everything ok.

@tgvoelker Sounds similar to my thread: https://forum.netgate.com/topic/196927/filterdns-has-stopped-resolving-hostnames-in-firewall-aliases

@patient0 Got it. Thanks for the help