Apt update resolve problem about kwsl HOT 7 CLOSED

@h13World Do you maybe have TailScale installed? That was what caused the resolv.conf issues for me.
I exited tailscaled and disabled the tunnel like here after which it worked

from kwsl.

From a Windows command prompt, does ping archive.neon.kde.org resolve?

from kwsl.

Yes it does.

>ping archive.neon.kde.org

Ping wird ausgeführt für 1613612302.rsc.cdn77.org [156.146.61.130] mit 32 Bytes Daten:
Antwort von 156.146.61.130: Bytes=32 Zeit=37ms TTL=53
Antwort von 156.146.61.130: Bytes=32 Zeit=35ms TTL=53
Antwort von 156.146.61.130: Bytes=32 Zeit=28ms TTL=53
Antwort von 156.146.61.130: Bytes=32 Zeit=28ms TTL=53

Ping-Statistik für 156.146.61.130:
    Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
    (0% Verlust),
Ca. Zeitangaben in Millisek.:
    Minimum = 28ms, Maximum = 37ms, Mittelwert = 32ms

nslookup from the wsl distribution:

nslookup archive.neon.kde.org
;; UDP setup with fec0:0:0:ffff::1#53(fec0:0:0:ffff::1) for archive.neon.kde.org failed: invalid file.
;; UDP setup with fec0:0:0:ffff::1#53(fec0:0:0:ffff::1) for archive.neon.kde.org failed: invalid file.
;; UDP setup with fec0:0:0:ffff::1#53(fec0:0:0:ffff::1) for archive.neon.kde.org failed: invalid file.
;; UDP setup with fec0:0:0:ffff::2#53(fec0:0:0:ffff::2) for archive.neon.kde.org failed: invalid file.
;; UDP setup with fec0:0:0:ffff::3#53(fec0:0:0:ffff::3) for archive.neon.kde.org failed: invalid file.

After I add the hostname config to the /etc/hosts file the ping from the wsl distribution succeeds
156.146.61.130 archive.neon.kde.org. archive.neon.kde.org

from kwsl.

Can you temporarily disable IPv6 in Windows?

;; UDP setup with fec0:0:0:ffff::3#53(fec0:0:0:ffff::3) for archive.neon.kde.org failed: invalid file.

This indicates you have IPv6 DNS set in Windows, but the DNS server is not replying to IPv6 queries.

from kwsl.

Sorry for the late reply.

I tried to disable IPv6 in Windows, but I even if I manually set the IPv4 DNS and disable IPv6 DNS at my ethernet adapter it still isn't able to resolve the hostnames.

I found out that I have the problem in all wsl distributions and it is an issue with my client and not an error in kWSL.

The file /etc/resolv.conf in all distributions:

nameserver fec0:0:0:ffff::1
nameserver fec0:0:0:ffff::2
nameserver fec0:0:0:ffff::3

When I edit /etc/wsl.conf and change the parameter generateResolvConf to false and then create the file /etc/resolv.conf myself with the IPv4-DNS then the hostname resolution works again as it should.

Tried to do the same in kWSL (Change parameter in dist/etc/wsl.conf and create dist/etc/resolv.conf), but here I still have the same problem. Am I missing something or is this resolution not possible in kWSL?

from kwsl.

@NullDev thank you very much for the hint. TailScale caused the issue for me also.
But I was able to resolve the issue differently. I didn't disable the tunnel, I just disabled IPv6 in configuration.

What I still don't fully understand is why I don't have the same problem with another client that also has TailScale installed.

from kwsl.

Interesting! Its good to know that disabling IPv6 instead of the entire tunnel is sufficient because I was afraid of re-enabling it so far 😅

from kwsl.