DNS na Azure P2S yana gazawa lokacin da resolver ke cikin VNet da aka haɗa

Abokin ciniki na iya isa nasa cibiyar sadarwa ta kamanceceniya kuma ya kasa warware sunaye a cikin wata da aka haɗa. Haɗin ba wucewar ƙofa ba ne har sai ɓangarorin biyu sun yarda.

Yi ping ga VM kuma tana amsa; tambaye ta sunanta kuma abokin ciniki ya ce ba a san mai masaukin ba. Lokacin da resolver ke cikin wata cibiyar sadarwa ta kamanceceniya da aka haɗa maimakon wadda ke ɗauke da ƙofar VPN, wannan biyun sakamakon ana tsammaninsa, kuma babu wani bincike na resolver da zai canja shi. Abin da ya ɓace shi ne yarjejeniyar tafarkin da haɗin ke riƙe ta asali. Tsarin biyu suna kama da juna a takarda, kuma tazarar da ke tsakanin aiki da lalacewa ita ce maɓallan haɗi guda biyu da aka saita a hanya madaidaiciya.

Ka yi tunanin kwamfutar tafi-da-gida tana yin rami zuwa wata ƙofa a VNet2, yayin da mai kula da yankin da ke ba da DNS yake zaune a VNet1.

Tsarin biyu, bambanci ɗaya

Sanya resolver a cikin nasa cibiyar sadarwa ta ƙofar kuma sunan zai warware a lokacin da ramin ya tashi. Babu wani saitin haɗi da ke shiga cikin wannan binciken.

Matsar da wannan resolver ɗin zuwa wancan gefen haɗi kuma abokin ciniki yana samun amsa daga VM yayin da sunan ya kasance ba a sani ba. Takardar shaida, rami da abokin ciniki ba su canja ba. Abin da ya motsa shi ne inda resolver yake zaune. Haɗin ya ba shi hanya zuwa wannan adireshin, ba ikon ƙofar ɗaukar zirga-zirga zuwa can ba.

Bangare A: ba da izinin wucewar ƙofa ga mai ƙofar

Haɗi yana haɗa cibiyoyin sadarwa biyu, amma haɗin ba ya wucewa ga zirga-zirgar da ke zuwa ta ƙofa, kuma buƙatar daga wuri zuwa wuri tana zuwa haka. Don haka ƙofar da ke VNet2 ba ta da ikon miƙa binciken ga VNet1 har sai tsarin ya ba ta. Izini ita ce maɓalli a kan haɗin da cibiyar da ke ɗauke da ƙofar ta mallaka.

Saita Allow gateway transit a kan haɗin VNet2 zuwa VNet1. Kayan ya na cikin abin haɗi, ba na albarkacin ƙofa ba, don haka kana karanta shi kuma kana canja shi a cikin fannin haɗi. Wannan shi ne dukan bangare A.

Bangare B: yi amfani da ƙofofin nesa a kan abokin haɗi

Sauran rabin shine hoton madubi: a kan haɗin VNet1 komawa VNet2, kunna Use remote gateways. Kunna wannan tuta a ƙarshen biyu, ko a ɗaya kawai, yana barin hanya da aka gina rabi da kuma alamun farko ba a taɓa ba. Ƙofar da ke da VPN ita ce kawai ke ba da izinin wucewa, kuma abokin haɗi shine gefen da ke amfani da shi.

Karanta duka kayan biyu a kan duka cibiyoyin biyu maimakon dogaro da fannin portal da ka buɗe na ƙarshe.

Get-AzVirtualNetworkPeering -ResourceGroupName rg-core -VirtualNetworkName vnet2 `
  | Format-List Name,AllowGatewayTransit,UseRemoteGateways
Get-AzVirtualNetworkPeering -ResourceGroupName rg-core -VirtualNetworkName vnet1 `
  | Format-List Name,AllowGatewayTransit,UseRemoteGateways

Ganin maɓallan biyu gefe da gefe ita ce hanya mafi sauri ta kama saitin da aka juya. Haɗin da ke ba da rahoton AllowGatewayTransit false a gefen ƙofa yana bayyana dukan gazawar ba tare da kama fakiti ba.

Abin da abokin ciniki ya kamata ya samu har yanzu

Tafarkin wajibi ne kuma bai isa ba, domin bayanin daga wuri zuwa wuri dole ya ba abokin ciniki adireshin DNS wanda zai amsa da zarar wucewa ta yi aiki. Resolver na dandali ba shine wannan adireshin ba: yana amsa yankunan Azure Private DNS da ke da alaƙa da cibiyar sadarwa, amma babu komai ga yankin da aka shirya a kan sabarorin jagorar ku, kuma wannan shine abin da wannan turawa ke amfani da shi. Nuna abokin ciniki zuwa gare shi kuma sunayen jama'a suna warwarewa cikin farin ciki yayin da mai masaukin ciki ya kasance ba a sani ba.

Tambayi resolver daga kwamfutar tafi-da-gida da aka haɗa kafin ka canja wani abu.

nslookup dc01.corp.example 10.1.0.4

Ƙarewar lokaci yana cewa hanya har yanzu ba ta nan. Amsa mai iko tana mayar da matsalar ga abokin ciniki, yawanci ƙarin da ba a taɓa ƙarawa ba, don haka gajerun sunaye suna tafiya zuwa resolver na jama'a wanda ke gazawa cikin farin ciki.

Kwatanta wannan yarjejeniya a gefen wuri-zuwa-wuri

Babu ɗaya daga cikin waɗannan da ya keɓanta ga kwamfutocin tafi-da-gida. Musanya abokin ciniki da reshe a wuri-zuwa-wuri kuma buƙatar gefe biyu ta dawo: reshen yana zuwa cibiyar ƙofa kai tsaye, kuma sabis da ke nisan cibiyoyi biyu har yanzu yana bayan haɗin.

Dole a ba da izinin wucewa a duka haɗe-haɗe biyu, kuma maɓallin da ke ba da ita yana zaune a kan haɗi ba a kan nau'in abokin ciniki ba.

Kafin ka zargi ƙofar

Windows yana riƙe da jerin resolver ga kowane adafta, don haka tabbatar da abin da ma'aunin rami ya samu kafin ka zargi ƙofar.

ipconfig /all
Get-DnsClientServerAddress -AddressFamily IPv4
ipconfig /flushdns

Amsa mara kyau tana rayuwa a cikin ajiya fiye da gyaran tafarki, kuma jerin ƙarin da ya tsufa yana ci gaba da aika tambayoyi zuwa wurin da ba a taɓa shirya yankin ba. Share, sake tambaya, kuma lura wace sabar ce ta amsa.

Ƙananan sharuɗɗa biyu ne ke yanke shawarar ko hanyar za ta tsaya: dole wuraren adireshi kada su yi karo, kuma ƙungiyar tsaron cibiyar sadarwa a cikin ƙaramin cibiyar resolver dole ta karɓi tafkin abokin ciniki, wanda wani yanki ne kawai na tushe. Tabbatar da shi da binciken tafarki mai tasiri daga gefen VM da kuma tambaya ɗaya kai tsaye daga abokin ciniki, don kada a taɓa rikita matsalar yanki, matsalar ƙari ko tacewa da rashin wucewa.

Labarai masu alaƙa