Sababta isbeddelka DNS uusan u dejin karin SOCKS proxy
Waxay sharraxaysaa sababta uusan u keenin in browser aan la habaynin uu isticmaalo proxy marka magaca host-ka bogga loo jeediyo server SOCKS.
Beddelka jawaabta DNS wuxuu beddelaa oo keliya ciwaanka uu browser-ku ku xirmo. Ma beddelo borotokoolka uu browser-ku ku hadlo marka uu halkaas gaaro.
Markaad furto URL HTTP caadi ah browser-ku wuxuu diraa HTTP. Markaad furto URL HTTPS wuxuu bilaabaa TLS boggaas. Laakiin server SOCKS5 wuxuu marka hore sugayaa wada-hadalkiisa: doorashada habka, wax kasta oo xaqiijin ah iyo codsi magacaaya halka loo socdo. Browser aan la habaynin wax ka mid ah ma diro.
Taasi waxay sharraxaysaa sababta dhegeyste Dante la gaari karo uu isla markiiba u xiri karo isku-xirka ka dib isbeddel DNS. Adeeggu wuu caafimaad qabi karaa; baaytyada soo gala waxay ka tirsan yihiin borotokool khaldan. U rarista dhegeystaha dekedda 80 ama 443 ma ka dhigto baaytyadaas SOCKS.
Habee interface-ka SOCKS ee browser-ka, tusaale ahaan dejinta SOCKS ee Firefox, ama dejinta proxy gaar u ah barnaamijka, si uu u sameeyo gacan-qaadista oo uu proxy-ga u weydiisto inuu sii xirmo. Fayl PAC wuxuu dooran karaa waddo proxy la taageeray barnaamijyada isticmaala. Weli waa habayn proxy gooni ah, ma aha sifo ku qoran diiwaanka A ama AAAA.
HTTPS wuxuu fikradda DNS-keliya ku darayaa carqalad kale. Browser-ku wuxuu weli filayaa aqoonsiga bogga ku jira URL-ka. Shahaadada host-ka proxy ma buuxin karto filashadaas kaliya sababtoo ah DNS ayaa isku-xirka halkaas u diray.
Dhex-gelinta shabakadda ee hufan waa naqshad kale oo ku lug leh marin-u-jiid iyo software dhex-gelin waafaqsan. Laguma heli karo in ciwaanka server SOCKS laga soo celiyo DNS.