You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 on alpine2 should take roughly the same time as explicit queries on alpine2.my-interdomain-vl3-network.
Current Behavior
DNS queries on alpine2 take around 400ms, while queries on the explicit alpine2.my-interdomain-vl3-network name take less than 50ms.
Steps to Reproduce
Deploy the interdomain vL3 example (while renaming one alpine pod to alpine2 to avoid confusion, setting the NSM_DNS_TEMPLATES environment variable to {{ index .Labels \"podName\" }}.my-interdomain-vl3-network. for the DNS service to work, and adding my-interdomain-vl3-network to alpine's DNS search path)
Open a shell in the alpine pod
Run time nslookup -type=a -debug alpine2.my-interdomain-vl3-network and check the time
Run time nslookup -type=a -debug alpine2 and check the time
Hi @fr-Pursuit,
Thanks for the report!
We pushed some fixes. Could you please test this on the latest main branch?
After the fix you no longer need to add my-interdomain-vl3-network to client's DNS search path
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: