Wouter Wijngaards

I think these two lines could be the problem: `Feb 19 19:01:46 Zushi dnssec-trigger-script[37807]: Cannot restore '/etc/resolv.conf' from '/run/dnssec-trigger/resolv.conf.backup': No such file or directory` `Feb 19 19:01:47 Zushi dnssec-trigger-script[37883]: Cannot...

With the command 'dig' the server can be inspected to see what answers it gives. With dig '@' and the IP address and the query to look at. For unbound,...

Surprising result, it prints no error, but also no data. It must have got a response somehow with zero data for this item. Is there items in the unbound configuration...

The config items, `log-local-actions: yes` and `log-queries: yes` and `log-replies: yes` can be useful here. With log local actions, it is visible that a local data or local zone action...

This is not the server that was queried by the dig command, that queried `192.168.115.210`, but the configuration is only for `127.0.0.1` with port `5335`. That is with the `-p...

So the one that is `dig @127.0.0.1 -p 5335 support.google.com` actually queried the unbound server. It has the same answer. I guess it means looking at the log files to...

Log files? Enable the options and look for the content of that file? With the `less` command, it displays the content of a file. Also for config files. There must...

So it says this: ``` 2024-08-30T10:58:03.061800+02:00 AdGuard unbound[122]: [1725008283] unbound[122:0] info: 127.0.0.1 support.google.com. A IN 2024-08-30T10:58:03.061826+02:00 AdGuard unbound[122]: [1725008283] unbound[122:0] info: 127.0.0.1 support.google.com. A IN NOERROR 0.000000 1 47 ```...

It could be an immediately reply from cache, for some reason. Could you restart the server and query again from a fresh start? Otherwise the immediate reply could be a...

If you restarted the server, the logs, but earlier parts, could contain the recursive resolution of the domain `support.google.com`. Search for that earlier in the log file.