{"id":88961,"date":"2020-07-16T19:42:34","date_gmt":"2020-07-16T17:42:34","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/anycast-protiv-unicast-chto-luchshe-vybirat-v-kazhdom-sluchae"},"modified":"2020-07-16T19:42:34","modified_gmt":"2020-07-16T17:42:34","slug":"anycast-protiv-unicast-chto-luchshe-vybirat-v-kazhdom-sluchae","status":"publish","type":"post","link":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/anycast-protiv-unicast-chto-luchshe-vybirat-v-kazhdom-sluchae","title":{"rendered":"Anycast versus Unicast: ce s\u0103 alegi \u00een fiecare caz","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Cu siguran\u021b\u0103, mul\u021bi au auzit de Anycast. Prin aceast\u0103 metod\u0103 de adresare \u0219i rutare \u00een re\u021bea, o adres\u0103 IP este atribuit\u0103 mai multor servere din re\u021bea. Aceste servere pot fi situate chiar \u0219i la distan\u021be mari unele de altele \u00een centrele de date. Ideea Anycast este c\u0103, \u00een func\u021bie de loca\u021bia sursei cererilor, datele sunt trimise c\u0103tre serverul cel mai aproape (conform topologiei re\u021belei, mai exact \u2014 protocolului de rutare BGP). Astfel, se poate reduce num\u0103rul de salturi (hop) \u0219i \u00eent\u00e2rzierea (latency). <\/p>\n<p>\u00cen esen\u021b\u0103, se anun\u021b\u0103 aceea\u0219i rut\u0103 din mai multe centre de procesare a datelor din \u00eentreaga lume. Astfel, clien\u021bii vor fi direc\u021biona\u021bi c\u0103tre centrul de procesare a datelor \u201ecel mai bun\u201d \u0219i \u201ecel mai apropiat\u201d pe baza rutelor BGP. De ce, totu\u0219i, Anycast? De ce s\u0103 folose\u0219ti Anycast \u00een loc de Unicast?<\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/ruvds\/blog\/511050\/\"><img decoding=\"async\" alt=\"Anycast versus Unicast: ce s\u0103 alegi \u00een fiecare caz\" src=\"\/wp-content\/uploads\/2020\/07\/6573f1e2d39d783575348734518c4bae.png\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><br \/>\nUnicast este \u00eentr-adev\u0103r potrivit pentru un site cu un singur server web \u0219i un volum moderat de trafic. Totu\u0219i, dac\u0103 serviciul are milioane de abona\u021bi, acesta utilizeaz\u0103, de obicei, mai multe servere web, fiecare av\u00e2nd aceea\u0219i adres\u0103 IP. Aceste servere sunt distribuite geografic pentru a optimiza procesarea cererilor.<\/p>\n<p>\u00centr-un astfel de scenariu, Anycast va oferi \u00eembun\u0103t\u0103\u021biri de performan\u021b\u0103 (traficul este \u00eendreptat c\u0103tre utilizator cu \u00eent\u00e2rzierea minim\u0103), va asigura fiabilitatea serviciului (datorit\u0103 serverelor de rezerv\u0103) \u0219i va permite balansarea \u00eenc\u0103rc\u0103turii \u2014 rutarea pe mai multe servere va distribui eficient \u00eenc\u0103rc\u0103tura \u00eentre acestea, \u00eembun\u0103t\u0103\u021bind astfel viteza de func\u021bionare a site-ului.<\/p>\n<p>Operatorii ofer\u0103 clien\u021bilor diverse tipuri de balansare a \u00eenc\u0103rc\u0103turii pe baza Anycast \u0219i DNS. Clien\u021bii pot specifica adresele IP la care vor fi trimise cererile \u00een func\u021bie de loca\u021bia geografic\u0103 a site-ului. Acest lucru permite o distribuire mai flexibil\u0103 a cererilor utilizatorilor.<\/p>\n<p>S\u0103 presupunem c\u0103 exist\u0103 c\u00e2teva platforme \u00eentre care trebuie s\u0103 se distribuie \u00eenc\u0103rc\u0103tura (utilizatorii), de exemplu, un magazin online cu 100.000 de cereri pe zi sau un blog popular. Pentru a limita regiunea din care utilizatorii acceseaz\u0103 o platform\u0103 anume, se poate folosi op\u021biunea Geo Community. Aceasta permite restric\u021bionarea regiunii \u00een cadrul c\u0103reia operatorul va anun\u021ba ruta.<\/p>\n<p><img decoding=\"async\" alt=\"Anycast versus Unicast: ce s\u0103 alegi \u00een fiecare caz\" src=\"\/wp-content\/uploads\/2020\/07\/54582f256a946a3ff557ab971cec087d.png\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p><img decoding=\"async\" alt=\"Anycast versus Unicast: ce s\u0103 alegi \u00een fiecare caz\" src=\"\/wp-content\/uploads\/2020\/07\/48849a5cf65cb1c7190c1f75aa33e2d8.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i>Anycast \u0219i Unicast: diferen\u021bele<\/i><\/p>\n<p>Anycast este adesea utilizat \u00een aplica\u021bii precum DNS (sistemul de nume de domenii) \u0219i CDN (re\u021bele de livrare a con\u021binutului), permi\u021b\u00e2nd luarea deciziilor de rutare care \u00eembun\u0103t\u0103\u021besc performan\u021ba re\u021belei. Re\u021belele de livrare a con\u021binutului folosesc Anycast datorit\u0103 volumelor mari de trafic, iar Anycast aduce \u00een acest caz o serie de avantaje (despre care se va discuta mai jos). \u00cen DNS, Anycast permite \u00eembun\u0103t\u0103\u021birea semnificativ\u0103 a nivelului de fiabilitate \u0219i disponibilitate a serviciului.<\/p>\n<p><img decoding=\"async\" alt=\"Anycast versus Unicast: ce s\u0103 alegi \u00een fiecare caz\" src=\"\/wp-content\/uploads\/2020\/07\/8043fec22ecef8aa2b3b9c1a06e8f5f9.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i>\u00cen Anycast IP, folosind BGP, exist\u0103 mai multe rute c\u0103tre un anumit gazd\u0103. De fapt, acestea sunt copii ale gazdelor \u00een mai multe centre de date, utilizate pentru a stabili conexiuni cu laten\u021b\u0103 mai mic\u0103.<\/i><\/p>\n<p>Astfel, \u00een re\u021beaua Anycast, aceea\u0219i adres\u0103 IP este anun\u021bat\u0103 din locuri diferite, iar re\u021beaua decide unde s\u0103 trimit\u0103 cererea utilizatorului \u00een func\u021bie de \u201ecostul\u201d rutei. De exemplu, de multe ori pentru a determina cea mai scurt\u0103 rut\u0103 de transmisie a datelor se utilizeaz\u0103 protocolul BGP. C\u00e2nd un utilizator trimite o cerere Anycast, BGP determin\u0103 cea mai bun\u0103 rut\u0103 pentru serverele disponibile \u00een re\u021beaua Anycast.<\/p>\n<h2>Avantajele Anycast<\/h2>\n<p>Reducerea laten\u021bei<br \/>\nSistemele cu Anycast pot reduce laten\u021ba \u00een procesarea cererilor utilizatorilor, deoarece permit ob\u021binerea datelor de la cel mai apropiat server. Adic\u0103, utilizatorii se vor conecta \u00eentotdeauna la serverul DNS \u201ecel mai apropiat\u201d (din punct de vedere al protocolului de rutare). Ca urmare, Anycast reduce timpul de interac\u021biune prin diminuarea distan\u021bei \u00een re\u021bea \u00eentre client \u0219i server. Aceasta nu numai c\u0103 reduce laten\u021ba, dar asigur\u0103 \u0219i o distribu\u021bie uniform\u0103 a \u00eenc\u0103rc\u0103turii.<\/p>\n<p>Vitez\u0103<\/p>\n<p>Deoarece traficul este direc\u021bionat c\u0103tre nodul cel mai apropiat \u0219i laten\u021ba \u00een transmiterea datelor \u00eentre client \u0219i nod este redus\u0103, rezultatul va fi optimizarea vitezei de livrare, indiferent de locul din care clientul solicit\u0103 informa\u021biile.<\/p>\n<p>Stabilitate \u0219i disponibilitate crescut\u0103<\/p>\n<p>Dac\u0103 mai multe servere din \u00eentreaga lume utilizeaz\u0103 aceea\u0219i adres\u0103 IP, \u00een cazul \u00een care unul dintre servere \u00eent\u00e2mpin\u0103 probleme sau este oprit, traficul va fi redirec\u021bionat c\u0103tre cel mai apropiat server. Ca urmare, Anycast face serviciul mai robust \u0219i asigur\u0103 o accesibilitate mai bun\u0103 la re\u021bea\/laten\u021b\u0103\/vitez\u0103.\u00a0<\/p>\n<p>Prin urmare, datorit\u0103 existen\u021bei mai multor servere, mereu disponibile pentru utilizatori, Anycast, de exemplu, cre\u0219te stabilitatea func\u021bion\u0103rii DNS. \u00cen cazul \u00een care un nod e\u0219ueaz\u0103, cererile utilizatorilor vor fi redirec\u021bionate c\u0103tre un alt server DNS f\u0103r\u0103 nicio interven\u021bie manual\u0103 sau reconfigurare. Anycast asigur\u0103 o comutare aproape transparent\u0103 c\u0103tre alte site-uri, elimin\u00e2nd pur \u0219i simplu rutele site-ului problematic.\u00a0<\/p>\n<p>\u00cenc\u0103rcare echilibrat\u0103<\/p>\n<p>\u00cen sistemul Anycast, traficul de re\u021bea este distribuit pe diferite servere. Adic\u0103 func\u021bioneaz\u0103 ca un echilibrator de \u00eenc\u0103rcare, prevenind ca orice server individual s\u0103 primeasc\u0103 cea mai mare parte a traficului. \u00cenc\u0103rcarea echilibrat\u0103 poate fi utilizat\u0103, de exemplu, atunci c\u00e2nd mai multe noduri de re\u021bea se afl\u0103 la aceea\u0219i distan\u021b\u0103 geografic\u0103 de sursa cererilor. \u00cen acest caz, sarcina este distribuit\u0103 \u00eentre noduri.<\/p>\n<p>Reducerea impactului atacurilor DoS\u00a0<\/p>\n<p>O alt\u0103 caracteristic\u0103 a Anycast-ului este rezisten\u021ba la DDoS. Atacurile DDoS ar avea dificult\u0103\u021bi s\u0103 pun\u0103 la p\u0103m\u00e2nt sistemul Anycast, deoarece ar trebui s\u0103 cople\u0219easc\u0103 cu o avalan\u0219\u0103 de cereri toate serverele dintr-o astfel de re\u021bea.\u00a0<\/p>\n<p>\u00cen atacurile DDoS se folosesc adesea botneturi, care pot genera un volum at\u00e2t de mare de trafic \u00eenc\u00e2t acestea suprasolicit\u0103 serverul atacat. Avantajul utiliz\u0103rii Anycast \u00een aceast\u0103 situa\u021bie este c\u0103 fiecare server poate \u201eabsorbi\u201d o parte din atac, reduc\u00e2nd sarcina pe un server specific. O atac de tip \u201erefuz al serviciului\u201d va fi, cel mai probabil, localizat pe server \u0219i nu va afecta \u00eentregul serviciu.<\/p>\n<p>Scalabilitate orizontal\u0103 ridicat\u0103<\/p>\n<p>Sistemele Anycast sunt bine adaptate pentru servicii cu volume mari de trafic. Dac\u0103 un serviciu care folose\u0219te Anycast necesit\u0103 servere noi pentru a gestiona traficul \u00een cre\u0219tere, noi servere pot fi ad\u0103ugate la re\u021bea pentru a-l gestiona. Acestea pot fi amplasate pe noi sau pe locuri existente.\u00a0<\/p>\n<p>Dac\u0103 \u00eentr-o anumit\u0103 zon\u0103 se observ\u0103 o cre\u0219tere semnificativ\u0103 a traficului, ad\u0103ugarea unui server va ajuta la echilibrarea \u00eenc\u0103rc\u0103rii pentru acel loc. Ad\u0103ugarea unui server \u00eentr-o nou\u0103 loca\u021bie va contribui la reducerea timpului de a\u0219teptare, cre\u00e2nd pentru unii utilizatori un nou traseu mai scurt. Ambele metode ajut\u0103 de asemenea la cre\u0219terea stabilit\u0103\u021bii serviciului, deoarece se fac disponibile servere noi \u00een re\u021bea. Astfel, dac\u0103 un server este suprasolicitat, se poate pur \u0219i simplu desf\u0103\u0219ura un alt server \u00een acel loc, care va putea prelua o parte din solicit\u0103rile serverului suprasolicitat. \u00cen acest proces, nu este necesar\u0103 configurarea din partea clien\u021bilor.\u00a0<\/p>\n<p>Numai astfel se poate gestiona terabi\u021bi de trafic \u0219i un num\u0103r foarte mare de utilizatori, atunci c\u00e2nd serverul are doar c\u00e2teva porturi de 10 sau 25 Gbit\/s. 100 de gazde cu o singur\u0103 adres\u0103 IP vor permite procesarea volumelor de trafic de terabi\u021bi.<\/p>\n<p>U\u0219urin\u021ba gestion\u0103rii configura\u021biei<\/p>\n<p>A\u0219a cum s-a men\u021bionat mai sus, o utilizare interesant\u0103 a Anycast-ului este DNS-ul. Pute\u021bi plasa la nodurile re\u021belei mai mul\u021bi servere DNS diferite, dar folosind o singur\u0103 adres\u0103 DNS. \u00cen func\u021bie de locul \u00een care se afl\u0103 sursa, solicit\u0103rile sunt direc\u021bionate c\u0103tre cel mai apropiat nod. Acest lucru asigur\u0103 o anumit\u0103 echilibrare a traficului \u0219i redundan\u021b\u0103 \u00een caz de e\u0219ec al serverului DNS. Astfel, \u00een loc s\u0103 configura\u021bi diferite servere DNS \u00een func\u021bie de locul \u00een care se afl\u0103, configura\u021bia unui singur server DNS poate fi extins\u0103 la toate nodurile.<\/p>\n<p>Re\u021belele Anycast pot fi configurate pentru rutarea solicit\u0103rilor nu numai pe baza distan\u021bei, ci \u0219i pe baza unor parametri precum disponibilitatea serverului, num\u0103rul de conexiuni stabilite sau timpul de r\u0103spuns.<\/p>\n<p>Pentru utilizarea tehnologii Anycast din partea clientului nu sunt necesare servere, re\u021bele sau componente speciale. Dar Anycast are \u0219i dezavantajele sale. Se consider\u0103 c\u0103 implementarea sa este o sarcin\u0103 complex\u0103, care necesit\u0103 echipamente suplimentare, furnizori de \u00eencredere \u0219i o rutare corect\u0103 a traficului.<\/p>\n<h2>Dintr-o surs\u0103 pur\u0103 \u00een dep\u0103rtare frumoas\u0103<\/h2>\n<p>\nDe\u0219i Anycast direc\u021bioneaz\u0103 utilizatorii pe baza celui mai mic num\u0103r de hop-uri, nu \u00eenseamn\u0103 neap\u0103rat o \u00eent\u00e2rziere minim\u0103. \u00cent\u00e2rzierea este o metric\u0103 mai complex\u0103, deoarece pentru un hop aceasta poate fi mai mare dec\u00e2t pentru zece. <\/p>\n<p><img decoding=\"async\" alt=\"Anycast versus Unicast: ce s\u0103 alegi \u00een fiecare caz\" src=\"\/wp-content\/uploads\/2020\/07\/8fb50007806759ab243c89bb88cdeb31.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i>Exemplu: comunica\u021biile intercontinentale pot include o leg\u0103tur\u0103 cu o \u00eent\u00e2rziere foarte mare.<\/i><\/p>\n<p>Anycast este utilizat \u00een principal pentru servicii bazate pe UDP, cum ar fi DNS. Cererile utilizatorilor sunt direc\u021bionate c\u0103tre cel mai \"bun\" \u0219i \"aproape\" datacenter pe baza c\u0103ilor BGP. <\/p>\n<p><img decoding=\"async\" alt=\"Anycast versus Unicast: ce s\u0103 alegi \u00een fiecare caz\" src=\"\/wp-content\/uploads\/2020\/07\/05a1b75b981d55967e44e3b90cfd88b9.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i>Exemplu: sta\u021bia de lucru a clientului DNS cu adresa IP Anycast DNS 123.10.10.10 efectueaz\u0103 rezolvarea DNS pentru cel mai apropiat dintre cele trei servere de nume DNS implementate cu aceea\u0219i adres\u0103 IP Anycast. \u00cen cazul unei defectiuni a routerului R1 sau a serverului A, pachetele clientului DNS vor fi redirec\u021bionate automat c\u0103tre urm\u0103torul server DNS cel mai apropiat prin routerele R2 \u0219i R3. Mai mult, ruta c\u0103tre serverul nostru A va fi eliminat\u0103 din tabelele de rutare, ceea ce va preveni utilizarea ulterioar\u0103 a acestui server de nume.<\/i><\/p>\n<h2>Scenarii de implementare<\/h2>\n<p>\nExist\u0103 dou\u0103 scheme comune utilizate pentru a determina la care server se conecteaz\u0103 utilizatorul:<\/p>\n<ul>\n<li><b>Anycast la nivel de re\u021bea<\/b>. Conecteaz\u0103 utilizatorul la cel mai apropiat server. Aici, traseul re\u021belei de la utilizator la server este important.<\/li>\n<li><b>Anycast la nivel de aplica\u021bie<\/b>. \u00cen aceast\u0103 schem\u0103, exist\u0103 metrici mai complexe, inclusiv disponibilitatea serverului, timpul de r\u0103spuns, num\u0103rul de conexiuni etc. Aceasta depinde de un monitor extern care ofer\u0103 statistici de re\u021bea.<\/li>\n<\/ul>\n<p><\/p>\n<h2>CDN pe baza Anycast<\/h2>\n<p>\nS\u0103 revenim acum la utilizarea Anycast \u00een re\u021belele de livrare de con\u021binut. Anycast reprezint\u0103 cu siguran\u021b\u0103 o concept re\u021bea interesant\u0103 \u0219i c\u00e2\u0219tig\u0103 tot mai mult\u0103 recunoa\u0219tere din partea furnizorilor de CDN de nou\u0103 genera\u021bie.<\/p>\n<p>CDN este o re\u021bea distribuit\u0103 de servere care livreaz\u0103 con\u021binut utilizatorilor finali cu o disponibilitate ridicat\u0103 \u0219i o \u00eent\u00e2rziere sc\u0103zut\u0103. Re\u021belele de livrare de con\u021binut joac\u0103 ast\u0103zi un rol important, fiind baza numeroaselor servicii online multimedia, iar consumatorii devin din ce \u00een ce mai pu\u021bin toleran\u021bi la vitezele lente de \u00eenc\u0103rcare. Aplica\u021biile video \u0219i vocale sunt deosebit de sensibile la jitter \u0219i \u00eent\u00e2rziere \u00een re\u021bea. <\/p>\n<p>CDN conecteaz\u0103 toate serverele \u00eentr-o singur\u0103 re\u021bea \u0219i asigur\u0103 o \u00eenc\u0103rcare mai rapid\u0103 a con\u021binutului. Uneori, timpul de a\u0219teptare al utilizatorului poate fi redus cu 5-6 secunde. Scopul CDN este de a optimiza livrarea prin furnizarea de con\u021binut de pe serverul cel mai apropiat de utilizatorul final. Aceasta este foarte asem\u0103n\u0103toare cu Anycast, unde serverul cel mai apropiat este selectat \u00een func\u021bie de loca\u021bia utilizatorului final. S-ar p\u0103rea c\u0103 fiecare furnizor de servicii CDN va folosi \u00een mod implicit Anycast, dar \u00een realitate acest lucru nu este \u00eentotdeauna cazul.<\/p>\n<p>Aplica\u021biile care utilizeaz\u0103 protocoale precum HTTP\/TCP se bazeaz\u0103 pe conexiuni stabile. Dac\u0103 un nou nod Anycast este selectat (de exemplu, \u00een caz de defectare a serverului), serviciul poate fi \u00eentrerupt. De aceea, Anycast a fost recomandat anterior pentru servicii f\u0103r\u0103 conexiune, cum ar fi UDP \u0219i DNS. Totu\u0219i, Anycast func\u021bioneaz\u0103 bine \u0219i pentru protocoalele orientate pe conexiune; de exemplu, TCP func\u021bioneaz\u0103 excelent \u00een modul Anycast.<\/p>\n<p>Unii furnizori de CDN utilizeaz\u0103 rutare pe baza Anycast, \u00een timp ce al\u021bii prefer\u0103 rutarea pe baza DNS: serverul cel mai apropiat este ales \u00een func\u021bie de loca\u021bia serverului DNS al utilizatorului.<\/p>\n<p>Infrastructurile hibride \u0219i infrastructurile cu mai multe centre de date sunt un alt exemplu de aplicare a Anycast. Adresa Load Balancing IP ob\u021binut\u0103 de la furnizor permite distribuirea \u00eenc\u0103rc\u0103turii \u00eentre adresele IP ale diferitelor servicii ale clien\u021bilor \u00een centrele de date ale furnizorului. Tehnologia de adresare asigur\u0103 o performan\u021b\u0103 mai bun\u0103 \u00een condi\u021bii de trafic semnificativ, disponibilitate ridicat\u0103 \u0219i ajut\u0103 la optimizarea timpului de r\u0103spuns atunci c\u00e2nd num\u0103rul de utilizatori este mare.<\/p>\n<p>\u00cen infrastructurile hibride cu mai multe centre de date, traficul poate fi distribuit \u00eentre servere sau chiar \u00eentre ma\u0219ini virtuale pe servere dedicate.<\/p>\n<p>Astfel, exist\u0103 o gam\u0103 larg\u0103 de solu\u021bii tehnice pentru construirea infrastructurii. De asemenea, se poate configura balansarea \u00eenc\u0103rc\u0103rii pe baza adreselor IP \u00een mai multe centre de date, folosind adresarea pentru orice dispozitiv din grup pentru a optimiza func\u021bionarea site-ului.<\/p>\n<p>Este posibil s\u0103 distribui\u021bi traficul conform propriilor reguli, stabilind \u201egreutatea\u201d fiec\u0103rei servere distribuite \u00een fiecare centru de date. Aceast\u0103 configura\u021bie este deosebit de util\u0103 atunci c\u00e2nd exist\u0103 un parc de servere distribuite \u0219i performan\u021ba serviciilor nu este constant\u0103. Acest lucru va permite o distribuire mai frecvent\u0103 a traficului pentru a \u00eembun\u0103t\u0103\u021bi performan\u021ba serverelor.<\/p>\n<p>Pentru a crea un sistem de monitorizare prin intermediul comenzii ping, exist\u0103 op\u021biunea de a configura sonde. Acest lucru le permite administratorilor s\u0103 defineasc\u0103 propriile proceduri de control \u0219i s\u0103 ob\u021bin\u0103 o imagine mai clar\u0103 a st\u0103rii fiec\u0103rui component din infrastructur\u0103. Astfel, se pot stabili criterii de disponibilitate.<\/p>\n<p>Exist\u0103 posibilitatea de a construi o infrastructur\u0103 hibrid\u0103: uneori este convenabil s\u0103 p\u0103stra\u021bi back-office-ul \u00een re\u021beaua corporativ\u0103, iar partea de interfa\u021b\u0103 s\u0103 fie externalizat\u0103 la un furnizor.<\/p>\n<p>Exist\u0103 posibilitatea de a ad\u0103uga certificate SSL pentru echilibrarea \u00eenc\u0103rc\u0103rii, criptarea datelor transferate \u0219i securizarea comunica\u021biei \u00eentre vizitatorii site-ului \u0219i infrastructura corporativ\u0103. Atunci c\u00e2nd se face echilibrarea \u00eenc\u0103rc\u0103rii \u00eentre centrele de date, SSL poate fi aplicat \u0219i aici.<\/p>\n<p>Serviciul Anycast cu echilibrarea \u00eenc\u0103rc\u0103rii adreselor poate fi ob\u021binut de la furnizor. Aceast\u0103 func\u021bie va ajuta la \u00eembun\u0103t\u0103\u021birea algoritmului de interac\u021biune a utilizatorilor cu aplica\u021biile \u00een func\u021bie de loca\u021bie. Este suficient s\u0103 anun\u021ba\u021bi ce servicii sunt disponibile \u00een centrele de date \u0219i traficul va fi redirec\u021bionat c\u0103tre cea mai apropiat\u0103 infrastructur\u0103. Dac\u0103 exist\u0103 servere dedicate, de exemplu, \u00een Fran\u021ba sau \u00een America de Nord, atunci clien\u021bii vor fi direc\u021biona\u021bi c\u0103tre cel mai apropiat server din re\u021bea.<\/p>\n<p>Una dintre op\u021biunile de utilizare a Anycast-ului este alegerea optim\u0103 a punctului de prezen\u021b\u0103 al operatorului (PoP). S\u0103 lu\u0103m ca exemplu <noindex><a rel=\"nofollow\" href=\"https:\/\/engineering.linkedin.com\/network-performance\/tcp-over-ip-anycast-pipe-dream-or-reality\">exemplu<\/a><\/noindex>. LinkedIn (blocat \u00een Rusia) \u00ee\u0219i propune nu doar s\u0103 \u00eembun\u0103t\u0103\u021beasc\u0103 performan\u021ba \u0219i viteza produselor sale \u2014 aplica\u021bii mobile \u0219i web \u2014 ci \u0219i s\u0103 \u00eembun\u0103t\u0103\u021beasc\u0103 infrastructura de re\u021bea pentru livrarea rapid\u0103 a con\u021binutului. Pentru livrarea dinamic\u0103 a con\u021binutului, LinkedIn folose\u0219te activ PoP-uri \u2013 puncte de prezen\u021b\u0103. Pentru a direc\u021biona utilizatorii c\u0103tre cel mai apropiat PoP, se folose\u0219te Anycast.<\/p>\n<p>Motivul este c\u0103 \u00een cazul Unycast, fiecare PoP LinkedIn are o adres\u0103 IP unic\u0103. Apoi, utilizatorii sunt aloca\u021bi PoP \u00een func\u021bie de loca\u021bia lor geografic\u0103 prin DNS. Problema este c\u0103, atunci c\u00e2nd se utilizeaz\u0103 DNS, aproximativ 30% dintre utilizatorii din Statele Unite erau redirec\u021biona\u021bi c\u0103tre un PoP neoptim. Datorit\u0103 implement\u0103rii progresive a Anycast, alocarea neoptim\u0103 a PoP-urilor a sc\u0103zut de la 31% la 10%.<\/p>\n<p><img decoding=\"async\" alt=\"Anycast versus Unicast: ce s\u0103 alegi \u00een fiecare caz\" src=\"\/wp-content\/uploads\/2020\/07\/f1635951294bc476639ec65d175c11e0.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i>Rezultatele testului pilot sunt prezentate \u00een grafic, unde axa Y reprezint\u0103 procentul aloc\u0103rilor optime PoP. Pe m\u0103sur\u0103 ce Anycast a fost \"scalat\" \u00een multe state din SUA, a existat o \u00eembun\u0103t\u0103\u021bire a procentului de trafic c\u0103tre PoP-uri optimale.<\/i><\/p>\n<h2>Monitorizarea re\u021belei Anycast<\/h2>\n<p>\nTeoretic, re\u021belele Anycast sunt simple: mai multor servere fizice le este atribuit aceea\u0219i adres\u0103 IP, pe care BGP o folose\u0219te pentru a determina ruta. \u00cens\u0103 implementarea \u0219i proiectarea platformelor Anycast sunt complexe, \u00een special re\u021belele Anycast cu fiabilitate crescut\u0103 sunt renumite pentru aceast\u0103 complexitate. Monitorizarea eficient\u0103 a re\u021belei Anycast pentru identificarea rapid\u0103 \u0219i localizarea defec\u021biunilor este \u0219i mai dificil\u0103. <\/p>\n<p>Dac\u0103 serviciile folosesc un furnizor CDN extern pentru livrarea con\u021binutului lor, este foarte important s\u0103 monitorizeze \u0219i s\u0103 verifice performan\u021ba re\u021belei. Atunci c\u00e2nd se monitorizeaz\u0103 un CDN bazat pe Anycast, accentul este pus pe m\u0103surarea \u00eent\u00e2rzierilor end-to-end \u0219i a caracteristicilor penultimului salt, pentru a \u00een\u021belege care centru de date livreaz\u0103 con\u021binutul. Analiza antetelor HTTP ale serverului este o alt\u0103 modalitate de a determina de unde provin datele.<\/p>\n<p><img decoding=\"async\" alt=\"Anycast versus Unicast: ce s\u0103 alegi \u00een fiecare caz\" src=\"\/wp-content\/uploads\/2020\/07\/9dfcf689c3c7a553b00de5f0dac4d0ec.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i>Exemplu: antetele r\u0103spunsului HTTP care indic\u0103 loca\u021bia serverului CDN.<\/i><\/p>\n<p>De exemplu, CloudFlare folose\u0219te propriul antet CF-Ray \u00een mesajele HTTP Response, care include indica\u021bia centrului de date la care a fost trimis\u0103 solicitarea. \u00cen cazul Zendesk, antetul CF-Ray pentru regiunea Seattle este CF-RAY: 2a21675e65fd2a3d-SEA, iar pentru Amsterdam este CF-RAY: 2a216896b93a0c71-AMS. Pentru a determina unde se afl\u0103 con\u021binutul, se pot utiliza de asemenea antetele HTTP-X din r\u0103spunsul HTTP.<\/p>\n<h2>Alte metode de adresare<\/h2>\n<p>\nExist\u0103 \u0219i alte metode de adresare pentru a ruteze cererile utilizatorilor c\u0103tre un anumit punct final al re\u021belei:<\/p>\n<p>Unicast<\/p>\n<p>Majoritatea internetului de ast\u0103zi utilizeaz\u0103 acest metod\u0103. Unicast este un tip de transmitere unidirec\u021bional\u0103, adresa IP este legat\u0103 doar de un anumit nod din re\u021bea. Acest lucru se nume\u0219te asociere unic\u0103.\u00a0<\/p>\n<p>Multicast<\/p>\n<p>Multicast folose\u0219te comunicarea \u201eunu la mul\u021bi din mul\u021bi\u201d sau \u201emul\u021bi la mul\u021bi\u201d. Distribu\u021bia multicast permite trimiterea cererilor de la expeditor simultan c\u0103tre diferite puncte finale selectate. Acest lucru ofer\u0103 clientului posibilitatea de a \u00eenc\u0103rca fi\u0219iere \u00een p\u0103r\u021bi de pe mai multe gazde simultan (ceea ce este util pentru streaming audio sau video). Multicast este adesea confundat cu Anycast, \u00eens\u0103 diferen\u021ba fundamental\u0103 const\u0103 \u00een faptul c\u0103 Anycast \u00eendrum\u0103 expeditorul c\u0103tre un anumit nod, chiar dac\u0103 mai multe noduri sunt disponibile.<\/p>\n<p>Broadcast<\/p>\n<p>Un pachet de date de la un singur expeditor este direc\u021bionat c\u0103tre toate punctele finale asociate cu o adres\u0103 de broadcast. Re\u021beaua replic\u0103 automat pachetele de date pentru a putea comunica cu to\u021bi destinatarii din difuzare (de obicei \u00eentr-o singur\u0103 subre\u021bea).<\/p>\n<p>Geocast<\/p>\n<p>Geocast este oarecum similar cu Multicast: cererile de la expeditor sunt direc\u021bionate simultan c\u0103tre mai multe puncte finale. Totu\u0219i, diferen\u021ba const\u0103 \u00een faptul c\u0103 destinatarul este definit de pozi\u021bia sa geografic\u0103. Aceasta este o form\u0103 specializat\u0103 de adresare de grup utilizat\u0103 de anumite protocoale de rutare pentru re\u021bele peer-to-peer mobile.<\/p>\n<p>Ruterul geografic (Geo Router) \u00ee\u0219i calculeaz\u0103 zona de serviciu \u0219i o aproximeaz\u0103. Ruterii geo, schimb\u00e2nd zonele de serviciu, construiesc tabele de rutare. Sistemul de rute geo are o structur\u0103 ierarhic\u0103.<\/p>\n<p><img decoding=\"async\" alt=\"Anycast versus Unicast: ce s\u0103 alegi \u00een fiecare caz\" src=\"\/wp-content\/uploads\/2020\/07\/fa98a1f0705bd754e1a9c8b479c834a7.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<img decoding=\"async\" alt=\"Anycast versus Unicast: ce s\u0103 alegi \u00een fiecare caz\" src=\"\/wp-content\/uploads\/2020\/07\/da36388f194ac565aba7b7661839ff6c.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<img decoding=\"async\" alt=\"Anycast versus Unicast: ce s\u0103 alegi \u00een fiecare caz\" src=\"\/wp-content\/uploads\/2020\/07\/16161b1bdc81867d8c8bba7bd084b7cf.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i>Unicast, Multicast \u0219i Broadcast.<\/i><\/p>\n<p>Utilizarea tehnologiei Anycast \u00eembun\u0103t\u0103\u021be\u0219te nivelul de fiabilitate, rezilien\u021b\u0103 \u0219i securitate al DNS-ului. Folosind aceast\u0103 tehnologie, operatorii ofer\u0103 clien\u021bilor lor servicii de tip load balancing bazate pe DNS. \u00cen panoul de control, pot fi specificate adrese IP c\u0103tre care vor fi trimise cererile, \u00een func\u021bie de localizarea geografic\u0103. Acest lucru va oferi clien\u021bilor posibilitatea de a distribui mai flexibil cererile utilizatorilor.<\/p>\n<p>Unii operatori aplic\u0103 instrumente de monitorizare a traseului la fiecare punct de prezen\u021b\u0103 (POP): sistemul analizeaz\u0103 automat cele mai scurte rute locale \u0219i globale pentru punctele de prezen\u021b\u0103 \u0219i le redirec\u021bioneaz\u0103 prin localiz\u0103ri geografice cu cea mai mic\u0103 laten\u021b\u0103 \u0219i timp de nefunc\u021bionare zero.<\/p>\n<p>\u00cen prezent, Anycast este cea mai stabil\u0103 \u0219i fiabil\u0103 solu\u021bie pentru construirea serviciilor DNS de mare \u00eenc\u0103rcare, care impun cerin\u021be ridicate de rezilien\u021b\u0103 \u0219i fiabilitate. <\/p>\n<p>Domeniul .ru suport\u0103 35 de servere Anycast DNS, grupate \u00een 20 de noduri, distribuite \u00een cinci cloud-uri Anycast. \u00cen acest caz, este utilizat principiul de construire pe baza caracteristicilor geografice, adic\u0103 Geocast. \u00cen amplasarea nodurilor DNS, se preconizeaz\u0103 distribuirea acestora \u00een loca\u021bii geografice disperse, apropiate de utilizatorii cei mai activi, cu o concentrare maxim\u0103 a furnizorilor ru\u0219i \u00een punctul de amplasare a nodului, precum \u0219i disponibilitatea de capacit\u0103\u021bi libere \u0219i u\u0219urin\u021ba interac\u021biunii cu platforma.<\/p>\n<h2>Cum s\u0103 construie\u0219ti un CDN?<\/h2>\n<p>\nCDN \u2014 re\u021bea de servere care accelereaz\u0103 livrarea con\u021binutului utilizatorilor.<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/ruvds\/blog\/503800\/\"> Re\u021beaua de livrare a con\u021binutului<\/a><\/noindex> \u00eenglobeaz\u0103 toate serverele \u00eentr-o singur\u0103 re\u021bea \u0219i asigur\u0103 o \u00eenc\u0103rcare mai rapid\u0103 a con\u021binutului. \u00cen viteza de \u00eenc\u0103rcare, distan\u021ba de la server la utilizator joac\u0103 un rol important.<\/p>\n<p>CDN permite utilizarea serverelor care sunt cele mai apropiate de publicul vizat. Acest lucru reduce timpul de a\u0219teptare, ajut\u0103 la accelerarea \u00eenc\u0103rc\u0103rii con\u021binutului site-urilor pentru to\u021bi vizitatorii, ceea ce este deosebit de critic pentru site-urile cu fi\u0219iere de mari dimensiuni sau servicii multimedia. Domeniile tipice de utilizare a CDN-ului includ comer\u021bul electronic \u0219i domeniul divertismentului.<\/p>\n<p>Re\u021beaua suplimentar\u0103 de servere creat\u0103 \u00een infrastructura CDN, care este amplasat\u0103 c\u00e2t mai aproape de utilizatori, contribuie la livrarea datelor mai stabil\u0103 \u0219i mai rapid\u0103. Conform statisticilor, utilizarea CDN reduce laten\u021ba la accesarea site-ului cu mai mult de 70% comparativ cu site-urile f\u0103r\u0103 CDN.<\/p>\n<p>Cum<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/ruvds\/blog\/466447\/\"> a crea un CDN folosind DNS<\/a><\/noindex>? \u041d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0430 CDN \u0441 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043d\u0438\u0435\u043c \u0441\u043e\u0431\u0441\u0442\u0432\u0435\u043d\u043d\u043e\u0433\u043e \u0440\u0435\u0448\u0435\u043d\u0438\u044f Anycast \u043c\u043e\u0436\u0435\u0442 \u0431\u044b\u0442\u044c \u0434\u043e\u0441\u0442\u0430\u0442\u043e\u0447\u043d\u043e \u0434\u043e\u0440\u043e\u0433\u0438\u043c \u043f\u0440\u043e\u0435\u043a\u0442\u043e\u043c, \u043d\u043e \u0435\u0441\u0442\u044c \u0431\u043e\u043b\u0435\u0435 \u0434\u0435\u0448\u0435\u0432\u044b\u0435 \u0432\u0430\u0440\u0438\u0430\u043d\u0442\u044b. \u041d\u0430\u043f\u0440\u0438\u043c\u0435\u0440, \u043c\u043e\u0436\u043d\u043e \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c GeoDNS \u0438 \u043e\u0431\u044b\u0447\u043d\u044b\u0435 \u0441\u0435\u0440\u0432\u0435\u0440\u044b \u0441 \u0443\u043d\u0438\u043a\u0430\u043b\u044c\u043d\u044b\u043c\u0438 IP-\u0430\u0434\u0440\u0435\u0441\u0430\u043c\u0438. \u0421 \u043f\u043e\u043c\u043e\u0449\u044c\u044e \u0441\u0435\u0440\u0432\u0438\u0441\u043e\u0432 GeoDNS \u043c\u043e\u0436\u043d\u043e \u0441\u043e\u0437\u0434\u0430\u0442\u044c CDN \u0441 \u0444\u0443\u043d\u043a\u0446\u0438\u044f\u043c\u0438 \u0433\u0435\u043e\u043b\u043e\u043a\u0430\u0446\u0438\u0438, \u0432 \u043a\u043e\u0442\u043e\u0440\u043e\u0439 \u0440\u0435\u0448\u0435\u043d\u0438\u044f \u043f\u0440\u0438\u043d\u0438\u043c\u0430\u044e\u0442\u0441\u044f \u043d\u0430 \u043e\u0441\u043d\u043e\u0432\u0435 \u0440\u0435\u0430\u043b\u044c\u043d\u043e\u0433\u043e \u043c\u0435\u0441\u0442\u043e\u043f\u043e\u043b\u043e\u0436\u0435\u043d\u0438\u044f \u043f\u043e\u0441\u0435\u0442\u0438\u0442\u0435\u043b\u044f, \u0430 \u043d\u0435 \u043c\u0435\u0441\u0442\u043e\u043f\u043e\u043b\u043e\u0436\u0435\u043d\u0438\u044f \u0440\u0435\u0441\u043e\u043b\u0432\u0435\u0440\u0430 DNS. \u041c\u043e\u0436\u043d\u043e \u043d\u0430\u0441\u0442\u0440\u043e\u0438\u0442\u044c \u0441\u0432\u043e\u044e DNS-\u0437\u043e\u043d\u0443 \u0442\u0430\u043a, \u0447\u0442\u043e\u0431\u044b \u043f\u043e\u043a\u0430\u0437\u044b\u0432\u0430\u0442\u044c IP-\u0430\u0434\u0440\u0435\u0441\u0430 \u0430\u043c\u0435\u0440\u0438\u043a\u0430\u043d\u0441\u043a\u0438\u0445 \u0441\u0435\u0440\u0432\u0435\u0440\u043e\u0432 \u043f\u043e\u0441\u0435\u0442\u0438\u0442\u0435\u043b\u044f\u043c \u0438\u0437 \u0421\u0428\u0410, \u0430 \u0435\u0432\u0440\u043e\u043f\u0435\u0439\u0441\u043a\u0438\u0435 \u043f\u043e\u0441\u0435\u0442\u0438\u0442\u0435\u043b\u0438 \u0431\u0443\u0434\u0443\u0442 \u0432\u0438\u0434\u0435\u0442\u044c IP-\u0430\u0434\u0440\u0435\u0441 \u0438\u0437 \u0415\u0432\u0440\u043e\u043f\u044b.<\/p>\n<p>Folosind GeoDNS, este posibil s\u0103 returnezi r\u0103spunsuri DNS diferite \u00een func\u021bie de adresa IP a utilizatorului. Pentru aceasta, serverul DNS este configurat astfel \u00eenc\u00e2t s\u0103 returneze adrese IP diferite \u00een func\u021bie de adresa IP ini\u021bial\u0103 din cerere. De obicei, pentru a determina regiunea din care se face cererea, se utilizeaz\u0103 o baz\u0103 de date GeoIP. Geoloca\u021bia utiliz\u00e2nd DNS permite livrarea con\u021binutului utilizatorilor din cel mai apropiat site.<\/p>\n<p>GeoDNS determin\u0103 adresa IP a clientului care a trimis cererea DNS sau a serverului DNS recursiv al furnizorului utilizat pentru procesarea cererii clientului. Pe baza adresei IP a clientului \u0219i a bazei GeoIP se determin\u0103 \u021bara\/regiunea. Apoi, clientul prime\u0219te adresa IP a celui mai apropiat server CDN. Despre configurarea GeoDNS se poate citi mai \u00een detaliu.<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/178727\/\"> aici<\/a><\/noindex>.<\/p>\n<h2>Anycast sau GeoDNS?<\/h2>\n<p>\nDe\u0219i Anycast este o modalitate excelent\u0103 de livrare a con\u021binutului la nivel global, \u00eei lipse\u0219te specificitatea. Aici intervine GeoDNS. Acest serviciu permite crearea de reguli care direc\u021bioneaz\u0103 utilizatorii c\u0103tre puncte finale unice \u00een func\u021bie de loca\u021bia lor.<\/p>\n<p><img decoding=\"async\" alt=\"Anycast versus Unicast: ce s\u0103 alegi \u00een fiecare caz\" src=\"\/wp-content\/uploads\/2020\/07\/05c9d6752ba196f90bfefe6091075b23.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i>Exemplu: utilizatorii din Europa sunt \u00eendrepta\u021bi c\u0103tre un alt punct final.<\/i><\/p>\n<p>De asemenea, se poate interzice accesul la domenii prin respingerea tuturor cererilor. Acesta este, \u00een special, un mod rapid de a izola atacatorii.<\/p>\n<p>GeoDNS ofer\u0103 r\u0103spunsuri mai precise dec\u00e2t Anycast. Dac\u0103 \u00een cazul Anycast cel mai scurt traseu este determinat prin num\u0103rul de hop-uri, \u00een GeoDNS rutarea pentru utilizatorii finali se face \u00een func\u021bie de loca\u021bia lor fizic\u0103. Acest lucru reduce laten\u021ba \u0219i cre\u0219te precizia \u00een crearea regulilor de rutare granular\u0103. <\/p>\n<p>Atunci c\u00e2nd se acceseaz\u0103 un domeniu, browserul se adreseaz\u0103 celui mai apropiat server DNS, care, \u00een func\u021bie de domeniu, va returna adresa IP pentru \u00eenc\u0103rcarea site-ului. S\u0103 presupunem c\u0103 un magazin online este popular \u00een SUA \u0219i Europa, iar serverele DNS pentru acesta exist\u0103 doar \u00een Europa. Atunci utilizatorii din SUA care doresc s\u0103 foloseasc\u0103 serviciile magazinului vor fi nevoi\u021bi s\u0103 trimit\u0103 cereri c\u0103tre cel mai apropiat server, iar deoarece acesta se afl\u0103 foarte departe, a\u0219teptarea r\u0103spunsului va dura mult \u2014 \u00eenc\u0103rcarea site-ului nu va fi rapid\u0103.<\/p>\n<p>Asez\u00e2nd un server GeoDNS \u00een SUA, utilizatorii se vor adresa deja acestuia. R\u0103spunsul va fi rapid, ceea ce va afecta viteza de \u00eenc\u0103rcare a site-ului.<\/p>\n<p>\u00cen situa\u021bia cu un server DNS existent \u00een SUA, atunci c\u00e2nd un utilizator din SUA acceseaz\u0103 acest domeniu, acesta se va adresa celui mai apropiat server care va returna IP-ul necesar. Utilizatorul va fi direc\u021bionat c\u0103tre un server care con\u021bine con\u021binutul site-ului, dar deoarece serverele cu con\u021binutul sunt departe, el nu \u00eel va primi rapid.<\/p>\n<p>Dac\u0103 g\u0103zduie\u0219ti \u00een SUA \u0219i servere CDN cu date \u00een cache, atunci c\u00e2nd un browser client \u00eencarc\u0103, acesta va trimite o solicitare c\u0103tre serverul DNS cel mai apropiat, care va returna adresa IP necesar\u0103. Browserul cu IP-ul ob\u021binut se adreseaz\u0103 celui mai apropiat server CDN \u0219i serverului principal, iar serverul CDN transmite browserului con\u021binutul \u00een cache. \u00cen timp ce se \u00eencarc\u0103 con\u021binutul \u00een cache, de pe serverul principal vin fi\u0219ierele lips\u0103 pentru a completa \u00eenc\u0103rcarea site-ului. Ca rezultat, timpul de \u00eenc\u0103rcare al site-ului scade, deoarece se trimit mult mai pu\u021bine fi\u0219iere de pe serverul principal. <\/p>\n<p>Determinarea loca\u021biei exacte a unei adrese IP nu este \u00eentotdeauna o sarcin\u0103 u\u0219oar\u0103: multe factori ac\u021bioneaz\u0103 aici, iar proprietarii de interven\u021bii IP pot decide s\u0103 declare aceast\u0103 adres\u0103 pe cel\u0103lalt cap\u0103t al lumii (atunci va trebui s\u0103 a\u0219tep\u021bi p\u00e2n\u0103 c\u00e2nd baza de date se actualizeaz\u0103 pentru a ob\u021bine loca\u021bia corect\u0103). Uneori, furnizorii de VPS aloc\u0103 adrese care, \u00een teorie, se afl\u0103 \u00een SUA, pentru VPS-uri \u00een Singapore.<\/p>\n<p>Spre deosebire de utilizarea adreselor Anycast, distribu\u021bia se face \u00een timpul rezolv\u0103rii numelui, nu \u00een timpul conect\u0103rii la serverul de cache. Dac\u0103 serverul recursiv nu suport\u0103 subre\u021belele clientului EDNS, se folose\u0219te loca\u021bia acestui server recursiv, nu a utilizatorului care se va conecta la serverul de cache.<\/p>\n<p>Subre\u021belele clientului \u00een DNS sunt o extensie DNS (RFC7871) care define\u0219te cum serverele DNS recursiv\u0103 pot trimite informa\u021bii despre client c\u0103tre un server DNS, \u00een special informa\u021bii despre re\u021bea, pe care serverul GeoDNS le poate folosi pentru a determina mai precis loca\u021bia clientului.<\/p>\n<p>Majoritatea oamenilor folosesc serverele DNS ale furnizorului lor de internet sau servere DNS care sunt geografic apropiate de ei, dar dac\u0103 cineva din SUA dintr-un anumit motiv decide s\u0103 foloseasc\u0103 un resolver DNS situat \u00een Australia, este foarte probabil s\u0103 primeasc\u0103 adresa IP a celui mai apropiat server din Australia. <\/p>\n<p>Dac\u0103 dore\u0219ti s\u0103 folose\u0219ti GeoDNS, este important s\u0103 \u0219tii despre aceste particularit\u0103\u021bi, deoarece \u00een unele cazuri acest lucru poate m\u0103ri distan\u021ba dintre serverele de cache \u0219i client.<\/p>\n<p>Rezumat: dac\u0103 dore\u0219ti s\u0103 integrezi mai multe VPS-uri \u00eentr-un CDN, cea mai bun\u0103 op\u021biune de desf\u0103\u0219urare este utilizarea unui server DNS cu func\u021bia GeoDNS + Anycast \"din cutie\".<\/p>\n<p><noindex><a rel=\"nofollow\" href=\"http:\/\/ruvds.com\/ru-rub?utm_source=habr&amp;utm_medium=article&amp;utm_campaign=caplin&amp;utm_content=anycastvsunicast#order\"><img decoding=\"async\" alt=\"Anycast versus Unicast: ce s\u0103 alegi \u00een fiecare caz\" src=\"\/wp-content\/uploads\/2020\/07\/73c6b0732883a352ddd9096804f2e533.png\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><br \/>\n<br \/>Sursa: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/ruvds\/blog\/511050\/\">habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u041f\u0440\u043e Anycast \u043d\u0430\u0432\u0435\u0440\u043d\u044f\u043a\u0430 \u043c\u043d\u043e\u0433\u0438\u0435 \u0441\u043b\u044b\u0448\u0430\u043b\u0438. \u041f\u0440\u0438 \u044d\u0442\u043e\u043c \u043c\u0435\u0442\u043e\u0434\u0435 \u0441\u0435\u0442\u0435\u0432\u043e\u0439 \u0430\u0434\u0440\u0435\u0441\u0430\u0446\u0438\u0438 \u0438 \u043c\u0430\u0440\u0448\u0440\u0443\u0442\u0438\u0437\u0430\u0446\u0438\u0438 \u043e\u0434\u0438\u043d IP-\u0430\u0434\u0440\u0435\u0441 \u043f\u0440\u0438\u0441\u0432\u0430\u0438\u0432\u0430\u0435\u0442\u0441\u044f \u043d\u0435\u0441\u043a\u043e\u043b\u044c\u043a\u0438\u043c \u0441\u0435\u0440\u0432\u0435\u0440\u0430\u043c \u0432 \u0441\u0435\u0442\u0438. \u042d\u0442\u0438 \u0441\u0435\u0440\u0432\u0435\u0440\u044b \u043c\u043e\u0433\u0443\u0442 \u043d\u0430\u0445\u043e\u0434\u0438\u0442\u044c\u0441\u044f \u0434\u0430\u0436\u0435 \u0432 \u0443\u0434\u0430\u043b\u0435\u043d\u043d\u044b\u0445 \u0434\u0440\u0443\u0433 \u043e\u0442 \u0434\u0440\u0443\u0433\u0430 \u0426\u041e\u0414. \u0418\u0434\u0435\u044f Anycast \u0432 \u0442\u043e\u043c, \u0447\u0442\u043e, \u0432 \u0437\u0430\u0432\u0438\u0441\u0438\u043c\u043e\u0441\u0442\u0438 \u043e\u0442 \u043c\u0435\u0441\u0442\u043e\u043f\u043e\u043b\u043e\u0436\u0435\u043d\u0438\u044f \u0438\u0441\u0442\u043e\u0447\u043d\u0438\u043a\u0430 \u0437\u0430\u043f\u0440\u043e\u0441\u043e\u0432, \u0434\u0430\u043d\u043d\u044b\u0435 \u043e\u0442\u043f\u0440\u0430\u0432\u043b\u044f\u044e\u0442\u0441\u044f \u043d\u0430 \u0431\u043b\u0438\u0436\u0430\u0439\u0448\u0438\u0439 (\u0441\u043e\u0433\u043b\u0430\u0441\u043d\u043e \u0442\u043e\u043f\u043e\u043b\u043e\u0433\u0438\u0438 \u0441\u0435\u0442\u0438, \u0442\u043e\u0447\u043d\u0435\u0435 \u2014 \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u0430 \u043c\u0430\u0440\u0448\u0440\u0443\u0442\u0438\u0437\u0430\u0446\u0438\u0438 BGP) \u0441\u0435\u0440\u0432\u0435\u0440. \u0422\u0430\u043a\u0438\u043c [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":88962,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-88961","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.2.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u041f\u0440\u043e Anycast \u043d\u0430\u0432\u0435\u0440\u043d\u044f\u043a\u0430 \u043c\u043d\u043e\u0433\u0438\u0435 \u0441\u043b\u044b\u0448\u0430\u043b\u0438. \u041f\u0440\u0438 \u044d\u0442\u043e\u043c \u043c\u0435\u0442\u043e\u0434\u0435 \u0441\u0435\u0442\u0435\u0432\u043e\u0439 \u0430\u0434\u0440\u0435\u0441\u0430\u0446\u0438\u0438 \u0438 \u043c\u0430\u0440\u0448\u0440\u0443\u0442\u0438\u0437\u0430\u0446\u0438\u0438 \u043e\u0434\u0438\u043d IP-\u0430\u0434\u0440\u0435\u0441 \u043f\u0440\u0438\u0441\u0432\u0430\u0438\u0432\u0430\u0435\u0442\u0441\u044f \u043d\u0435\u0441\u043a\u043e\u043b\u044c\u043a\u0438\u043c \u0441\u0435\u0440\u0432\u0435\u0440\u0430\u043c \u0432 \u0441\u0435\u0442\u0438. \u042d\u0442\u0438 \u0441\u0435\u0440\u0432\u0435\u0440\u044b \u043c\u043e\u0433\u0443\u0442 \u043d\u0430\u0445\u043e\u0434\u0438\u0442\u044c\u0441\u044f \u0434\u0430\u0436\u0435 \u0432 \u0443\u0434\u0430\u043b\u0435\u043d\u043d\u044b\u0445 \u0434\u0440\u0443\u0433 \u043e\u0442 \u0434\u0440\u0443\u0433\u0430 \u0426\u041e\u0414.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/anycast-protiv-unicast-chto-luchshe-vybirat-v-kazhdom-sluchae\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.2.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"ro_RO\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47Anycast \u043f\u0440\u043e\u0442\u0438\u0432 Unicast: \u0447\u0442\u043e \u043b\u0443\u0447\u0448\u0435 \u0432\u044b\u0431\u0438\u0440\u0430\u0442\u044c \u0432 \u043a\u0430\u0436\u0434\u043e\u043c \u0441\u043b\u0443\u0447\u0430\u0435 | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u041f\u0440\u043e Anycast \u043d\u0430\u0432\u0435\u0440\u043d\u044f\u043a\u0430 \u043c\u043d\u043e\u0433\u0438\u0435 \u0441\u043b\u044b\u0448\u0430\u043b\u0438. \u041f\u0440\u0438 \u044d\u0442\u043e\u043c \u043c\u0435\u0442\u043e\u0434\u0435 \u0441\u0435\u0442\u0435\u0432\u043e\u0439 \u0430\u0434\u0440\u0435\u0441\u0430\u0446\u0438\u0438 \u0438 \u043c\u0430\u0440\u0448\u0440\u0443\u0442\u0438\u0437\u0430\u0446\u0438\u0438 \u043e\u0434\u0438\u043d IP-\u0430\u0434\u0440\u0435\u0441 \u043f\u0440\u0438\u0441\u0432\u0430\u0438\u0432\u0430\u0435\u0442\u0441\u044f \u043d\u0435\u0441\u043a\u043e\u043b\u044c\u043a\u0438\u043c \u0441\u0435\u0440\u0432\u0435\u0440\u0430\u043c \u0432 \u0441\u0435\u0442\u0438. \u042d\u0442\u0438 \u0441\u0435\u0440\u0432\u0435\u0440\u044b \u043c\u043e\u0433\u0443\u0442 \u043d\u0430\u0445\u043e\u0434\u0438\u0442\u044c\u0441\u044f \u0434\u0430\u0436\u0435 \u0432 \u0443\u0434\u0430\u043b\u0435\u043d\u043d\u044b\u0445 \u0434\u0440\u0443\u0433 \u043e\u0442 \u0434\u0440\u0443\u0433\u0430 \u0426\u041e\u0414.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/anycast-protiv-unicast-chto-luchshe-vybirat-v-kazhdom-sluchae\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2020-07-16T17:42:34+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-07-16T17:42:34+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47Anycast vs Unicast: ce s\u0103 alegi \u00een fiecare caz | ProHoster","description":"Despre Anycast se \u0219tie cu siguran\u021b\u0103. Prin aceast\u0103 metod\u0103 de adresare \u0219i rutare de re\u021bea, o adres\u0103 IP este alocat\u0103 mai multor servere din re\u021bea. Aceste servere pot fi, de fapt, situate la distan\u021be mari unele de altele \u00een centre de date.","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/anycast-protiv-unicast-chto-luchshe-vybirat-v-kazhdom-sluchae","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"ro_RO","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47Anycast \u043f\u0440\u043e\u0442\u0438\u0432 Unicast: \u0447\u0442\u043e \u043b\u0443\u0447\u0448\u0435 \u0432\u044b\u0431\u0438\u0440\u0430\u0442\u044c \u0432 \u043a\u0430\u0436\u0434\u043e\u043c \u0441\u043b\u0443\u0447\u0430\u0435 | ProHoster","og:description":"\u041f\u0440\u043e Anycast \u043d\u0430\u0432\u0435\u0440\u043d\u044f\u043a\u0430 \u043c\u043d\u043e\u0433\u0438\u0435 \u0441\u043b\u044b\u0448\u0430\u043b\u0438. \u041f\u0440\u0438 \u044d\u0442\u043e\u043c \u043c\u0435\u0442\u043e\u0434\u0435 \u0441\u0435\u0442\u0435\u0432\u043e\u0439 \u0430\u0434\u0440\u0435\u0441\u0430\u0446\u0438\u0438 \u0438 \u043c\u0430\u0440\u0448\u0440\u0443\u0442\u0438\u0437\u0430\u0446\u0438\u0438 \u043e\u0434\u0438\u043d IP-\u0430\u0434\u0440\u0435\u0441 \u043f\u0440\u0438\u0441\u0432\u0430\u0438\u0432\u0430\u0435\u0442\u0441\u044f \u043d\u0435\u0441\u043a\u043e\u043b\u044c\u043a\u0438\u043c \u0441\u0435\u0440\u0432\u0435\u0440\u0430\u043c \u0432 \u0441\u0435\u0442\u0438. \u042d\u0442\u0438 \u0441\u0435\u0440\u0432\u0435\u0440\u044b \u043c\u043e\u0433\u0443\u0442 \u043d\u0430\u0445\u043e\u0434\u0438\u0442\u044c\u0441\u044f \u0434\u0430\u0436\u0435 \u0432 \u0443\u0434\u0430\u043b\u0435\u043d\u043d\u044b\u0445 \u0434\u0440\u0443\u0433 \u043e\u0442 \u0434\u0440\u0443\u0433\u0430 \u0426\u041e\u0414.","og:url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/anycast-protiv-unicast-chto-luchshe-vybirat-v-kazhdom-sluchae","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2020-07-16T17:42:34+00:00","article:modified_time":"2020-07-16T17:42:34+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"88961","title":null,"description":null,"keywords":null,"keyphrases":{"focus":[],"additional":[]},"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 13:19:34","updated":"2026-08-11 12:50:13","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/88961","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/comments?post=88961"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/88961\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media\/88962"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=88961"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=88961"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=88961"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}