Karanta DNS na Android daidai: bisa kowace hanyar sadarwa, ba resolv.conf ba

Kana samun shell a kan na'urar, ka karanta /etc/resolv.conf ko ka tono tsohuwar darajar net.dns1, sai ka sami adireshi ɗaya. Manhajar da ke gabanka tana warware ta wani abu daban kware. A cikin sigar Android ta yanzu resolver na kowace hanyar sadarwa ne: tsarin yana riƙe da manufa ga kowace Network kuma yana amfani da ita a kan socket ɗin da ya aika buƙatar. Fayil ɗin da tsohuwar sifa raguwa ne, kuma babu ɗayansu da ke bayyana hanyar da tambayarka ta bi da gaske.

Wannan gibin yana bayyana lokacin tura split-tunnel da Private DNS, inda manhajoji biyu a kan waya ɗaya za su iya ganin amsoshi daban-daban bisa doka. Wannan jagorar tana farawa daga warwarewar da ba daidai ba ko da babu, sannan ta koma kan tsarin da ya mallake ta.

Resolver na hanyar sadarwa ne, ba na'urar ba

Warware suna a Android 9 da sama yana wucewa ta resolver na tsarin da ya dogara da Network da socket ke ɗaure da ita. Kowace hanyar sadarwa tana ɗauke da LinkProperties nata, kuma waɗannan sifofin suna riƙe da jerin uwar garken DNS, yankunan bincike da yanayin Private DNS na wannan hanyar sadarwa kaɗai. Babu abin da ke cikin wannan tsari da ya dace da jerin ɗaya na dukan na'urar da za ka karanta daga fayil.

VPN yana bayyana rabuwar. Lokacin da ramin ya tashi, manhajar VPN tana ba da uwar garken DNS waɗanda aka yi rajista a kan hanyar sadarwar VPN ɗin kanta, don haka manhajoji da aka tura ta cikinta suna warware a kan waɗannan uwar garken yayin da manhajoji da aka ware ke ci gaba da amfani da hanyar sadarwar da ke ƙasa. Na'ura ɗaya, hanyoyin amsa biyu, babu sabani.

Karanta hoton a cikin manhajar da abin ya shafa

Tambayi manhajar kanta. Hanyar da ke da Context da izinin android.permission.ACCESS_NETWORK_STATE na yau da kullum za ta iya karanta hoton ba tare da taɓa sifofin tsarin ba:

val cm = getSystemService(ConnectivityManager::class.java) ?: return
val network = cm.activeNetwork
val links = network?.let { cm.getLinkProperties(it) }

val dnsServers = links?.dnsServers
val privateDnsActive = links?.isPrivateDnsActive
val privateDnsName = links?.privateDnsServerName

activeNetwork ita ce hanyar sadarwar da aka saba amfani da ita ga tsarinka, ba ita kaɗai a na'urar ba, kuma tana iya zama null lokacin da mai kira ba shi da wadda za a iya amfani da ita. VPN da aka toshe ta zama ta asali ita ce sanannen dalili. isPrivateDnsActive yana gaya maka ko tambayoyin a wannan hanyar sadarwa suna bi ta TLS zuwa resolver mai suna, wanda ke canza abin da binciken UDP 53 mai sauƙi zai nuna maka. Fuskar API an rubuta ta ƙarƙashin LinkProperties, kuma kowace daraja a cikinta hoton tsari ne, ba hujjar cewa wata tambaya ta isa wani uwar garke ba.

Lokacin da hanyar sadarwar asali ba ita ce ke yin aikin ba

Hoton yana amsa ne kawai ga ta asali. Manhaja na iya ɗaure tsarinta ko socket ɗaya ga wata hanyar sadarwa, sannan warwarewar tana bin wannan zaɓi yayin da bincikenka ke ci gaba da bayar da rahoton ta asali. Burauza da ke kawo resolver ɗinta na DNS-over-HTTPS ba ya taɓa tuntuɓar jerin tsarin kwata-kwata, don haka amsoshinta ba su ce komai game da sauran na'urar ba. Manhajar bayanan aiki tana gudana ƙarƙashin wani mai amfani daban da manufarta. Duba ɗaurin kafin ka zargi uwar garken.

Haɗin VPN shi ne rabin na biyu. Karɓar layin dhcp-option DNS a cikin bayanan OpenVPN da yin rijistar wannan adireshi a kan hanyar sadarwar VPN ta Android matakai biyu ne daban, kuma hanyar da ta ɓace zuwa uwar garken tana faduwa cikin shiru kamar adireshin da ba daidai ba. Daga na'urar haɓakawa, adb shell dumpsys connectivity yana buga waɗannan sifofin haɗi ga kowace hanyar sadarwa lokacin da build ya yarda, wanda ke tabbatar da jerin ba tare da rubuta code ba.

Kwatanta tsarin da warwarewa ɗaya da aka ba ka izini ka yi

Zaɓi suna da dole ne a warware shi cikin wurin suna na sirri da suna na jama'a ɗaya, sannan ka rubuta duka sakamakon biyu kusa da hoton: hanyar sadarwa, uwar garken da aka saita, yanayin Private DNS da ainihin rubutun kuskure. Tambaya kai tsaye zuwa uwar garke mai suna tana tabbatar da cewa wannan uwar garken tana amsa maka; ba ta tabbatar da cewa warwarewar manhaja ta yau da kullum ta zaɓe ta ba. Amsa daga cache ba sabon gwaji ba ne, don haka share cache ko yi amfani da sunan da babu wanda ya tambaya a yau.

Idan resolver yana hidima ne kawai ga abokan ciniki daga wata hanyar sadarwa ta shiga, abin da yake gani bayan fitowar VPN zai iya yanke hukunci, kuma wannan tambaya ce ta manufa ga wanda ke tafiyar da shi, ba hujjar cewa masu aiki suna toshe UDP 53 ba. Inda Private DNS ke aiki, sunan mai masauki mara cikawa na iya ƙi bisa ƙira yayin da wannan uwar garken ke amsa sunayen jama'a kamar yadda aka saba. Karanta sifofin yana gaya maka wace yanayi ce ke aiki, don haka ka daina hasashen matatun fakiti.

Gyara shiɓin da ya mallaki rashin daidaito

Yi aiki zuwa sama maimakon gyara yanayin duniya. Idan manhajar an ɗaure ta ga kuskuren hanyar sadarwa, gyara ɗaurin. Idan bayanan suna ba da kuskuren zaɓin DNS, gyara bayanan. Idan Private DNS yana da tsanani a kan hanyar sadarwar da resolver ɗinta ba zai iya hidima ga yankinka na sirri ba, wannan shawara ce ta sarrafa na'ura, ba dalilin kashe fasalin a ko'ina ba.

Tura resolver na jama'a cikin ƙugiyar DHCP ko sifar tsarin ita ce gyaran da ke ci gaba da haifar da hatsari: sunayen sirri suna daina warwarewa, canjin yana rayuwa fiye da zaman VPN, kuma mutum na gaba a na'urar ya sami tsohon adireshi mara mai shi. Riƙe canjin cikin VPN, manhaja ko shiɓin sarrafawa da ya mallaki rashin daidaiton, sannan ka sake karanta hoton don tabbatar da jerin uwar garken ya canza da gaske.

A ƙarshe abin da kake so shi ne buƙatar manhaja ɗaya da aka ɗaure ga hanyar sadarwa ɗaya, jerin resolver da yanayin Private DNS. Da zarar ka iya nuna wannan sarkar, sanannen adireshi a cikin fayil ba ya zama hujja ga komai.