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

local dns resolver to listen on 127.0.0.53 #8328

Closed
Tracked by #8010
smira opened this issue Feb 16, 2024 · 0 comments · Fixed by #8368
Closed
Tracked by #8010

local dns resolver to listen on 127.0.0.53 #8328

smira opened this issue Feb 16, 2024 · 0 comments · Fixed by #8368
Assignees
@DmitriyMV

Comments

@smira
Copy link
Member

smira commented Feb 16, 2024 •
edited
Loading

Don't use port :53, so that a workload can listen on *:53.
@smira smira mentioned this issue Feb 16, 2024
Closed
DmitriyMV added a commit to DmitriyMV/talos that referenced this issue Feb 26, 2024
@DmitriyMV
chore: listen for dns requests on 127.0.0.53
3b2e6f2 
Turns out there is actually no black magic in systemd, they simply listen on 127.0.0.53 and forward dns requests there in resolv.conf.
Reason is the same as ours — to preserve compatibility with other applications. So we do the same in our code.

This PR also does two things:
- Adds `::1` into resolv.conf for IPv6 only resolvers.
- Drops `SO_REUSEPORT` from control options (it works without them).

Closes siderolabs#8328

Signed-off-by: Dmitriy Matrenichev <dmitry.matrenichev@siderolabs.com>
@DmitriyMV DmitriyMV mentioned this issue Feb 26, 2024
Merged
DmitriyMV added a commit to DmitriyMV/talos that referenced this issue Feb 26, 2024
@DmitriyMV
chore: listen for dns requests on 127.0.0.53
9a469b3 
Turns out there is actually no black magic in systemd, they simply listen on 127.0.0.53 and forward dns requests there in resolv.conf.
Reason is the same as ours — to preserve compatibility with other applications. So we do the same in our code.

This PR also does two things:
- Adds `::1` into resolv.conf for IPv6 only resolvers.
- Drops `SO_REUSEPORT` from control options (it works without them).

Closes siderolabs#8328

Signed-off-by: Dmitriy Matrenichev <dmitry.matrenichev@siderolabs.com>
DmitriyMV added a commit to DmitriyMV/talos that referenced this issue Feb 26, 2024
@DmitriyMV
chore: listen for dns requests on 127.0.0.53
f8c556a 
Turns out there is actually no black magic in systemd, they simply listen on 127.0.0.53 and forward dns requests there in resolv.conf.
Reason is the same as ours — to preserve compatibility with other applications. So we do the same in our code.

This PR also does two things:
- Adds `::1` into resolv.conf for IPv6 only resolvers.
- Drops `SO_REUSEPORT` from control options (it works without them).

Closes siderolabs#8328

Signed-off-by: Dmitriy Matrenichev <dmitry.matrenichev@siderolabs.com>
dsseng pushed a commit to dsseng/talos that referenced this issue Mar 7, 2024
@DmitriyMV @dsseng
chore: listen for dns requests on 127.0.0.53
b9cfdfa 
Turns out there is actually no black magic in systemd, they simply listen on 127.0.0.53 and forward dns requests there in resolv.conf.
Reason is the same as ours — to preserve compatibility with other applications. So we do the same in our code.

This PR also does two things:
- Adds `::1` into resolv.conf for IPv6 only resolvers.
- Drops `SO_REUSEPORT` from control options (it works without them).

Closes siderolabs#8328

Signed-off-by: Dmitriy Matrenichev <dmitry.matrenichev@siderolabs.com>
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 6, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@DmitriyMV DmitriyMV

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

chore: listen for dns requests on 127.0.0.53 DmitriyMV/talos
2 participants
@smira @DmitriyMV