@ericwentz where did you set that in kea? If kea is registering the entry? Did you set min ttl in unbound or something?

And watchdog sure shouldn't be needed.. It has had series issues in the past.

I'd backup the config.xml, edit it in Notepad++, and "Find/Replace All" the old prefix with the new. Save and import it when the time comes. But that's me, just an idiot on the Interwebs who doesn't even use v6.

@SteveITS I did restart but I have been adding a lot reservations so I I noticed it intermittently and just decided to give up and move away from Kea

I was able to find and delete the entry by searching the XML file and it was in virtual IPs.

@Gertjan Unbound's been running since May 1 on this router. Not using DHCP registration, or even DHCP on this router.

unbound 19499 0.0 2.3 124144 92208 - Ss 1May25 14:45.04 /usr/local/sbin/unbound -c /var/unbound/unbound.conf

One of Jim's comments in 8758 was, "The I state indicates it's sleeping for over 20 seconds and per-se is not the problem because filterdns threads sleep for 1 minute so it will stay as S in the first 20 seconds and then move to I." So that may just be a red herring.

I didn't write it above but the missing IP in question this time was my home, and I log in every single day. Also AFAICT the IP didn't change (no notification in pfSense). So the IP just disappeared from the table one day.

@Andy142

Pretty solid proof then that the ISP device, connected to the pfSense WAN port took down the interface.
Afaik : reasons can be : if its a modem type device : they do this to signal down stream a data carrier loss.
Bad power.
Bad NIC.

Most often, these ISP devices have also a GUI. It's time to have a look at, maybe there are details about the loss available.

@Gokulapandi
The DNS resolver doesn't hand out private IPs by default. You have to enable this with a custom option:

server: private-domain: "<your-domain.tld>"

The server line is only needed if you haven't one already, otherwise you can write the private-domain line below of it.

@johnpoz yeah, I guess 10 would be enough for some IoT devices like light bulbs, you garage door, window blinds or sun shades (whatever the right word).
For the DMZ on the other hand it may be a bit slow.

@DjJoakim yeah so stuff using other than your IP will be redirected, and stuff using the pfsense IP will be allowed.

@Gertjan

will do, thank you very much for your help

I have a laptop with a mapping for both the wired and wireless MAC, but when it gets a lease, instead of, for example, "laptop" as the client ID, it is "laptop." and gets a pool address instead, even though the MAC matches the reservation. Very annoying.

@webdawg said in KEA DHCP missing "Register DHCP leases in DNS Resolver...":

Sorry to necrobump, but I am a long term user of pfSense. I really feel strongly that this thread has been cr*apped on.
[ . . . ]
You are breaking things in one market segment, and then being rude to your users when they jump on your forums.

Your post seems to be directed at Netgate. But I count only two official Netgate replies (from the same poster) up until this point—and both are empathetic and respectful.

As one of the 'crappers' on the thread, I feel obligated to point out that the rest of us here are merely users like you, who may simply disagree with some of the points you and others are making.

@jeffry-maynard said in Kea server is down:

let me know if you have figured out a fix

You are using ... 2.7.2 ?
Afaik, there was a small patch avaible since the beginning to solve this situation.
Or, even better : 2.8.0 beta is out now for several weeks, and it look very promising,

@rtadams89 Is it the check-mk agent? Have you managed to solve?

@Gertjan said in Cannot contact VM via host name:

@tknospdr said in Cannot contact VM via host name:

When I try to ping by IP, it times out.

ICMP (is not UDP neither TCP) is allowed with firewall rules ?

I did say it worked via host name, that would show that ICMP is allowed, right?

@tknospdr said in Cannot contact VM via host name:

from a browser in

That browser uses what DNS ? Maybe not pfSense so it couldn't know about the host over ride.

Yes, all the browsers in my LAN use my pf box for DNS.

@tknospdr said in Cannot contact VM via host name:

If I enter the host name from a different subnet, I get a 'server dropped the connection' error.

The device with that host name, does it allow connections coming in from your other local networks ?

It does.

So I found out that I had to create a bridge network connection in order for my VM and host to talk to one another.
Everything seems to be talking correctly now.

My next hurdle is to get the packages I built the VM for to work, but that's beyond the scope of this forum.

For posterity, if you have TrueNAS and a VM, watch this video:
Network Bridge in TrueNAS