Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

nslookup in WSL rancher-desktop distro doesn't handle the host-resolver result cleanly

See original GitHub issue

Actual Behavior

IPs are being mapped to names w/o an issue. Tested w docker and w curl as example.

Specifically w nslookup though I am getting an error in the result.

Steps to Reproduce

Enable the host-resolver
Start RD
wsl -d rancher-desktop
nslookup google.com

Result

# nslookup google.com
Server: 172.23.172.135
Address: 172.23.172.135:53

Non-authoritative answer:
*** Can't find google.com: Parse error

Expected Behavior

...
Non-authoritative answer:
Name: google.com
Address: 142.251.15.102
...

Additional Information

Again not noticing any functional difference with host-resolver. Just noticed that one test had an unexpected result.

Rancher Desktop Version

1.3.0

Rancher Desktop K8s Version

1.23.4

Which container runtime are you using?

moby (docker cli)

What operating system are you using?

Windows

Operating System / Build Version

20H2 19042.1645

What CPU architecture are you using?

x64

Linux only: what package format did you use to install Rancher Desktop?

No response

Windows User Only

No response

Issue Analytics

State:
Created a year ago
Comments:9 (6 by maintainers)

Top GitHub Comments

1reaction

mook-ascommented, May 3, 2022

Hi! Sorry, I’m temporarily reopening this issue… so that I can track that I still need to review that other PR (since we mostly work off the Rancher Desktop board).

I’ll close this again once the other PR is merged (plus additional PR to pick up the new host resolver).

0reactions

Nino-Kcommented, May 12, 2022

Going to close this, as this specific issue is fixed.

Top Results From Across the Web

Epic: Use Lima host resolver on Windows · Issue #1899 - GitHub

We want to use the Lima host resolver to take advantage of all the ... DNS process in the rancher desktop will be...

Troubleshooting Tips - Rancher Desktop Docs

This page provides tips to troubleshoot issues you may have with Rancher Desktop. Q: Why do I not see my WSL distro under...

sitemap-questions-2.xml - Unix Stack Exchange

... /modules-devname-not-found-after-updating-process-was-cancelled 2019-03-04 ... https://unix.stackexchange.com/questions/504149/host-header-url-for-linux ...

DNS lookup not working in WLS2 SUSE subsystem

I met a DNS problem in my SUSE WSL2 subsystem. I configure my windows DNS servers in /etc/resolv.conf but it does not help...

the of and to a in for is on s that by this with i you it not

the of and to a in for is on s that by this with i you it not or be are from ......