-
Notifications
You must be signed in to change notification settings - Fork 36
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
vL3 DNS is slow when using the DNS search path #1426
Comments
Hi @fr-Pursuit, |
Hi @glazychev-art ! Without adding
The issue seems to be fixed. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Context
We're using the interdomain vL3 example, with one of the alpine pods renamed to
alpine2
to avoid confusion. The vL3 domain names of the alpine pods are therefore:alpine.my-interdomain-vl3-network
alpine2.my-interdomain-vl3-network
Expected Behavior
When
my-interdomain-vl3-network
is in the DNS search path, DNS queries onalpine2
should take roughly the same time as explicit queries onalpine2.my-interdomain-vl3-network
.Current Behavior
DNS queries on
alpine2
take around 400ms, while queries on the explicitalpine2.my-interdomain-vl3-network
name take less than 50ms.Steps to Reproduce
alpine2
to avoid confusion, setting theNSM_DNS_TEMPLATES
environment variable to{{ index .Labels \"podName\" }}.my-interdomain-vl3-network.
for the DNS service to work, and addingmy-interdomain-vl3-network
toalpine
's DNS search path)alpine
podtime nslookup -type=a -debug alpine2.my-interdomain-vl3-network
and check the timetime nslookup -type=a -debug alpine2
and check the timeAdditional context
This problem was diagnosed as part of #1414
The example was deployed on three kind clusters using kind
0.17.0
and the kindestv1.25.3
imageThe text was updated successfully, but these errors were encountered: