{"id":84900,"date":"2020-06-11T13:43:28","date_gmt":"2020-06-11T11:43:28","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/prostoj-failover-dlya-vebsajta-monitoring-dinamicheskij-dns"},"modified":"2020-06-11T13:43:28","modified_gmt":"2020-06-11T11:43:28","slug":"prostoj-failover-dlya-vebsajta-monitoring-dinamicheskij-dns","status":"publish","type":"post","link":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/prostoj-failover-dlya-vebsajta-monitoring-dinamicheskij-dns","title":{"rendered":"Failover simplu pentru site web (monitorizare + DNS dinamic)","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>\u00cen acest articol, vreau s\u0103 ar\u0103t c\u00e2t de u\u0219or \u0219i gratuit se poate crea un sistem de failover pentru un website (sau orice alt serviciu online) folosind o combina\u021bie de monitorizare <noindex><a rel=\"nofollow\" href=\"https:\/\/okerr.com\/\">okerr<\/a><\/noindex> \u0219i un serviciu DNS dinamic. Adic\u0103, \u00een cazul \u00een care apar probleme cu site-ul principal (de la erori \u00abPHP\u00bb pe pagin\u0103 p\u00e2n\u0103 la lipsa de spa\u021biu sau pur \u0219i simplu un num\u0103r suspect de mic de comenzi \u00een cazul unui magazin online), noii vizitatori vor fi redirec\u021biona\u021bi c\u0103tre un server secundar (ter\u021b, etc.) care func\u021bioneaz\u0103, sau chiar pe o pagin\u0103 \u00abNe pare r\u0103u\u00bb, unde li se va explica politicos c\u0103 \u00abexist\u0103 o problem\u0103, suntem la curent \u0219i lucr\u0103m pentru a o remedia, va fi rezolvat\u0103 \u00een cur\u00e2nd\u00bb (iar \u00een acest caz, de fapt, ve\u021bi fi deja la curent \u0219i ve\u021bi putea remedia problema).<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h2>S\u0103 tr\u0103ie\u0219ti cu failover sau f\u0103r\u0103?<\/h2>\n<p>\nP\u00e2n\u0103 nu apare o problem\u0103, nu exist\u0103 o mare diferen\u021b\u0103. Dar c\u00e2nd apare, f\u0103r\u0103 failover, se \u00eent\u00e2mpl\u0103 adesea urm\u0103toarele: \u00eencerci s\u0103 \u00een\u021belegi rapid care este problema, dar nu reu\u0219e\u0219ti (backup-urile nu se desf\u0103\u0219oar\u0103, software-ul nu func\u021bioneaz\u0103 cum ar trebui conform documenta\u021biei etc.), iar timpul nu este suficient, serverele\/site-urile sunt c\u0103zute, clien\u021bii sun\u0103, toat\u0103 lumea este nervoas\u0103 \u0219i \u00eencerci cumva s\u0103 repari totul \u00een grab\u0103 \u0219i \u00eentr-un mod neglijent, apoi cumva, pare c\u0103 se reporne\u0219te cu solu\u021bii improvizate \u0219i mai tr\u0103ie\u0219te. Crezi c\u0103 \u00eentr-o zi ar trebui s\u0103 te ocupi mai \u00een detaliu \u0219i s\u0103 refaci totul frumos, dar nu exist\u0103 nimic mai permanent dec\u00e2t solu\u021biile temporare.<\/p>\n<p>Acum, cum se \u00eent\u00e2mpl\u0103 acest lucru \u00een varianta elegant\u0103 cu failover:<\/p>\n<ul>\n<li>Se produce o eroare<\/li>\n<li>Eroarea este detectat\u0103 automat<\/li>\n<li>Se trimite o notificare<\/li>\n<li>Se realizeaz\u0103 comutarea pe unul dintre serverele de rezerv\u0103<\/li>\n<li>Problema este analizat\u0103 lini\u0219tit \u0219i f\u0103r\u0103 panic\u0103, se repar\u0103 \u0219i serverul este repus \u00een func\u021biune.<\/li>\n<\/ul>\n<p>\n\u00cen acest sistem, bine\u00een\u021beles, pot ap\u0103rea unele blocaje, dar totu\u0219i, schema este linear\u0103, fiecare pas este simplu \u0219i, cel mai important, poate fi testat separat, astfel c\u0103 \u0219ansa de e\u0219ec a acestui sistem este mult mai mic\u0103, iar toate ac\u021biunile pot fi automatizate \u0219i executate rapid (spre deosebire de sarcina de a g\u0103si \u0219i remedia o problem\u0103 epic\u0103 necunoscut\u0103). Aeronava ta a aterizat \u00eentr-o \u021bar\u0103 \u00eendep\u0103rtat\u0103, \u00ee\u021bi porne\u0219ti telefonul \u0219i vezi \u00een Telegram o notificare c\u0103 serverul a c\u0103zut, dar totul este bine, serverul de rezerv\u0103 a fost activat, po\u021bi continua c\u0103l\u0103toria, nu trebuie s\u0103 te \u00eentorci \u00eenapoi sau s\u0103 repari prin SSH din cea mai apropiat\u0103 cafenea cu WiFi. Te vei ocupa de asta c\u00e2nd \u00ee\u021bi va fi convenabil.<\/p>\n<h2>Viitorul este deja aici!<\/h2>\n<p>\n\u00cen trecut, principala problem\u0103 care f\u0103cea ca failover-ul s\u0103 fie adesea o solu\u021bie inacceptabil\u0103 era suma costurilor implicate. Fie era necesar s\u0103 achizi\u021bionezi echipamente scumpe (\u0219i s\u0103 angajezi speciali\u0219ti \u0219i mai scumpi). Fie era nevoie de solu\u021bii complicate pe baza unor ghiduri (am \u00eent\u00e2lnit chiar op\u021biuni \u00een care dou\u0103 servere erau legate printr-un cablu null-modem \u0219i trimiteau heartbeat pe acesta, pentru ca la momentul potrivit serverul de rezerv\u0103 s\u0103 \u0219tie \u0219i s\u0103 preia controlul). Acum exist\u0103 metode mai simple \u0219i gratuite. Dac\u0103 ai un site cu pisici \u2014 nu ai nicio scuz\u0103 dac\u0103 \u00eenc\u0103 nu ai implementat failover pentru el!<\/p>\n<p>\u00cen plus, pentru schema de failover este nevoie de un server (sau poate chiar de mai multe) \u0219i, \u00een trecut, acest lucru a implicat costuri mari, dar acum po\u021bi ob\u021bine un VDS la un pre\u021b mic.<\/p>\n<h2>Cel mai fiabil site cu pisici<\/h2>\n<p>\nPentru a ilustra practic solu\u021bia cu okerr + dynamic dns, am lansat propriul nostru site cu pisici <noindex><a rel=\"nofollow\" href=\"https:\/\/cat.okerr.com\/\">cat.okerr.com<\/a><\/noindex>. Detest\u0103m pisicile, a\u0219a c\u0103 acolo nu vor fi aproape deloc. Exist\u0103 trei site-uri, fiecare arat\u0103 aproximativ la fel (toate pe acela\u0219i \u0219ablon), dar cu pisici diferite pentru a fi u\u0219or de distins, iar fiecare ofer\u0103 informa\u021bii tehnice pentru a vedea cum func\u021bioneaz\u0103 failover-ul. Pagina se actualizeaz\u0103 automat la fiecare minut, dar po\u021bi s\u0103 dai mereu refresh \u00een browser.<\/p>\n<p>Informa\u021biile tehnice con\u021bin r\u00e2ndul \u201cstatus=OK\u201d. Uneori, serverele simuleaz\u0103 probleme \u0219i scriu status=ERR. Serverul principal \u201ecade\u201d la fiecare 20 de minute ale fiec\u0103rei ore (0:20, 1:20, 2:20, ...). Serverul de rezerv\u0103 (backup) la 40 de minute. Ultimul server (\u201csorry\u201d-server) func\u021bioneaz\u0103 mereu. La 0 minute ale fiec\u0103rei ore, serverul principal \u0219i cel de rezerv\u0103 \u201ese restabilesc\u201d.<\/p>\n<p><img decoding=\"async\" alt=\"Failover simplu pentru site web (monitorizare + DNS dinamic)\" src=\"\/wp-content\/uploads\/2020\/06\/5bc603b6379cc5a745a65d3316c4ad3b.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nDac\u0103 deschizi site-ul \u0219i \u00eel la\u0219i deschis \u00een tab-ul t\u0103u \u2014 vei observa c\u0103 nu se pr\u0103bu\u0219e\u0219te niciodat\u0103 (de\u0219i fiecare server simuleaz\u0103 periodic o problem\u0103), iar \u00een cazul unei probleme cu serverul, pur \u0219i simplu \u201ezbura\u201d \u00eentre serverele active. Se va schimba imaginea, numele \u0219i adresa serverului \u0219i rolul s\u0103u. Uneori po\u021bi surprinde momentul c\u00e2nd status=ERR (problema deja exist\u0103, dar \u00eentreaga schem\u0103 de failover nu a ac\u021bionat \u00eenc\u0103), dar urm\u0103toarea actualizare \u00ee\u021bi va ar\u0103ta pagina de pe serverul activ. <\/p>\n<h2>Failover pe okerr + dynamic DNS<\/h2>\n<p>\nS\u0103 vedem cum este acesta organizat \u00een interior. Sarcina sistemului de failover este ca adresa cat.okerr.com s\u0103 indice \u00eentotdeauna spre adresa IP a serverului activ.<br \/>\nFiecare server care sus\u021bine site-ul nostru de pisici \u00een okerr are un indicator care verific\u0103 starea sa o dat\u0103 pe minut.<\/p>\n<p><img decoding=\"async\" alt=\"Failover simplu pentru site web (monitorizare + DNS dinamic)\" src=\"\/wp-content\/uploads\/2020\/06\/cdb81e84a7f5dd8cb14ea6844517cd55.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n\u00cen aceast\u0103 captur\u0103 de ecran, vedem cum site-ul cat.okerr.com este verificat de serverul alpha.okerr.com. Pagina ar trebui s\u0103 con\u021bin\u0103 status=OK, iar a\u0219a cum observ\u0103m mai sus, starea indicatorului nostru este acum OK. C\u00e2nd serverul \u201ese stric\u0103\u201d, va ap\u0103rea ERR. (Acesta este doar un exemplu de indicator, okerr este un serviciu de monitorizare, a\u0219adar se poate folosi orice tip de indicator, de exemplu, pentru a verifica spa\u021biul liber pe disc, num\u0103rul de comenzi noi \u00een baz\u0103, \u0219i chiar indicatori logici, cum ar fi, noaptea, vor exista anumite criterii de eroare, iar ziua, altele).<\/p>\n<p>\u00cen set\u0103rile proiectului, am creat un sistem de failover cu ace\u0219ti indicatori:<\/p>\n<p><img decoding=\"async\" alt=\"Failover simplu pentru site web (monitorizare + DNS dinamic)\" src=\"\/wp-content\/uploads\/2020\/06\/9670b496b8f01bdcce6e4b472b3ec37e.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n\u00cen schema sunt trei indicatori (trei servere), diferite ca priorit\u0103\u021bi. Serverul principal pentru site este charlie; dac\u0103 acesta nu func\u021bioneaz\u0103 (nu va avea \u201estatus=OK\u201d sau este pur \u0219i simplu inaccesibil), atunci va interveni bravo \u0219i, \u00een cele din urm\u0103, alpha. \u00cen partea dreapt\u0103 a paginii se arat\u0103 starea \u00eenregistr\u0103rii DNS pe diferite servere.<\/p>\n<p>Pentru cei care au observat c\u0103 utiliz\u0103m numele cat.he.okerr.com: Folosim o schem\u0103 pu\u021bin mai complicat\u0103. \u00cen loc s\u0103 modific\u0103m pur \u0219i simplu \u00eenregistrarea DNS cat.okerr.com, modific\u0103m cat.he.okerr.com (la un provider de Dynamic DNS <noindex><a rel=\"nofollow\" href=\"http:\/\/he.net\/\">Hurricane Electric<\/a><\/noindex>), iar cat.okerr.com este un CNAME (alias) care nu se schimb\u0103, indic\u00e2nd \u00eentotdeauna c\u0103tre cat.he.okerr.com. Ne place mai mult Hurricane ca provider de DNS dinamic \u0219i are chei pentru gestionarea unei \u00eenregistr\u0103ri separate (nu a \u00eentregii zone); ni se pare mai sigur. Pute\u021bi, de asemenea, s\u0103 nu specifica\u021bi \u00een okerr parolele-cheie pentru gestionarea \u00eentregului domeniu, ci doar pentru subdomeniu sau \u00eenregistrare.<\/p>\n<h2>De la c\u0103dere la ridicare<\/h2>\n<p>\nPa\u0219ii prin care func\u021bioneaz\u0103 aceast\u0103 schem\u0103:<\/p>\n<ol>\n<li>Se \u00eent\u00e2mpl\u0103 (se simuleaz\u0103) o problem\u0103 pe server<\/li>\n<li>Senzorul okerr verific\u0103 o dat\u0103 pe minut starea fiec\u0103rui server \u0219i raporteaz\u0103 pe serverul principal al proiectului \u00een okerr<\/li>\n<li>Indicatorul serverului corespunz\u0103tor \u00ee\u0219i schimb\u0103 starea de la OK la ERR<\/li>\n<li>La schimbarea st\u0103rii indicatorului, se recalculeaz\u0103 failover-ul, se determin\u0103 ce adres\u0103 trebuie setat\u0103 (dac\u0103 este necesar. De exemplu, dac\u0103 serverul principal func\u021bioneaz\u0103, iar \u00een acest timp serverul de rezerv\u0103 a c\u0103zut \u2014 nu vor avea loc modific\u0103ri)<\/li>\n<li>Aceast\u0103 adres\u0103 este comunicat\u0103 serviciului de dynamic dns. La finalizarea acestei etape, \u00een partea dreapt\u0103 ve\u021bi vedea starea \u201esynced\u201d<\/li>\n<li>Foarte cur\u00e2nd (\u00een c\u00e2teva secunde), \u00eenregistrarea va ajunge la serverele DNS ale domeniului dumneavoastr\u0103 (pentru site-ul nostru de pisici, acestea sunt ns1-ns5.he.net).<\/li>\n<li>\u00cencep\u00e2nd cu acest moment, unii utilizatori vor accesa deja noul server live. \u00cens\u0103 nu toate serverele DNS din lume au actualizat \u00eenregistr\u0103rile, iar unele pot avea \u00eenc\u0103 vechea \u00eenregistrare \u00een cache. Se poate observa cum datele de pe serverele DNS publice \u201edansaz\u0103\u201d, ar\u0103t\u00e2nd alternativ valoarea nou\u0103 \u0219i cea veche. Dac\u0103 re\u00eemprosp\u0103ta\u021bi pagina de set\u0103ri pentru failover, okerr va solicita noi date de la serverele DNS.<\/li>\n<li>Dup\u0103 ce datele s-au stabilizat, vechea \u00eenregistrare \u00een cache s-a expirat complet \u2014 100% din cereri merg pe noul server.<\/li>\n<\/ol>\n<p>\nPentru a accelera etapa 7 (care este adesea cea mai lung\u0103), TTL-ul \u00eenregistr\u0103rii DNS dinamice trebuie setat c\u00e2t mai sc\u0103zut posibil. De obicei, serviciile permit intervale de 90-120 de secunde. Acesta este un compromis rezonabil.<\/p>\n<h2>\u00cen plus<\/h2>\n<p>\nToate acestea pot fi configurate \u00eentr-o sear\u0103 (dac\u0103 ave\u021bi deja un server duplicat). At\u00e2t okerr, c\u00e2t \u0219i serviciile de DNS dinamic sunt gratuite. Pentru a ob\u021bine mai multe verific\u0103ri \u00een okerr \u0219i un interval de verificare mai scurt, trebuie s\u0103 urma\u021bi un training (de pe pagina de profil). Dup\u0103 finalizare, se va cre\u0219te imediat nivelul (20 de indicatori pe or\u0103 + 1 rapid, de 10 minute). \u0218i dac\u0103 nu vor fi suficiente \u2014 scrie\u021bi la support@okerr.com, cel mai probabil se va putea cre\u0219te (p\u00e2n\u0103 acum a fost \u00eentotdeauna posibil, niciodat\u0103 nu a fost refuzat, din contr\u0103, mi s-a propus). Pur \u0219i simplu, nu vreau s\u0103 promit tuturor totul de la bun \u00eenceput, nu sunt sigur c\u0103 vor fi suficiente resurse pentru a-mi onora cuv\u00e2ntul. Dar momentan utilizatorii sunt pu\u021bini, a\u0219a c\u0103 nu sunt probleme cu majorarea limitelor. <\/p>\n<p>Ce poate face okerr \u00een general \u2014 verifica\u021bi pe site <noindex><a rel=\"nofollow\" href=\"https:\/\/okerr.com\/presentation.html\">o prezentare<\/a><\/noindex>. \u00cen general, este un sistem de monitorizare (zabbix din cloud), iar file checker-ul este o func\u021bie suplimentar\u0103 pl\u0103cut\u0103. De asemenea, se poate accesa demo-ul de pe site f\u0103r\u0103 \u00eenregistrare.<\/p>\n<p>La schimbarea st\u0103rii indicatorului \u2014 se trimite o notificare pe email sau Telegram. (Am observat ce se \u00eent\u00e2mpl\u0103 \u0219i am realizat c\u0103, se pare, telegram-ul este cel mai fiabil mesager. Mul\u021bumim RKN pentru testul de stres!) Cu o configurare corect\u0103 a okerr, orice notificare este fie un semnal \u201el\u0103sa\u021bi totul, trebuie s\u0103 repar\u0103m!\u201d, fie \u201ese poate opri!\u201d. Nu ar trebui s\u0103 existe alerte suplimentare din partea okerr (dac\u0103 sunt, trebuie configurat diferit). De exemplu, pentru site-ul nostru de pisici, serverul alpha este ultimul \u0219i nu simuleaz\u0103 niciodat\u0103 o eroare. Dac\u0103 acesta cedeaz\u0103 \u2014 trebuie s\u0103 \u0219tim. Ceilal\u021bi serveri simuleaz\u0103 constant erori, a\u0219a c\u0103, pentru a nu primi alerte de mai multe ori pe or\u0103, ace\u0219ti indicatori au statutul \u201et\u0103cut\u201d. <\/p>\n<p>Este logic s\u0103 crea\u021bi \u0219i un server de avertizare (pe orice gazduire foarte ieftin\u0103), care s\u0103 aib\u0103 fie pagina dvs. de scuze (\u00een cazul \u00een care toate serverele principale \u0219i de rezerv\u0103 sunt c\u0103zute), fie s\u0103 redirec\u021bioneze la pagina de stare de pe okerr (de exemplu, a noastr\u0103 <noindex><a rel=\"nofollow\" href=\"https:\/\/cp.okerr.com\/status\/okerr\/\">cp.okerr.com\/status\/okerr<\/a><\/noindex>) sau statuspage.io.<br \/>\n<br \/>Sursa: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/359372\/\">habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u0412 \u044d\u0442\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0435 \u044f \u0445\u043e\u0447\u0443 \u043f\u043e\u043a\u0430\u0437\u0430\u0442\u044c, \u043a\u0430\u043a \u043b\u0435\u0433\u043a\u043e \u0438 \u0431\u0435\u0441\u043f\u043b\u0430\u0442\u043d\u043e \u043c\u043e\u0436\u043d\u043e \u0441\u0434\u0435\u043b\u0430\u0442\u044c failover \u0441\u0445\u0435\u043c\u0443 \u0434\u043b\u044f \u0432\u0435\u0431-\u0441\u0430\u0439\u0442\u0430 (\u0438\u043b\u0438 \u043b\u044e\u0431\u043e\u0433\u043e \u0434\u0440\u0443\u0433\u043e\u0433\u043e \u0438\u043d\u0442\u0435\u0440\u043d\u0435\u0442-\u0441\u0435\u0440\u0432\u0438\u0441\u0430) \u043d\u0430 \u043a\u043e\u043c\u0431\u0438\u043d\u0430\u0446\u0438\u0438 \u043c\u043e\u043d\u0438\u0442\u043e\u0440\u0438\u043d\u0433\u0430 okerr \u0438 \u0434\u0438\u043d\u0430\u043c\u0438\u0447\u0435\u0441\u043a\u043e\u0433\u043e DNS \u0441\u0435\u0440\u0432\u0438\u0441\u0430. \u0422\u043e \u0435\u0441\u0442\u044c, \u0432 \u0441\u043b\u0443\u0447\u0430\u0435 \u043b\u044e\u0431\u044b\u0445 \u043f\u0440\u043e\u0431\u043b\u0435\u043c \u0441 \u043e\u0441\u043d\u043e\u0432\u043d\u044b\u043c \u0441\u0430\u0439\u0442\u043e\u043c (\u043d\u0430\u0447\u0438\u043d\u0430\u044f \u043e\u0442 \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u044b \u0441 \u00abPHP Error\u00bb \u043d\u0430 \u0441\u0442\u0440\u0430\u043d\u0438\u0446\u0435, \u0438 \u0434\u043e \u043d\u0435\u0445\u0432\u0430\u0442\u043a\u0438 \u043c\u0435\u0441\u0442\u0430 \u0438\u043b\u0438 \u043f\u0440\u043e\u0441\u0442\u043e \u043f\u043e\u0434\u043e\u0437\u0440\u0438\u0442\u0435\u043b\u044c\u043d\u043e \u043c\u0430\u043b\u043e\u043c \u0447\u0438\u0441\u043b\u0435 \u0437\u0430\u043a\u0430\u0437\u043e\u0432 [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":84901,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-84900","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=\"\u0412 \u044d\u0442\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0435 \u044f \u0445\u043e\u0447\u0443 \u043f\u043e\u043a\u0430\u0437\u0430\u0442\u044c, \u043a\u0430\u043a \u043b\u0435\u0433\u043a\u043e \u0438 \u0431\u0435\u0441\u043f\u043b\u0430\u0442\u043d\u043e \u043c\u043e\u0436\u043d\u043e \u0441\u0434\u0435\u043b\u0430\u0442\u044c failover \u0441\u0445\u0435\u043c\u0443 \u0434\u043b\u044f \u0432\u0435\u0431-\u0441\u0430\u0439\u0442\u0430 (\u0438\u043b\u0438 \u043b\u044e\u0431\u043e\u0433\u043e \u0434\u0440\u0443\u0433\u043e\u0433\u043e \u0438\u043d\u0442\u0435\u0440\u043d\u0435\u0442-\u0441\u0435\u0440\u0432\u0438\u0441\u0430) \u043d\u0430 \u043a\u043e\u043c\u0431\u0438\u043d\u0430\u0446\u0438\u0438 \u043c\u043e\u043d\u0438\u0442\u043e\u0440\u0438\u043d\u0433\u0430\" \/>\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\/prostoj-failover-dlya-vebsajta-monitoring-dinamicheskij-dns\" \/>\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\udd47\u041f\u0440\u043e\u0441\u0442\u043e\u0439 failover \u0434\u043b\u044f \u0432\u0435\u0431\u0441\u0430\u0439\u0442\u0430 (\u043c\u043e\u043d\u0438\u0442\u043e\u0440\u0438\u043d\u0433 + \u0434\u0438\u043d\u0430\u043c\u0438\u0447\u0435\u0441\u043a\u0438\u0439 DNS) | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u0412 \u044d\u0442\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0435 \u044f \u0445\u043e\u0447\u0443 \u043f\u043e\u043a\u0430\u0437\u0430\u0442\u044c, \u043a\u0430\u043a \u043b\u0435\u0433\u043a\u043e \u0438 \u0431\u0435\u0441\u043f\u043b\u0430\u0442\u043d\u043e \u043c\u043e\u0436\u043d\u043e \u0441\u0434\u0435\u043b\u0430\u0442\u044c failover \u0441\u0445\u0435\u043c\u0443 \u0434\u043b\u044f \u0432\u0435\u0431-\u0441\u0430\u0439\u0442\u0430 (\u0438\u043b\u0438 \u043b\u044e\u0431\u043e\u0433\u043e \u0434\u0440\u0443\u0433\u043e\u0433\u043e \u0438\u043d\u0442\u0435\u0440\u043d\u0435\u0442-\u0441\u0435\u0440\u0432\u0438\u0441\u0430) \u043d\u0430 \u043a\u043e\u043c\u0431\u0438\u043d\u0430\u0446\u0438\u0438 \u043c\u043e\u043d\u0438\u0442\u043e\u0440\u0438\u043d\u0433\u0430\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/prostoj-failover-dlya-vebsajta-monitoring-dinamicheskij-dns\" \/>\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-06-11T11:43:28+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-06-11T11:43:28+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\udd47Failover simplu pentru site web (monitorizare + DNS dinamic) | ProHoster","description":"\u00cen acest articol, vreau s\u0103 ar\u0103t c\u00e2t de u\u0219or \u0219i gratuit se poate crea un sistem de failover pentru un website (sau orice alt serviciu online) folosind o combina\u021bie de monitorizare","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/prostoj-failover-dlya-vebsajta-monitoring-dinamicheskij-dns","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\udd47\u041f\u0440\u043e\u0441\u0442\u043e\u0439 failover \u0434\u043b\u044f \u0432\u0435\u0431\u0441\u0430\u0439\u0442\u0430 (\u043c\u043e\u043d\u0438\u0442\u043e\u0440\u0438\u043d\u0433 + \u0434\u0438\u043d\u0430\u043c\u0438\u0447\u0435\u0441\u043a\u0438\u0439 DNS) | ProHoster","og:description":"\u0412 \u044d\u0442\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0435 \u044f \u0445\u043e\u0447\u0443 \u043f\u043e\u043a\u0430\u0437\u0430\u0442\u044c, \u043a\u0430\u043a \u043b\u0435\u0433\u043a\u043e \u0438 \u0431\u0435\u0441\u043f\u043b\u0430\u0442\u043d\u043e \u043c\u043e\u0436\u043d\u043e \u0441\u0434\u0435\u043b\u0430\u0442\u044c failover \u0441\u0445\u0435\u043c\u0443 \u0434\u043b\u044f \u0432\u0435\u0431-\u0441\u0430\u0439\u0442\u0430 (\u0438\u043b\u0438 \u043b\u044e\u0431\u043e\u0433\u043e \u0434\u0440\u0443\u0433\u043e\u0433\u043e \u0438\u043d\u0442\u0435\u0440\u043d\u0435\u0442-\u0441\u0435\u0440\u0432\u0438\u0441\u0430) \u043d\u0430 \u043a\u043e\u043c\u0431\u0438\u043d\u0430\u0446\u0438\u0438 \u043c\u043e\u043d\u0438\u0442\u043e\u0440\u0438\u043d\u0433\u0430","og:url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/prostoj-failover-dlya-vebsajta-monitoring-dinamicheskij-dns","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-06-11T11:43:28+00:00","article:modified_time":"2020-06-11T11:43:28+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"84900","title":null,"description":null,"keywords":null,"keyphrases":null,"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 14:47:43","updated":"2022-10-07 20:30:02","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\/84900","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=84900"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/84900\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media\/84901"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=84900"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=84900"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=84900"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}