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.

Sign up for GitHub

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

Jump to bottom

DNS listener seems to only be bound to IPv4 #8064

Open
lahabana opened this issue Oct 18, 2023 · 2 comments · May be fixed by #8978
Open

DNS listener seems to only be bound to IPv4 #8064

lahabana opened this issue Oct 18, 2023 · 2 comments · May be fixed by #8978
Labels
kind/bug A bug triage/accepted The issue was reviewed and is complete enough to start working on it

Comments

@lahabana
Copy link
Contributor

What happened?

See we only bind on 127.0.0.1 I guess this just fails on IPv6 only stacks.

kuma/pkg/xds/generator/dns_generator.go

Line 51 in 5ab6b44

listener, err := envoy_listeners.NewInboundListenerBuilder(proxy.APIVersion, "127.0.0.1", dnsPort, core_xds.SocketAddressProtocolUDP).

@lahabana lahabana added triage/pending This issue will be looked at on the next triage meeting kind/bug A bug labels Oct 18, 2023
@jakubdyszkiewicz jakubdyszkiewicz added triage/accepted The issue was reviewed and is complete enough to start working on it and removed triage/pending This issue will be looked at on the next triage meeting labels Oct 23, 2023
@github-actions GitHub Actions
Copy link
Contributor

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Jan 22, 2024
@michaelbeaumont michaelbeaumont linked a pull request Jan 22, 2024 that will close this issue
Draft
5 tasks
@jakubdyszkiewicz jakubdyszkiewicz removed the triage/stale Inactive for some time. It will be triaged again label Jan 22, 2024
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Apr 22, 2024
@github-actions GitHub Actions
Copy link
Contributor

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@lobkovilya lobkovilya removed the triage/stale Inactive for some time. It will be triaged again label Apr 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug A bug triage/accepted The issue was reviewed and is complete enough to start working on it
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(dns): listen on both ipv6 and ipv4 if possible michaelbeaumont/kuma
3 participants
@lahabana @jakubdyszkiewicz @lobkovilya