Skip to content

fix: bind to dual-stack address#107

Merged
lukebond merged 1 commit into
mainfrom
chore/bind-to-dualstack-addr
Mar 25, 2026
Merged

fix: bind to dual-stack address#107
lukebond merged 1 commit into
mainfrom
chore/bind-to-dualstack-addr

Conversation

@lukebond
Copy link
Copy Markdown
Contributor

@lukebond lukebond commented Mar 24, 2026

closes #93

the existing code bound to 0.0.0.0, which works for IP 4&6. in fact :: is technically more correct for dual-stack, but since 0.0.0.0 works for most people most people just use that. IP6-only is rare but becoming less rare, so this will come up more and more. TIL.

credit to @miran248 for finding this and suggesting the fix.

existing code bound to 0.0.0.0, which works for IP 4&6. in fact :: is
technically more correct for dual-stack, but since 0.0.0.0 works for
most people most people just use that. IP6-only is rare but becoming
less rare, so this will come up more and more. TIL.
Copy link
Copy Markdown
Contributor

@tillrohrmann tillrohrmann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. +1 for merging :-)

@lukebond lukebond merged commit 2b65f9c into main Mar 25, 2026
2 checks passed
@github-actions github-actions Bot locked and limited conversation to collaborators Mar 25, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Readiness probe fails on ipv6-only cluster

3 participants