F5F Stay Refreshed Power Users Networks Issue during saving DNS resolver settings

Issue during saving DNS resolver settings

Issue during saving DNS resolver settings

N
Neidro
Senior Member
453
08-09-2023, 05:06 AM
#1
Hi everyone, I'm using Pfsense with the DNS Resolver feature. Unbound has stopped working and isn't restarting when I apply config changes. The error message says: the config file can't be parsed because it doesn't exist at the specified path. I've tried fixing it by copying the file and updating Pfsense, but the problem persists for a short time. Let me know if you need more details. Thanks!
N
Neidro
08-09-2023, 05:06 AM #1

Hi everyone, I'm using Pfsense with the DNS Resolver feature. Unbound has stopped working and isn't restarting when I apply config changes. The error message says: the config file can't be parsed because it doesn't exist at the specified path. I've tried fixing it by copying the file and updating Pfsense, but the problem persists for a short time. Let me know if you need more details. Thanks!

P
putney10
Junior Member
15
08-25-2023, 05:00 AM
#2
Consider switching to a simpler version with older stability and standard configurations.
P
putney10
08-25-2023, 05:00 AM #2

Consider switching to a simpler version with older stability and standard configurations.

D
Dagora_
Junior Member
14
09-04-2023, 08:55 AM
#3
You didn’t acknowledge the warning. A certificate file is required for DoT or DoH; otherwise Unbound won’t use PKI.
D
Dagora_
09-04-2023, 08:55 AM #3

You didn’t acknowledge the warning. A certificate file is required for DoT or DoH; otherwise Unbound won’t use PKI.

S
sCx_Batman
Member
163
09-11-2023, 05:31 AM
#4
I think you were also testing the previous build before. Usually the unbound config is in /var/unbound/ rather than /var/unbound/test/. I was sure it had open issues on the 2.4.5 test builds, which is why I delayed upgrading until the stable release.
S
sCx_Batman
09-11-2023, 05:31 AM #4

I think you were also testing the previous build before. Usually the unbound config is in /var/unbound/ rather than /var/unbound/test/. I was sure it had open issues on the 2.4.5 test builds, which is why I delayed upgrading until the stable release.