Getting SERVFAIL when trying to reach .co.il domains

[Gil Levy]

Hi Joe,

Thanks for the reply!
The verbosity of Unbound is set to 3 and all I get is:

pi at raspberrypi:/var/log $ tail -f syslog
Dec 31 23:13:31 raspberrypi avahi-daemon[363]: Registering new address
record for 192.168.1.2 on eth0.IPv4.
Dec 31 23:13:31 raspberrypi dbus-daemon[300]: [system] Successfully
activated service 'org.freedesktop.hostname1'
Dec 31 23:13:31 raspberrypi systemd[1]: Started Hostname Service.
Dec 31 23:13:35 raspberrypi systemd[1]: systemd-rfkill.service: Succeeded.
Dec 31 23:13:39 raspberrypi dhcpcd[380]: eth0: no IPv6 Routers available
Dec 31 23:13:52 raspberrypi systemd[1]: systemd-fsckd.service: Succeeded.
Dec 31 23:14:04 raspberrypi systemd-timesyncd[284]: Synchronized to time
server for the first time 217.147.208.1:123 (2.debian.pool.ntp.org).
Dec 31 23:14:11 raspberrypi systemd[1]: systemd-hostnamed.service:
Succeeded.
Dec 31 23:14:51 raspberrypi systemd[1]: Started Session 6 of user pi.
Dec 31 23:15:14 raspberrypi systemd[1]: Started Session 7 of user pi.
Dec 31 23:16:05 raspberrypi systemd[1]: Started Session 8 of user pi.
Dec 31 23:16:17 raspberrypi systemd[1]: Stopping Unbound DNS server via
resolvconf...
Dec 31 23:16:17 raspberrypi package-helper[978]: Too few arguments.
Dec 31 23:16:17 raspberrypi systemd[1]: unbound-resolvconf.service:
Succeeded.
Dec 31 23:16:17 raspberrypi systemd[1]: Stopped Unbound DNS server via
resolvconf.
Dec 31 23:16:17 raspberrypi systemd[1]: Stopping Unbound DNS server...
Dec 31 23:16:17 raspberrypi systemd[1]: unbound.service: Succeeded.
Dec 31 23:16:17 raspberrypi systemd[1]: Stopped Unbound DNS server.
Dec 31 23:16:17 raspberrypi systemd[1]: Starting Unbound DNS server...
Dec 31 23:16:17 raspberrypi unbound[1028]: [1609416977] unbound[1028:0]
debug: chdir to /etc/unbound
Dec 31 23:16:17 raspberrypi unbound[1028]: [1609416977] unbound[1028:0]
debug: drop user privileges, run as unbound
Dec 31 23:16:17 raspberrypi unbound[1028]: [1609416977] unbound[1028:0]
debug: switching log to /dev/null
Dec 31 23:16:17 raspberrypi systemd[1]: Started Unbound DNS server.
Dec 31 23:16:18 raspberrypi systemd[1]: Started Unbound DNS server via
resolvconf.
Dec 31 23:16:18 raspberrypi package-helper[1029]: Too few arguments.

If I was to guess I'd say that you have a full set of servers for some zone
> or other that is causing trouble
>
Sorry, I don't know what it means. I didn't set up anything like that.
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 <jabley at hopcount.ca> wrote:

> Hi Gil,
>
> On Dec 31, 2020, at 12:23, Gil Levy via Unbound-users <
> unbound-users at lists.nlnetlabs.nl> wrote:
>
> The tail log of the SERVFAIL can be found here:
> https://textuploader.com/185f0
>
>
> Unless I'm missing something, that log seems to be mainly (entirely?)
> messages from dnsmasq. You probably want to see log messages from unbound
> to shed light on the events leading up to the SERVFAIL that dnsmasq is
> receiving from localhost.
>
> If I was to guess I'd say that you have a full set of servers for some
> zone or other that is causing trouble, e.g. sending repeated SERVFAIL
> responses or timing out, and unbound is putting them all in the penalty box.
>
> The trick in that case will be to determine whether the problem is local
> (e.g. a broken firewall or persistent local routing problem for IPv6) or
> remote (e.g. your resolver or the subnet it's numbered in has been
> blacklisted for some reason).
>
> But this is just wild speculation; you should see what the logs say.
>
> Happy New Year in advance :-)
>
>
> Joe
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nlnetlabs.nl/pipermail/unbound-users/attachments/20201231/8c7d9207/attachment.htm>