Project

General

Profile

Actions

Bug #13497

open

unbound process looks like stuck periodically

Added by Yaroslav Semenenko over 1 year ago. Updated 6 months ago.

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

0%

Estimated time:
Release Notes:
Default
Affected Plus Version:
22.05
Affected Architecture:
SG-2100

Description

Hello,

I have Netgate 2100.
Unbound service is needed to restart sometimes due to it could not resolve public domain name.

Thanks,
Yaroslav

Actions #1

Updated by Jim Pingle over 1 year ago

  • Status changed from New to Incomplete
  • Target version deleted (23.01)

There isn't enough information 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 Steven Cedrone about 1 year ago

Yaroslav Semenenko wrote:

Hello,

I have Netgate 2100.
Unbound service is needed to restart sometimes due to it could not resolve public domain name.

Thanks,
Yaroslav

I'm having the same issue. I've used the Service Watchdog to restart it when it fails. But even this sometimes doesn't work. My unbound will sometimes fail when my VPN's are coming online and Service Watchdog won't notice it right away so internet traffic fails.

This unbound not restarting has been an ongoing issue for a while now I've seen in my builds.

Actions #3

Updated by Tom Joad about 1 year ago

I use the Netgate 1100 with 23.01-RELEASE and can second that unbound from time to time stuck. Only restart the service will help. When I can help to provide more information, I like to do. It is a really annoying problem for me.

Actions #4

Updated by Ketul Patel about 1 year ago

Yaroslav Semenenko wrote:

Hello,

I have Netgate 2100.
Unbound service is needed to restart sometimes due to it could not resolve public domain name.

Thanks,
Yaroslav

I use 23.01- RELEASE as well. I was facing the same issue. Each time Pfblocker cron job used to run (Pfblocker & resolver both running on Python mode) DNS resolution used to break when the database was assembling.

Upon restarting my PfSense I used to get FATAL error messages in notification.

I tried to restart unbound from SSH and it was giving the same PHP Fatal errors.

I am practically unable to use the DNS resolver. I am unable to resolve netflix and many other domains unless I enable the forwarding mode in DNS Resolver.

Hope these issues get resolved at the earliest.

Actions #5

Updated by Jonathan Lee 6 months ago

Post this in the forum it could be you are not using the correct settings and ACL's for unbound.

Actions

Also available in: Atom PDF