Problems resolving DNS names in kubernetes environments

%3CLINGO-SUB%20id%3D%22lingo-sub-1760480%22%20slang%3D%22en-US%22%3EProblems%20resolving%20DNS%20names%20in%20kubernetes%20environments%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1760480%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20seeing%20a%20problem%20with%20being%20able%20to%20resolve%20DNS%20names%20from%20within%20POD%20containers%20on%20a%20windows%20node%20that%20has%20been%20joined%20to%20a%20kubernetes%20cluster.%26nbsp%3B%20I'm%20using%20flannel%20and%20the%20network%20setup%20uses%20host-gw%20(not%20vxlan).%26nbsp%3B%20Everything%20was%20fine%20until%20I%20applied%20the%20cumulative%20update%20from%20Sept%202020%20to%20the%20windows%20server%20OS.%26nbsp%3B%20After%20that%20point%2C%20nslookup%20calls%20in%20the%20containers%20result%20in%20not%20being%20able%20to%20reach%20the%20DNS%20server%20over%20on%20the%20kubernetes%20master.%26nbsp%3B%20I%20have%20my%20firewall%20turned%20off%20and%20cannot%20see%20any%20DNS%20traffic%20leaving%20the%20windows%20server%20environment%20using%20wireshark.%26nbsp%3B%20When%20I%20revert%20this%20patch%2C%20DNS%20works%20just%20fine.%26nbsp%3B%20I%20am%20able%20to%20reach%20the%20internal%20(if%20using%20IP%20addrs)...it%20seems%20to%20be%20specific%20to%20DNS%20lookup.%26nbsp%3B%20Others%20experienced%20this%20problem%3F%26nbsp%3B%20Could%20it%20related%20to%20the%20%2210%20year%20old%20DNS%20hole%22%20that%20was%20plugged%20back%20in%20a%20July%20release%20of%20Windows%20Server%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1760480%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EContainers%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ENetworking%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Occasional Visitor

I am seeing a problem with being able to resolve DNS names from within POD containers on a windows node that has been joined to a kubernetes cluster.  I'm using flannel and the network setup uses host-gw (not vxlan).  Everything was fine until I applied the cumulative update from Sept 2020 to the windows server OS.  After that point, nslookup calls in the containers result in not being able to reach the DNS server over on the kubernetes master.  I have my firewall turned off and cannot see any DNS traffic leaving the windows server environment using wireshark.  When I revert this patch, DNS works just fine.  I am able to reach the internet (if using just IP addrs) so it doesn't appear to be a general networking problem...it seems to be specific to DNS lookup.  Others experienced this problem?  Could it related to the "10 year old DNS hole" that was plugged back in a July release of Windows Server?

0 Replies