Unbound DNS fails after reconnect?

[Drakon]

Hi everybody!

I am new to OPNSense, set it up over the weekend and to 99% everything works fine. However i get a forced reconnect once a day by my ISP and to counter that i set up a cron job into the OPNSense to do a forced reconnect at 3:30 AM for the WAN Interface.

The WAN Interface leads to a fiber Modem and from there to the Internet. I setup PPPoE on that.

Now last night the reconnect happened and at first glance it all seemed to work good, i got a new IPv4 Adress and a new IPv6 Prefix, all worked fine, however i noticed that the Unbound DNS seemed to stop working.

Devices in my Network weren't able to do any name resolving at all across all networks. I am a bit confused on why this happened, the Logs of Unbound are also not really helping, as there were no errors or warning. I only found this under  System -> Log Files -> Backend:

Code: [Select]

2022-04-05T03:32:39 Error configd.py Timeout (120) executing : unbound cache dump
But nothing more. I have the checkbox ticked to receive new DNS Servers over the WAN / PPPoE connection. I have a suspicion that this might be the issue? That i did not receive, for whatever reason, new DNS Servers?

Also my setup for the Cron Job, not sure if that might be the problem:

Code: [Select]

Minutes: 30
Hours: 3
Day of Month: *
Months: *
Days of Week: *
Command: Periodic Interface Reset
Parameter: opt1

(My WAN interface is namend: WAN interface (opt1, pppoe0), so i was unsure if either op1 or pppoe0).

I then tried to stop and start the unbound service, but that did not worked (it just didn't stopped at all). So i rebooted the OPNSense and that worked at least.

I am glad for any help, thanks in advance!

[daelos]

Did you find out what this was in the end? I've just started having similar problems. If I reboot the modem, I have to reboot the OPNsense router too.