WSL2 ya rasa DNS bayan haɗin VPN? Dalilai biyu

Ping ta adireshi yana aiki a cikin rarraba, shigar da fakiti da jawo git ba sa aiki, kuma gazawar ta bayyana daidai bayan tunnel ya tashi. Sunaye ne kawai suka daina warwarewa, wanda ke nuni ga DNS maimakon haɗi. Sake shigar da fakiti shine mafi shaharar matakin farko mara kyau a nan. WSL2 na da hanyoyi biyu masu zaman kansu na haifar da wannan alama daidai, kuma suna buƙatar gyara daban-daban.

Me ya sa rarraba ke riƙe da nata resolver

Ba a amfani da abokin ciniki na DNS na Windows a cikin rarraba. WSL2 na gina nata fayil na resolver yayin farawa, yana nuni ga adireshin stub da Windows ke wallafawa a kan maɓallin kama-da-wane na injin kama-da-wane mai taimako.

Wannan tsari yana da ƙarfi a cikin sauye-sauyen cibiyar sadarwa na yau da kullum domin ana rubuta shi sau ɗaya kuma ana sake amfani da shi. Tsarin yana daina zama daidai lokacin da abokin ciniki na tunnel ya sake rubuta jerin adaftan mai masauki bayan injin kama-da-wane mai taimako ya riga ya fara.

Babu wani abu a cikin rarraba da ke lura da canjin, don haka fayil ɗin yana ci gaba da nuni ga adireshin da wataƙila ba ya kan hanya kuma. Bincike na gaba sai ya jira, ya ƙare lokaci, ko ya sami amsa daga uwar garke da bai taɓa jin labarin yankin ciki ba. Daga ciki, resolver yana daina amsawa kawai, kuma duk sunaye suna kasawa lokaci ɗaya.

Da farko tattara shaida a kowane gefe

Rubuta abin da rarraba ke gani, sannan abin da Windows ke gani, kafin ka canza ko ɗaya. Ra’ayoyin biyu tare ne ke bambance hanyoyin gazawa.

A cikin rarraba, buga fayil ɗin resolver, teburin hanya da bincike na ciki ɗaya da na jama’a ɗaya:

ip -4 route
cat /etc/resolv.conf
getent hosts intranet.corp.example
getent hosts example.com

A Windows, lissafa uwar garken DNS ta kowane adafta da teburin IPv4 tare da ma’auni. Abokin ciniki na VPN yakan shigar da hanya don ƙaramin cibiyar sadarwar WSL2, kuma ma’auninsa ne ke yanke shawarar ko wannan zirga-zirgar zai fita ta tunnel ɗin ko ya kasance na gida.

Get-NetAdapter | Get-DnsClientServerAddress
route print -4

Ma’aunin hanya ko tsohon fayil

Gazawar farko ita ce tsohuwar fayil. An rubuta resolver don yanayin adafta lokacin farawa, kuma tunnel ɗin ya canza wannan yanayin. Adireshin stub ɗinsa yanzu yana iya zama ba za a iya isa ba, ko kuma yana ambaton uwar garke da bai san komai game da yankin ciki ba.

Na biyu matsalar hanya ce. Lokacin da VPN ya ƙara hanya da ke rufe ƙaramin cibiyar sadarwar WSL2 da ma’auni ƙasa da na hanyar haɗin mai masauki, fakiti da aka aika zuwa injin kama-da-wane mai taimako suna shiga tunnel ɗin. Sannan kowane sabis na WSL2 yana ƙare lokaci, ba DNS kaɗai ba.

Gwajin da ke bambancewa yana kashe layi ɗaya. Idan adireshin lamba kamar resolver na jama’a har yanzu yana amsa ping yayin da sunaye ke kasawa, hanyar tana da lafiya kuma DNS ita ce matsala. Wannan shine yanayin da canjin resolver ya dace a ciki, kuma yanayin da bai dace ba shima yana bayyana. Idan gwajin lambar ma ya kasa, injin kama-da-wane mai taimako ya rasa hanyarsa kuma babu fayil na resolver da zai gyara hakan.

Don yanayin hanya, cire ma’aunin atomatik daga adaftan tunnel ɗin kuma ba shi lamba sama da hanyar haɗin WSL2:

Get-NetAdapter | Where-Object InterfaceDescription -Match VPN | Set-NetIPInterface -InterfaceMetric 5500
wsl.exe --shutdown

Kashewa yana da muhimmanci. Canza ma’aunin baya sake rubuta injin kama-da-wane mai taimako da ke gudana, don haka dole a sake gina rarraba kafin canjin ya bayyana.

Karɓi fayil ɗin, da gangan

Idan hanya daidai take kuma sunaye na ciki kaɗai ke kasawa, resolver ne ke da laifi kuma zaka iya dakatar da janareta. Wannan canji ne da gangan tare da kuɗin kulawa, ba wani magani na wucin gadi da za a yi amfani da shi cikin sakaci ba.

Ƙirƙiri /etc/wsl.conf a cikin rarraba tare da sashin cibiyar sadarwa wanda ke kashe ƙirƙira, sannan ka rubuta fayil ɗin resolver da kanka, uwar garken kamfani da farko sannan na jama’a a matsayin madadi:

[network]
generateResolvConf = false

search corp.example
nameserver 10.88.4.53
nameserver 9.9.9.9

Tsari yana da muhimmanci. Resolver na jama’a ba zai iya amsa sunan ciki ba, kuma madadin yana wanzuwa ne kawai don binciken intanet. Da zarar fayil ɗin naka ne, babu abin da ke sake ƙirƙirarsa, don haka resolver na kamfani da ke ƙaura yana zama tsayawa da dole ka lura da kanka.

Duba sunaye, sannan fakiti

Tabbatar da sunan ciki ɗaya da na jama’a ɗaya da resolver na tsarin, sannan ka maimaita aikin da ya kasa. Masu kula da fakiti wani lokaci suna amfani da nasu resolver, shi ya sa getent mai aiki zai iya kasancewa tare da shigarwa da ta lalace.

Idan ka sarrafa sake rubutawa, sanya shi idempotent: ba tare da tunnel ba, riƙe fayil ɗin da ya riga ya wanzu maimakon rubuta jerin uwar garke mara komai.

getent hosts intranet.corp.example
resolvectl status | head -20
getent hosts example.com

Bincike na ciki mai aiki da bincike na jama’a mai aiki, daga cikin rarraba, shine sakamakon da ya cancanci rubutawa. Alamar VPN kore a kan mai masauki ba ta tabbatar da ko ɗaya ba.