OPNsense Forum
English Forums => General Discussion => Topic started by: ressurex on January 07, 2019, 06:45:25 pm
-
hi all.
using this manual: https://www.routerperformance.net/opnsense/dnsbl-via-bind-plugin/
and setting the ACLs access list to: 192.168.1.1/24 ( OPNsense is 192.168.1.1)
I cant get the DNSBL started. it goes red after on second trying to start it.
what am I doing wrong ?
-
What does the log say? Perhaps the port is used by different application?
-
Services: BIND: Log File
Search for a specific message...
Date Message
General
Queries
Blocked
File /var/log/named/named.log yielded no results.
Im a running DNS.WATCH in general setting
84.200.69.80
84.200.70.40
so all connections are forced to use this DNS.
could this do issues with the DNSBL ?
-
when i set Recursion i general to NONE, the DNSBL can be started..
is my ACLs access list wrong ?
my ip of opnsense is 192.168.1.1 and dhcp to clients from 192.168.1.100 to 115
-
got it working.. i thought.!
but when enableling the DNSBL the service stops af a second..
here is the error from system.
DateMessage
Jan 10 20:32:18configd.py: [1388610f-aa40-46ef-8a8c-8b8174141f8e] request BIND status
Jan 10 20:32:17configd.py: [3957517a-e18c-45e0-9903-db5ab8c8b81e] request BIND status
Jan 10 20:32:17configd.py: [259ca30f-30e9-440b-ba0c-0713319d4849] returned exit status 3
Jan 10 20:32:17configd.py: [259ca30f-30e9-440b-ba0c-0713319d4849] starting BIND
-
and i system log general, alot of these fore everytime i start the BLIND plugin
root: /usr/local/etc/rc.d/named: ERROR: named-checkconf for /usr/local/etc/namedb/named.conf failed
anyone know what im doing wrong ?