DNS stops resolving following WAN IP change

DANgerous25

To make a long story very short :

Remove the check from here :

DNS resolver => DHCP Registration [ _] Register DHCP leases in the DNS Resolver

What happens is that for every new lease, dhcpleases process restart unbound ....
If some stupid device is asking a lease every second, unbound will get hail-stormed.

You can check the DHCP log, see what device is asking a lot (often) of leases.

I've disabled the DHCP registration.
I don't have a long DHCP log, but interestingly there is one device (which happens to be a Dyson fan) which almost exclusively fills up the log with DHCP requests... so you could be right @Gertjan . I've changed its lease to a static lease for now as well. I'm not sure what it is doing so will investigate separately.

Let's give it a few more days and see what happens again. Thanks a lot for your continued help!

DANgerous25

Hi @Gertjan , it's been a couple of days and in my logs I can see that "rc.newwanip" has been kicked off a couple of times, but I haven't had the "bind: address already in use" error and hence my automatic restart script has not needed to kick in. This looks likely due to the change of my Dyson fan to a static lease.

Thanks a lot for the suggestion for checking the DHCP log, I believe that has got to the bottom of this issue.

I'm considering this one solved! Thanks everyone for your help and suggestions.