{"id":615,"date":"2025-06-01T20:25:01","date_gmt":"2025-06-01T17:25:01","guid":{"rendered":"https:\/\/dds.ro\/blog\/?p=615"},"modified":"2025-06-01T20:27:14","modified_gmt":"2025-06-01T17:27:14","slug":"cum-sa-configurezi-un-cluster-dns-cpanel-cu-disponibilitate-ridicata-pe-servere-vps-de-la-dds","status":"publish","type":"post","link":"https:\/\/dds.ro\/blog\/cum-sa-configurezi-un-cluster-dns-cpanel-cu-disponibilitate-ridicata-pe-servere-vps-de-la-dds\/","title":{"rendered":"Cum s\u0103 configurezi un cluster DNS cPanel cu disponibilitate ridicat\u0103 pe servere VPS de la DDS"},"content":{"rendered":"<span class=\"span-reading-time rt-reading-time\" style=\"display: block;\"><span class=\"rt-label rt-prefix\">Reading Time: <\/span> <span class=\"rt-time\"> 8<\/span> <span class=\"rt-label rt-postfix\">minutes<\/span><\/span>\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"439\" src=\"https:\/\/dds.ro\/blog\/wp-content\/uploads\/2025\/06\/dns-1024x439.jpg\" alt=\"\" class=\"wp-image-617\" srcset=\"https:\/\/dds.ro\/blog\/wp-content\/uploads\/2025\/06\/dns-1024x439.jpg 1024w, https:\/\/dds.ro\/blog\/wp-content\/uploads\/2025\/06\/dns-300x129.jpg 300w, https:\/\/dds.ro\/blog\/wp-content\/uploads\/2025\/06\/dns-768x329.jpg 768w, https:\/\/dds.ro\/blog\/wp-content\/uploads\/2025\/06\/dns-1200x514.jpg 1200w, https:\/\/dds.ro\/blog\/wp-content\/uploads\/2025\/06\/dns.jpg 1500w\" sizes=\"auto, (max-width: 709px) 85vw, (max-width: 909px) 67vw, (max-width: 1362px) 62vw, 840px\" \/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">1. Introducere \u00een DNS Clustering cPanel<\/h2>\n\n\n\n<p>\u00cen lumea g\u0103zduirii web, un singur punct de e\u0219ec poate pune \u00een pericol \u00eentregul site, iar DNS-ul (Domain Name System) reprezint\u0103 un astfel de punct critic. Atunci c\u00e2nd un VPS cPanel\/WHM g\u0103zduie\u0219te DNS-ul primar \u0219i acesta r\u0103m\u00e2ne offline, site-ul devine inaccesibil, de\u0219i serverul web func\u021bioneaz\u0103 perfect. Solu\u021bia este implementarea unui <strong>cluster DNS cPanel HA (High Availability)<\/strong>: dou\u0103 (sau mai multe) VPS-uri cPanel\/WHM care \u00ee\u0219i sincronizeaz\u0103 \u00een timp real zonele DNS. Dac\u0103 un nod cade, cel\u0103lalt preia automat traficul de rezolu\u021bie DNS, minimaliz\u00e2nd riscul de inactivitate a site-ului.<\/p>\n\n\n\n<p>\u00cen acest articol detaliat, vei \u00eenv\u0103\u021ba cum s\u0103 configurezi un cluster DNS cu cPanel\/WHM pe <strong>VPS-urile DDS Hosting<\/strong>, astfel \u00eenc\u00e2t domeniile tale s\u0103 r\u0103m\u00e2n\u0103 rezolvate f\u0103r\u0103 \u00eentreruperi \u0219i s\u0103 po\u021bi migra conturi cPanel \u00eentre noduri f\u0103r\u0103 downtime. Vom folosi ca exemplu dou\u0103 VPS-uri DDS cu cPanel preinstalat, dar aceia\u0219i pa\u0219i aplic\u0103 pentru orice alt furnizor care permite instalarea cPanel\/WHM pe VPS.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">2. De ce ai nevoie de un cluster DNS cPanel HA?<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Eliminarea punctului unic de e\u0219ec (SPOF):<\/strong> Dac\u0103 VPS-ul principal de DNS cade, domeniul nu se mai rezolv\u0103. Cu dou\u0103 noduri sincronizate, cel secundar preia automat cererile DNS.<\/li>\n\n\n\n<li><strong>Migrare f\u0103r\u0103 downtime a conturilor cPanel:<\/strong> Po\u021bi transfera un site de pe un nod pe altul, f\u0103r\u0103 ca vizitatorii s\u0103 observe c\u0103 site-ul este mutat, deoarece DNS-ul este duplicat pe ambele servere.<\/li>\n\n\n\n<li><strong>Scalabilitate \u00een perioade de trafic intens:<\/strong> Dac\u0103 ai un site care a\u0219teapt\u0103 un v\u00e2rf de trafic (Black Friday, Cyber Monday), \u00eel mu\u021bi temporar pe un VPS cu resurse mai mari, f\u0103r\u0103 s\u0103 afectezi restul conturilor de pe nodul original.<\/li>\n\n\n\n<li><strong>Redundan\u021b\u0103 DNS eficient\u0103:<\/strong> Cererile DNS pot fi distribuite \u00eentre ambele VPS-uri, reduc\u00e2nd \u00eenc\u0103rcarea pe fiecare server \u0219i \u00eembun\u0103t\u0103\u021bind timpii de r\u0103spuns globali.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">3. Avantajele utiliz\u0103rii VPS-urilor DDS Hosting<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Performan\u021b\u0103 ridicat\u0103 NVMe \u0219i infrastructur\u0103 KVM<\/strong>\n<ul class=\"wp-block-list\">\n<li>DDS Hosting ofer\u0103 <strong>VPS KVM cu stocare NVMe<\/strong>, ideale pentru cPanel\/WHM, \u00eencep\u00e2nd de la <strong>8,88 \u20ac\/lun\u0103<\/strong> pentru pachete cu 4 GB RAM \u0219i peste .<\/li>\n\n\n\n<li>Conectivitate intern\u0103 gigabit \u0219i CPU puternice asigur\u0103 timpi de r\u0103spuns DNS foarte rapizi.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Licen\u021be cPanel\/WHM incluse \u0219i suport 24\/7<\/strong>\n<ul class=\"wp-block-list\">\n<li>Orice VPS DDS pentru cPanel\/WHM vine cu licen\u021b\u0103 oficial\u0103 cPanel pre-configurat\u0103.<\/li>\n\n\n\n<li>Suport tehnic \u00een limba rom\u00e2n\u0103, disponibil 24\/7 prin ticket \u0219i live chat, gata s\u0103 te ajute \u00een orice pas al configur\u0103rii.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Flexibilitate \u00een alegerea resurselor<\/strong>\n<ul class=\"wp-block-list\">\n<li>Po\u021bi \u00eencepe cu un VPS de 4 GB RAM \u0219i, pe m\u0103sur\u0103 ce volumul de clien\u021bi cre\u0219te, adaugi rapid un al doilea VPS identic, form\u00e2nd clusterul DNS.<\/li>\n\n\n\n<li>Mai multe op\u021biuni de upgrade c\u0103tre VPS de 8 GB, 16 GB sau chiar servere dedicate, f\u0103r\u0103 complica\u021bii de migrare.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Backup extern \u0219i Storage Box<\/strong>\n<ul class=\"wp-block-list\">\n<li>DDS ofer\u0103 un serviciu separat de <strong>Storage Box<\/strong> (solu\u021bie de backup SSH\/SFTP), pentru copii automate ale zonelor DNS \u0219i ale fi\u0219ierelor cPanel. Astfel, clusterul t\u0103u DNS r\u0103m\u00e2ne protejat \u0219i \u00een cazul unei defec\u021biuni critice.<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">4. Pa\u0219i pentru configurarea clusterului DNS cPanel pe DDS Hosting<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">4.1. Achizi\u021bia \u0219i preg\u0103tirea VPS-urilor DDS<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Alege dou\u0103 VPS-uri cu cPanel\/WHM preinstalat<\/strong> de la DDS Hosting:\n<ul class=\"wp-block-list\">\n<li>\u00cen panoul DDS (<a class=\"\" href=\"https:\/\/dds.ro\">https:\/\/dds.ro<\/a>), navigheaz\u0103 la <strong>Servere VPS<\/strong> \u0219i selecteaz\u0103 un pachet minimal de <strong>4 GB RAM<\/strong> pentru fiecare nod (\u00eencep\u00e2nd de la 8,88 \u20ac\/lun\u0103) .<\/li>\n\n\n\n<li>Asigur\u0103-te c\u0103 licen\u021ba cPanel\/WHM este activat\u0103 (de regul\u0103 se face automat \u00een cadrul comenzii).<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Conecteaz\u0103-te prin SSH<\/strong> la fiecare VPS cu utilizatorul <code>root<\/code>.<\/li>\n\n\n\n<li><strong>Actualizeaz\u0103 sistemul de operare<\/strong> \u0219i instaleaz\u0103 eventual un firewall (de ex. <code>firewalld<\/code>): bashCopiaz\u0103Editeaz\u0103<code>yum update -y yum install firewalld -y systemctl enable --now firewalld firewall-cmd --add-service=http --add-service=https --permanent firewall-cmd --reload<\/code><\/li>\n\n\n\n<li><strong>Controleaz\u0103 SSH<\/strong>: seteaz\u0103 \u00een <code>\/etc\/ssh\/sshd_config<\/code> op\u021biunea <code>PasswordAuthentication no<\/code> (dup\u0103 finalizarea migra\u021biilor) pentru a limita accesul prin chei private.<\/li>\n<\/ol>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">4.2. Activarea DNS Cluster \u00een WHM<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Serverul A (nodul 1):<\/strong>\n<ul class=\"wp-block-list\">\n<li>Acceseaz\u0103 WHM la <code>https:\/\/IP-VPS-A:2087<\/code> \u0219i autentific\u0103-te cu <code>root<\/code>.<\/li>\n\n\n\n<li>\u00cen bara de c\u0103utare, tasteaz\u0103 <strong>\u201cDNS Cluster\u201d<\/strong>, apoi d\u0103 click pe <strong>\u201cEnable DNS Cluster\u201d<\/strong>. Vei vedea statusul curent ca <strong>Disabled<\/strong>.<\/li>\n\n\n\n<li>Apas\u0103 <strong>\u201cEnable\u201d<\/strong> pentru a activa func\u021bionalitatea.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Serverul B (nodul 2):<\/strong>\n<ul class=\"wp-block-list\">\n<li>Reia pa\u0219ii de mai sus: logheaz\u0103-te \u00een WHM (<code>https:\/\/IP-VPS-B:2087<\/code>), caut\u0103 <strong>\u201cDNS Cluster\u201d<\/strong> \u0219i apas\u0103 <strong>\u201cEnable\u201d<\/strong>.<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n<p>Dup\u0103 ce ai activat DNS Cluster pe ambele servere, trecem la generarea de token-uri API pentru a crea leg\u0103tura securizat\u0103 \u00eentre ele.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">4.3. Generarea API Token-urilor pentru comunicare securizat\u0103<\/h3>\n\n\n\n<p>Pentru a evita utilizarea parolei <code>root<\/code> \u00een configurare, vom crea dou\u0103 <strong>API Tokens<\/strong> cu drepturi minimal necesare.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Pe Serverul B (nod B):<\/strong>\n<ul class=\"wp-block-list\">\n<li>\u00cen WHM, \u00een c\u0103su\u021ba de c\u0103utare, tasteaz\u0103 <strong>\u201cManage API Tokens\u201d<\/strong> \u0219i apas\u0103 <strong>\u201cGenerate Token\u201d<\/strong>.<\/li>\n\n\n\n<li>D\u0103-i un nume descriptiv, de ex. <code>dns_cluster_nodB<\/code>.<\/li>\n\n\n\n<li>La <strong>IP Whitelist<\/strong>, po\u021bi ad\u0103uga IP-ul serverului A (ex.: <code>192.0.2.10<\/code>) pentru a limita accesul doar de la nodul A.<\/li>\n\n\n\n<li>\u00cen sec\u021biunea <strong>Privileges<\/strong>, dezactiveaz\u0103 tot, apoi bifeaz\u0103 doar:\n<ul class=\"wp-block-list\">\n<li><strong>Cluster: Add\/Remove Servers<\/strong><\/li>\n\n\n\n<li><strong>DNS: Modify Zones<\/strong> (pentru sincronizarea zonelor).<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Apas\u0103 <strong>\u201cSave\u201d<\/strong>. Copiaz\u0103 API Token-ul generat \u0219i stocheaz\u0103-l offline (nu \u00eel publica).<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Pe Serverul A (nod A):<\/strong>\n<ul class=\"wp-block-list\">\n<li>Repet\u0103 pa\u0219ii, dar d\u0103 token-ului numele <code>dns_cluster_nodA<\/code>, cu acela\u0219i IP Whitelist (IP server B, ex.: <code>192.0.2.11<\/code>) \u0219i acelea\u0219i drepturi:\n<ul class=\"wp-block-list\">\n<li><strong>Cluster: Add\/Remove Servers<\/strong><\/li>\n\n\n\n<li><strong>DNS: Modify Zones<\/strong><\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Salveaz\u0103 \u0219i stocheaz\u0103 token-ul \u00een siguran\u021b\u0103.<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p><strong>Not\u0103 de securitate:<\/strong> Revoc\u0103 aceste token-uri dup\u0103 configurare complet\u0103 sau limiteaz\u0103 expirarea la c\u00e2teva zile pentru a evita poten\u021biale compromiteri.<\/p>\n<\/blockquote>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">4.4. Crearea leg\u0103turii DNS Cluster (Reverse Trust Relationship)<\/h3>\n\n\n\n<p>Acum c\u0103 ambele noduri au API Token-urile, le vom conecta \u00eentr-un cluster DNS sincronizat bidirec\u021bional.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Pe Serverul A (nod A):<\/strong>\n<ul class=\"wp-block-list\">\n<li>\u00cen WHM, caut\u0103 <strong>\u201cDNS Cluster\u201d<\/strong>, apoi apas\u0103 <strong>\u201cConfigure\u201d<\/strong>.<\/li>\n\n\n\n<li>La <strong>Remote Hostname<\/strong>, introdu hostname-ul sau IP-ul serverului B (ex.: <code>vpsB.dds.ro<\/code> sau <code>192.0.2.11<\/code>).<\/li>\n\n\n\n<li>Sub <strong>Authentication<\/strong>, selecteaz\u0103 <strong>\u201cUse an API Token\u201d<\/strong>, apoi lipe\u0219te token-ul generat pe nodul B (<code>dns_cluster_nodB<\/code>).<\/li>\n\n\n\n<li>Bifeaz\u0103 <strong>\u201cSynchronize Changes\u201d<\/strong> (sincronizare bidirec\u021bional\u0103), nu <strong>Standalone<\/strong>. Astfel, orice modificare a zonei DNS pe nod A va fi trimis\u0103 \u0219i pe nod B, \u0219i invers.<\/li>\n\n\n\n<li>La <strong>Sync Type<\/strong>, alege <strong>Direct (Direct Sync)<\/strong>. Evit\u0103 intermediari care pot introduce \u00eent\u00e2rzieri \u0219i complexitate suplimentar\u0103.<\/li>\n\n\n\n<li>D\u0103 click pe <strong>\u201cSubmit\u201d<\/strong>. Va ap\u0103rea mesajul <strong>\u201cReverse trust relationship established\u201d<\/strong> \u0219i statusul se va schimba \u00een <strong>Connected<\/strong> (verde).<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Pe Serverul B (nod B):<\/strong>\n<ul class=\"wp-block-list\">\n<li>Repet\u0103 secven\u021ba: \u00een WHM, intr\u0103 la <strong>DNS Cluster<\/strong> \u203a <strong>Configure<\/strong>.<\/li>\n\n\n\n<li>La <strong>Remote Hostname<\/strong>, introdu hostname-ul sau IP-ul serverului A (<code>vpsA.dds.ro<\/code> sau <code>192.0.2.10<\/code>).<\/li>\n\n\n\n<li>Sub <strong>Authentication<\/strong>, selecteaz\u0103 <strong>\u201cUse an API Token\u201d<\/strong>, apoi lipe\u0219te token-ul generat pe nodul A (<code>dns_cluster_nodA<\/code>).<\/li>\n\n\n\n<li>Bifeaz\u0103 tot <strong>\u201cSynchronize Changes\u201d<\/strong> \u0219i alege <strong>Direct Sync<\/strong>.<\/li>\n\n\n\n<li>Apas\u0103 <strong>\u201cSubmit\u201d<\/strong>. Vei vedea tot statusul pe <strong>Connected<\/strong> (f\u0103r\u0103 erori).<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p><strong>Verificare:<\/strong> At\u00e2t pe nod A, c\u00e2t \u0219i pe nod B, \u00een tab-ul <strong>DNS Cluster<\/strong>, ar trebui s\u0103 apar\u0103 cealalt\u0103 ma\u0219in\u0103 cu o iconi\u021b\u0103 verde (Connected), iar modul de sincronizare s\u0103 fie <strong>Bidirec\u021bional<\/strong>.<\/p>\n<\/blockquote>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">4.5. Verificarea zonelor DNS \u00een cluster<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\u00cen WHM, acceseaz\u0103 <strong>DNS Zone Manager<\/strong> pe <strong>Serverul A<\/strong>.<\/li>\n\n\n\n<li>Vei g\u0103si lista complet\u0103 a zonelor DNS active pe acest VPS.<\/li>\n\n\n\n<li>\u00centr-o alt\u0103 ferestr\u0103, intr\u0103 pe <strong>DNS Zone Manager<\/strong> al <strong>Serverului B<\/strong>.<\/li>\n\n\n\n<li>Zonele trebuie s\u0103 fie identice (acela\u0219i num\u0103r de serial, acelea\u0219i \u00eenregistr\u0103ri A, MX, CNAME etc.).<\/li>\n<\/ol>\n\n\n\n<p>De fiecare dat\u0103 c\u00e2nd adaugi sau modifici o zon\u0103 DNS pe orice nod, modificarea se va propaga instantaneu pe nodul partener, f\u0103r\u0103 sincronizare manual\u0103 suplimentar\u0103.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">5. Configurarea domeniului de test \u0219i nameserver-e implicite<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">5.1. Crearea contului cPanel pe nodul A<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\u00cen WHM pe <strong>Serverul A<\/strong>, mergi la <strong>Create a New Account<\/strong>.<\/li>\n\n\n\n<li>Completeaz\u0103 c\u00e2mpurile de baz\u0103:\n<ul class=\"wp-block-list\">\n<li><strong>Domain:<\/strong> <code>exemplu-dns-dds.ro<\/code> (domeniu de test).<\/li>\n\n\n\n<li><strong>Username:<\/strong> <code>exempludns<\/code><\/li>\n\n\n\n<li><strong>Password:<\/strong> folose\u0219te generatorul complex cPanel.<\/li>\n\n\n\n<li>La <strong>Package<\/strong>, alege un pachet existent sau seteaz\u0103 manual spa\u021biul disk\/trafic.<\/li>\n\n\n\n<li>La <strong>DNS Settings<\/strong>, vei vedea name-server-ele implicite, de exemplu:\n<ul class=\"wp-block-list\">\n<li><code>ns1.vpsA.dds.ro<\/code> (IP: 192.0.2.10)<\/li>\n\n\n\n<li><code>ns2.vpsA.dds.ro<\/code> (IP: 192.0.2.10)<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Apas\u0103 <strong>Create<\/strong>.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Dup\u0103 finalizare, intr\u0103 \u00een <strong>List Accounts<\/strong> \u0219i verific\u0103 c\u0103 domeniul apare activ.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">5.2. Modificarea nameserver-elor la registrar<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Conecteaz\u0103-te la contul t\u0103u de la registrar (Ex: RoTLD, DDS etc.) pentru <code>exemplu-dns-dds.ro<\/code>.<\/li>\n\n\n\n<li>La set\u0103rile de <strong>Nameservers<\/strong>, actualizeaz\u0103 cu:<ul><li><code>ns1.vpsA.dds.ro<\/code><\/li><li><code>ns2.vpsB.dds.ro<\/code><\/li><\/ul>Deoarece serverele sunt \u00een cluster, oricare dintre ele va r\u0103spunde cererilor DNS.<\/li>\n\n\n\n<li>Salveaz\u0103 modific\u0103rile \u0219i a\u0219teapt\u0103 propagarea (30\u201360 minute \u00een majoritatea \u021b\u0103rilor, p\u00e2n\u0103 la 24 de ore \u00een unele regiuni mai lente).<\/li>\n<\/ol>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p><strong>Aten\u021bionare:<\/strong> Asigur\u0103-te c\u0103 ai \u00eenc\u0103rcat fi\u0219ierele site-ului \u0219i ai creat contul cPanel \u00eenainte de a schimba nameserver-ele. \u00cen caz contrar, vizitatorii pot vedea o pagin\u0103 goal\u0103 sau eroare temporar\u0103.<\/p>\n<\/blockquote>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">6. Configurarea HA pentru rezolu\u021bia DNS<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">6.1. Ad\u0103ugarea nameserver-elor secundare \u00een zona DNS<\/h3>\n\n\n\n<p>Pentru a te asigura c\u0103 ambele noduri pot r\u0103spunde, completeaz\u0103 fi\u0219ierul de zon\u0103 cu cele patru NS records (dou\u0103 pentru fiecare VPS):<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\u00cen <strong>DNS Zone Manager<\/strong> pe <strong>Serverul A<\/strong>, selecteaz\u0103 <code>exemplu-dns-dds.ro<\/code>.<\/li>\n\n\n\n<li>Apas\u0103 pe <strong>Add Record<\/strong> \u203a <strong>Add NS Record<\/strong> \u0219i adaug\u0103:\n<ul class=\"wp-block-list\">\n<li><strong>Name:<\/strong> <code>exemplu-dns-dds.ro.<\/code><\/li>\n\n\n\n<li><strong>TTL:<\/strong> <code>14400<\/code><\/li>\n\n\n\n<li><strong>NS:<\/strong> <code>ns1.vpsB.dds.ro.<\/code><\/li>\n\n\n\n<li>Apas\u0103 <strong>Save<\/strong>.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Repet\u0103 pasul pentru <code>ns2.vpsB.dds.ro.<\/code> (aceea\u0219i zon\u0103). Dac\u0103 apare o modificare de serial, WHM o va sincroniza direct pe <strong>Serverul B<\/strong>.<\/li>\n\n\n\n<li>Verific\u0103 pe <strong>Serverul B<\/strong> \u00een <strong>DNS Zone Manager<\/strong> pentru <code>exemplu-dns-dds.ro<\/code> c\u0103 cele patru NS records apar identic:\n<ul class=\"wp-block-list\">\n<li><code>ns1.vpsA.dds.ro.<\/code><\/li>\n\n\n\n<li><code>ns2.vpsA.dds.ro.<\/code><\/li>\n\n\n\n<li><code>ns1.vpsB.dds.ro.<\/code><\/li>\n\n\n\n<li><code>ns2.vpsB.dds.ro.<\/code><\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n<p>Astfel, dac\u0103 <code>vpsA.dds.ro<\/code> devine inaccesibil, rezolu\u021bia continu\u0103 prin <code>vpsB.dds.ro<\/code>.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">7. Testarea rezolu\u021biei DNS HA<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Deschide un terminal (Linux, macOS) sau Git Bash (Windows): bashCopiaz\u0103Editeaz\u0103<code>dig @ns1.vpsA.dds.ro exemplu-dns-dds.ro A +short dig @ns2.vpsB.dds.ro exemplu-dns-dds-ro A +short<\/code> Ambele comenzi trebuie s\u0103 returneze aceea\u0219i adres\u0103 IP (a nodului pe care este g\u0103zduit contul cPanel).<\/li>\n\n\n\n<li>Pentru verificare extern\u0103, folose\u0219te tool-uri online precum DNS Hero sau IntoDNS. Dac\u0103 totul este configurat corect, nu vei vedea erori (niciun \u201cred\u201d la verific\u0103rile de NS, A, MX, SOA).<\/li>\n<\/ol>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">8. Migrarea conturilor cPanel live \u00eentre noduri<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">8.1. Scenariu: Site-ul (exemplu-dns-dds.ro) are trafic crescut pe nodul A<\/h3>\n\n\n\n<p>\u00cen cazul \u00een care <code>vpsA.dds.ro<\/code> ajunge la limita resurselor (ex.: Black Friday), po\u021bi muta contul cPanel pe <code>vpsB.dds.ro<\/code> f\u0103r\u0103 downtime, datorit\u0103 clusterului DNS sincronizat.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Pe nodul B<\/strong>, intr\u0103 \u00een WHM \u203a <strong>Transfer Tool<\/strong>.<\/li>\n\n\n\n<li>La <strong>Remote Server<\/strong>, completeaz\u0103:\n<ul class=\"wp-block-list\">\n<li><strong>Hostname\/IP:<\/strong> <code>vpsA.dds.ro<\/code><\/li>\n\n\n\n<li><strong>Port:<\/strong> <code>22<\/code><\/li>\n\n\n\n<li><strong>Authentication:<\/strong>\n<ul class=\"wp-block-list\">\n<li><strong>Root Password<\/strong> (temporar, doar pe durata transferului)<br><em>sau<\/em><\/li>\n\n\n\n<li><strong>SSH Key<\/strong> (dac\u0103 ai configurat autentificarea prin cheie \u00eentre cele dou\u0103 servere).<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Apas\u0103 <strong>Fetch Account List<\/strong>:\n<ul class=\"wp-block-list\">\n<li>Vei vedea contul <code>exemplu-dns-dds-ro<\/code>.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Bifeaz\u0103 op\u021biunile:\n<ul class=\"wp-block-list\">\n<li><strong>Copy over and suspend source account<\/strong> (copiere \u0219i suspendare pe nodul A, pentru a p\u0103stra un singur punct activ).<\/li>\n\n\n\n<li><strong>Preserve DNS<\/strong> (nu modifica set\u0103rile DNS \u00een timpul migr\u0103rii, deoarece DNS-ul este deja sincronizat).<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Apas\u0103 <strong>Copy<\/strong> \u0219i a\u0219teapt\u0103 finalizarea transferului.<\/li>\n<\/ol>\n\n\n\n<p>Dup\u0103 finalizare:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Contul <code>exemplu-dns-dds-ro<\/code> va fi activ pe <code>vpsB.dds.ro<\/code>.<\/li>\n\n\n\n<li>DNS-ul (cu zonele deja propagate) va indica <code>exemplu-dns-dds-ro<\/code> c\u0103tre noua adres\u0103 IP a nodului B, f\u0103r\u0103 s\u0103 existe downtime intermediar.<\/li>\n\n\n\n<li>Pe <strong>Serverul A<\/strong>, contul va ap\u0103rea \u00een WHM la <strong>List Accounts<\/strong> ca <strong>Suspended<\/strong>.<\/li>\n<\/ul>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p><strong>Sfat:<\/strong> Dac\u0103 ai configurat anterior <code>PasswordAuthentication no<\/code>, re-activeaz\u0103 temporar pentru migrare \u0219i apoi revino la <code>no<\/code> dup\u0103 ce transferul s-a \u00eencheiat.<\/p>\n<\/blockquote>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">9. Crearea vanity name servers (name servers private)<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">9.1. Ad\u0103ugarea \u00eenregistr\u0103rilor A pentru vanity NS \u00een zona DNS<\/h3>\n\n\n\n<p>Pentru branding propriu, folose\u0219te <code>ns1.exemplu-dns-dds.ro<\/code> \u0219i <code>ns2.exemplu-dns-dds-ro<\/code> \u00een locul <code>vpsA.dds.ro<\/code>\/<code>vpsB.dds-ro<\/code>. Pa\u0219ii:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\u00cen <strong>DNS Zone Manager<\/strong> pe <strong>nod A<\/strong>, selecteaz\u0103 <code>exemplu-dns-dds-ro<\/code>.<\/li>\n\n\n\n<li>Apas\u0103 <strong>Add Record<\/strong> \u203a <strong>Add A Record<\/strong>:\n<ul class=\"wp-block-list\">\n<li><strong>Name:<\/strong> <code>ns1<\/code><\/li>\n\n\n\n<li><strong>TTL:<\/strong> <code>14400<\/code><\/li>\n\n\n\n<li><strong>Address:<\/strong> <code>192.0.2.10<\/code> (IP-ul lui <code>vpsA.dds.ro<\/code>).<\/li>\n\n\n\n<li>Apas\u0103 <strong>Save<\/strong>.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>\u00cen acela\u0219i mod, adaug\u0103:\n<ul class=\"wp-block-list\">\n<li><strong>Name:<\/strong> <code>ns2<\/code><\/li>\n\n\n\n<li><strong>TTL:<\/strong> <code>14400<\/code><\/li>\n\n\n\n<li><strong>Address:<\/strong> <code>192.0.2.11<\/code> (IP-ul lui <code>vpsB.dds-ro<\/code>).<\/li>\n\n\n\n<li>Apas\u0103 <strong>Save<\/strong>.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Verific\u0103 pe <strong>nod B<\/strong> \u00een <strong>DNS Zone Manager<\/strong> c\u0103 \u0219i aceste \u00eenregistr\u0103ri A apar identice.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">9.2. \u00cenregistrarea vanity name servers la registrar<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Conecteaz\u0103-te la panel-ul registrarului (ex.: RoTLD) pentru <code>exemplu-dns-dds.ro<\/code>.<\/li>\n\n\n\n<li>Caut\u0103 op\u021biunea <strong>Register Private Name Servers<\/strong> (sau \u201cCreate Hostnames\u201d):\n<ul class=\"wp-block-list\">\n<li>Adaug\u0103:\n<ul class=\"wp-block-list\">\n<li><code>ns1.exemplu-dns-dds.ro<\/code> \u2192 <code>192.0.2.10<\/code><\/li>\n\n\n\n<li><code>ns2.exemplu-dns-dds-ro<\/code> \u2192 <code>192.0.2.11<\/code><\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Salveaz\u0103 aceste \u201eglue records\u201d.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Apoi, la sec\u021biunea <strong>Nameservers<\/strong> a domeniului, \u00eenlocuie\u0219te:\n<ul class=\"wp-block-list\">\n<li><code>ns1.vpsA.dds.ro<\/code> \u2192 <code>ns1.exemplu-dns-dds.ro<\/code><\/li>\n\n\n\n<li><code>ns2.vpsB.dds-ro<\/code> \u2192 <code>ns2.exemplu-dns-dds.ro<\/code><\/li>\n\n\n\n<li>Salveaz\u0103 modific\u0103rile.<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p><strong>Aten\u021bie:<\/strong> Dac\u0103 nu regi\u0219trezi la registrar <code>ns1.exemplu-dns-dds.ro<\/code> \u0219i <code>ns2.exemplu-dns-dds.ro<\/code> ca glue records, site-ul poate deveni inaccesibil. Glue records sunt necesare pentru ca registrarul s\u0103 \u0219tie c\u0103 nameserver-ele private rezolv\u0103 exact la IP-urile VPS-urilor.<\/p>\n<\/blockquote>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">10. Verific\u0103ri finale \u0219i bune practici<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">10.1. Testarea configura\u021biei DNS HA<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Dup\u0103 ce nameserver-ele vanity s-au propagat (de obicei 30-60 min, p\u00e2n\u0103 la 24h): bashCopiaz\u0103Editeaz\u0103<code>dig @ns1.exemplu-dns-dds.ro exemplu-dns-dds.ro A +short dig @ns2.exemplu-dns-dds-ro exemplu-dns-dds-ro A +short<\/code> Rezultatul trebuie s\u0103 fie IP-ul corect (al nodului activ).<\/li>\n\n\n\n<li>Folose\u0219te DNS Hero sau <a class=\"\" href=\"https:\/\/intodns.com\" target=\"_blank\" rel=\"noopener\">IntoDNS<\/a> pentru a verifica c\u0103 nu exist\u0103 erori (no records missing, no errors). Toate testele trebuie s\u0103 fie verzi.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">10.2. Recomand\u0103ri de securitate \u0219i performan\u021b\u0103<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>SSH Security<\/strong>\n<ul class=\"wp-block-list\">\n<li>Dup\u0103 migrare, \u00een <code>\/etc\/ssh\/sshd_config<\/code>, seteaz\u0103 <code>PermitRootLogin no<\/code> \u0219i <code>PasswordAuthentication no<\/code> pentru acces exclusiv prin chei private.<\/li>\n\n\n\n<li>Administreaz\u0103 cu grij\u0103 cheile SSH.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>API Tokens<\/strong>\n<ul class=\"wp-block-list\">\n<li>Dup\u0103 finalizarea clusterului, po\u021bi <strong>revoca<\/strong> API Token-urile temporare folosite pentru migrare sau ad\u0103uga expirare (ex.: 24 h).<\/li>\n\n\n\n<li>Creeaz\u0103 noi token-uri doar dac\u0103 adaugi un al treilea nod.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Actualiz\u0103ri<\/strong>\n<ul class=\"wp-block-list\">\n<li>\u00cen WHM \u203a <strong>Update Preferences<\/strong>, selecteaz\u0103 actualiz\u0103ri automate pentru patch-uri de securitate cPanel \u0219i kernel.<\/li>\n\n\n\n<li>Ruleaz\u0103 periodic <code>yum update<\/code> pe VPS-uri (\u00een afara orelor de v\u00e2rf).<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Backup \u0219i Storage Box<\/strong>\n<ul class=\"wp-block-list\">\n<li>Activeaz\u0103 \u00een WHM \u203a <strong>Backup Configuration<\/strong> backup-uri zilnice ale conturilor cPanel.<\/li>\n\n\n\n<li>Utilizeaz\u0103 serviciul <strong>Storage Box<\/strong> de la DDS pentru stocarea copiilor de siguran\u021b\u0103:\n<ul class=\"wp-block-list\">\n<li>Po\u021bi face backup SSH\/SFTP direct din cPanel.<\/li>\n\n\n\n<li>P\u0103streaz\u0103 versiuni vechi \u0219i copii incremental diferite (utile \u00een caz de compromiterea zonei DNS).<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Monitorizare uptime<\/strong>\n<ul class=\"wp-block-list\">\n<li>Folose\u0219te servicii precum <strong>UptimeRobot<\/strong> sau <strong>StatusCake<\/strong> pentru a primi alerte \u00een timp real dac\u0103 unul dintre noduri nu mai r\u0103spunde.<\/li>\n\n\n\n<li>Trimite scripturi de health check automate pe ambele IP-uri \u0219i verific\u0103 difuzarea \u00eenregistr\u0103rilor NS.<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">11. Concluzie: Beneficii \u0219i recomand\u0103ri finale<\/h2>\n\n\n\n<p>Configurarea unui <strong>cluster DNS cPanel HA<\/strong> pe <strong>VPS-urile DDS Hosting<\/strong> \u00ee\u021bi ofer\u0103:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Fiabilitate continu\u0103 a serviciului DNS<\/strong>: Chiar dac\u0103 unul dintre VPS-uri se defecteaz\u0103, DNS-ul r\u0103m\u00e2ne func\u021bional.<\/li>\n\n\n\n<li><em>Migrare live a conturilor cPanel<\/em>*: Mut\u0103 rapid site-uri \u00eentre noduri f\u0103r\u0103 ca utilizatorii s\u0103 observe vreo perioad\u0103 de nefunc\u021bionare.<\/li>\n\n\n\n<li><strong>Scalabilitate flexibil\u0103<\/strong>: Adaug\u0103 node-uri DNS suplimentare pe m\u0103sur\u0103 ce lista de site-uri cre\u0219te, f\u0103r\u0103 investi\u021bii majore ini\u021biale.<\/li>\n\n\n\n<li><strong>Branding unic prin vanity name servers<\/strong>: Clien\u021bii sau vizitatorii t\u0103i vor vedea <code>ns1.exemplu-dns-dds.ro<\/code>, \u00een loc de un hostname generic DDS.<\/li>\n\n\n\n<li><strong>Costuri reduse<\/strong>: Cu doar dou\u0103 VPS-uri de 4 GB RAM (8,88 \u20ac\/lun\u0103 fiecare) \u0219i licen\u021be cPanel incluse, ob\u021bii un DNS cluster complet func\u021bional.<\/li>\n<\/ul>\n\n\n\n<p><strong>DDS Hosting<\/strong> este partenerul ideal pentru a implementa acest setup:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Planuri VPS KVM NVMe cu resurse dedicate \u0219i licen\u021be cPanel incluse.<\/li>\n\n\n\n<li>Suport tehnic 24\/7 \u00een limba rom\u00e2n\u0103, gata s\u0103 te asiste \u00een pa\u0219ii de configurare DNS clustering.<\/li>\n\n\n\n<li>Demonstra\u021bii \u0219i tutoriale detaliate (video \u0219i documenta\u021bie scris\u0103) disponibile \u00een contul t\u0103u DDS.<\/li>\n<\/ul>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p>Dac\u0103 vrei s\u0103-\u021bi protejezi domeniile \u0219i s\u0103 elimini riscul downtime-ului DNS, comand\u0103 imediat dou\u0103 VPS-uri cPanel\/WHM de la DDS Hosting (<a class=\"\" href=\"https:\/\/dds.ro\/servere-vps\">https:\/\/dds.ro\/servere-vps<\/a>) \u0219i urmeaz\u0103 pa\u0219ii de mai sus pentru a crea un <strong>cluster DNS cPanel HA<\/strong> solid, scalabil \u0219i eficient.<\/p>\n<\/blockquote>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<p><strong>Resurse suplimentare:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Documenta\u021bia oficial\u0103 cPanel pentru DNS Cluster<\/li>\n\n\n\n<li>Ghid complet DDS Hosting: <a class=\"\" href=\"https:\/\/dds.ro\/servere-vps\">Servere VPS cPanel\/WHM<\/a><\/li>\n\n\n\n<li>Configurarea <strong>Storage Box<\/strong> pentru backup extern: <a class=\"\" href=\"https:\/\/dds.ro\/storage-box\">https:\/\/dds.ro\/storage-box<\/a><\/li>\n\n\n\n<li>Tool-uri de testare DNS:\n<ul class=\"wp-block-list\">\n<li>DNS Hero<\/li>\n\n\n\n<li>IntoDNS<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<p>Implement\u00e2nd acest tutorial pas cu pas, vei ob\u021bine un mediu DNS rezilient \u0219i performant, capabil s\u0103 mute site-uri live \u00eentre servere f\u0103r\u0103 \u00eentreruperi, garant\u00e2nd astfel satisfac\u021bia utilizatorilor \u0219i cre\u0219terea afacerii tale online.<\/p>\n\n\n\n<p><\/p>\n","protected":false},"excerpt":{"rendered":"<p><span class=\"span-reading-time rt-reading-time\" style=\"display: block;\"><span class=\"rt-label rt-prefix\">Reading Time: <\/span> <span class=\"rt-time\"> 8<\/span> <span class=\"rt-label rt-postfix\">minutes<\/span><\/span>1. Introducere \u00een DNS Clustering cPanel \u00cen lumea g\u0103zduirii web, un singur punct de e\u0219ec poate pune \u00een pericol \u00eentregul site, iar DNS-ul (Domain Name System) reprezint\u0103 un astfel de punct critic. Atunci c\u00e2nd un VPS cPanel\/WHM g\u0103zduie\u0219te DNS-ul primar \u0219i acesta r\u0103m\u00e2ne offline, site-ul devine inaccesibil, de\u0219i serverul web func\u021bioneaz\u0103 perfect. Solu\u021bia este implementarea<\/p>\n","protected":false},"author":3,"featured_media":618,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[109],"tags":[124,123],"class_list":["post-615","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-tutoriale","tag-cpanel-dns","tag-dns-clustering"],"_links":{"self":[{"href":"https:\/\/dds.ro\/blog\/wp-json\/wp\/v2\/posts\/615","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dds.ro\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dds.ro\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dds.ro\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/dds.ro\/blog\/wp-json\/wp\/v2\/comments?post=615"}],"version-history":[{"count":4,"href":"https:\/\/dds.ro\/blog\/wp-json\/wp\/v2\/posts\/615\/revisions"}],"predecessor-version":[{"id":621,"href":"https:\/\/dds.ro\/blog\/wp-json\/wp\/v2\/posts\/615\/revisions\/621"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/dds.ro\/blog\/wp-json\/wp\/v2\/media\/618"}],"wp:attachment":[{"href":"https:\/\/dds.ro\/blog\/wp-json\/wp\/v2\/media?parent=615"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dds.ro\/blog\/wp-json\/wp\/v2\/categories?post=615"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dds.ro\/blog\/wp-json\/wp\/v2\/tags?post=615"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}