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
When the request is sent from the pod and we analyse the response in windows with wireshark the dns response is correct and then when we analyse the response with tcpdump inside the kubernetes cluster there is this CNAME appearing.
Expected behavior
This dns query is supposed to have the same behaviour on windows, linux and macos.
Here is my machine information :
Version WSL : 1.2.1.0
Version du noyau : 5.15.90.1
Version WSLg : 1.0.51
Version MSRDC : 1.2.3770
Version direct3D : 1.608.2-61064218
Version de DXCore : 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Version de Windows : 10.0.22621.1555
I tried with Docker for Windows v4.18 (with WSL2 and Hyper-V backend) and minikube.
Steps to reproduce the behavior
Install Docker for dekstop latest release
Enable kubernetes
kubectl run tmp-shell --rm -i --tty --image nicolaka/netshoot
dig _acme-challenge.linoa.dev. CNAME
The text was updated successfully, but these errors were encountered:
First, here is some context, I have a domain for local dev with this records :
This issue is only happening on windows 11 (maybe 10 ?), there is no problem on Linux and MacOS.
Now if run this dns query from windows I have this result which is the expected one according to the zone :
Now if I run the same query from a pod inside the kubernetes cluster I have this result, with a CNAME pointing to itselft coming from nowhere.
When the request is sent from the pod and we analyse the response in windows with wireshark the dns response is correct and then when we analyse the response with tcpdump inside the kubernetes cluster there is this CNAME appearing.
Expected behavior
This dns query is supposed to have the same behaviour on windows, linux and macos.
Here is my machine information :
I tried with Docker for Windows v4.18 (with WSL2 and Hyper-V backend) and minikube.
Steps to reproduce the behavior
The text was updated successfully, but these errors were encountered: