Project

General

Profile

Actions

Bug #13337

closed

After upgrading from 22.01 to 22.05 unbound intermittently stops resolving until manually restarted

Added by Vaidotas Butkus over 2 years ago. Updated about 2 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
DNS Resolver
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
Affected Architecture:

Description

Config haven't changed from 22.01 but after upgrade started having problems with dns resolver just timing out on resolves, until manually restarting unbound service, then after 1-2 days problem returns, manual restart of unbound fixes it again.
Service when its broken does not show any signs in dashboard it shows as running and ok status.

I have register DHCP leases on dns enabled settings otherwise default settings.

Plugins that I use are nut (for ups) openvpn export, watchdog (installed to solve https://redmine.pfsense.org/issues/11316 now not needed).


Files

unboundlogs.txt (361 KB) unboundlogs.txt logs from around the time unbound stopped working. Vaidotas Butkus, 07/05/2022 03:36 AM
Actions #1

Updated by Jim Pingle over 2 years ago

  • Project changed from pfSense Plus to pfSense
  • Category changed from DNS Resolver to DNS Resolver
  • Status changed from New to Rejected

There isn't enough information to go on here and it's working fine for thousands of others. It's possible it's related to an existing issue such as #5413 but again there isn't enough to go on here and this site is not for support or diagnostic discussion.

For assistance in solving problems, please post on the Netgate Forum or the pfSense Subreddit .

See Reporting Issues with pfSense Software for more information.

Actions #2

Updated by Chris R about 2 years ago

This sounds like how I've always had #11316 , services window says its online but all DNS is dead until manually restarted, fixed by unchecking that checkbox.
Was fine also on 22.01 (and non plus before I upgraded), but from 05 it seems #11316 has come back somehow. Shame that the rollback feature that was introduced in 05 is future only.

Actions

Also available in: Atom PDF