Unboudn v13 - error: udp connect failed
bkonings84 at gmail.com
Thu Feb 4 04:55:33 UTC 2021
*unbound-anchor -a -4 "root.key" *is not a configuration setting, it is a
Brendan J Konings, BEng(Electronics)(Hons), BCompSc
On Thu, Feb 4, 2021 at 3:18 PM Gil Levy via Unbound-users <
unbound-users at lists.nlnetlabs.nl> wrote:
> Doing a bit more digging on why I'm getting
> * libunbound[451:0] error: udp connect failed: Network is unreachable for
> 22.214.171.124 port 53 *
> I found this link:
> which described exactly what I'm experiencing.
> However, I couldn't find where in my unbound.conf file I can use this *unbound-anchor
> -a -4 "root.key" *without having errors when running *unbount-checkconf*
> This is what I tried doing:
> chroot: "/etc/unbound"
> username: "unbound"
> directory: "/etc/unbound"
> logfile: "/etc/unbound/unbound.log"
> root-hints: "root.hints"
> pidfile: "unbound.pid"
> #auto-trust-anchor-file: "/etc/unbound/root.key"
> unbound-anchor -a -4 "root.key"
> Can someone please inform me how can I incorporate *unbound-anchor -a -4 *in
> my unbound.conf file so I won't get these errors?
> I'm running on RaspberryOS and I'm not using any firewall. No ufw, no
> iptables and no firewalld. I don't think I'm blocking port 53, so I'm
> assuming I'm experiencing the same issue Herbert experienced.
> On a side note, wouldn't it be better if we have a subreddit r/UnboundDNS
> to use for support issues instead email chains? Just a suggestion.
> On Fri, 29 Jan 2021 at 15:11, Gil Levy <just.gil at gmail.com> wrote:
>> I'm getting udp connection failed and I'm not sure if this is normal or
>> I pasted below a link to the entire output of the 'status' command.
>> #: sudo systemctl status unbound
>> *Example: *Jan 29 15:02:47 raspberrypi unbound-anchor: 
>> libunbound[451:0] error: udp connect failed: Network is unreachable for
>> 126.96.36.199 port 53
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Unbound-users