<div dir="ltr"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
But apparently your unbound.conf file indicates it's here:<br>
>> /etc/unbound/var/log/unbound<br></blockquote><div><br></div><div>This has already been fixed in my unbound.conf file (see here: <a href="https://pastebin.com/GsA8GtJF">unbound.conf</a>), but it still errors: <b>error: Could not open logfile /var/log/unbound/unbound.log: No such file or directory</b></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
See the difference?<br>
Are you running unbound in a chroot(8)?</blockquote><div>I don't know how to check that.</div><div> <br></div>
</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, 1 Jan 2021 at 22:23, Unbound <<a href="mailto:unbound@tacomawireless.net">unbound@tacomawireless.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 2021-01-01 03:06, Gil Levy via Unbound-users wrote:<br>
> Thanks, Daisuke.<br>
> <br>
> However, I'm past that line. While I will change the settings as you kindly<br>
> suggested (thank you for that), I'm encountering other issues which disable<br>
> me from using Unbound.<br>
> I shot an email earlier today with the following:<br>
> <br>
> <br>
>> <br>
>> 1. Cannot open log file (despite it's configured in unbound.conf)<br>
>> 2. Cannot use the unbound-checkconf utility<br>
>> <br>
>> I provided a link to my config file at the bottom.<br>
>> Appreciate your help!<br>
>> <br>
>> Gil<br>
>> <br>
>> <br>
>> *pi@raspberrypi:/etc/unbound $ sudo systemctl status unbound*<br>
>> ● unbound.service - Unbound DNS resolver<br>
>> Loaded: loaded (/lib/systemd/system/unbound.service; enabled; vendor<br>
>> preset: enabled)<br>
>> Active: active (running) since Fri 2021-01-01 10:44:56 AEDT; 19min ago<br>
>> Process: 456 ExecStartPre=/usr/sbin/unbound-anchor -r<br>
>> /etc/unbound/root.hints -a /etc/unbound/root.key (code=exited,<br>
>> status=0/SUCCESS)<br>
>> Main PID: 481 (unbound)<br>
>> Tasks: 1 (limit: 2063)<br>
>> CGroup: /system.slice/unbound.service<br>
>> └─481 /usr/sbin/unbound -c /etc/unbound/unbound.conf -d<br>
>> <br>
>> Jan 01 10:44:56 raspberrypi unbound-anchor[456]: [1609458296]<br>
>> libunbound[456:0] error: udp connect failed: Network is unreachable for<br>
>> 198.41.0.4 port 53<br>
>> Jan 01 10:44:56 raspberrypi unbound-anchor[456]: [1609458296]<br>
>> libunbound[456:0] error: udp connect failed: Network is unreachable for<br>
>> 192.33.4.12 port 53<br>
>> Jan 01 10:44:56 raspberrypi unbound-anchor[456]: [1609458296]<br>
>> libunbound[456:0] error: udp connect failed: Network is unreachable for<br>
>> 2001:dc3::35 port 53<br>
>> Jan 01 10:44:56 raspberrypi unbound-anchor[456]: [1609458296]<br>
>> libunbound[456:0] error: udp connect failed: Network is unreachable for<br>
>> 2001:500:1::53 port 53<br>
>> Jan 01 10:44:56 raspberrypi unbound-anchor[456]: [1609458296]<br>
>> libunbound[456:0] error: udp connect failed: Network is unreachable for<br>
>> 2001:500:9f::42 port 53<br>
>> Jan 01 10:44:56 raspberrypi unbound-anchor[456]: [1609458296]<br>
>> libunbound[456:0] error: udp connect failed: Network is unreachable for<br>
>> 199.7.91.13 port 53<br>
>> Jan 01 10:44:56 raspberrypi unbound[481]: [1609458296] unbound[481:0] <br>
>> *error:<br>
>> Could not open logfile /var/log/unbound/unbound.log: No such file or<br>
>> directory*<br>
>> Jan 01 10:44:57 raspberrypi unbound[481]: [1609458297] unbound[481:0]<br>
>> notice: init module 0: validator<br>
>> Jan 01 10:44:57 raspberrypi unbound[481]: [1609458297] unbound[481:0]<br>
>> notice: init module 1: iterator<br>
>> Jan 01 10:44:57 raspberrypi unbound[481]: [1609458297] unbound[481:0]<br>
>> info: start of service (unbound 1.13.0).<br>
>> <br>
>> pi@raspberrypi:/var/log/unbound $ ls<br>
>> unbound.log<br>
>> <br>
>> pi@raspberrypi:/etc/unbound $ unbound-checkconf /etc/unbound/unbound.conf<br>
>> /etc/unbound/var/log/unbound: *No such file or directory*<br>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>
I won't speak for all your woes. But this line (above) says it all.<br>
On one hand you indicate your log file is located here:<br>
>> pi@raspberrypi:/var/log/unbound $ ls<br>
>> unbound.log<br>
But apparently your unbound.conf file indicates it's here:<br>
>> /etc/unbound/var/log/unbound<br>
<br>
See the difference?<br>
Are you running unbound in a chroot(8)?<br>
<br>
>> [1609459551] unbound-checkconf[1316:0] fatal error: logfile directory<br>
>> does not exist<br>
>> <br>
>> pi@raspberrypi:/etc/unbound $ ls<br>
>> root.hints root.key root.zone unbound.conf unbound_control.key<br>
>> unbound_control.pem unbound.log unbound.pid unbound_server.key<br>
>> unbound_server.pem<br>
>> <br>
>> *unbound.conf* here -> <a href="https://pastebin.com/ZAUVFVEF" rel="noreferrer" target="_blank">https://pastebin.com/ZAUVFVEF</a><br>
>> <br>
> <br>
> Any ideas what should I do? I'm really lost here and would like to keep<br>
> using unbound.<br>
> <br>
> Thanks in advance.<br>
> <br>
> On Fri, 1 Jan 2021 at 20:29, Daisuke HIGASHI <<a href="mailto:daisuke.higashi@gmail.com" target="_blank">daisuke.higashi@gmail.com</a>><br>
> wrote:<br>
> <br>
>> Hi,<br>
>> <br>
>> ".<a href="http://co.il" rel="noreferrer" target="_blank">co.il</a>" and ".il" (seemingly under DNSSEC algorithm rollover) have<br>
>> several errors. Current versions of Unbound in default configuration<br>
>> tolerate them, but in a specific configuration Unbound could make<br>
>> fatal errors.<br>
>> <br>
>> Assuming [1] is your configuration file, the offending line is:<br>
>> <br>
>> > harden-algo-downgrade: yes<br>
>> <br>
>> "harden-algo-downgrade: no" (this is the current default value) makes<br>
>> Unbound tolerant.<br>
>> <br>
>> [1] <a href="https://pastebin.com/ZAUVFVEF" rel="noreferrer" target="_blank">https://pastebin.com/ZAUVFVEF</a><br>
>> <br>
</blockquote></div>