Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docker container: connection refused #16

Open
kirbylink opened this issue Dec 29, 2023 · 1 comment
Open

Docker container: connection refused #16

kirbylink opened this issue Dec 29, 2023 · 1 comment

Comments

@kirbylink
Copy link

kirbylink commented Dec 29, 2023

Since https://unboundtest.com/ currently returns 502 Bad Gateway, I wanted to run the current version in my network.
I cloned the project, built and started the current version from main branch (tag v0.1.0) using Docker.
Unfortunately, when testing a domain, the following logs are printed:

Query results for CAA example.com
----- Unbound logs -----
Dec 29 18:08:31 unbound[38:0] debug: creating udp6 socket ::1 1053
Dec 29 18:08:31 unbound[38:0] error: can't bind socket: Address not available for ::1 port 1053 (len 28)
Dec 29 18:08:31 unbound[38:0] fatal error: could not open ports


Error running query: read udp 127.0.0.1:47050->127.0.0.1:1053: read: connection refused

The last line suggests that unbound probably won't start with the current Dockerfile.

@kirbylink
Copy link
Author

Okay, i did some research. In my setup IPv6 is not activated and used.
This is the reason why unbound stops working instead of skipping IPv6 support.

When i disable IPv6 support in the unbound.conf and rebuilt the image then the service is running as expected.

I could close the issue or let it open for a feature request:
Make IPv6 optional :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant