unbound DNS Resolver Will Not Start

pete35

So insert that line again, but dont copy it from anywhere, just type it in. save and Restart, if that is ok then, you can enable pfblocker.

newUser2pfSense

Ok, so I tried this two times and no luck -
I went to Diagnostics > Edit File and browsed to the file and typed the line back in and saved the file. As a test to make sure the line stayed in the file, I restarted pfSense. When logging back into the GUI, the unbound DNS Resolver is working, however, when I check the file, the line is not there.

Going to Services > DNS Resolver > General Settings > Custom options, I tried typing the line in there and saving and I eceived the following error message:

The following input errors were detected:

The generated config file cannot be parsed by unbound. Please correct the following errors:
/var/unbound/test/unbound.conf:105: error: syntax error
read /var/unbound/test/unbound.conf failed: 1 errors in configuration file

Hmm, /test/ is in this path. When I look in the file with the /test/ in the path, the line is there.

pete35

Hmm, i dont think you need that option. If it is ok for you, just forget about it. Enable pfblocker. Sugestion: in advance to reconfigure anything or do an update, please do a backup of a running config.

bmeeks

@newUser2pfSense said in unbound DNS Resolver Will Not Start:

Ok, so I tried this two times and no luck -
I went to Diagnostics > Edit File and browsed to the file and typed the line back in and saved the file. As a test to make sure the line stayed in the file, I restarted pfSense. When logging back into the GUI, the unbound DNS Resolver is working, however, when I check the file, the line is not there.

Going to Services > DNS Resolver > General Settings > Custom options, I tried typing the line in there and saving and I eceived the following error message:

The following input errors were detected:

The generated config file cannot be parsed by unbound. Please correct the following errors:

/var/unbound/test/unbound.conf:105: error: syntax error

read /var/unbound/test/unbound.conf failed: 1 errors in configuration file

Hmm, /test/ is in this path. When I look in the file with the /test/ in the path, the line is there.

Manually typing into the config files will not be persistent. The GUI code recreates the conf files for all packages each time you start/stop the service or otherwise modify something in pfSense. All configuration is stored in the firewall's config.xml file and read out from there when creating or recreating conf files. When you go into SERVICES > DNS Resolver > General Settings > Custom Options and type in something, then when you click Save the conf file is recreated from scratch. Any changes you make directly on the filesystem (such as when using DIAGNOSTICS > EDIT FILE) are overwritten. This is true for all packages, and is something new users typically get confused by. You edit something on the command line and yet it doesn't "stay edited".

newUser2pfSense

Maybe that's why I'm now seeing the following line in Custom options as it wasn't there before:

server:include: /var/unbound/pfb_dnsbl.*conf

I was actually going to go into the console and use vi to add the line as a test to see what happens but now that this line is in there, on line 105, I'm not sure what to do.

bmeeks

@newUser2pfSense said in unbound DNS Resolver Will Not Start:

Maybe that's why I'm now seeing the following line in Custom options as it wasn't there before:

server:include: /var/unbound/pfb_dnsbl.*conf

I was actually going to go into the console and use vi to add the line as a test to see what happens but now that this line is in there, on line 105, I'm not sure what to do.

pfBlockerNG's DNSBL functionality puts that line in there. It tells the unbound resolver to load up the additional configuration info it finds in that file (or files matching that wildcard). That's how the ad blocking and other stuff works. Now, it may be that unbound is no longer liking that wildcard spec or something.

newUser2pfSense

Interestingly, I went to Services > DNS Resolver > General Settings > General DNS Resolver Options > Custom options and typed in the line, saved it, and then restarted pfSense. Everything seems to work now for whatever reason, odd. The Custom options box now shows these two lines:

server:include: /var/unbound/pfb_dnsbl.*conf
log-replies: yes

Wouldn't you know it, as I look on the GUI Dashboard, there's a new version of pfBlockerNG-devel.

newUser2pfSense

Everything seems to be back online and working now.

I made sure I completed a pfSense backup.

I want to thank bmeeks and pete35 for all of their assistance. I appreciate you taking time out of your day to help!

serbus

Hello!

I have been bit by this before...

log-replies has to go in a server block.
You are leaching off the "server:" specified by pfb, but when that package is removed you get the error.
I recommend that that you enter the full block specifiers for all custom unbound commands.
So:

server:log-replies:yes

It is OK to have multiple server blocks specified.

John

newUser2pfSense

serbus...thank you for the reply. I've made the edit, saved, restarted, and everything is still working. I've also made my backups to the system. Wheeew!

reza.mnp

i can not start unbound service:

The following input errors were detected:
The generated config file cannot be parsed by unbound. Please correct the following errors:
Shared object "libevent-2.1.so.7" not found, required by "unbound-checkconf"

Gertjan

@reza-mnp said in unbound DNS Resolver Will Not Start:

Shared object "libevent-2.1.so.7" not found, required by "unbound-checkconf"

"libevent-2.1.so.7" is not /var/unbound/unbound.conf.

I saw this one https://forum.netgate.com/topic/154509/libevent-2-1-so-7-not-found and I can create that situation rather easily : by deleting that lib file.
Still, there is not enough info.

Couponfond

This post is deleted!