Troubleshooting: warning: so-sndbuf 4194304 was not granted

Hi there, Hope everyone is doing well these days. Using unbound 1.9.0. My config file has so-dnbuf = 4m so-rcvbuf = 4m When I type #: unbound I get these warnings: --- *[1603203700] unbound[4853:0] warning: so-rcvbuf 4194304 was not granted. Got 360448. To fix: start with root

Re: fail: the anchor is NOT ok and could not be fixed

und-anchor -- -a "$ROOT_TRUST_ANCHOR_FILE" -v || true fi fi} Should I add the *-R *to --exec /usr/sbin/unbound-anchor -- -a *-R *"$ROOT_TRUST_ANCHOR_FILE" -v || true ? On Tue, 27 Oct 2020 at 22:29, Bernardo Reino via Unbound-users < unbound-users@lists.nlnetlabs.nl> wrote: &g

Re: fail: the anchor is NOT ok and could not be fixed

Anyone? Still couldn't fix this on boot. Appreciate your help. On Fri, 23 Oct 2020 at 13:51, Gil Levy wrote: > After a system reboot, I get the following message when I run > #> sudo systemctl status unbound > > Oct 23 13:31:38 raspberrypi systemd[1]: Starting Unbound DNS server... > Oct 23

fail: the anchor is NOT ok and could not be fixed

After a system reboot, I get the following message when I run #> sudo systemctl status unbound Oct 23 13:31:38 raspberrypi systemd[1]: Starting Unbound DNS server... Oct 23 13:31:39 raspberrypi package-helper[513]: /var/lib/unbound/root.key has content Oct 23 13:31:39 raspberrypi

Cannot update Ubuntu

Not sure if it's Unbound related, but this problem appeared after installing unbound on Ubuntu 20.04 on an Oracle cloud instance. If I issue #: sudo apt update I get: Err:1 http://ap-sydney-1-ad-1.clouds.archive.ubuntu.com/ubuntu focal InRelease Could not connect to 127.0.0.1:8080 (127.0.0.1).

Am I supposed to see my public IP as the DNS server during leak test?

No real issue here. Just trying to understand how to read the results. Using https://ipleak.net I'm seeing that the DNS Address is exactly the same as my public IP address. It seems reasonable because I'm running my own DNS server hence my IP is the DNS, but I just wanted to be sure that this is

Re: Getting SERVFAIL when trying to reach .co.il domains

Does that mean that the problem is not with my network? I don't know how to compile the latest build of unbound for Pihole using RaspberryOS (Debian) Thanks for the info. On Thu, 31 Dec 2020 at 23:39, Havard Eidnes wrote: > > Using Unbound 1.9.0 on Raspberry Pi with Pihole. > > > > Since two

Re: Getting SERVFAIL when trying to reach .co.il domains

I also don't use ipv6. I don't know why it worked well 2 days ago and now I have this issue. How do I proceed from here? Thanks and happy new year! :D On Thu, 31 Dec 2020 at 23:33, Joe Abley wrote: > Hi Gil, > > On Dec 31, 2020, at 12:23, Gil Levy via Unbound-users < > unbound-use

Getting SERVFAIL when trying to reach .co.il domains

Using Unbound 1.9.0 on Raspberry Pi with Pihole. Since two days ago I cannot access .co.il domains, such as hwzone.co.il or ynet.co.il. When I issue# sudo systemctl stop unbound and then #sudo systemctl start unbound, I can access these sites for a few seconds and then they become unavailable

Re: Getting SERVFAIL when trying to reach .co.il domains

/log/unbound/unbound.log: No such file or directory* > > See the difference? > Are you running unbound in a chroot(8)? I don't know how to check that. On Fri, 1 Jan 2021 at 22:23, Unbound wrote: > On 2021-01-01 03:06, Gil Levy via Unbound-users wrote: > > Thanks, Daisuke. &g

Trying to run unbound-1.13.0 after compiling on RaspberryOS

Happy new year everyone! :) After a failure in accessing .co.il domains with unbound 1.9.0, I decided to give it a go and compile unbound 1.13.0 on my RaspberryOS (Debian Buster). I'm encountering issues that I'm out of ideas on how to solve. 1. Cannot open log file (despite it's configured

Re: Getting SERVFAIL when trying to reach .co.il domains

Thanks, Daisuke. However, I'm past that line. While I will change the settings as you kindly suggested (thank you for that), I'm encountering other issues which disable me from using Unbound. I shot an email earlier today with the following: > >1. Cannot open log file (despite it's

Re: Getting SERVFAIL when trying to reach .co.il domains

Jan 1, 2021, at 14:15, Gil Levy via Unbound-users < > unbound-users@lists.nlnetlabs.nl> wrote: > > > > >> Are you running unbound in a chroot(8)? > > > I don't know how to check that. > > > > man chroot > > > > for a better description

Unboudn v13 - error: udp connect failed

Hi. I'm getting udp connection failed and I'm not sure if this is normal or not. I pasted below a link to the entire output of the 'status' command. #: sudo systemctl status unbound https://pastebin.com/5p9PvJj4 *Example: *Jan 29 15:02:47 raspberrypi unbound-anchor[451]: [1611892967]

Troubleshooting SERVFAIL

Upon trying to reach the domain Attenix Login I encounter SERVFAIL dig saas.attenix.co.il ; <<>> DiG 9.16.1-Ubuntu <<>> saas.attenix.co.il ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 18269 ;; flags: qr rd ra; QUERY: 1,

remote control faild ssl crypto error

Running Unbound 1.18.0 on my Pihole RPi device. I get this error: tail -n 20 /etc/unbound/unbound.log Sep 24 18:57:22 unbound[6565:0] info: generate keytag query _ta-4f66. NULL IN Sep 24 18:59:03 unbound[6565:0] notice: failed connection from 127.0.0.1 port 52304 Sep 24 18:59:03 unbound[6565:0]

Updating Unbound from 1.9.0 to latest version ?

Dear community, I'm using my Pihole with Unbound 1.9.0. PRETTY_NAME="Raspbian GNU/Linux 10 (buster)" NAME="Raspbian GNU/Linux" VERSION_ID="10" VERSION="10 (buster)" VERSION_CODENAME=buster ID=raspbian The OS repo doesn't provide any updates for Unbound. Is there any benefit to update to the

Re: Updating Unbound from 1.9.0 to latest version ?

te the OS from 10 to 11) > > The pihole community is better for these type of questions. See > https://discourse.pi-hole.net > > > > On Jan 28, 2024, at 3:04 PM, Gil Levy via Unbound-users < > unbound-users@lists.nlnetlabs.nl> wrote: > > Dear community, > &g