-
Notifications
You must be signed in to change notification settings - Fork 544
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
Machine config DNS order doesn't seem to be preserved by resolver #9274
Comments
Just some additional verification, the config is correctly applied/merged, but DNSUpstreams lose the original order: $ talosctl -n 172.20.0.5 get resolvers
NODE NAMESPACE TYPE ID VERSION RESOLVERS
172.20.0.5 network ResolverStatus resolvers 3 ["fd7a:115c:a1e0::53","2606:4700:4700::1111","1.1.1.1"]
$ talosctl -n 172.20.0.5 get dnsupstream
NODE NAMESPACE TYPE ID VERSION HEALTHY ADDRESS
172.20.0.5 network DNSUpstream 1.1.1.1 1 true 1.1.1.1:53
172.20.0.5 network DNSUpstream 2606:4700:4700::1111 1 true [2606:4700:4700::1111]:53
172.20.0.5 network DNSUpstream fd7a:115c:a1e0::53 1 true [fd7a:115c:a1e0::53]:53 |
DmitriyMV
added a commit
to DmitriyMV/talos
that referenced
this issue
Sep 11, 2024
`List` returns a sorted (by id) list of resources. This doesn't work when the order of dns upstreams is important. Because of that we need to rework "DNSUpstreams.net.talos.dev" resource ID from destination host to "dns №<num>". Fixes siderolabs#9274 Signed-off-by: Dmitriy Matrenichev <dmitry.matrenichev@siderolabs.com>
DmitriyMV
added a commit
to DmitriyMV/talos
that referenced
this issue
Sep 12, 2024
`List` returns a sorted (by id) list of resources. This doesn't work when the order of dns upstreams is important. Because of that add an `Idx` field to the "DNSUpstreams.net.talos.dev" resource, so we can preserve order. Fixes siderolabs#9274 Signed-off-by: Dmitriy Matrenichev <dmitry.matrenichev@siderolabs.com>
DmitriyMV
added a commit
to DmitriyMV/talos
that referenced
this issue
Sep 12, 2024
`List` returns a sorted (by id) list of resources. This doesn't work when the order of dns upstreams is important. Because of that add an `Idx` field to the "DNSUpstreams.net.talos.dev" resource, so we can preserve order. Fixes siderolabs#9274 Signed-off-by: Dmitriy Matrenichev <dmitry.matrenichev@siderolabs.com>
DmitriyMV
added a commit
to DmitriyMV/talos
that referenced
this issue
Sep 12, 2024
`List` returns a sorted (by id) list of resources. This doesn't work when the order of dns upstreams is important. Because of that add an `Idx` field to the "DNSUpstreams.net.talos.dev" resource, so we can preserve order. Fixes siderolabs#9274 Signed-off-by: Dmitriy Matrenichev <dmitry.matrenichev@siderolabs.com>
smira
pushed a commit
to smira/talos
that referenced
this issue
Sep 13, 2024
`List` returns a sorted (by id) list of resources. This doesn't work when the order of dns upstreams is important. Because of that add an `Idx` field to the "DNSUpstreams.net.talos.dev" resource, so we can preserve order. Fixes siderolabs#9274 Signed-off-by: Dmitriy Matrenichev <dmitry.matrenichev@siderolabs.com> (cherry picked from commit 79cd031)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
Description
I'm trying to get Tailscale DNS to work on my nodes and in my machine config I have
where
fd7a:115c:a1e0::53
is the Tailscale DNS server. I see:Then on a
hostNetwork: true
Pod I see:which is the response I want, but on the local resolver:
and cloudflare:
I see here:
talos/internal/app/machined/pkg/controllers/network/dns_resolve_cache.go
Lines 158 to 172 in bc8bf9e
which like
get dnsupstreams
doesn't seem to preserve the order from the machine config.Logs
None
Environment
The text was updated successfully, but these errors were encountered: