{"id":3995,"date":"2026-01-02T16:59:34","date_gmt":"2026-01-02T13:59:34","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/alan-adini-farkli-kayit-firmasina-transfer-etmek-epp-dns-ve-e-postayi-kesintisiz-tasimak\/"},"modified":"2026-01-02T16:59:34","modified_gmt":"2026-01-02T13:59:34","slug":"alan-adini-farkli-kayit-firmasina-transfer-etmek-epp-dns-ve-e-postayi-kesintisiz-tasimak","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/alan-adini-farkli-kayit-firmasina-transfer-etmek-epp-dns-ve-e-postayi-kesintisiz-tasimak\/","title":{"rendered":"Alan Ad\u0131n\u0131 Farkl\u0131 Kay\u0131t Firmas\u0131na Transfer Etmek: EPP, DNS ve E\u2011Postay\u0131 Kesintisiz Ta\u015f\u0131mak"},"content":{"rendered":"<div class=\"dchost-blog-content-wrapper\"><div id=\"toc_container\" class=\"toc_transparent no_bullets\"><p class=\"toc_title\">\u0130&ccedil;indekiler<\/p><ul class=\"toc_list\"><li><a href=\"#Alan_adini_farkli_kayit_firmasina_transfer_etmek_neden_bu_kadar_kritik\"><span class=\"toc_number toc_depth_1\">1<\/span> Alan ad\u0131n\u0131 farkl\u0131 kay\u0131t firmas\u0131na transfer etmek neden bu kadar kritik?<\/a><\/li><li><a href=\"#Neden_alan_adini_farkli_kayit_firmasina_transfer_edersiniz\"><span class=\"toc_number toc_depth_1\">2<\/span> Neden alan ad\u0131n\u0131 farkl\u0131 kay\u0131t firmas\u0131na transfer edersiniz?<\/a><\/li><li><a href=\"#Transfer_oncesi_kritik_kontrol_listesi_sureler_zamanlama_ve_riskler\"><span class=\"toc_number toc_depth_1\">3<\/span> Transfer \u00f6ncesi kritik kontrol listesi: s\u00fcreler, zamanlama ve riskler<\/a><ul><li><a href=\"#1_Alan_adinin_suresi_ve_yenileme_penceresi\"><span class=\"toc_number toc_depth_2\">3.1<\/span> 1. Alan ad\u0131n\u0131n s\u00fcresi ve yenileme penceresi<\/a><\/li><li><a href=\"#2_60_gunluk_transfer_kisiti_ve_yeni_kayitlar\"><span class=\"toc_number toc_depth_2\">3.2<\/span> 2. 60 g\u00fcnl\u00fck transfer k\u0131s\u0131t\u0131 ve yeni kay\u0131tlar<\/a><\/li><li><a href=\"#3_Whois_ve_iletisim_epostasi_dogrulugu\"><span class=\"toc_number toc_depth_2\">3.3<\/span> 3. Whois ve ileti\u015fim e\u2011postas\u0131 do\u011frulu\u011fu<\/a><\/li><li><a href=\"#4_SSL_SEO_ve_yonlendirmeler\"><span class=\"toc_number toc_depth_2\">3.4<\/span> 4. SSL, SEO ve y\u00f6nlendirmeler<\/a><\/li><\/ul><\/li><li><a href=\"#EPP_Auth_kodu_ve_transfer_kilidi_Transferin_kalbi\"><span class=\"toc_number toc_depth_1\">4<\/span> EPP (Auth) kodu ve transfer kilidi: Transferin kalbi<\/a><ul><li><a href=\"#Transfer_kilidi_Registrar_Lock_nedir\"><span class=\"toc_number toc_depth_2\">4.1<\/span> Transfer kilidi (Registrar Lock) nedir?<\/a><\/li><li><a href=\"#EPP_Auth_kodu_nedir_nasil_alinir\"><span class=\"toc_number toc_depth_2\">4.2<\/span> EPP (Auth) kodu nedir, nas\u0131l al\u0131n\u0131r?<\/a><\/li><li><a href=\"#Iki_faktorlu_dogrulama_ve_hesap_guvenligi\"><span class=\"toc_number toc_depth_2\">4.3<\/span> \u0130ki fakt\u00f6rl\u00fc do\u011frulama ve hesap g\u00fcvenli\u011fi<\/a><\/li><\/ul><\/li><li><a href=\"#DNS_stratejisi_Transfer_sirasinda_sitenizi_online_tutmak\"><span class=\"toc_number toc_depth_1\">5<\/span> DNS stratejisi: Transfer s\u0131ras\u0131nda sitenizi online tutmak<\/a><ul><li><a href=\"#DNSin_temellerini_hatirlayalim\"><span class=\"toc_number toc_depth_2\">5.1<\/span> DNS\u2019in temellerini hat\u0131rlayal\u0131m<\/a><\/li><li><a href=\"#Nameserver_NS_ve_DNS_barindirma_karari\"><span class=\"toc_number toc_depth_2\">5.2<\/span> Nameserver (NS) ve DNS bar\u0131nd\u0131rma karar\u0131<\/a><\/li><li><a href=\"#TTL_planlamasi_ve_DNS_yayilimini_yonetmek\"><span class=\"toc_number toc_depth_2\">5.3<\/span> TTL planlamas\u0131 ve DNS yay\u0131l\u0131m\u0131n\u0131 y\u00f6netmek<\/a><\/li><li><a href=\"#Senaryo_1_Sadece_domain_registrari_degisiyor_hosting_ayni_kaliyor\"><span class=\"toc_number toc_depth_2\">5.4<\/span> Senaryo 1: Sadece domain registrar\u0131 de\u011fi\u015fiyor, hosting ayn\u0131 kal\u0131yor<\/a><\/li><li><a href=\"#Senaryo_2_Hem_domain_hem_hosting_DCHosta_tasiniyor\"><span class=\"toc_number toc_depth_2\">5.5<\/span> Senaryo 2: Hem domain hem hosting DCHost\u2019a ta\u015f\u0131n\u0131yor<\/a><\/li><\/ul><\/li><li><a href=\"#Epostayi_kesintisiz_tasimak_MX_SPF_DKIM_ve_zamanlama\"><span class=\"toc_number toc_depth_1\">6<\/span> E\u2011postay\u0131 kesintisiz ta\u015f\u0131mak: MX, SPF, DKIM ve zamanlama<\/a><ul><li><a href=\"#Eposta_altyapinizi_haritalandirin\"><span class=\"toc_number toc_depth_2\">6.1<\/span> E\u2011posta altyap\u0131n\u0131z\u0131 haritaland\u0131r\u0131n<\/a><\/li><li><a href=\"#Kutulari_onceden_olusturun_ve_IMAP_senkronizasyonu_planlayin\"><span class=\"toc_number toc_depth_2\">6.2<\/span> Kutular\u0131 \u00f6nceden olu\u015fturun ve IMAP senkronizasyonu planlay\u0131n<\/a><\/li><li><a href=\"#MX_ve_SPF_degisikligini_dogru_zamanda_yapmak\"><span class=\"toc_number toc_depth_2\">6.3<\/span> MX ve SPF de\u011fi\u015fikli\u011fini do\u011fru zamanda yapmak<\/a><\/li><li><a href=\"#DKIM_ve_DMARCi_unutmamak\"><span class=\"toc_number toc_depth_2\">6.4<\/span> DKIM ve DMARC\u2019\u0131 unutmamak<\/a><\/li><\/ul><\/li><li><a href=\"#Adim_adim_tam_transfer_akisi_EPP_DNS_ve_eposta_birlikte\"><span class=\"toc_number toc_depth_1\">7<\/span> Ad\u0131m ad\u0131m tam transfer ak\u0131\u015f\u0131: EPP, DNS ve e\u2011posta birlikte<\/a><ul><li><a href=\"#1_Envanter_ve_sure_kontrolu\"><span class=\"toc_number toc_depth_2\">7.1<\/span> 1. Envanter ve s\u00fcre kontrol\u00fc<\/a><\/li><li><a href=\"#2_TTL_dusurme_asamasi\"><span class=\"toc_number toc_depth_2\">7.2<\/span> 2. TTL d\u00fc\u015f\u00fcrme a\u015famas\u0131<\/a><\/li><li><a href=\"#3_DCHost_tarafinda_yeni_ortami_hazirlama\"><span class=\"toc_number toc_depth_2\">7.3<\/span> 3. DCHost taraf\u0131nda yeni ortam\u0131 haz\u0131rlama<\/a><\/li><li><a href=\"#4_EPP_kodunu_alma_ve_transferi_baslatma\"><span class=\"toc_number toc_depth_2\">7.4<\/span> 4. EPP kodunu alma ve transferi ba\u015flatma<\/a><\/li><li><a href=\"#5_Transfer_devam_ederken_DNSi_sabit_tutmak\"><span class=\"toc_number toc_depth_2\">7.5<\/span> 5. Transfer devam ederken DNS\u2019i sabit tutmak<\/a><\/li><li><a href=\"#6_Transfer_tamamlandiktan_sonra_DNS_cutover\"><span class=\"toc_number toc_depth_2\">7.6<\/span> 6. Transfer tamamland\u0131ktan sonra DNS cutover<\/a><\/li><li><a href=\"#7_Web_sitesi_trafigini_yeni_sunucuya_almak\"><span class=\"toc_number toc_depth_2\">7.7<\/span> 7. Web sitesi trafi\u011fini yeni sunucuya almak<\/a><\/li><li><a href=\"#8_Eposta_trafigini_yeni_sunucuya_tasimak\"><span class=\"toc_number toc_depth_2\">7.8<\/span> 8. E\u2011posta trafi\u011fini yeni sunucuya ta\u015f\u0131mak<\/a><\/li><li><a href=\"#9_Izleme_ve_temizlik\"><span class=\"toc_number toc_depth_2\">7.9<\/span> 9. \u0130zleme ve temizlik<\/a><\/li><li><a href=\"#10_Guvenlik_son_dokunuslari\"><span class=\"toc_number toc_depth_2\">7.10<\/span> 10. G\u00fcvenlik son dokunu\u015flar\u0131<\/a><\/li><\/ul><\/li><li><a href=\"#DCHost_ile_alan_adi_ve_hosting_tasimayi_sadelestirmek\"><span class=\"toc_number toc_depth_1\">8<\/span> DCHost ile alan ad\u0131 ve hosting ta\u015f\u0131may\u0131 sadele\u015ftirmek<\/a><\/li><li><a href=\"#Sonuc_ve_onerilen_yol_haritasi\"><span class=\"toc_number toc_depth_1\">9<\/span> Sonu\u00e7 ve \u00f6nerilen yol haritas\u0131<\/a><\/li><\/ul><\/div>\n<h2><span id=\"Alan_adini_farkli_kayit_firmasina_transfer_etmek_neden_bu_kadar_kritik\">Alan ad\u0131n\u0131 farkl\u0131 kay\u0131t firmas\u0131na transfer etmek neden bu kadar kritik?<\/span><\/h2>\n<p>Alan ad\u0131 transferi, teknik olarak birka\u00e7 form ve bir EPP (Auth) kodundan ibaret gibi g\u00f6r\u00fcnse de pratikte web siteniz, e\u2011posta trafi\u011finiz ve markan\u0131z\u0131n dijital itibar\u0131 a\u00e7\u0131s\u0131ndan en riskli anlardan biridir. Yanl\u0131\u015f zamanda ba\u015flat\u0131lan bir transfer, hatal\u0131 DNS yap\u0131land\u0131rmas\u0131 veya g\u00f6zden ka\u00e7an bir MX kayd\u0131; web sitenizin saatlerce a\u00e7\u0131lmamas\u0131na, kurumsal e\u2011postalar\u0131n\u0131z\u0131n kaybolmas\u0131na ve hatta alan ad\u0131n\u0131z\u0131 ge\u00e7ici olarak kaybetmenize kadar giden zincirleme problemlere yol a\u00e7abilir. DCHost olarak sahada en \u00e7ok m\u00fcdahale etti\u011fimiz acil durumlar\u0131n \u00f6nemli bir k\u0131sm\u0131, plans\u0131z veya hatal\u0131 <a href=\"https:\/\/www.dchost.com\/tr\/alan-adi\/transfer-et\">alan ad\u0131 transfer<\/a>lerinden kaynaklan\u0131yor.<\/p>\n<p>Bu rehberde, <strong>alan ad\u0131n\u0131 farkl\u0131 kay\u0131t firmas\u0131na transfer etmek<\/strong> isteyen herkes i\u00e7in ad\u0131m ad\u0131m, riskleri minimize eden bir yol haritas\u0131 payla\u015faca\u011f\u0131z. EPP kodu nedir, transfer kilidi nas\u0131l kald\u0131r\u0131l\u0131r, DNS kay\u0131tlar\u0131 ve nameserver\u2019lar ne zaman de\u011fi\u015ftirilmelidir, e\u2011postay\u0131 kesintisiz ta\u015f\u0131mak i\u00e7in nas\u0131l bir MX ve SPF stratejisi izlemelisiniz; hepsini pratik senaryolarla anlataca\u011f\u0131z. Hedefimiz, transferi sadece ba\u015far\u0131yla tamamlamak de\u011fil; ayn\u0131 zamanda ziyaret\u00e7i ve e\u2011posta kayb\u0131 ya\u015famadan, yani ger\u00e7ekten <strong>kesintisiz<\/strong> ger\u00e7ekle\u015ftirebilmenizi sa\u011flamak.<\/p>\n<h2><span id=\"Neden_alan_adini_farkli_kayit_firmasina_transfer_edersiniz\">Neden alan ad\u0131n\u0131 farkl\u0131 kay\u0131t firmas\u0131na transfer edersiniz?<\/span><\/h2>\n<p>\u00d6nce motivasyonu netle\u015ftirelim. M\u00fc\u015fterilerimizin alan ad\u0131n\u0131 farkl\u0131 bir kay\u0131t firmas\u0131na, \u00e7o\u011fu zaman da bize, DCHost\u2019a transfer etmek istemesinin en yayg\u0131n nedenleri \u015funlar:<\/p>\n<ul>\n<li><strong>Fiyat ve \u015feffafl\u0131k:<\/strong> Yenileme \u00fccretleri ilk y\u0131l promosyonundan sonra beklenmedik \u015fekilde artabilir. Daha \u00f6ng\u00f6r\u00fclebilir ve \u015feffaf fiyatland\u0131rma i\u00e7in transfer tercih edilir.<\/li>\n<li><strong>T\u00fcm altyap\u0131y\u0131 tek elde toplama iste\u011fi:<\/strong> Domain, hosting, VPS, dedicated ve e\u2011posta servisleri farkl\u0131 yerlerde da\u011f\u0131n\u0131k oldu\u011funda y\u00f6netim zorla\u015f\u0131r. Hepsini DCHost alt\u0131nda toplamak operasyonel y\u00fck\u00fc ciddi bi\u00e7imde azalt\u0131r.<\/li>\n<li><strong>G\u00fcvenlik ve yetki y\u00f6netimi:<\/strong> \u0130ki fakt\u00f6rl\u00fc do\u011frulama (2FA), transfer kilidi, DNSSEC gibi \u00f6zellikleri daha rahat y\u00f6netmek i\u00e7in daha kurumsal ve g\u00fcvenlik odakl\u0131 bir kay\u0131t firmas\u0131 tercih edilir.<\/li>\n<li><strong>Destek kalitesi:<\/strong> DNS, SSL, e\u2011posta ve hosting taraf\u0131n\u0131 ayn\u0131 ekipten destek alarak y\u00f6netmek transfer motivasyonlar\u0131n\u0131n ba\u015f\u0131nda gelir.<\/li>\n<li><strong>Alan ad\u0131 portf\u00f6y\u00fcn\u00fc konsolide etme:<\/strong> Ajanslar ve \u00e7ok say\u0131da domain y\u00f6neten ekipler, onlarca alan ad\u0131n\u0131 tek panelden kolayca y\u00f6netmek i\u00e7in toplu transfer yapar.<\/li>\n<\/ul>\n<p>Motivasyon ne olursa olsun, teknik a\u00e7\u0131dan yap\u0131lmas\u0131 gerekenler hemen hemen ayn\u0131d\u0131r. \u00d6nemli olan, <strong>do\u011fru zamanlama<\/strong> ve <strong>do\u011fru s\u0131rayla ad\u0131m atmak<\/strong>.<\/p>\n<h2><span id=\"Transfer_oncesi_kritik_kontrol_listesi_sureler_zamanlama_ve_riskler\">Transfer \u00f6ncesi kritik kontrol listesi: s\u00fcreler, zamanlama ve riskler<\/span><\/h2>\n<p>Alan ad\u0131 transfer s\u00fcrecini g\u00fcvenli hale getirmek, ba\u015flamadan \u00f6nce birka\u00e7 temel kural\u0131 bilmekle ba\u015flar. \u00d6zellikle alan ad\u0131n\u0131n ya\u015fam d\u00f6ng\u00fcs\u00fc ve s\u00fcreler kritik \u00f6neme sahiptir.<\/p>\n<h3><span id=\"1_Alan_adinin_suresi_ve_yenileme_penceresi\">1. Alan ad\u0131n\u0131n s\u00fcresi ve yenileme penceresi<\/span><\/h3>\n<p>Alan ad\u0131n\u0131z\u0131n s\u00fcresi bitmeye yak\u0131nsa, transfer en riskli hale gelir. \u00c7\u00fcnk\u00fc:<\/p>\n<ul>\n<li>Bir\u00e7ok uzant\u0131da transfer s\u0131ras\u0131nda alan ad\u0131n\u0131n aktif olmas\u0131 gerekir; grace veya redemption d\u00f6nemine d\u00fc\u015fm\u00fc\u015f alanlar ek \u00fccretler gerektirebilir.<\/li>\n<li>Transfer reddedilirse, yenileme s\u00fcresi i\u00e7inde kalman\u0131z gerekebilir; aksi halde alan ad\u0131 ask\u0131ya al\u0131n\u0131r.<\/li>\n<\/ul>\n<p>Bu noktada, alan ad\u0131n\u0131n ne zaman d\u00fc\u015fece\u011fini ve grace\/redemption d\u00f6nemlerini anlamak i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/alan-adi-yenileme-grace-ve-redemption-sureleri-degerli-domainleri-kaybetmemek-icin-strateji-rehberi\/\">alan ad\u0131 yenileme ve grace\/redemption s\u00fcreleri rehberimize<\/a> mutlaka g\u00f6z atman\u0131z\u0131 \u00f6neririz. De\u011ferli bir domain s\u00f6z konusuysa, \u00f6nce yenileyip sonra transfer etmek \u00e7o\u011fu zaman daha g\u00fcvenlidir.<\/p>\n<h3><span id=\"2_60_gunluk_transfer_kisiti_ve_yeni_kayitlar\">2. 60 g\u00fcnl\u00fck transfer k\u0131s\u0131t\u0131 ve yeni kay\u0131tlar<\/span><\/h3>\n<p>Bir\u00e7ok uzant\u0131da (\u00f6zellikle klasik gTLD\u2019lerde) \u015fu durumlarda <strong>60 g\u00fcn transfer k\u0131s\u0131t\u0131<\/strong> devreye girer:<\/p>\n<ul>\n<li>Alan ad\u0131n\u0131 yeni kaydettiyseniz (kay\u0131ttan itibaren 60 g\u00fcn ge\u00e7meden transfer yap\u0131lamaz).<\/li>\n<li>Alan ad\u0131nda sahiplik (registrant) bilgisi yak\u0131n zamanda k\u00f6kl\u00fc bi\u00e7imde de\u011fi\u015ftirildiyse.<\/li>\n<\/ul>\n<p>Bu k\u0131s\u0131t, ICANN politikalar\u0131 kaynakl\u0131d\u0131r ve kay\u0131t firmalar\u0131 taraf\u0131ndan kald\u0131r\u0131lmas\u0131 genellikle m\u00fcmk\u00fcn de\u011fildir. Bu nedenle, yeni ald\u0131\u011f\u0131n\u0131z bir alan ad\u0131n\u0131 hemen ba\u015fka bir firmaya ta\u015f\u0131ma plan\u0131n\u0131z varsa 60 g\u00fcnl\u00fck pencereyi hesaba katmal\u0131s\u0131n\u0131z.<\/p>\n<h3><span id=\"3_Whois_ve_iletisim_epostasi_dogrulugu\">3. Whois ve ileti\u015fim e\u2011postas\u0131 do\u011frulu\u011fu<\/span><\/h3>\n<p>Transfer onay\u0131 \u00e7o\u011fu zaman <strong>alan ad\u0131 sahibinin ileti\u015fim e\u2011postas\u0131na<\/strong> g\u00f6nderilen onay linkleriyle yap\u0131l\u0131r. Whois bilginizdeki e\u2011posta adresi hatal\u0131ysa veya kullanm\u0131yorsan\u0131z, transfer onay\u0131n\u0131 veremez ve s\u00fcre\u00e7 kilitlenebilirsiniz. Transferden \u00f6nce mutlaka:<\/p>\n<ul>\n<li>Alan ad\u0131 sahibi (registrant) e\u2011posta adresini g\u00fcncelleyin.<\/li>\n<li>Bu e\u2011posta hesab\u0131na ger\u00e7ekten eri\u015febildi\u011finizden emin olun.<\/li>\n<li>Gerekiyorsa spam\/junk klas\u00f6rlerini de kontrol edin.<\/li>\n<\/ul>\n<h3><span id=\"4_SSL_SEO_ve_yonlendirmeler\">4. SSL, SEO ve y\u00f6nlendirmeler<\/span><\/h3>\n<p>Alan ad\u0131 transferi, do\u011frudan web sitenizin i\u00e7eri\u011fine dokunmasa da DNS ve nameserver de\u011fi\u015fikli\u011fi yapacaksan\u0131z <strong>SSL, 301 y\u00f6nlendirmeler ve SEO<\/strong> \u00fczerinde dolayl\u0131 etkileri olabilir. Daha \u00f6nce haz\u0131rlad\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/alan-adi-degistirirken-seo-kaybetmemek\/\">alan ad\u0131 de\u011fi\u015ftirirken SEO kaybetmemek \u00fczerine rehber<\/a> teknik olarak farkl\u0131 bir senaryoyu anlatsa da, DNS ve y\u00f6nlendirme taraf\u0131ndaki mant\u0131k burada da aynen ge\u00e7erli.<\/p>\n<h2><span id=\"EPP_Auth_kodu_ve_transfer_kilidi_Transferin_kalbi\">EPP (Auth) kodu ve transfer kilidi: Transferin kalbi<\/span><\/h2>\n<p>Alan ad\u0131 transferinin merkezinde iki kavram var: <strong>transfer kilidi (Registrar Lock)<\/strong> ve <strong>EPP\/Auth kodu<\/strong>. Bu ikisini do\u011fru y\u00f6netmeden transfer ba\u015flat\u0131lamaz.<\/p>\n<h3><span id=\"Transfer_kilidi_Registrar_Lock_nedir\">Transfer kilidi (Registrar Lock) nedir?<\/span><\/h3>\n<p>Transfer kilidi, alan ad\u0131n\u0131z\u0131n ba\u015fka bir firmaya siz istemeden transfer edilmesini engelleyen bir g\u00fcvenlik mekanizmas\u0131d\u0131r. Genellikle kay\u0131t panelinde <em>Domain Lock<\/em>, <em>Transfer Lock<\/em> gibi isimlerle ge\u00e7er. Transfer yapmak istiyorsan\u0131z:<\/p>\n<ol>\n<li>Mevcut kay\u0131t firman\u0131z\u0131n alan ad\u0131 y\u00f6netim paneline giri\u015f yap\u0131n.<\/li>\n<li>\u0130lgili domaini se\u00e7in.<\/li>\n<li>\u201cTransfer Lock\u201d veya benzeri bir ayar\u0131 <strong>Kapal\u0131\/Disabled\/Unlocked<\/strong> konuma getirin.<\/li>\n<li>De\u011fi\u015fikli\u011fin birka\u00e7 dakika i\u00e7inde aktif oldu\u011fundan emin olun.<\/li>\n<\/ol>\n<p>G\u00fcvenlik a\u00e7\u0131s\u0131ndan, transfer tamamland\u0131ktan sonra yeni firmada (\u00f6rne\u011fin DCHost hesab\u0131n\u0131zda) transfer kilidini tekrar <strong>A\u00e7\u0131k<\/strong> konuma getirmenizi \u015fiddetle tavsiye ederiz.<\/p>\n<h3><span id=\"EPP_Auth_kodu_nedir_nasil_alinir\">EPP (Auth) kodu nedir, nas\u0131l al\u0131n\u0131r?<\/span><\/h3>\n<p><strong>EPP kodu<\/strong> (veya Auth Code, Transfer Key), alan ad\u0131n\u0131z\u0131 yeni kay\u0131t firmas\u0131 hesab\u0131n\u0131za ta\u015f\u0131yabilmeniz i\u00e7in gereken, alan ad\u0131 bazl\u0131 bir \u015fifre gibidir. Bu kod olmadan transfer ba\u015flatamazs\u0131n\u0131z. EPP kodunu almak i\u00e7in tipik ad\u0131mlar \u015f\u00f6yledir:<\/p>\n<ul>\n<li>Mevcut kay\u0131t firmas\u0131n\u0131n paneline giri\u015f yap\u0131n.<\/li>\n<li>\u0130lgili domainin y\u00f6netim sayfas\u0131na girin.<\/li>\n<li>\u201cGet EPP Code\u201d, \u201cAuth Code Request\u201d gibi bir b\u00f6l\u00fcm bulun.<\/li>\n<li>Kimi sistemlerde kod an\u0131nda panelde g\u00f6sterilir, kimilerinde whois e\u2011postan\u0131za g\u00f6nderilir.<\/li>\n<\/ul>\n<p>EPP kodunu ald\u0131\u011f\u0131n\u0131zda, bu bilgiyi gizli bir yerde saklay\u0131n ve sadece yeni kay\u0131t firmas\u0131n\u0131n (\u00f6rne\u011fin DCHost m\u00fc\u015fteri panelinizin) transfer formuna girerken kullan\u0131n. Bu kodu kimseyle payla\u015fmay\u0131n; \u00e7\u00fcnk\u00fc alan ad\u0131n\u0131z\u0131n transfer yetkisi anlam\u0131na gelir.<\/p>\n<h3><span id=\"Iki_faktorlu_dogrulama_ve_hesap_guvenligi\">\u0130ki fakt\u00f6rl\u00fc do\u011frulama ve hesap g\u00fcvenli\u011fi<\/span><\/h3>\n<p>Transfer s\u00fcrecinde hem eski hem yeni kay\u0131t firmas\u0131 hesab\u0131n\u0131zda hareket edece\u011finiz i\u00e7in, bu d\u00f6nem hesap g\u00fcvenli\u011fi a\u00e7\u0131s\u0131ndan da kritiktir. \u00d6zellikle:<\/p>\n<ul>\n<li>Mevcut kay\u0131t firmas\u0131 hesab\u0131n\u0131zda 2FA (Google Authenticator, SMS vb.) aktif olsun.<\/li>\n<li>DCHost m\u00fc\u015fteri panelinizde de 2FA kullan\u0131n ve g\u00fc\u00e7l\u00fc bir parola belirleyin.<\/li>\n<\/ul>\n<p>Bu sayede, EPP kodunuz ele ge\u00e7irilse bile hesap eri\u015fimi olmadan k\u00f6t\u00fc niyetli transfer riski b\u00fcy\u00fck \u00f6l\u00e7\u00fcde engellenmi\u015f olur.<\/p>\n<h2><span id=\"DNS_stratejisi_Transfer_sirasinda_sitenizi_online_tutmak\">DNS stratejisi: Transfer s\u0131ras\u0131nda sitenizi online tutmak<\/span><\/h2>\n<p>Alan ad\u0131 transferi tek ba\u015f\u0131na web sitenizi kapatmaz. As\u0131l problem, DNS taraf\u0131nda yap\u0131lan kontrols\u00fcz de\u011fi\u015fikliklerden \u00e7\u0131kar. DNS stratejinizi ba\u015ftan planlarsan\u0131z, ziyaret\u00e7ileriniz hi\u00e7bir kesinti fark etmez.<\/p>\n<h3><span id=\"DNSin_temellerini_hatirlayalim\">DNS\u2019in temellerini hat\u0131rlayal\u0131m<\/span><\/h3>\n<p>Transfer s\u00fcrecine girmeden \u00f6nce, hangi kay\u0131t ne i\u015fe yar\u0131yor netle\u015ftirmek \u00f6nemli. Aksi halde yanl\u0131\u015f bir kayd\u0131 silmek t\u00fcm altyap\u0131n\u0131z\u0131 etkileyebilir. Bu konuda <a href=\"https:\/\/www.dchost.com\/blog\/dns-kayitlari-adan-zye-a-aaaa-cname-mx-txt-srv-caa-ve-sizi-yakan-o-kucuk-hatalar\/\">DNS kay\u0131t t\u00fcrlerini ad\u0131m ad\u0131m anlatt\u0131\u011f\u0131m\u0131z rehbere<\/a> mutlaka g\u00f6z at\u0131n. \u00d6zetle:<\/p>\n<ul>\n<li><strong>A \/ AAAA:<\/strong> Alan ad\u0131n\u0131 web sunucunuzun IP adresine y\u00f6nlendirir.<\/li>\n<li><strong>MX:<\/strong> E\u2011posta trafi\u011finin hangi sunucuya gidece\u011fini belirler.<\/li>\n<li><strong>CNAME:<\/strong> Bir alan ad\u0131n\u0131 ba\u015fka bir alan ad\u0131na y\u00f6nlendirir.<\/li>\n<li><strong>TXT:<\/strong> SPF, do\u011frulama kay\u0131tlar\u0131 gibi pek \u00e7ok alan\u0131 ta\u015f\u0131r.<\/li>\n<\/ul>\n<h3><span id=\"Nameserver_NS_ve_DNS_barindirma_karari\">Nameserver (NS) ve DNS bar\u0131nd\u0131rma karar\u0131<\/span><\/h3>\n<p>Alan ad\u0131n\u0131 farkl\u0131 kay\u0131t firmas\u0131na ta\u015f\u0131rken iki temel senaryo vard\u0131r:<\/p>\n<ol>\n<li>Nameserver\u2019lar ayn\u0131 kal\u0131r, sadece registrant (kay\u0131t firmas\u0131) de\u011fi\u015fir.<\/li>\n<li>Hem kay\u0131t firmas\u0131 hem nameserver (DNS hizmeti) de\u011fi\u015fir.<\/li>\n<\/ol>\n<p>En g\u00fcvenli yakla\u015f\u0131m genellikle \u015fudur:<\/p>\n<ul>\n<li><strong>\u00d6nce alan ad\u0131 transferini tamamlamak<\/strong>,<\/li>\n<li>Ard\u0131ndan DNS ve nameserver de\u011fi\u015fikli\u011fini kontroll\u00fc \u015fekilde yapmak.<\/li>\n<\/ul>\n<p>B\u00f6ylece ayn\u0131 anda iki b\u00fcy\u00fck de\u011fi\u015fikli\u011fi y\u00f6netmek zorunda kalmazs\u0131n\u0131z ve sorun \u00e7\u0131kt\u0131\u011f\u0131nda hangi ad\u0131mda problem do\u011fdu\u011funu daha net g\u00f6rebilirsiniz.<\/p>\n<h3><span id=\"TTL_planlamasi_ve_DNS_yayilimini_yonetmek\">TTL planlamas\u0131 ve DNS yay\u0131l\u0131m\u0131n\u0131 y\u00f6netmek<\/span><\/h3>\n<p>DNS taraf\u0131nda de\u011fi\u015fiklik yapt\u0131\u011f\u0131n\u0131zda devreye giren kavram <strong>TTL (Time To Live)<\/strong> de\u011feridir. TTL, bir kayd\u0131n DNS \u00f6nbelleklerinde ne kadar s\u00fcre tutulaca\u011f\u0131n\u0131 belirler. De\u011feri ne kadar y\u00fcksekse, de\u011fi\u015fikliklerin d\u00fcnya genelinde yay\u0131lmas\u0131 o kadar uzun s\u00fcrer.<\/p>\n<p>\u00d6rne\u011fin, A kayd\u0131n\u0131z\u0131n TTL de\u011feri 86400 saniye (24 saat) ise, IP de\u011fi\u015fikli\u011finizin tam olarak her yerde etkili olmas\u0131 1 g\u00fcn\u00fc bulabilir. Bu nedenle, transfer veya hosting ta\u015f\u0131ma \u00f6ncesinde TTL\u2019i <strong>\u00f6nceden d\u00fc\u015f\u00fcrmek<\/strong> en kritik ad\u0131md\u0131r. TTL ve yay\u0131lma s\u00fcresini daha iyi anlamak i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/dns-yayilim-suresi-nedir-neden-24-saat-surer-ve-nasil-hizlandirilir\/\">DNS yay\u0131l\u0131m s\u00fcresinin nas\u0131l \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 anlatt\u0131\u011f\u0131m\u0131z detayl\u0131 yaz\u0131ya<\/a> bakabilirsiniz.<\/p>\n<p>Kesintisiz ge\u00e7i\u015f planl\u0131yorsan\u0131z, <a href=\"https:\/\/www.dchost.com\/blog\/zero-downtime-tasima-icin-ttl-stratejileri-dns-yayilimini-gercekten-nasil-hizlandirirsin\/\">zero\u2011downtime ta\u015f\u0131ma i\u00e7in TTL stratejileri yaz\u0131m\u0131zda<\/a> payla\u015ft\u0131\u011f\u0131m\u0131z yakla\u015f\u0131m\u0131 uygulayabilirsiniz: Ta\u015f\u0131ma tarihinden birka\u00e7 g\u00fcn \u00f6nce TTL\u2019i d\u00fc\u015f\u00fcr, de\u011fi\u015fiklik an\u0131nda yay\u0131l\u0131m\u0131 h\u0131zland\u0131r, i\u015fler stabilize olunca TTL\u2019i tekrar mant\u0131kl\u0131 bir seviyeye y\u00fckselt.<\/p>\n<h3><span id=\"Senaryo_1_Sadece_domain_registrari_degisiyor_hosting_ayni_kaliyor\">Senaryo 1: Sadece domain registrar\u0131 de\u011fi\u015fiyor, hosting ayn\u0131 kal\u0131yor<\/span><\/h3>\n<p>Bu, en az riskli senaryodur. \u00d6rnek: Web siteniz h\u00e2l\u00e2 mevcut hosting sa\u011flay\u0131c\u0131n\u0131zda duruyor, sadece domaini DCHost\u2019a transfer etmek istiyorsunuz.<\/p>\n<ul>\n<li>Nameserver\u2019lar (NS) <strong>hi\u00e7 de\u011fi\u015fmez<\/strong>. Eski firmadaki NS kay\u0131tlar\u0131 yeni kay\u0131t firmas\u0131 panelinize aktar\u0131l\u0131r.<\/li>\n<li>Web sitesi ve e\u2011posta i\u00e7in kulland\u0131\u011f\u0131n\u0131z DNS kay\u0131tlar\u0131 aynen \u00e7al\u0131\u015fmaya devam eder.<\/li>\n<li>Bu senaryoda tek yapman\u0131z gereken, transfer tamamland\u0131ktan sonra yeni panelinizden DNS kay\u0131tlar\u0131n\u0131z\u0131 kontrol etmektir.<\/li>\n<\/ul>\n<p>Avantaj\u0131, web sitesi ve e\u2011posta taraf\u0131nda neredeyse s\u0131f\u0131ra yak\u0131n risk olmas\u0131d\u0131r. Dezavantaj\u0131 ise DNS\u2019in h\u00e2l\u00e2 farkl\u0131 bir altyap\u0131da olmas\u0131 ve t\u00fcm\u00fcyle tek panelde toplanmam\u0131\u015f olmas\u0131d\u0131r.<\/p>\n<h3><span id=\"Senaryo_2_Hem_domain_hem_hosting_DCHosta_tasiniyor\">Senaryo 2: Hem domain hem hosting DCHost\u2019a ta\u015f\u0131n\u0131yor<\/span><\/h3>\n<p>Bu senaryo, en \u00e7ok dikkat isteyen ama uzun vadede y\u00f6netimi en konforlu hale getiren yakla\u015f\u0131md\u0131r. Alan ad\u0131n\u0131z\u0131 DCHost\u2019a transfer ederken ayn\u0131 zamanda:<\/p>\n<ul>\n<li>Web sitenizi DCHost <a href=\"https:\/\/www.dchost.com\/tr\/web-hosting\">payla\u015f\u0131ml\u0131 hosting<\/a>, VPS veya <a href=\"https:\/\/www.dchost.com\/tr\/fiziksel-sunucu\">dedicated sunucu<\/a>ya ta\u015f\u0131yabilirsiniz.<\/li>\n<li>DNS y\u00f6netimini DCHost\u2019un DNS altyap\u0131s\u0131na devrederek t\u00fcm kay\u0131tlar\u0131 tek panelden kontrol edebilirsiniz.<\/li>\n<li>E\u2011postalar\u0131n\u0131z\u0131 da DCHost \u00fczerinde bar\u0131nd\u0131rarak tam entegre bir yap\u0131 kurabilirsiniz.<\/li>\n<\/ul>\n<p>Bu durumda izlenebilecek pratik yol haritas\u0131n\u0131 a\u015fa\u011f\u0131da geni\u015f\u00e7e anlataca\u011f\u0131z; ama prensip de\u011fi\u015fmiyor: \u00d6nce TTL planlamas\u0131, sonra paralel ortam kurma, en sonda kontroll\u00fc <em>cutover<\/em>.<\/p>\n<h2><span id=\"Epostayi_kesintisiz_tasimak_MX_SPF_DKIM_ve_zamanlama\">E\u2011postay\u0131 kesintisiz ta\u015f\u0131mak: MX, SPF, DKIM ve zamanlama<\/span><\/h2>\n<p>Alan ad\u0131 transferlerinde en \u00e7ok korkulan konu e\u2011posta kesintisidir. \u00c7\u00fcnk\u00fc web sitesi birka\u00e7 dakika kapal\u0131 kalabilir ama kaybolan bir i\u015f e\u2011postas\u0131n\u0131n telafisi \u00e7ok daha zordur. DCHost\u2019ta yeni m\u00fc\u015fteri ge\u00e7i\u015flerinde en titiz oldu\u011fumuz b\u00f6l\u00fcm de buras\u0131.<\/p>\n<h3><span id=\"Eposta_altyapinizi_haritalandirin\">E\u2011posta altyap\u0131n\u0131z\u0131 haritaland\u0131r\u0131n<\/span><\/h3>\n<p>\u00d6nce mevcut durumu netle\u015ftirin:<\/p>\n<ul>\n<li>\u015eu anda e\u2011posta sunucunuz nerede? Hosting ile ayn\u0131 sunucuda m\u0131, ayr\u0131 bir mail sunucusunda m\u0131?<\/li>\n<li>MX kay\u0131tlar\u0131 hangi hostname\u2019e i\u015faret ediyor?<\/li>\n<li>SPF kayd\u0131n\u0131zda hangi sunuculara e\u2011posta g\u00f6ndermek i\u00e7in yetki vermi\u015fsiniz?<\/li>\n<li>DKIM ve DMARC kay\u0131tlar\u0131n\u0131z var m\u0131?<\/li>\n<\/ul>\n<p>Bu sorular\u0131n cevab\u0131n\u0131 netle\u015ftirmek i\u00e7in DNS kay\u0131tlar\u0131n\u0131z\u0131 inceleyebilir, ayr\u0131nt\u0131l\u0131 yap\u0131y\u0131 \u00e7\u0131karmak i\u00e7in de <a href=\"https:\/\/www.dchost.com\/blog\/spf-dkim-dmarc-ve-rdns-ile-e-posta-teslim-edilebilirligini-nasil-adim-adim-yukseltirsin\/\">SPF, DKIM ve DMARC ile e\u2011posta teslim edilebilirli\u011fini art\u0131rma rehberimize<\/a> g\u00f6z atabilirsiniz.<\/p>\n<h3><span id=\"Kutulari_onceden_olusturun_ve_IMAP_senkronizasyonu_planlayin\">Kutular\u0131 \u00f6nceden olu\u015fturun ve IMAP senkronizasyonu planlay\u0131n<\/span><\/h3>\n<p>Yeni hosting veya mail sunucusuna ge\u00e7iyorsan\u0131z yap\u0131lacak ilk i\u015f, <strong>ayn\u0131 kullan\u0131c\u0131 adlar\u0131yla e\u2011posta kutular\u0131n\u0131 \u00f6nceden olu\u015fturmak<\/strong> olmal\u0131. \u00d6rne\u011fin info@, destek@, ad.soyad@ gibi t\u00fcm adresler yeni tarafta da haz\u0131r olmal\u0131.<\/p>\n<p>Ard\u0131ndan, m\u00fcmk\u00fcnse eski ve yeni sunucu aras\u0131nda <strong>IMAP senkronizasyonu<\/strong> yap\u0131lmas\u0131n\u0131 \u00f6neriyoruz. B\u00f6ylece eski sunucudaki gelen kutusu ve klas\u00f6r yap\u0131s\u0131, yeni sunucuya kopyalan\u0131r. DCHost ekibi olarak bu tip ge\u00e7i\u015flerde s\u0131k\u00e7a kulland\u0131\u011f\u0131m\u0131z y\u00f6ntemlerden biri, ta\u015f\u0131ma \u00f6ncesi bir kere, ta\u015f\u0131ma an\u0131nda bir kere IMAP sync yapmakt\u0131r. B\u00f6ylece veri kayb\u0131 minimuma iner.<\/p>\n<h3><span id=\"MX_ve_SPF_degisikligini_dogru_zamanda_yapmak\">MX ve SPF de\u011fi\u015fikli\u011fini do\u011fru zamanda yapmak<\/span><\/h3>\n<p>E\u2011posta taraf\u0131nda kritik e\u015fik, <strong>MX kay\u0131tlar\u0131n\u0131n yeni sunucuya y\u00f6nlendirilmesi<\/strong> an\u0131d\u0131r. Bunu g\u00fcvenli yapmak i\u00e7in:<\/p>\n<ol>\n<li>MX kay\u0131tlar\u0131n\u0131z\u0131n TTL de\u011ferini birka\u00e7 g\u00fcn \u00f6nceden d\u00fc\u015f\u00fcr\u00fcn (\u00f6rne\u011fin 3600 saniye).<\/li>\n<li>Yeni mail sunucusunda t\u00fcm kullan\u0131c\u0131 hesaplar\u0131n\u0131 a\u00e7\u0131n ve test edin.<\/li>\n<li>SPF kayd\u0131n\u0131za yeni sunucunun IP\u2019sini veya hostname\u2019ini ekleyin; bir s\u00fcre eski sunucuyu da yetkili b\u0131rak\u0131n.<\/li>\n<li>Planlad\u0131\u011f\u0131n\u0131z ta\u015f\u0131ma saatinde MX kay\u0131tlar\u0131n\u0131 yeni sunucuya \u00e7evirin.<\/li>\n<li>Eski sunucuyu birka\u00e7 g\u00fcn daha sadece <em>gelen kutusunu izlemek<\/em> amac\u0131yla ayakta tutun.<\/li>\n<\/ol>\n<p>Bu s\u00fcreci daha detayl\u0131 bir \u00f6rnekle g\u00f6rmek isterseniz, ad\u0131m ad\u0131m anlatt\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/alan-adi-tasirken-e%e2%80%91posta-kesintisini-onlemek\/\">alan ad\u0131 ta\u015f\u0131rken e\u2011posta kesintisini \u00f6nleme rehberimize<\/a> mutlaka g\u00f6z at\u0131n. Ayr\u0131ca, sadece e\u2011posta altyap\u0131s\u0131n\u0131 de\u011fi\u015ftiriyorsan\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/e-posta-altyapisini-tasirken-kesinti-yasamamak\/\">e\u2011posta altyap\u0131s\u0131n\u0131 ta\u015f\u0131rken kesinti ya\u015famamak \u00fczerine yazd\u0131\u011f\u0131m\u0131z yaz\u0131<\/a> da pratik kontrol listeleri sunuyor.<\/p>\n<h3><span id=\"DKIM_ve_DMARCi_unutmamak\">DKIM ve DMARC\u2019\u0131 unutmamak<\/span><\/h3>\n<p>MX de\u011fi\u015fikli\u011fi yapt\u0131\u011f\u0131n\u0131zda, e\u2011posta <strong>g\u00f6nderim taraf\u0131<\/strong> da etkilenir. Yeni sunucudan g\u00f6nderilen iletilerin spam klas\u00f6r\u00fcne d\u00fc\u015fmemesi i\u00e7in:<\/p>\n<ul>\n<li>Yeni mail sunucusu i\u00e7in DKIM anahtarlar\u0131n\u0131 olu\u015fturun ve ilgili TXT kayd\u0131n\u0131 DNS\u2019e ekleyin.<\/li>\n<li>DMARC politikas\u0131 kullan\u0131yorsan\u0131z, raporlar\u0131 izleyerek ge\u00e7i\u015f s\u00fcrecinde anormallik olup olmad\u0131\u011f\u0131n\u0131 kontrol edin.<\/li>\n<\/ul>\n<p>Bu ad\u0131mlar, \u00f6zellikle transactional (\u015fifre s\u0131f\u0131rlama, sipari\u015f bildirimi) e\u2011postalar g\u00f6nderen e\u2011ticaret ve SaaS projeleri i\u00e7in hayati \u00f6nem ta\u015f\u0131r.<\/p>\n<h2><span id=\"Adim_adim_tam_transfer_akisi_EPP_DNS_ve_eposta_birlikte\">Ad\u0131m ad\u0131m tam transfer ak\u0131\u015f\u0131: EPP, DNS ve e\u2011posta birlikte<\/span><\/h2>\n<p>\u015eimdiye kadar her par\u00e7ay\u0131 ayr\u0131 ayr\u0131 anlatt\u0131k. Gelin, hepsini bir araya getiren pratik bir <strong>u\u00e7tan uca senaryo<\/strong> \u00fczerinden gidelim. Varsay\u0131m: Alan ad\u0131n\u0131z\u0131 ve hostinginizi DCHost\u2019a ta\u015f\u0131yorsunuz, e\u2011postalar\u0131n\u0131z da ayn\u0131 alan ad\u0131nda \u00e7al\u0131\u015fmaya devam edecek.<\/p>\n<h3><span id=\"1_Envanter_ve_sure_kontrolu\">1. Envanter ve s\u00fcre kontrol\u00fc<\/span><\/h3>\n<ul>\n<li>Alan ad\u0131n\u0131z\u0131n biti\u015f tarihini kontrol edin, gerekirse \u00f6nce 1 y\u0131l yenileyin.<\/li>\n<li>Whois sahibinin e\u2011posta adresinin do\u011fru oldu\u011fundan emin olun.<\/li>\n<li>Aktif DNS kay\u0131tlar\u0131n\u0131 (A, AAAA, MX, CNAME, TXT\u2026) d\u0131\u015fa aktar\u0131n veya ekran g\u00f6r\u00fcnt\u00fcs\u00fc al\u0131n.<\/li>\n<\/ul>\n<h3><span id=\"2_TTL_dusurme_asamasi\">2. TTL d\u00fc\u015f\u00fcrme a\u015famas\u0131<\/span><\/h3>\n<ul>\n<li>Ta\u015f\u0131ma plan\u0131ndan en az 48 saat \u00f6nce; A, MX, \u00f6nemli CNAME ve TXT kay\u0131tlar\u0131n\u0131n TTL de\u011ferini 300\u20133600 saniye aral\u0131\u011f\u0131na \u00e7ekin.<\/li>\n<li>Bu sayede ileride yapaca\u011f\u0131n\u0131z de\u011fi\u015fiklikler \u00e7ok daha h\u0131zl\u0131 yay\u0131lacak.<\/li>\n<\/ul>\n<h3><span id=\"3_DCHost_tarafinda_yeni_ortami_hazirlama\">3. DCHost taraf\u0131nda yeni ortam\u0131 haz\u0131rlama<\/span><\/h3>\n<ul>\n<li>DCHost \u00fczerinde uygun bir <strong>payla\u015f\u0131ml\u0131 hosting, VPS veya dedicated sunucu<\/strong> plan\u0131 olu\u015fturun.<\/li>\n<li>Web sitenizin dosya ve veritaban\u0131 kopyas\u0131n\u0131 yeni sunucuya ta\u015f\u0131y\u0131n.<\/li>\n<li>Alan ad\u0131n\u0131z i\u00e7in DNS b\u00f6lgesini (zone) \u00f6nceden olu\u015fturun; eski sunucudaki kay\u0131tlar\u0131n birebir kopyas\u0131n\u0131 girin.<\/li>\n<li>E\u2011posta kutular\u0131n\u0131 DCHost \u00fczerinde a\u00e7\u0131n; gerekiyorsa ilk IMAP senkronizasyonunu yap\u0131n.<\/li>\n<\/ul>\n<h3><span id=\"4_EPP_kodunu_alma_ve_transferi_baslatma\">4. EPP kodunu alma ve transferi ba\u015flatma<\/span><\/h3>\n<ul>\n<li>Mevcut kay\u0131t firmas\u0131ndan transfer kilidini kald\u0131r\u0131n.<\/li>\n<li>EPP\/Auth kodunu al\u0131n ve DCHost m\u00fc\u015fteri panelinizdeki alan ad\u0131 transfer formuna girin.<\/li>\n<li>Transfer onay e\u2011postalar\u0131n\u0131 takip edin, gerekli onaylar\u0131 verin.<\/li>\n<\/ul>\n<h3><span id=\"5_Transfer_devam_ederken_DNSi_sabit_tutmak\">5. Transfer devam ederken DNS\u2019i sabit tutmak<\/span><\/h3>\n<ul>\n<li>Transfer s\u00fcresi boyunca m\u00fcmk\u00fcnse nameserver\u2019lar\u0131 de\u011fi\u015ftirmeyin.<\/li>\n<li>DNS kay\u0131tlar\u0131 h\u00e2l\u00e2 eski nameserver\u2019da \u00e7al\u0131\u015fmaya devam ederken, DCHost taraf\u0131ndaki DNS b\u00f6lgenizi de haz\u0131rda tutun.<\/li>\n<\/ul>\n<h3><span id=\"6_Transfer_tamamlandiktan_sonra_DNS_cutover\">6. Transfer tamamland\u0131ktan sonra DNS cutover<\/span><\/h3>\n<p>Transfer tamamland\u0131\u011f\u0131nda, art\u0131k domain y\u00f6netimi DCHost hesab\u0131n\u0131za ge\u00e7mi\u015f olur. Bu noktada:<\/p>\n<ul>\n<li>DCHost DNS b\u00f6lgenizin eski DNS ile birebir ayn\u0131 oldu\u011fundan emin olun.<\/li>\n<li>Nameserver\u2019lar\u0131 DCHost\u2019un size verdi\u011fi NS adreslerine \u00e7evirin.<\/li>\n<li>DNS yay\u0131l\u0131m\u0131n\u0131 izleyin; TTL d\u00fc\u015f\u00fck oldu\u011fu i\u00e7in de\u011fi\u015fiklikler g\u00f6rece h\u0131zl\u0131 oturacakt\u0131r.<\/li>\n<\/ul>\n<h3><span id=\"7_Web_sitesi_trafigini_yeni_sunucuya_almak\">7. Web sitesi trafi\u011fini yeni sunucuya almak<\/span><\/h3>\n<p>Art\u0131k DNS sizde oldu\u011funa g\u00f6re, web trafi\u011fini yeni sunucuya y\u00f6nlendirebilirsiniz:<\/p>\n<ul>\n<li>A (ve gerekiyorsa AAAA) kay\u0131tlar\u0131n\u0131 DCHost sunucunuzun IP adresine g\u00fcncelleyin.<\/li>\n<li>Eski sunucuyu en az 24\u201348 saat boyunca ayakta tutarak olas\u0131 geri d\u00f6n\u00fc\u015f ihtimaline kar\u015f\u0131 haz\u0131r bekletin.<\/li>\n<\/ul>\n<h3><span id=\"8_Eposta_trafigini_yeni_sunucuya_tasimak\">8. E\u2011posta trafi\u011fini yeni sunucuya ta\u015f\u0131mak<\/span><\/h3>\n<ul>\n<li>MX kay\u0131tlar\u0131n\u0131 DCHost mail sunucusuna i\u015faret edecek \u015fekilde g\u00fcncelleyin.<\/li>\n<li>SPF kayd\u0131n\u0131za yeni sunucuyu ekleyin, ge\u00e7i\u015f s\u00fcrecinde m\u00fcmk\u00fcnse eskiyi de bir s\u00fcre daha yetkili b\u0131rak\u0131n.<\/li>\n<li>Gerekirse ikinci bir IMAP senkronizasyonu yaparak ta\u015f\u0131ma s\u0131ras\u0131nda gelen e\u2011postalar\u0131 da yeni sunucuya \u00e7ekin.<\/li>\n<\/ul>\n<h3><span id=\"9_Izleme_ve_temizlik\">9. \u0130zleme ve temizlik<\/span><\/h3>\n<ul>\n<li>Web trafi\u011fini, hata loglar\u0131n\u0131 ve mail kuyru\u011funu birka\u00e7 g\u00fcn yak\u0131ndan takip edin.<\/li>\n<li>Her \u015fey stabil hale geldi\u011finde eski sunucudaki gereksiz kay\u0131tlar\u0131 ve servisleri temizleyin.<\/li>\n<\/ul>\n<h3><span id=\"10_Guvenlik_son_dokunuslari\">10. G\u00fcvenlik son dokunu\u015flar\u0131<\/span><\/h3>\n<ul>\n<li>DCHost hesab\u0131n\u0131zda alan ad\u0131 <strong>transfer kilidini tekrar a\u00e7\u0131n<\/strong>.<\/li>\n<li>DNSSEC, 2FA gibi ek g\u00fcvenlik \u00f6nlemlerini devreye al\u0131n.<\/li>\n<\/ul>\n<h2><span id=\"DCHost_ile_alan_adi_ve_hosting_tasimayi_sadelestirmek\">DCHost ile alan ad\u0131 ve hosting ta\u015f\u0131may\u0131 sadele\u015ftirmek<\/span><\/h2>\n<p>Yukar\u0131daki ad\u0131mlar size uzun g\u00f6r\u00fcnebilir; ama bunun b\u00fcy\u00fck k\u0131sm\u0131, riskleri minimize etmek i\u00e7in planlama ad\u0131mlar\u0131d\u0131r. DCHost olarak \u00f6zellikle \u015funlar\u0131 kolayla\u015ft\u0131r\u0131yoruz:<\/p>\n<ul>\n<li><strong>Alan ad\u0131 transfer sihirbaz\u0131:<\/strong> M\u00fc\u015fteri panelimizde EPP kodu, whois ileti\u015fim kontrol\u00fc ve transfer durumu tek ekranda takip edilebilir.<\/li>\n<li><strong>DNS y\u00f6netimi:<\/strong> Alan ad\u0131n\u0131z\u0131 bize ta\u015f\u0131d\u0131\u011f\u0131n\u0131zda A, AAAA, CNAME, MX, TXT, SRV ve CAA kay\u0131tlar\u0131n\u0131 tek panelden y\u00f6netebilir; geli\u015fmi\u015f DNS \u00f6zelliklerinden yararlanabilirsiniz.<\/li>\n<li><strong>\u00c7oklu \u00fcr\u00fcn deste\u011fi:<\/strong> Sitenizi payla\u015f\u0131ml\u0131 hosting, NVMe VPS, dedicated sunucu veya colocation \u00fczerinde bar\u0131nd\u0131rsan\u0131z da DNS ve alan ad\u0131 tek hesapta toplan\u0131r.<\/li>\n<li><strong>Ge\u00e7i\u015f deste\u011fi:<\/strong> \u00d6zellikle e\u2011posta ve veritaban\u0131 ta\u015f\u0131ma s\u00fcre\u00e7lerinde, destek ekibimizle birlikte planl\u0131 ve kontroll\u00fc bir cutover senaryosu olu\u015fturabilirsiniz.<\/li>\n<\/ul>\n<p>Daha \u00f6nce yazd\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/alan-adi-transferi-nasil-yapilir-epp-kodu-transfer-kilidi-ve-kesintisiz-gecise-sakin-bir-rehber\/\">alan ad\u0131 transferi nas\u0131l yap\u0131l\u0131r rehberimiz<\/a>, bu yaz\u0131da anlatt\u0131klar\u0131m\u0131z\u0131n daha sade bir \u00f6zetidir. Bu makaleyi ise; \u00f6zellikle e\u2011posta, DNS ve hosting taraf\u0131n\u0131 da birlikte ta\u015f\u0131yan, biraz daha karma\u015f\u0131k senaryolar i\u00e7in haz\u0131rlad\u0131k.<\/p>\n<h2><span id=\"Sonuc_ve_onerilen_yol_haritasi\">Sonu\u00e7 ve \u00f6nerilen yol haritas\u0131<\/span><\/h2>\n<p>Alan ad\u0131n\u0131 farkl\u0131 kay\u0131t firmas\u0131na transfer etmek, do\u011fru planlan\u0131rsa sadece birka\u00e7 g\u00fcn s\u00fcren ve d\u0131\u015far\u0131dan bak\u0131ld\u0131\u011f\u0131nda kimsenin fark etmeyece\u011fi kadar sorunsuz bir i\u015flem haline gelebilir. \u0130\u015fin s\u0131rr\u0131; EPP kodu ve transfer kilidi gibi temel ad\u0131mlar\u0131 aceleye getirmemek, DNS taraf\u0131nda TTL ve kay\u0131t kopyalama i\u015fini \u00f6nceden yapmak ve e\u2011posta altyap\u0131n\u0131z i\u00e7in MX, SPF, DKIM de\u011fi\u015fikliklerini <strong>senkronize<\/strong> y\u00fcr\u00fctmektir.<\/p>\n<p>\u00d6zellikle kurumsal bir marka, e\u2011ticaret projesi veya yo\u011fun e\u2011posta trafi\u011fi olan bir yap\u0131 y\u00f6netiyorsan\u0131z, transferi tek ba\u015f\u0131n\u0131za omuzlamak zorunda de\u011filsiniz. DCHost\u2019ta; domain, hosting, VPS, dedicated sunucu ve colocation hizmetlerimizi <strong>tek y\u00f6netim paneli<\/strong> alt\u0131nda sunarken, ta\u015f\u0131ma s\u00fcre\u00e7lerinde de yan\u0131n\u0131zda oluyoruz. Plan\u0131n\u0131z ne kadar karma\u015f\u0131k olursa olsun, \u00f6nce yaz\u0131l\u0131 bir yol haritas\u0131 \u00e7\u0131kar\u0131p ard\u0131ndan ad\u0131mlar\u0131 s\u0131rayla uygulad\u0131\u011f\u0131n\u0131zda, \u201cta\u015f\u0131ma\u201d kelimesi art\u0131k korkutucu olmaktan \u00e7\u0131k\u0131yor.<\/p>\n<p>Alan ad\u0131n\u0131z\u0131 DCHost\u2019a transfer etmeyi d\u00fc\u015f\u00fcn\u00fcyorsan\u0131z; mevcut durumunuzu, DNS kay\u0131tlar\u0131n\u0131z\u0131 ve e\u2011posta altyap\u0131n\u0131z\u0131 birlikte g\u00f6zden ge\u00e7irip size \u00f6zel bir ge\u00e7i\u015f plan\u0131 haz\u0131rlayabiliriz. B\u00f6ylece hem maliyet hem de operasyonel karma\u015fa a\u00e7\u0131s\u0131ndan daha verimli bir altyap\u0131ya ge\u00e7erken, ziyaret\u00e7i ve e\u2011posta kayb\u0131 ya\u015famadan, ger\u00e7ekten <strong>kesintisiz bir transfer<\/strong> deneyimi ya\u015fars\u0131n\u0131z.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>\u0130&ccedil;indekiler1 Alan ad\u0131n\u0131 farkl\u0131 kay\u0131t firmas\u0131na transfer etmek neden bu kadar kritik?2 Neden alan ad\u0131n\u0131 farkl\u0131 kay\u0131t firmas\u0131na transfer edersiniz?3 Transfer \u00f6ncesi kritik kontrol listesi: s\u00fcreler, zamanlama ve riskler3.1 1. Alan ad\u0131n\u0131n s\u00fcresi ve yenileme penceresi3.2 2. 60 g\u00fcnl\u00fck transfer k\u0131s\u0131t\u0131 ve yeni kay\u0131tlar3.3 3. Whois ve ileti\u015fim e\u2011postas\u0131 do\u011frulu\u011fu3.4 4. SSL, SEO ve y\u00f6nlendirmeler4 [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":3996,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-3995","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-teknoloji"],"_links":{"self":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/3995","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/comments?post=3995"}],"version-history":[{"count":0,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/3995\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/3996"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=3995"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=3995"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=3995"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}