udp connect failed

[MatthewVance]

I build 1.13 at my Server but dont work. also klutchell/unbound dont work it has the same error.
and Pihole can't connect on unbound. Reinstall Matthews Version and all are running fine.
[1607543446] libunbound[47:0] error: udp connect failed: Address not available for 2001:500:200::b port 53
[1607543446] libunbound[47:0] error: udp connect failed: Address not available for 2001:7fe::53 port 53
[1607543446] libunbound[47:0] error: udp connect failed: Address not available for 2001:500:a8::e port 53

Originally posted by @beroliv in #54 (comment)

[MatthewVance]

The IPv6 addresses in the error appear to be associated with root servers: https://www.iana.org/domains/root/servers

[MatthewVance]

Continuing to research. This may be related to NLnetLabs/unbound#364.

[mxmartins]

I have a raspberry pi running 1.13.0 and I am not seeing any of those issues.
I also have a docker container running 1.12.0 and no issues noted as well.....

On both systems, the unbound.conf is properly setup to handle IPv6 upstream and downstream...

(Possibly check you unbound.conf settings, here are mine as they pertain to IPv6
Listen to for queries from clients and answer from this network interface
and port.)
interface: 0.0.0.0@53
interface: ::@53

(May be set to yes if you have IPv6 connectivity)
do-ip6: yes

(Only give access to recursion clients from LAN IPs)
access-control: 2xxx:xxxx:xxxx:ee21::0/64 allow

(These private network addresses are not allowed to be returned for public
internet names. Any occurrence of such addresses are removed from DNS
answers. Additionally, the DNSSEC validator may mark the answers bogus.
This protects against DNS Rebinding)
private-address: 2xxx:xxxx:xxxx:ee20::/60

[mxmartins]

Just saw this as I was digging around.....

NLnetLabs/unbound#364

https://forums.freebsd.org/threads/libunbound-error.78121/

[MatthewVance]

Thanks for sharing. I hadn't seen the forum post yet. I think that is the same upstream issue I found.

…

On Tue, Dec 22, 2020, 3:55 PM mxmartins ***@***.***> wrote: Just saw this as I was digging around..... NLnetLabs/unbound#364 <NLnetLabs/unbound#364> https://forums.freebsd.org/threads/libunbound-error.78121/ — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#55 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAUMHOQTYCYJDAY6IGUP6TTSWEIWVANCNFSM4VFZRKOA> .

[dannytsang]

I'm seeing similar errors all looking like IPv6 related.

[MatthewVance]

This will hopefully be fixed in the next release of Unbound. A fix appears to have been merged into the main branch: NLnetLabs/unbound@08968ba

…

On Thu, Jan 28, 2021, 6:24 PM Danny Tsang ***@***.***> wrote: I'm seeing similar errors all looking like IPv6 related. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#55 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAUMHOWDJSNZW7NMZM4373DS4H53DANCNFSM4VFZRKOA> .

[MatthewVance]

Closing this because this is an upstream issue.

[MatthewVance]

Fix #358 in 1.13.1 should address this: https://nlnetlabs.nl/projects/unbound/download/#unbound-1-13-1

[ajostergaard]

Hello - I seem to have this issue with this container and as described in it stops Unbound from starting at all. Any suggestions for a workaround while a fix is underway? Would it be possible to re-open this issue or shall I monitor the other issue instead.

[MatthewVance]

This, I think, is an upstream Unbound issue or an IPv6 Docker issue. The container will start and run with the UDP connect error in the log. The other causes that trips some people up and wil cause the container not to run are either a custom configuration with an error in it or an improperly mounted volume (wrong mount point or file missing locally).

…

On Sat, May 8, 2021, 7:43 AM AJ ***@***.***> wrote: Hello - I seem to have this issue with this container and as described in <MatthewVance/unbound-docker-rpi#12> it stops Unbound from starting at all. Any suggestions for a workaround while a fix is underway? Would it be possible to re-open this issue or shall I monitor the other issue instead. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#55 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAUMHOSGLZUHP7M546BPB7LTMUWXLANCNFSM4VFZRKOA> .

[ajostergaard]

You are right. :) I found my stupid error - sorry! Left the A out of my A records... DUH. :-/

[MatthewVance]

No worries. It happens to the best of us. It's common enough I should probably work on improving the readme.

…

On Sat, May 8, 2021, 8:51 AM AJ ***@***.***> wrote: You are right. :) I found my stupid error - sorry! Left the A out of my A records... DUH. :-/ — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#55 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAUMHOQE3MZQGBKZRKVBDADTMU6WTANCNFSM4VFZRKOA> .