{"id":2131,"date":"2025-12-12T22:03:15","date_gmt":"2025-12-12T22:03:15","guid":{"rendered":"https:\/\/blog.eu.enginyr.ing\/?p=2131"},"modified":"2025-12-12T22:03:16","modified_gmt":"2025-12-12T22:03:16","slug":"cum-sa-transferi-un-domeniu-fara-downtime-mutare-registrar-cutover-dns-si-siguranta-email-ului","status":"publish","type":"post","link":"https:\/\/www.serverspan.ro\/blog\/cum-sa-transferi-un-domeniu-fara-downtime-mutare-registrar-cutover-dns-si-siguranta-email-ului\/","title":{"rendered":"Cum s\u0103 transferi un domeniu f\u0103r\u0103 downtime: mutare registrar, cutover DNS \u0219i siguran\u021ba email-ului"},"content":{"rendered":"\n\n<p class=\"wp-block-paragraph\">Po\u021bi transfera un domeniu la un nou registrar f\u0103r\u0103 downtime dac\u0103 men\u021bii DNS-ul autoritativ al domeniului neschimbat \u00een timpul transferului. Site-ul \u0219i email-ul t\u0103u r\u0103m\u00e2n online at\u00e2ta timp c\u00e2t nameserver-ele \u0219i \u00eenregistr\u0103rile DNS din spatele lor nu se schimb\u0103. Downtime-ul apare c\u00e2nd combini un transfer de registrar cu o schimbare de nameserver sau o reconstruire gr\u0103bit\u0103 a DNS-ului.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Rul\u0103m mut\u0103ri de domenii ca parte a opera\u021biunilor de hosting la ENGINYRING. Asta \u00eenseamn\u0103 c\u0103 ne preocup\u0103 rezultatele banale: paginile de checkout continu\u0103 s\u0103 se \u00eencarce, email-urile de resetare parol\u0103 continu\u0103 s\u0103 soseasc\u0103 \u0219i nu afli despre o gre\u0219eal\u0103 DNS de la un client. Abordarea practic\u0103 este simpl\u0103. Separ\u0103 mutarea registrar-ului de modific\u0103rile DNS, stabile\u0219te o linie de baz\u0103 pentru tot ce depinzi \u0219i schimb\u0103 c\u00e2te o component\u0103 mobil\u0103 la un moment dat.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Registrar, hosting DNS, hosting web \u0219i email sunt straturi diferite<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Majoritatea downtime-ului \u00een timpul unui transfer de domeniu nu este cauzat\u0103 de transferul \u00een sine. Este cauzat\u0103 de schimbarea stratului gre\u0219it. Ai nevoie de un model clar \u00eenainte s\u0103 atingi orice.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Registrar-ul este locul unde domeniul este \u00eenregistrat. Controleaz\u0103 re\u00eennoirea, detaliile de contact, starea de blocare a domeniului \u0219i procesul de transfer al \u00eenregistr\u0103rii c\u0103tre alt registrar. Hosting-ul DNS este locul unde zona ta DNS tr\u0103ie\u0219te. Acea zon\u0103 con\u021bine \u00eenregistr\u0103rile tale A, AAAA, CNAME, MX, TXT, SRV \u0219i CAA. Hosting-ul web este locul unde aplica\u021bia ta ruleaz\u0103. Hosting-ul email este locul unde tr\u0103iesc c\u0103su\u021bele po\u0219tale \u0219i rutarea mailurilor.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Un transfer de registrar schimb\u0103 doar registrar-ul. Nu schimb\u0103 automat nameserver-ele tale. Dac\u0103 nameserver-ele r\u0103m\u00e2n acelea\u0219i, DNS-ul autoritativ r\u0103m\u00e2ne acela\u0219i \u0219i utilizatorii t\u0103i nu ar trebui s\u0103 observe schimbarea registrar-ului. Aceasta este calea cea mai sigur\u0103 \u0219i este cea pe care o recomand\u0103m c\u00e2nd scopul t\u0103u principal este consolidarea sau controlul factur\u0103rii.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ai nevoie de un plan DNS doar dac\u0103 inten\u021bionezi s\u0103 schimbi nameserver-ele sau \u00eenregistr\u0103rile DNS. Ai nevoie de un plan de hosting doar dac\u0103 inten\u021bionezi s\u0103 schimbi serverele din spatele acelor \u00eenregistr\u0103ri. Trateaz\u0103-le ca proiecte separate dac\u0103 nu ai un motiv puternic s\u0103 le cuplezi.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">\u00cencepe prin a alege calea corect\u0103<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Exist\u0103 dou\u0103 modalit\u0103\u021bi comune de a aborda o mutare de domeniu. Ambele pot fi sigure. Doar una este cu risc sc\u0103zut pentru \u00eencep\u0103tori.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Calea A: transfer doar de registrar.<\/strong> Mu\u021bi \u00eenregistrarea la un nou registrar \u0219i p\u0103strezi acelea\u0219i nameservere. DNS-ul r\u0103m\u00e2ne g\u0103zduit unde este. Site-ul \u0219i email-ul t\u0103u continu\u0103 s\u0103 foloseasc\u0103 acelea\u0219i r\u0103spunsuri DNS.<\/li>\n<li><strong>Calea B: transfer registrar plus cutover DNS.<\/strong> Mu\u021bi \u0219i hosting-ul DNS la o nou\u0103 platform\u0103 \u0219i schimbi nameserver-ele. Aceasta necesit\u0103 planificare TTL, verific\u0103ri de paritate a \u00eenregistr\u0103rilor \u0219i aten\u021bie suplimentar\u0103 la autentificarea email.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 ai nevoie doar de Calea A, nu atinge DNS-ul. P\u0103streaz\u0103 nameserver-ele neschimbate. Nu reconstrui zona. Nu faci munc\u0103 de cur\u0103\u021bare \u00een mijlocul transferului. Cel mai rapid mod de a crea downtime este s\u0103 tratezi fereastra de transfer ca pe o oportunitate de a schimba tot ce nu \u00ee\u021bi place la DNS-ul t\u0103u.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 \u0219tii c\u0103 ai nevoie de Calea B, trateaz\u0103-o ca pe o migrare DNS de produc\u021bie. Acea migrare poate fi f\u0103cut\u0103 f\u0103r\u0103 downtime, dar doar dac\u0103 construie\u0219ti paritate mai \u00eent\u00e2i \u0219i validezi r\u0103spunsurile authoritative \u00eenainte s\u0103 schimbi delegarea.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 vrei ca mutarea registrar-ului s\u0103 fie gestionat\u0103 ca o schimbare controlat\u0103, \u00eencepe cu ENGINYRING <a href=\"https:\/\/www.enginyring.com\/ro\/domains\">Domenii<\/a>. Putem rula Calea A \u00een siguran\u021b\u0103, apoi programa un cutover DNS ca o faz\u0103 separat\u0103 dac\u0103 chiar ai nevoie de el.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Pre-zbor: verific\u0103ri care previn majoritatea e\u0219ecurilor de transfer<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Transferurile e\u0219ueaz\u0103 sau se blocheaz\u0103 din motive previzibile. Remediaz\u0103 acestea \u00eenainte de a ini\u021bia transferul, astfel \u00eenc\u00e2t s\u0103 nu r\u0103m\u00e2i blocat la jum\u0103tatea procesului cu domeniul t\u0103u \u00een limbo.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Confirm\u0103 c\u0103 controlezi calea de email pentru aprobare<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Majoritatea registrarilor se bazeaz\u0103 pe confirm\u0103ri prin email trimise la adresa de contact a titularului. Dac\u0103 email-ul de contact al titularului sau transferului este defect, procesul se poate bloca. Vedem des acest lucru c\u00e2nd c\u0103su\u021ba po\u0219tal\u0103 de contact tr\u0103ie\u0219te pe acela\u0219i domeniu care este transferat \u0219i configura\u021bia de mail a fost neglijat\u0103. Testeaz\u0103-l de la o adres\u0103 extern\u0103. Verific\u0103 inbound \u0219i outbound. Dac\u0103 email-ul nu este fiabil, remediaz\u0103 asta \u00eenainte de a programa o fereastr\u0103 de transfer.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Verific\u0103 bloc\u0103rile, eligibilitatea \u0219i momentul potrivit<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Multe domenii nu pot fi transferate \u00een anumite perioade. gTLD-urile au o blocare de transfer de 60 de zile dup\u0103 \u00eenregistrarea ini\u021bial\u0103 \u0219i dup\u0103 un transfer anterior. Exist\u0103, de asemenea, o blocare de transfer de 60 de zile care se poate aplica dup\u0103 o schimbare a informa\u021biilor titularului, \u00een func\u021bie de cum registrar-ul t\u0103u implementeaz\u0103 politica ICANN. Dac\u0103 ai actualizat recent detaliile titularului, nu presupune c\u0103 po\u021bi transfera imediat.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">De asemenea, verific\u0103 data de expirare a domeniului. Nu \u00eencepe un transfer c\u00e2nd domeniul este aproape de expirare. Re\u00eennoie\u0219te devreme \u0219i planific\u0103 cu spa\u021biu de respira\u021bie. Scopul este s\u0103 evi\u021bi o situa\u021bie \u00een care urm\u0103re\u0219ti aprob\u0103ri \u00een timp ce domeniul este aproape de expirare.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Deblocheaz\u0103 \u0219i ob\u021bine Auth-Code \u00eenainte de a \u00eencepe<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Asigur\u0103-te c\u0103 domeniul este deblocat la registrar-ul cedent. Apoi solicit\u0103 Auth-Code, numit \u0219i cod EPP sau Cod de Autorizare Transfer. Ob\u021bine-l mai \u00eent\u00e2i, p\u0103streaz\u0103-l \u00een siguran\u021b\u0103 \u0219i abia apoi ini\u021biaz\u0103 transferul la registrar-ul primitiv. A\u0219teptarea codului dup\u0103 ce ai \u00eenceput procesul este o modalitate comun\u0103 de a pierde timp \u0219i control.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Perspectiv\u0103 opera\u021bional\u0103 din transferuri reale: transferul registrar \u00een sine este rar declan\u0219atorul \u00eentreruperii. Declan\u0219atorul \u00eentreruperii este e\u0219ecul de acces \u00een cel mai prost moment. Dac\u0103 nu te po\u021bi autentifica la registrar-ul cedent, nu po\u021bi debloca domeniul sau nu po\u021bi accesa email-ul de aprobare, nu ai o problem\u0103 DNS. Ai o problem\u0103 de recuperare cont. Rezolv\u0103 asta mai \u00eent\u00e2i.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Stabile\u0219te o linie de baz\u0103 pentru DNS-ul t\u0103u \u00eenainte s\u0103 atingi orice<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Chiar dac\u0103 planifici un transfer doar de registrar, ia o linie de baz\u0103. \u00ce\u021bi ofer\u0103 o referin\u021b\u0103 dac\u0103 se \u00eent\u00e2mpl\u0103 ceva nea\u0219teptat, cum ar fi o schimbare de nameserver pe care nu ai inten\u021bionat-o. Pentru cutover-uri DNS, liniile de baz\u0103 sunt obligatorii. A\u0219a dovede\u0219ti paritatea \u00eenregistr\u0103rilor.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cencepe cu nameserver-ele pentru c\u0103 nameserver-ele controleaz\u0103 delegarea. Dac\u0103 delegarea se schimb\u0103, totul se schimb\u0103. Apoi stabile\u0219te linia de baz\u0103 pentru \u00eenregistr\u0103rile care conduc web-ul \u0219i mail-ul. Salveaz\u0103 acest output \u00eentr-un ticket de schimbare sau o not\u0103 \u00een vault-ul de parole ca s\u0103 po\u021bi compara rapid mai t\u00e2rziu.<\/p>\n\n\n\n<pre class=\"wp-block-code\">de># Delegare\ndig +noall +answer example.com NS\n\n# Puncte de intrare web \u0219i app\ndig +noall +answer example.com A\ndig +noall +answer example.com AAAA\ndig +noall +answer www.example.com CNAME\n\n# Rutare mail \u0219i autentificare mail\ndig +noall +answer example.com MX\ndig +noall +answer example.com TXT\ndig +noall +answer _dmarc.example.com TXT<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 publici DKIM, nu uita c\u0103 selectoarele tr\u0103iesc sub selector._domainkey.example.com. Multe dashboard-uri DNS ascund acestea \u00een spatele filtrelor, iar oamenii copiaz\u0103 doar \u00eenregistr\u0103rile TXT evidente de la r\u0103d\u0103cin\u0103. Acea gre\u0219eal\u0103 este unul dintre motivele principale pentru care livrabilitatea se degradeaz\u0103 dup\u0103 o mutare DNS.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 vrei s\u0103 \u00een\u021belegi tipurile de \u00eenregistr\u0103ri \u00eenainte s\u0103 copiezi ceva, folose\u0219te ghidul nostru intern: <a href=\"https:\/\/www.enginyring.com\/ro\/blog\/ce-este-o-inregistrare-dns-un-ghid-pentru-incepatori-despre-agenda-telefonica-a-internetului\">Ce este o \u00eenregistrare DNS<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">TTL nu este magie, dar este o p\u00e2rghie util\u0103<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">TTL controleaz\u0103 c\u00e2t timp resolver-ele cache-uiesc un r\u0103spuns DNS. TTL conteaz\u0103 doar c\u00e2nd schimbi r\u0103spunsurile. Dac\u0103 p\u0103strezi nameserver-ele \u0219i con\u021binutul zonei neschimbate, TTL nu afecteaz\u0103 un transfer doar de registrar pentru c\u0103 nu exist\u0103 nimic pentru cache-uri de re\u00eemprosp\u0103tat.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">TTL conteaz\u0103 pentru schimb\u0103rile de nameserver \u0219i schimb\u0103rile de \u00eenregistr\u0103ri. Gre\u0219eala pe care o vedem este cobor\u00e2rea TTL-ului cu zece minute \u00eenainte de un cutover \u0219i a\u0219teptarea ca internetul s\u0103 urmeze imediat. Un resolver poate respecta TTL-ul mai scurt doar dup\u0103 ce a interogat din nou \u0219i a \u00eenv\u0103\u021bat acea nou\u0103 valoare TTL. De aceea cobor\u00e2m TTL-ul cu 24 p\u00e2n\u0103 la 48 de ore \u00eenainte de un cutover planificat c\u00e2nd avem nevoie de convergen\u021b\u0103 rapid\u0103.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Pentru cutover-uri de afaceri mici, 300 de secunde (5 minute) este un TTL temporar practic pentru c\u0103 balanseaz\u0103 re\u00eemprosp\u0103tarea mai rapid\u0103 cu volum acceptabil de interog\u0103ri. Dup\u0103 ce migrarea se stabilizeaz\u0103, ridic\u0103 TTL-ul \u00eenapoi la 3600 de secunde (1 or\u0103) sau mai mult pentru a reduce \u00eenc\u0103rcarea DNS \u0219i a reduce sensibilitatea la probleme DNS authoritative tranzitorii.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Perspectiv\u0103 opera\u021bional\u0103 care cauzeaz\u0103 durere real\u0103: cache-uirea negativ\u0103 este real\u0103. Dac\u0103 un resolver prime\u0219te NXDOMAIN pentru un hostname, poate cache-ui acel rezultat negativ conform RFC 2308. Dac\u0103 adaugi \u00eenregistrarea lips\u0103 mai t\u00e2rziu, unii utilizatori vor vedea \u00een continuare e\u0219ec p\u00e2n\u0103 c\u00e2nd acel cache negativ expir\u0103. De aceea paritatea \u00eenregistr\u0103rilor \u00eenainte de o schimbare de nameserver conteaz\u0103. Previne ca \u00eenregistr\u0103rile lips\u0103 s\u0103 devin\u0103 \u00eentreruperi \u00eent\u00e2rziate.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Runbook Calea A: transfer doar de registrar cu nameservere neschimbate<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Aceasta este calea cu risc sc\u0103zut. Transferi \u00eenregistrarea, p\u0103strezi DNS-ul neatins \u0219i utilizatorii t\u0103i nu ar trebui s\u0103 vad\u0103 nicio schimbare. C\u00e2nd rul\u0103m aceasta pentru clien\u021bi, focusul este pe acces, momentul confirm\u0103rii \u0219i validare post-transfer.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">F\u0103 aceasta<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\u00cengheaz\u0103 edit\u0103rile DNS nerela\u021bionate \u00een timpul ferestrei de transfer.<\/li>\n<li>Noteaz\u0103 nameserver-ele tale curente din output-ul liniei de baz\u0103.<\/li>\n<li>Deblocheaz\u0103 domeniul la registrar-ul cedent \u0219i ob\u021bine Auth-Code.<\/li>\n<li>Ini\u021biaz\u0103 transferul la registrar-ul primitiv folosind Auth-Code.<\/li>\n<li>Aprob\u0103 prompt orice email-uri de transfer.<\/li>\n<li>Dup\u0103 finalizare, confirm\u0103 c\u0103 nameserver-ele sunt neschimbate \u0219i \u00eenregistr\u0103rile principale \u00eenc\u0103 se potrivesc cu linia de baz\u0103.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Fii atent la aceast\u0103 capcan\u0103 UI<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Unii registrari prezint\u0103 un set implicit de nameservere \u00een timpul configur\u0103rii transferului, adesea \u00eempachetat cu hosting-ul lor DNS. Dac\u0103 \u00eel accep\u021bi din gre\u0219eal\u0103, ai transformat un transfer doar de registrar \u00eentr-un cutover DNS. Dac\u0103 nu ai paritate de \u00eenregistr\u0103ri preg\u0103tit\u0103, acolo \u00eencepe downtime-ul.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 vrei Calea A executat\u0103 ca o schimbare controlat\u0103 cu validare, ENGINYRING <a href=\"https:\/\/www.enginyring.com\/ro\/domains\">Domenii<\/a> este construit exact pentru aceasta. Valoarea nu este ap\u0103sarea unui buton de transfer. Valoarea este men\u021binerea deleg\u0103rii stabile \u0219i prinderea surprizelor rapid.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Runbook Calea B: schimbarea nameserver-elor f\u0103r\u0103 downtime<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Calea B este unde oamenii se ard. O schimbare de nameserver este o migrare DNS. Migr\u0103rile DNS e\u0219ueaz\u0103 c\u00e2nd zona nou\u0103 nu se potrive\u0219te cu zona veche. Treaba ta este s\u0103 faci ca noile nameservere authoritative s\u0103 r\u0103spund\u0103 exact ca cele vechi \u00eenainte de a schimba delegarea.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Facem aceasta ca un proiect de paritate, nu ca un experiment live. Construie\u0219ti, verifici, apoi schimbi. Nu schimbi \u0219i apoi construie\u0219ti.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Pasul 1: construie\u0219te un inventar complet<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Listeaz\u0103 fiecare hostname pe care afacerea ta \u00eel folose\u0219te. Include eviden\u021bele \u0219i cele enervante. Multe \u00eentreruperi reale sunt cauzate de hostname-uri lips\u0103 care nu sunt folosite \u00een fiecare minut, precum api, webhook, status, autodiscover sau o \u00eenregistrare de validare pentru o integrare de serviciu.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Apex \u0219i www<\/li>\n<li>Hostname-uri app \u0219i API<\/li>\n<li>Hostname-uri mail (mail, smtp, imap, pop3)<\/li>\n<li>Hostname-uri autoconfig \u0219i autodiscover pentru clien\u021bi email<\/li>\n<li>\u00cenregistr\u0103ri de validare precum _acme-challenge pentru Let&#8217;s Encrypt<\/li>\n<li>Orice subzone delegate care folosesc propriile \u00eenregistr\u0103ri NS<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Apoi inventariaz\u0103 tipurile de \u00eenregistr\u0103ri: A, AAAA, CNAME, MX, TXT, SRV, CAA \u0219i \u00eenregistr\u0103ri NS pentru deleg\u0103ri. Dac\u0103 host-ul t\u0103u DNS curent suport\u0103 export de zon\u0103 (AXFR sau desc\u0103rcare fi\u0219ier zon\u0103), folose\u0219te-l. Dac\u0103 nu, copiaz\u0103 \u00eenregistr\u0103rile sistematic \u0219i verific\u0103 totul de dou\u0103 ori. Trateaz\u0103 aceasta ca migrarea unui ruleset de firewall. Lipsirea unei linii poate strica un flux critic.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Pasul 2: paritatea \u00eenregistr\u0103rilor email este non-negociabil\u0103<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Email-ul este unde migr\u0103rile e\u0219ueaz\u0103 \u00een t\u0103cere. O \u00eenregistrare A lips\u0103 stric\u0103 site-ul t\u0103u vizibil. Un selector DKIM lips\u0103 sau o politic\u0103 DMARC stricat\u0103 poate reduce livrabilitatea \u00een t\u0103cere, iar vei descoperi mai t\u00e2rziu c\u00e2nd facturile sau reset\u0103rile de parol\u0103 nu sosesc. Protejeaz\u0103 MX, SPF, selectoarele DKIM \u0219i DMARC.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 echipa ta nu vrea s\u0103 opereze infrastructur\u0103 mail, nu ar trebui s\u0103 folose\u0219ti o migrare DNS ca momentul s\u0103 o \u00eenve\u021bi. ENGINYRING <a href=\"https:\/\/www.enginyring.com\/ro\/mailhosting\">Hosting Mail<\/a> exist\u0103 pentru echipele care au nevoie ca mail-ul s\u0103 func\u021bioneze f\u0103r\u0103 a de\u021bine fiecare detaliu al opera\u021biunilor mail.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Perspectiv\u0103 opera\u021bional\u0103: p\u0103streaz\u0103 suprapunere c\u00e2nd schimbi \u021bintele MX. Sistemele de primire re\u00eencearc\u0103 livrarea timp de 24-48 de ore sau mai mult. Dac\u0103 tai MX \u0219i \u00eenchizi destina\u021bia veche prea devreme, po\u021bi pierde mesaje care erau deja \u00een zbor. Planific\u0103 suprapunere sau forwarding astfel \u00eenc\u00e2t re\u00eencerc\u0103rile s\u0103 aterizeze \u00een continuare \u00een siguran\u021b\u0103.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Pasul 3: valideaz\u0103 noile servere authoritative direct<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cenainte de a schimba nameserver-ele la registrar, interogheaz\u0103 noile nameservere authoritative direct. Nu te baza pe r\u0103spunsuri cache-uite. Compar\u0103 vechi versus nou pentru \u00eenregistr\u0103rile care conteaz\u0103. Dac\u0103 r\u0103spunsurile nu se potrivesc, nu schimba. Remediaz\u0103 paritatea mai \u00eent\u00e2i.<\/p>\n\n\n\n<pre class=\"wp-block-code\">de>OLD_NS=ns1.old-dns.example\nNEW_NS=ns1.new-dns.example\n\ndig @$OLD_NS +noall +answer example.com A\ndig @$NEW_NS +noall +answer example.com A\n\ndig @$OLD_NS +noall +answer example.com MX\ndig @$NEW_NS +noall +answer example.com MX\n\ndig @$OLD_NS +noall +answer _dmarc.example.com TXT\ndig @$NEW_NS +noall +answer _dmarc.example.com TXT<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Pasul 4: schimb\u0103 delegarea, apoi p\u0103streaz\u0103 DNS-ul vechi activ<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Odat\u0103 ce paritatea este dovedit\u0103 \u0219i TTL-ul a fost cobor\u00e2t din timp, schimb\u0103 nameserver-ele la registrar. Dup\u0103 schimbare, p\u0103streaz\u0103 zona DNS veche online cel pu\u021bin 48 de ore. Este asigurare ieftin\u0103. \u00ce\u021bi ofer\u0103 rollback dac\u0103 descoperi o \u00eenregistrare lips\u0103 de care doar un flux de lucru specific are nevoie.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Perspectiv\u0103 opera\u021bional\u0103: multe echipe decomisioneaz\u0103 DNS-ul vechi prea repede. Schimb\u0103, testeaz\u0103 de pe o re\u021bea de birou \u0219i \u00eenchid zona veche. Apoi un partener raporteaz\u0103 un e\u0219ec de pe o re\u021bea diferit\u0103 pentru c\u0103 \u00eenc\u0103 foloseau delegarea cache-uit\u0103. P\u0103strarea zonei vechi active previne aceast\u0103 clas\u0103 de probleme evitabile.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">DNSSEC poate face e\u0219ecurile s\u0103 par\u0103 aleatoare<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 DNSSEC este activat, o schimbare de nameserver devine mai complex\u0103. DNSSEC adaug\u0103 un lan\u021b de \u00eencredere folosind semn\u0103turi criptografice. Dac\u0103 \u00eenregistrarea DS \u00een zona p\u0103rinte nu se potrive\u0219te cu DNSKEY din zona ta, resolver-ele care valideaz\u0103 vor respinge r\u0103spunsurile tale. Asta poate ar\u0103ta ca downtime par\u021bial pentru c\u0103 unele resolvere valideaz\u0103 \u0219i altele nu.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Exist\u0103 dou\u0103 abord\u0103ri sigure.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>P\u0103streaz\u0103 DNSSEC neschimbat.<\/strong> Aceasta func\u021bioneaz\u0103 doar dac\u0103 operatorul t\u0103u DNS \u0219i cheile de semnare r\u0103m\u00e2n consistente pe parcursul migr\u0103rii.<\/li>\n<li><strong>Planific\u0103 tranzi\u021bia DNSSEC.<\/strong> Coordoneaz\u0103 actualiz\u0103rile \u00eenregistr\u0103rii DS la nivelul registrar-ului sau registrului cu noul operator DNS. Noile nameservere trebuie s\u0103 serveasc\u0103 \u00eenregistr\u0103ri RRSIG semnate cu chei care se potrivesc cu \u00eenregistr\u0103rile DS din p\u0103rinte. Dac\u0103 nu po\u021bi coordona corect, dezactiveaz\u0103 DNSSEC \u00eenainte de schimbarea nameserver-ului \u0219i reactiveaz\u0103-l dup\u0103 ce validezi zona nou\u0103 \u0219i semnarea ei.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 nu e\u0219ti sigur care abordare se aplic\u0103 configura\u021biei tale, nu ghici. Acesta este un punct de decizie clasic unde ajutorul administrat previne o \u00eentrerupere greu de depanat.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">\u00cenregistr\u0103ri glue: capcana nameserver-ului in-domain care stric\u0103 totul<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 nameserver-ele tale authoritative sunt \u00een interiorul domeniului t\u0103u (in-bailiwick), precum ns1.example.com \u0219i ns2.example.com, te bazezi pe \u00eenregistr\u0103ri glue. Glue ofer\u0103 adresa IP a nameserver-ului la nivel p\u0103rinte astfel \u00eenc\u00e2t resolver-ele s\u0103 poat\u0103 ajunge la nameserver chiar \u00eenainte ca zona \u00eens\u0103\u0219i s\u0103 poat\u0103 fi rezolvat\u0103. F\u0103r\u0103 glue, exist\u0103 o dependen\u021b\u0103 circular\u0103: resolver-ele au nevoie de nameserver pentru a rezolva domeniul, dar trebuie s\u0103 rezolve domeniul pentru a g\u0103si nameserver-ul.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 migrezi DNS-ul \u0219i schimbi IP-urile nameserver-elor in-domain, trebuie s\u0103 actualizezi glue la registrar sau registru. Uitarea glue poate crea e\u0219ec total de rezolvare pentru c\u0103 resolver-ele nu pot ajunge la nameserver-ele tale pentru a \u00eenv\u0103\u021ba zona.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Perspectiv\u0103 opera\u021bional\u0103: c\u00e2nd glue este implicat, nu comprima cronologia. F\u0103 schimb\u0103ri cu un plan, verific\u0103 starea glue folosind dig +trace sau whois, \u0219i p\u0103streaz\u0103 infrastructura veche activ\u0103 p\u00e2n\u0103 po\u021bi dovedi stabilitate pe mai multe resolvere externe.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Re\u00eennoirea certificatelor: ce stric\u0103 migr\u0103rile DNS mai t\u00e2rziu<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Unele gre\u0219eli de migrare nu dor imediat. Dor la momentul re\u00eennoirii. Dou\u0103 tipuri de \u00eenregistr\u0103ri sunt vinovate comune: CAA \u0219i _acme-challenge.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cenregistr\u0103rile CAA restric\u021bioneaz\u0103 care autorit\u0103\u021bi de certificare pot emite certificate pentru domeniul t\u0103u. Copiaz\u0103 CAA cu aten\u021bie. Dac\u0103 o omi\u021bi, schimbi controalele de emitere. Dac\u0103 o copiezi gre\u0219it, po\u021bi bloca emiterea \u0219i strica re\u00eennoirile.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 folose\u0219ti validare ACME bazat\u0103 pe DNS (precum provocarea DNS-01 Let&#8217;s Encrypt), vei avea \u00eenregistr\u0103ri _acme-challenge. Ele pot fi dinamice, dar abilitatea de a le publica trebuie s\u0103 r\u0103m\u00e2n\u0103. Dac\u0103 automatizarea ta depinde de aceste \u00eenregistr\u0103ri \u0219i cutover-ul t\u0103u DNS stric\u0103 fluxul de lucru, certificatele tale vor expira mai t\u00e2rziu. De aceea trat\u0103m aceste \u00eenregistr\u0103ri ca critice \u0219i test\u0103m c\u0103ile de re\u00eennoire dup\u0103 o migrare.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Validare post-schimbare: testeaz\u0103 ca utilizatorii t\u0103i, nu ca biroul t\u0103u<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Dup\u0103 un transfer de registrar sau o schimbare de nameserver, valideaz\u0103 din exterior. Testarea de pe o singur\u0103 re\u021bea poate ascunde e\u0219ecuri pentru c\u0103 resolver-ul t\u0103u ar putea avea \u00eenc\u0103 r\u0103spunsuri cache-uite. Valid\u0103m delegarea, accesibilitatea web \u0219i rutarea mail de pe mai multe resolvere.<\/p>\n\n\n\n<pre class=\"wp-block-code\">de># Delegare\ndig +short NS example.com\n\n# \u00cenregistr\u0103ri web\ndig +short A example.com\ndig +short A www.example.com\ndig +short AAAA example.com\n\n# Rutare mail \u0219i auth\ndig +short MX example.com\ndig +short TXT example.com\ndig +short TXT _dmarc.example.com\n\n# Verificare sanity HTTP\ncurl -I https:\/\/example.com\/\ncurl -I https:\/\/www.example.com\/<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 vezi inconsisten\u021b\u0103, nu te agita. Identific\u0103 nameserver-ele authoritative, interogheaz\u0103-le direct \u0219i compar\u0103 cu linia ta de baz\u0103. Remediaz\u0103 c\u00e2te o \u00eenregistrare lips\u0103 la un moment dat. Schimb\u0103rile aleatorii sunt cum transformi o problem\u0103 mic\u0103 \u00eentr-un incident prelungit.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Un \u0219ablon de fereastr\u0103 de schimbare pe care \u00eel po\u021bi refolosi<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Aceast\u0103 structur\u0103 func\u021bioneaz\u0103 pentru majoritatea afacerilor mici \u0219i mijlocii care vor risc minim.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Cu 48 de ore \u00eenainte: dac\u0103 vei schimba nameserver-ele, coboar\u0103 TTL-ul pe \u00eenregistr\u0103rile cheie la 300 de secunde.<\/li>\n<li>Cu 24 de ore \u00eenainte: construie\u0219te zona nou\u0103, confirm\u0103 paritatea \u0219i testeaz\u0103 r\u0103spunsurile authoritative direct.<\/li>\n<li>Start fereastr\u0103 schimbare: \u00eengheaz\u0103 edit\u0103rile DNS nerela\u021bionate \u0219i confirm\u0103 accesul la conturile registrar.<\/li>\n<li>Execut\u0103: finalizeaz\u0103 transferul registrar, apoi schimb\u0103 nameserver-ele doar dac\u0103 paritatea este dovedit\u0103.<\/li>\n<li>Imediat dup\u0103: valideaz\u0103 NS, web \u0219i mail de pe re\u021bele externe.<\/li>\n<li>Urm\u0103toarele 48 de ore: p\u0103streaz\u0103 DNS-ul vechi online, monitorizeaz\u0103 \u0219i abia apoi decomisioneaz\u0103 DNS-ul vechi.<\/li>\n<li>Dup\u0103 7 zile: ridic\u0103 TTL-ul \u00eenapoi la 3600 de secunde sau valoarea ta normal\u0103.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 mu\u021bi \u0219i hosting-ul, \u00eemparte asta \u00eentr-o faz\u0103 separat\u0103. F\u0103 munca registrar mai \u00eent\u00e2i. F\u0103 cutover-ul DNS mai apoi. Apoi mut\u0103 aplica\u021bia \u0219i serverele mail, dac\u0103 este necesar. Dac\u0103 combini schimb\u0103ri de hosting cu o schimbare de nameserver, rollback-ul devine neclar pentru c\u0103 nu po\u021bi spune dac\u0103 e\u0219ecul este DNS sau serverul nou.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">C\u00e2nd chiar trebuie s\u0103 mu\u021bi workload-uri, ENGINYRING <a href=\"https:\/\/www.enginyring.com\/ro\/virtual-servers\">Servere Virtuale<\/a> sunt o baz\u0103 curat\u0103 pentru migr\u0103ri controlate. Putem proviziona un VPS nou, muta aplica\u021bia cu o fereastr\u0103 de suprapunere \u0219i abia apoi actualiza \u00eenregistr\u0103rile DNS. Acea secven\u021b\u0103 previne edit\u0103ri DNS de urgen\u021b\u0103 \u00een timpul unei mut\u0103ri de server.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">C\u00e2nd ar trebui s\u0103 opre\u0219ti DIY \u0219i s\u0103 predai<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Unele transferuri sunt sarcini DIY sigure. Altele nu sunt. Dac\u0103 oricare dintre acestea este adev\u0103rat, trateaz\u0103 munca ca o schimbare administrat\u0103:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Rulezi ecommerce, abonamente pl\u0103tite sau un portal pentru clien\u021bi unde downtime-ul \u00eenseamn\u0103 venituri pierdute.<\/li>\n<li>Afacerea ta depinde de email pentru facturi, reset\u0103ri de parol\u0103 \u0219i primire suport.<\/li>\n<li>DNSSEC este activat \u0219i schimbi operatori DNS.<\/li>\n<li>Zona ta DNS are multe \u00eenregistr\u0103ri \u0219i nu e\u0219ti sigur ce fac toate.<\/li>\n<li>Folose\u0219ti automatizare de certificate \u0219i nu \u00ee\u021bi po\u021bi permite e\u0219ec de re\u00eennoire mai t\u00e2rziu.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">La acel punct, riscul nu este formularul de transfer. Riscul este execu\u021bia opera\u021bional\u0103. Dac\u0103 vrei s\u0103 fie f\u0103cut cu un plan, validare \u0219i rollback, folose\u0219te ENGINYRING <a href=\"https:\/\/www.enginyring.com\/ro\/domains\">Domenii<\/a>. Evi\u021bi capcanele cele mai comune: schimb\u0103ri accidentale de nameserver, \u00eenregistr\u0103ri TXT lips\u0103, autentificare mail stricat\u0103 \u0219i nepotriviri DNSSEC.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 vrei lectur\u0103 de sus\u021binere din propriul nostru blog, aceste post\u0103ri completeaz\u0103 conceptele care cauzeaz\u0103 majoritatea gre\u0219elilor de migrare: <a href=\"https:\/\/www.enginyring.com\/ro\/blog\/cum-sa-cumperi-un-nume-de-domeniu-inceputul-succesului-afacerii-tale\">Cum s\u0103 cumperi un nume de domeniu<\/a>, <a href=\"https:\/\/www.enginyring.com\/ro\/blog\/ce-este-confidentialitatea-whois-ghid-complet-despre-protectia-datelor-pentru-domenii\">Ce este confiden\u021bialitatea WHOIS<\/a>, <a href=\"https:\/\/www.enginyring.com\/ro\/blog\/ghidul-incepatorului-pentru-securitatea-dns-de-ce-este-importanta-pentru-site-ul-tau\">Bazele securit\u0103\u021bii DNS<\/a> \u0219i <a href=\"https:\/\/www.enginyring.com\/ro\/blog\/ghidul-livrarii-emailurilor-de-ce-gazduirea-web-iti-poate-garanta-succesul-in-comunicare\">Ghid livrabilitate email<\/a>.<\/p>\n\n","protected":false},"excerpt":{"rendered":"<p>Po\u021bi transfera un domeniu la un nou registrar f\u0103r\u0103 downtime dac\u0103 men\u021bii DNS-ul autoritativ al domeniului neschimbat \u00een timpul transferului. Site-ul \u0219i email-ul t\u0103u r\u0103m\u00e2n online at\u00e2ta timp c\u00e2t nameserver-ele \u0219i \u00eenregistr\u0103rile DNS din spatele lor nu se schimb\u0103. Downtime-ul apare c\u00e2nd combini un transfer de registrar cu o schimbare de nameserver sau o reconstruire [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":2129,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9],"tags":[12977,12980,12978,12993,12982,12989,12974,12987,12975,12976,13004,12991,12970,12979,13008,12949,13012,13009,13002,12997,13001,13000,12994,13007,12999,12998,12996,12995,12988,12983,12984,12985,13011,12992,13005,12981,13006,12971,12986,12972,12973,13010,12990,13003],"class_list":["post-2131","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-tutorials","tag-auth-code-transfer-domeniu","tag-blocare-transfer-domeniu-60-zile","tag-blocare-transfer-schimbare-titular","tag-cache-negativ-dns-nxdomain","tag-checklist-migrare-dns","tag-checklist-migrare-dnssec","tag-checklist-transfer-domeniu","tag-coborare-ttl-inainte-schimbare-dns","tag-cod-autorizare-transfer","tag-cod-epp-transfer-domeniu","tag-configurare-inregistrare-spf","tag-copiere-inregistrari-dns-in-siguranta","tag-cum-sa-transferi-un-domeniu","tag-deblocare-domeniu-pentru-transfer","tag-dig-trace-inregistrari-glue","tag-dnskey-ds-rrsig","tag-email-aprobare-transfer-domeniu","tag-hosting-dns-administrat","tag-inregistrare-_acme-challenge","tag-inregistrare-caa-emitere-certificat","tag-inregistrare-provocare-acme-dns","tag-inregistrare-selector-dkim","tag-inregistrari-glue-nameservere","tag-migrare-dns-profesionala","tag-migrare-inregistrare-mx","tag-nameserver-in-bailiwick","tag-nameserver-in-domain-glue","tag-nepotrivire-inregistrare-ds-dnssec","tag-paritate-inregistrari-dns","tag-pastrare-nameservere-in-timpul-transferului","tag-plan-cutover-dns","tag-planificare-ttl-dns","tag-politica-transfer-icann","tag-rfc-2308-cache-negativ","tag-schimbare-dns-livrabilitate-email","tag-schimbare-nameservere-fara-downtime","tag-serviciu-transfer-domeniu-administrat","tag-transfer-domeniu-fara-downtime","tag-transfer-domeniu-fara-schimbare-dns","tag-transfer-domeniu-la-registrar-nou","tag-transfer-registrar-domeniu","tag-transfer-zona-axfr","tag-verificare-dns-cu-dig","tag-verificare-inregistrare-dmarc"],"_links":{"self":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2131","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2131"}],"version-history":[{"count":1,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2131\/revisions"}],"predecessor-version":[{"id":2132,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2131\/revisions\/2132"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/media\/2129"}],"wp:attachment":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2131"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2131"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2131"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}