DNS Resolver Custom Options Do Not Start on Startup
-
I have configured DNS Resolver with the custom option:
log-queries: yes
When pfsense is restarted, remote logging does not resume.
2.4.4-RELEASE-p2 (amd64)
built on Wed Dec 12 07:40:18 EST 2018
FreeBSD 11.2-RELEASE-p6Instead, I must go into the Resolver General Settings, and click Save. Then, everything starts logging to my remote syslogd server.
Any help is appreciated.
-
Hi,
I entered this (adding #anchor(log-queries: yes)).
After hitting "Save", unbound restarted.
And my logs, locally and remotely, were getting swamped with query log lines. -
@user2 said in DNS Resolver Custom Options Do Not Start on Startup:
When pfsense is restarted, remote logging does not resume.
Next restart, if you don't see any logging, just restart unbound from the Status Service tab. I will probably start logging.
-
@ronpfs Thank you for responding. It is true that restarting unbound after a pfsense reboot resumes logging. Instead I was hoping (expecting) the unbound settings to start logging automatically. Doesn't it seem odd to go into a service to restart it just after rebooting the pfsense firewall?
-
@gertjan Thank you for sharing your custom options. It is also my observation that hitting "Save" resumes external logging. However, I was hoping this setting would automatically start upon a pfsense reboot. Maybe this is a bug?
-
@user2 said in DNS Resolver Custom Options Do Not Start on Startup:
Doesn't it seem odd to go into a service to restart it just after rebooting the pfsense firewall?
It's odd but it's been like that for years.
-
@ronpfs Hmm... I see. Since this is new to me, I was not expecting it. (I think this is also observed for snort alerts - the need to restart the service after a reboot.) Is there a way to recommend a change?
-
pfsense demand TLC
