The funny thing is, I sent the exact the same feedback to @mimugmail via Twitter. As the form doesn't accept "#" or hostnames into the field.At the moment I've workedaround it by modifying the config file directly: (to be honest I don't know if that's persistent across reboots)Code: [Select]# cat /var/unbound/etc/dot.confserver: tls-cert-bundle: /etc/ssl/cert.pemforward-zone: name: "." forward-tls-upstream: yes forward-addr: 45.90.28.0#xx.dns1.nextdns.io forward-addr: 2a07:a8c0::#xx.dns1.nextdns.io forward-addr: 45.90.30.0#xx.dns2.nextdns.io forward-addr: 2a07:a8c1::#xx.dns2.nextdns.io
# cat /var/unbound/etc/dot.confserver: tls-cert-bundle: /etc/ssl/cert.pemforward-zone: name: "." forward-tls-upstream: yes forward-addr: 45.90.28.0#xx.dns1.nextdns.io forward-addr: 2a07:a8c0::#xx.dns1.nextdns.io forward-addr: 45.90.30.0#xx.dns2.nextdns.io forward-addr: 2a07:a8c1::#xx.dns2.nextdns.io
Quote from: pkernstock on May 04, 2020, 03:52:06 pmThe funny thing is, I sent the exact the same feedback to @mimugmail via Twitter. As the form doesn't accept "#" or hostnames into the field.At the moment I've workedaround it by modifying the config file directly: (to be honest I don't know if that's persistent across reboots)Code: [Select]# cat /var/unbound/etc/dot.confserver: tls-cert-bundle: /etc/ssl/cert.pemforward-zone: name: "." forward-tls-upstream: yes forward-addr: 45.90.28.0#xx.dns1.nextdns.io forward-addr: 2a07:a8c0::#xx.dns1.nextdns.io forward-addr: 45.90.30.0#xx.dns2.nextdns.io forward-addr: 2a07:a8c1::#xx.dns2.nextdns.ioSoooo....yeah, it does not survive a reboot...oh well.
Sorry to bring this up again, but has there been any progress in the logging functionality surrounding blocked queries?
Hi,It replaces all to 0.0.0.0:https://github.com/opnsense/plugins/blob/master/dns/unbound-plus/src/opnsense/scripts/OPNsense/Unboundplus/dnsbl.py#L111