{"id":2200,"date":"2025-11-20T16:13:08","date_gmt":"2025-11-20T13:13:08","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/alan-adi-tasirken-e%e2%80%91posta-kesintisini-onlemek\/"},"modified":"2025-11-20T16:13:08","modified_gmt":"2025-11-20T13:13:08","slug":"alan-adi-tasirken-e%e2%80%91posta-kesintisini-onlemek","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/alan-adi-tasirken-e%e2%80%91posta-kesintisini-onlemek\/","title":{"rendered":"Alan Ad\u0131 Ta\u015f\u0131rken E\u2011Posta Kesintisini \u00d6nlemek"},"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_Adi_Tasima_Surecinde_EPosta_Neden_En_Kirilgan_Nokta\"><span class=\"toc_number toc_depth_1\">1<\/span> Alan Ad\u0131 Ta\u015f\u0131ma S\u00fcrecinde E\u2011Posta Neden En K\u0131r\u0131lgan Nokta?<\/a><\/li><li><a href=\"#Temel_Kavramlar_MX_SPF_DKIM_ve_TTL_Ne_Ise_Yarar\"><span class=\"toc_number toc_depth_1\">2<\/span> Temel Kavramlar: MX, SPF, DKIM ve TTL Ne \u0130\u015fe Yarar?<\/a><\/li><li><a href=\"#Hangi_Tasima_Senaryosunda_Ne_Degisiyor\"><span class=\"toc_number toc_depth_1\">3<\/span> Hangi Ta\u015f\u0131ma Senaryosunda Ne De\u011fi\u015fiyor?<\/a><ul><li><a href=\"#Senaryo_1_Sadece_Alan_Adi_Registrari_Degisiyor_DNS_Ayni\"><span class=\"toc_number toc_depth_2\">3.1<\/span> Senaryo 1: Sadece Alan Ad\u0131 Registrar\u2019\u0131 De\u011fi\u015fiyor (DNS Ayn\u0131)<\/a><\/li><li><a href=\"#Senaryo_2_DNS_Saglayicisi_Degisiyor_Mail_Sunucusu_Ayni\"><span class=\"toc_number toc_depth_2\">3.2<\/span> Senaryo 2: DNS Sa\u011flay\u0131c\u0131s\u0131 De\u011fi\u015fiyor (Mail Sunucusu Ayn\u0131)<\/a><\/li><li><a href=\"#Senaryo_3_EPosta_Hizmeti_de_Baska_Sunucuya_Tasiniyor\"><span class=\"toc_number toc_depth_2\">3.3<\/span> Senaryo 3: E\u2011Posta Hizmeti de Ba\u015fka Sunucuya Ta\u015f\u0131n\u0131yor<\/a><\/li><\/ul><\/li><li><a href=\"#TTL_Stratejisi_MX_ve_TXT_Kayitlari_Icin_Yayilimi_Kontrol_Etmek\"><span class=\"toc_number toc_depth_1\">4<\/span> TTL Stratejisi: MX ve TXT Kay\u0131tlar\u0131 \u0130\u00e7in Yay\u0131l\u0131m\u0131 Kontrol Etmek<\/a><ul><li><a href=\"#Hangi_Kayitlarda_TTL_Onemli\"><span class=\"toc_number toc_depth_2\">4.1<\/span> Hangi Kay\u0131tlarda TTL \u00d6nemli?<\/a><\/li><li><a href=\"#Onerilen_TTL_Zamanlamasi\"><span class=\"toc_number toc_depth_2\">4.2<\/span> \u00d6nerilen TTL Zamanlamas\u0131<\/a><\/li><\/ul><\/li><li><a href=\"#MX_Kayitlarini_Guvenle_Tasimak_Adim_Adim_Uygulama\"><span class=\"toc_number toc_depth_1\">5<\/span> MX Kay\u0131tlar\u0131n\u0131 G\u00fcvenle Ta\u015f\u0131mak: Ad\u0131m Ad\u0131m Uygulama<\/a><ul><li><a href=\"#1_Adim_Mevcut_DNS_Zoneunuzun_Tam_Envanterini_Alin\"><span class=\"toc_number toc_depth_2\">5.1<\/span> 1. Ad\u0131m: Mevcut DNS Zone\u2019unuzun Tam Envanterini Al\u0131n<\/a><\/li><li><a href=\"#2_Adim_Yeni_DNSte_Zoneu_Onden_Hazirlayin\"><span class=\"toc_number toc_depth_2\">5.2<\/span> 2. Ad\u0131m: Yeni DNS\u2019te Zone\u2019u \u00d6nden Haz\u0131rlay\u0131n<\/a><\/li><li><a href=\"#3_Adim_Yeni_Zoneu_Disaridan_Test_Edin\"><span class=\"toc_number toc_depth_2\">5.3<\/span> 3. Ad\u0131m: Yeni Zone\u2019u D\u0131\u015far\u0131dan Test Edin<\/a><\/li><li><a href=\"#4_Adim_NS_Gecisini_Planli_Bir_Zaman_Diliminde_Yapin\"><span class=\"toc_number toc_depth_2\">5.4<\/span> 4. Ad\u0131m: NS Ge\u00e7i\u015fini Planl\u0131 Bir Zaman Diliminde Yap\u0131n<\/a><\/li><li><a href=\"#5_Adim_Kisa_Sureli_Cift_Takip_Monitoring\"><span class=\"toc_number toc_depth_2\">5.5<\/span> 5. Ad\u0131m: K\u0131sa S\u00fcreli \u00c7ift Takip (Monitoring)<\/a><\/li><\/ul><\/li><li><a href=\"#SPF_Kaydini_Tasirken_Gonderilebilirligi_Bozmamak\"><span class=\"toc_number toc_depth_1\">6<\/span> SPF Kayd\u0131n\u0131 Ta\u015f\u0131rken G\u00f6nderilebilirli\u011fi Bozmamak<\/a><ul><li><a href=\"#Mevcut_SPF_Kaydinizi_Dogru_Okuyun\"><span class=\"toc_number toc_depth_2\">6.1<\/span> Mevcut SPF Kayd\u0131n\u0131z\u0131 Do\u011fru Okuyun<\/a><\/li><li><a href=\"#Yeni_Sunucuyu_SPFe_Onden_Ekleyin\"><span class=\"toc_number toc_depth_2\">6.2<\/span> Yeni Sunucuyu SPF\u2019e \u00d6nden Ekleyin<\/a><\/li><li><a href=\"#-all_Yerine_Kisa_Sureli_all_Kullanmaya_Deger_mi\"><span class=\"toc_number toc_depth_2\">6.3<\/span> \u201c-all\u201d Yerine K\u0131sa S\u00fcreli \u201c~all\u201d Kullanmaya De\u011fer mi?<\/a><\/li><\/ul><\/li><li><a href=\"#DKIM_Selector_ve_Anahtarlarini_Tasirken_Yapmaniz_Gerekenler\"><span class=\"toc_number toc_depth_1\">7<\/span> DKIM Selector ve Anahtarlar\u0131n\u0131 Ta\u015f\u0131rken Yapman\u0131z Gerekenler<\/a><ul><li><a href=\"#1_Mevcut_DKIM_Selectorlarini_Tespit_Edin\"><span class=\"toc_number toc_depth_2\">7.1<\/span> 1. Mevcut DKIM Selector\u2019lar\u0131n\u0131 Tespit Edin<\/a><\/li><li><a href=\"#2_Yeni_Sunucuda_DKIMi_Etkinlestirip_Public_Keyi_DNSe_Ekleyin\"><span class=\"toc_number toc_depth_2\">7.2<\/span> 2. Yeni Sunucuda DKIM\u2019i Etkinle\u015ftirip Public Key\u2019i DNS\u2019e Ekleyin<\/a><\/li><li><a href=\"#3_Eski_Selectori_Hemen_Silmeyin\"><span class=\"toc_number toc_depth_2\">7.3<\/span> 3. Eski Selector\u2019\u0131 Hemen Silmeyin<\/a><\/li><\/ul><\/li><li><a href=\"#DMARC_rDNS_ve_Diger_Ince_Ayarlar_Bonus_Katman\"><span class=\"toc_number toc_depth_1\">8<\/span> DMARC, rDNS ve Di\u011fer \u0130nce Ayarlar (Bonus Katman)<\/a><\/li><li><a href=\"#Ornek_Zaman_Cizelgesi_24_Saatlik_EPosta_Tasima_Plani\"><span class=\"toc_number toc_depth_1\">9<\/span> \u00d6rnek Zaman \u00c7izelgesi: 24 Saatlik E\u2011Posta Ta\u015f\u0131ma Plan\u0131<\/a><ul><li><a href=\"#Tasima_Oncesi_4872_Saat\"><span class=\"toc_number toc_depth_2\">9.1<\/span> Ta\u015f\u0131ma \u00d6ncesi 48\u201372 Saat<\/a><\/li><li><a href=\"#Tasima_Oncesi_24_Saat\"><span class=\"toc_number toc_depth_2\">9.2<\/span> Ta\u015f\u0131ma \u00d6ncesi 24 Saat<\/a><\/li><li><a href=\"#T0_Gecis_Ani\"><span class=\"toc_number toc_depth_2\">9.3<\/span> T0 \u2013 Ge\u00e7i\u015f An\u0131<\/a><\/li><li><a href=\"#T0_16_Saat\"><span class=\"toc_number toc_depth_2\">9.4<\/span> T0 + 1\u20136 Saat<\/a><\/li><li><a href=\"#T0_24_Saat\"><span class=\"toc_number toc_depth_2\">9.5<\/span> T0 + 24 Saat<\/a><\/li><\/ul><\/li><li><a href=\"#DCHost_ile_Alan_Adi_ve_EPosta_Tasimada_Is_Akisimiz\"><span class=\"toc_number toc_depth_1\">10<\/span> DCHost ile Alan Ad\u0131 ve E\u2011Posta Ta\u015f\u0131mada \u0130\u015f Ak\u0131\u015f\u0131m\u0131z<\/a><\/li><li><a href=\"#Sonuc_EPosta_Kesintisiz_Alan_Adi_Tasima_Icin_Yol_Haritan\"><span class=\"toc_number toc_depth_1\">11<\/span> Sonu\u00e7: E\u2011Posta Kesintisiz Alan Ad\u0131 Ta\u015f\u0131ma \u0130\u00e7in Yol Haritan<\/a><\/li><\/ul><\/div>\n<h2><span id=\"Alan_Adi_Tasima_Surecinde_EPosta_Neden_En_Kirilgan_Nokta\">Alan Ad\u0131 Ta\u015f\u0131ma S\u00fcrecinde E\u2011Posta Neden En K\u0131r\u0131lgan Nokta?<\/span><\/h2>\n<p>Alan ad\u0131n\u0131z\u0131 ba\u015fka bir kay\u0131t firmas\u0131na ta\u015f\u0131yor, DNS sa\u011flay\u0131c\u0131n\u0131z\u0131 de\u011fi\u015ftiriyor veya <a href=\"https:\/\/www.dchost.com\/tr\/web-hosting\">web hosting<\/a>\u2019inizi yeniliyorsan\u0131z; teknik olarak en hassas katman \u00e7o\u011fu zaman e\u2011posta oluyor. Web sitesi birka\u00e7 dakikal\u0131k kesintiyi \u00e7o\u011fu zaman tolere edebilir; ziyaret\u00e7i say\u0131s\u0131 biraz d\u00fc\u015fer, sayfa bir s\u00fcre ula\u015f\u0131lmaz olur ve sorun \u00e7\u00f6z\u00fcl\u00fcnce hayat normale d\u00f6ner. Ancak e\u2011posta taraf\u0131nda kaybolan bir i\u015f teklifi, ka\u00e7an bir destek bileti veya ula\u015fmayan bir fatura, finansal ve itibar a\u00e7\u0131s\u0131ndan geri d\u00f6nd\u00fcr\u00fclemez sonu\u00e7lar do\u011furabilir.<\/p>\n<p>DCHost taraf\u0131nda alan ad\u0131 ve hosting ta\u015f\u0131ma operasyonlar\u0131nda en \u00e7ok g\u00f6rd\u00fc\u011f\u00fcm\u00fcz hatalar hep ayn\u0131 yerde toplan\u0131yor: <strong>MX kay\u0131tlar\u0131 aceleyle g\u00fcncelleniyor<\/strong>, <strong>SPF\/DKIM ta\u015f\u0131nm\u0131yor veya yanl\u0131\u015f kopyalan\u0131yor<\/strong>, <strong>TTL de\u011ferleri y\u00fcksek b\u0131rak\u0131l\u0131yor<\/strong> ve sonu\u00e7ta birka\u00e7 saatlik \u201ce\u2011posta bo\u015flu\u011fu\u201d olu\u015fuyor. Bu bo\u015flukta gelen mailler kimi zaman eski sunucuya gidiyor, kimi zaman yeni sunucuda hen\u00fcz a\u00e7\u0131lmam\u0131\u015f kutulara teslim edilmeye \u00e7al\u0131\u015f\u0131l\u0131yor, kimi zaman da tamamen kayboluyor.<\/p>\n<p>Bu yaz\u0131da, alan ad\u0131n\u0131z\u0131 ta\u015f\u0131rken <strong>MX, SPF, DKIM ve TTL ayarlar\u0131n\u0131<\/strong> do\u011fru y\u00f6neterek <strong>s\u0131f\u0131ra yak\u0131n e\u2011posta kesintisi<\/strong> ile nas\u0131l ge\u00e7i\u015f yapabilece\u011finizi ad\u0131m ad\u0131m anlataca\u011f\u0131z. Ger\u00e7ek senaryolardan s\u00fczd\u00fc\u011f\u00fcm\u00fcz pratikleri, kontrol listelerini ve zamanlama ipu\u00e7lar\u0131n\u0131 payla\u015faca\u011f\u0131z; b\u00f6ylece bir sonraki ta\u015f\u0131ma operasyonunda \u201cmail kesildi mi?\u201d sorusu yerine \u201ciyi ki \u00f6nceden plan yapm\u0131\u015f\u0131z\u201d c\u00fcmlesini duyars\u0131n\u0131z.<\/p>\n<h2><span id=\"Temel_Kavramlar_MX_SPF_DKIM_ve_TTL_Ne_Ise_Yarar\">Temel Kavramlar: MX, SPF, DKIM ve TTL Ne \u0130\u015fe Yarar?<\/span><\/h2>\n<p>\u00d6nce k\u0131sa bir s\u00f6zl\u00fckle ba\u015flayal\u0131m; \u00e7\u00fcnk\u00fc alan ad\u0131 ta\u015f\u0131rken hangi kayd\u0131n ne yapt\u0131\u011f\u0131n\u0131 bilmek, nerede hata yapmaman\u0131z gerekti\u011fini netle\u015ftirir.<\/p>\n<ul>\n<li><strong>MX (Mail Exchanger)<\/strong>: Bir alan ad\u0131 i\u00e7in e\u2011postalar\u0131 hangi sunucular\u0131n kabul edece\u011fini s\u00f6yleyen DNS kayd\u0131d\u0131r. \u00d6rne\u011fin <em>mail.ornek.com<\/em> adresine i\u015faret eden bir MX kayd\u0131, gelen t\u00fcm maillerin o sunucuya y\u00f6nlenmesini sa\u011flar.<\/li>\n<li><strong>SPF (Sender Policy Framework)<\/strong>: Hangi IP adresleri veya sunucular\u0131n alan ad\u0131n\u0131z ad\u0131na e\u2011posta g\u00f6ndermeye yetkili oldu\u011funu tan\u0131mlayan bir <strong>TXT kayd\u0131<\/strong>d\u0131r. Al\u0131c\u0131 taraf, gelen mailin IP\u2019si bu kayda uymuyorsa \u201cspoofing olabilir\u201d diye \u015f\u00fcphelenir.<\/li>\n<li><strong>DKIM (DomainKeys Identified Mail)<\/strong>: G\u00f6nderilen maile kriptografik bir imza ekler. \u0130mzan\u0131n do\u011frulanabilmesi i\u00e7in DNS\u2019te <strong>public key<\/strong> (a\u00e7\u0131k anahtar) kay\u0131tlar\u0131 tutulur. Bu da genellikle <code>selector._domainkey.ornek.com<\/code> bi\u00e7iminde bir <strong>TXT kayd\u0131<\/strong>d\u0131r.<\/li>\n<li><strong>TTL (Time To Live)<\/strong>: DNS kay\u0131tlar\u0131n\u0131n \u00f6nbellek (cache) s\u00fcresini belirler. \u00d6rne\u011fin bir MX kayd\u0131n\u0131n TTL\u2019i 86400 saniye (24 saat) ise; bir kez sorgulayan istemci bu kayd\u0131 24 saat boyunca g\u00fcncellemeden kullan\u0131r.<\/li>\n<\/ul>\n<p>DNS kay\u0131t tipleri, ad sunucular\u0131 ve yay\u0131l\u0131m davran\u0131\u015flar\u0131 hakk\u0131nda temel bilginizi tazelemek isterseniz, \u00f6nce <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\u0131tlar\u0131 A\u2019dan Z\u2019ye ve s\u0131k yap\u0131lan hatalar<\/a> yaz\u0131m\u0131za g\u00f6z atman\u0131z faydal\u0131 olacakt\u0131r.<\/p>\n<h2><span id=\"Hangi_Tasima_Senaryosunda_Ne_Degisiyor\">Hangi Ta\u015f\u0131ma Senaryosunda Ne De\u011fi\u015fiyor?<\/span><\/h2>\n<p>Alan ad\u0131 ta\u015f\u0131rken her zaman ayn\u0131 bile\u015fenleri oynatm\u0131yorsunuz. \u00d6nce hangi senaryoda oldu\u011funuzu netle\u015ftirin; sonraki t\u00fcm ad\u0131mlar buna g\u00f6re \u015fekillenecek.<\/p>\n<h3><span id=\"Senaryo_1_Sadece_Alan_Adi_Registrari_Degisiyor_DNS_Ayni\">Senaryo 1: Sadece Alan Ad\u0131 Registrar\u2019\u0131 De\u011fi\u015fiyor (DNS Ayn\u0131)<\/span><\/h3>\n<p>Burada sadece alan ad\u0131n\u0131z\u0131 tuttu\u011funuz firma de\u011fi\u015fiyor; <strong>nameserver (NS) kay\u0131tlar\u0131n\u0131z<\/strong> ayn\u0131 kal\u0131yorsa teknik olarak MX, SPF, DKIM ve TTL taraf\u0131nda bir de\u011fi\u015fiklik olmaz. Yine de pratik olarak \u015fu kontrolleri \u00f6neriyoruz:<\/p>\n<ul>\n<li>Transfer sonras\u0131nda NS kay\u0131tlar\u0131n\u0131z\u0131n <strong>otomatik olarak de\u011fi\u015ftirilmedi\u011finden<\/strong> emin olun.<\/li>\n<li>Registrar panelinde <strong>DNSSEC veya \u00f6zel glue record<\/strong> gibi ek \u00f6zellikler kullan\u0131yorsan\u0131z, yeni tarafa birebir aktar\u0131ld\u0131\u011f\u0131n\u0131 kontrol edin.<\/li>\n<li><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 ad\u0131mlar\u0131n\u0131<\/a> takip ederken e\u2011posta kay\u0131tlar\u0131n\u0131zda (MX\/TXT) hi\u00e7bir otomatik \u201coptimizasyon\u201d yap\u0131lmad\u0131\u011f\u0131n\u0131 do\u011frulay\u0131n.<\/li>\n<\/ul>\n<p>Bu senaryoda e\u2011posta kesintisi ya\u015fanma ihtimali en d\u00fc\u015f\u00fck olsa da, yanl\u0131\u015fl\u0131kla DNS\u2019in de ta\u015f\u0131nmas\u0131 veya bo\u015f bir zone ile \u00fczerine yaz\u0131lmas\u0131 h\u00e2l\u00e2 ger\u00e7ek bir risk.<\/p>\n<h3><span id=\"Senaryo_2_DNS_Saglayicisi_Degisiyor_Mail_Sunucusu_Ayni\">Senaryo 2: DNS Sa\u011flay\u0131c\u0131s\u0131 De\u011fi\u015fiyor (Mail Sunucusu Ayn\u0131)<\/span><\/h3>\n<p>Bu, pratikte en \u00e7ok kafa kar\u0131\u015ft\u0131ran durum. Mail h\u00e2l\u00e2 ayn\u0131 sunucuda kal\u0131yor, ama alan ad\u0131n\u0131z\u0131n DNS y\u00f6netimi farkl\u0131 bir yere ta\u015f\u0131n\u0131yor. Dolay\u0131s\u0131yla:<\/p>\n<ul>\n<li>Eski DNS\u2019teki <strong>t\u00fcm MX, A\/AAAA, SPF (TXT), DKIM (TXT) ve olas\u0131 DMARC (TXT)<\/strong> kay\u0131tlar\u0131n\u0131n yeni DNS\u2019te <strong>birebir olu\u015fturulmas\u0131<\/strong> gerekiyor.<\/li>\n<li><strong>TTL de\u011ferleri do\u011fru stratejiyle d\u00fc\u015f\u00fcr\u00fclmezse<\/strong>, baz\u0131 kullan\u0131c\u0131lar g\u00fcnlerce eski MX kayd\u0131n\u0131 kullanmaya devam edebilir.<\/li>\n<\/ul>\n<p>Burada odak noktam\u0131z: <strong>DNS zone\u2019unuzu kusursuz klonlamak ve ge\u00e7i\u015ften \u00f6nce TTL\u2019i ayarlamak<\/strong>.<\/p>\n<h3><span id=\"Senaryo_3_EPosta_Hizmeti_de_Baska_Sunucuya_Tasiniyor\">Senaryo 3: E\u2011Posta Hizmeti de Ba\u015fka Sunucuya Ta\u015f\u0131n\u0131yor<\/span><\/h3>\n<p>En riskli ama do\u011fru planland\u0131\u011f\u0131nda en kontroll\u00fc ilerleyen senaryo budur. Hem web hosting\u2019iniz hem de e\u2011postan\u0131z DCHost taraf\u0131na ge\u00e7iyor olabilir; ya da sadece e\u2011postay\u0131 farkl\u0131 bir sunucuya al\u0131yor olabilirsiniz. Bu durumda:<\/p>\n<ul>\n<li>Hem <strong>MX kay\u0131tlar\u0131n\u0131z<\/strong> hem de bu MX\u2019lerin i\u015faret etti\u011fi <strong>A\/AAAA kay\u0131tlar\u0131<\/strong> de\u011fi\u015fecektir.<\/li>\n<li>Yeni sunucunun IP\u2019si <strong>SPF kayd\u0131na<\/strong> mutlaka eklenmeli, eski IP ise bir s\u00fcre daha listede kalmal\u0131d\u0131r.<\/li>\n<li>Yeni e\u2011posta sunucusunda olu\u015fturulan <strong>DKIM selector\u2019lar\u0131<\/strong> DNS\u2019e eklenmeli; m\u00fcmk\u00fcnse eski selector en az birka\u00e7 g\u00fcn daha a\u00e7\u0131k tutulmal\u0131d\u0131r.<\/li>\n<\/ul>\n<p>Bu senaryoda birazdan anlataca\u011f\u0131m\u0131z <strong>zaman \u00e7izelgesi ve \u00e7ift tarafl\u0131 SPF\/DKIM stratejisi<\/strong> kritik \u00f6nem kazan\u0131yor.<\/p>\n<h2><span id=\"TTL_Stratejisi_MX_ve_TXT_Kayitlari_Icin_Yayilimi_Kontrol_Etmek\">TTL Stratejisi: MX ve TXT Kay\u0131tlar\u0131 \u0130\u00e7in Yay\u0131l\u0131m\u0131 Kontrol Etmek<\/span><\/h2>\n<p>E\u2011posta kesintisini \u00f6nlemenin omurgas\u0131 TTL stratejisidir. MX, A\/AAAA ve TXT (SPF, DKIM, DMARC) kay\u0131tlar\u0131n\u0131z\u0131n TTL de\u011feri ne kadar y\u00fcksekse, de\u011fi\u015fikliklerin t\u00fcm d\u00fcnyaya yay\u0131lmas\u0131 o kadar ge\u00e7 olur.<\/p>\n<h3><span id=\"Hangi_Kayitlarda_TTL_Onemli\">Hangi Kay\u0131tlarda TTL \u00d6nemli?<\/span><\/h3>\n<ul>\n<li><strong>MX kay\u0131tlar\u0131<\/strong>: Maillerin hangi sunucuya gidece\u011fini belirler.<\/li>\n<li><strong>A\/AAAA kay\u0131tlar\u0131<\/strong>: MX\u2019in i\u015faret etti\u011fi mail sunucusunun IP adresini g\u00f6sterir.<\/li>\n<li><strong>TXT (SPF\/DKIM\/DMARC)<\/strong>: G\u00f6nderici do\u011frulama ve itibar i\u00e7in kullan\u0131l\u0131r.<\/li>\n<\/ul>\n<p>Ta\u015f\u0131ma \u00f6ncesi bu kay\u0131tlar\u0131n TTL\u2019lerini planl\u0131 \u015fekilde d\u00fc\u015f\u00fcrmek, ge\u00e7i\u015f an\u0131nda geri d\u00f6n\u00fc\u015f\u00fc kolay ve h\u0131zl\u0131 bir yap\u0131 sa\u011flar. TTL planlamas\u0131n\u0131 daha derinlemesine anlamak isterseniz, <a href=\"https:\/\/www.dchost.com\/blog\/zero-downtime-tasima-icin-ttl-stratejileri-dns-yayilimini-gercekten-nasil-hizlandirirsin\/\">zero-downtime ta\u015f\u0131ma i\u00e7in TTL stratejileri<\/a> rehberimizi mutlaka okuyun.<\/p>\n<h3><span id=\"Onerilen_TTL_Zamanlamasi\">\u00d6nerilen TTL Zamanlamas\u0131<\/span><\/h3>\n<ol>\n<li><strong>Ta\u015f\u0131ma tarihinden 48\u201372 saat \u00f6nce<\/strong>: Mevcut DNS \u00fczerinde ilgili MX, A\/AAAA ve TXT kay\u0131tlar\u0131n\u0131n TTL\u2019ini d\u00fc\u015f\u00fcr\u00fcn.<br \/>Tipik olarak:\n<ul>\n<li>MX: 300\u2013600 saniye<\/li>\n<li>Mail sunucusuna i\u015faret eden A\/AAAA: 300\u2013600 saniye<\/li>\n<li>SPF\/DKIM\/DMARC TXT: 300\u2013600 saniye<\/li>\n<\/ul>\n<\/li>\n<li><strong>Ge\u00e7i\u015ften hemen sonra<\/strong>: Her \u015feyin stabil \u00e7al\u0131\u015ft\u0131\u011f\u0131ndan emin olduktan sonra TTL\u2019leri tekrar 3600\u201314400 saniye band\u0131na y\u00fckseltebilirsiniz.<\/li>\n<\/ol>\n<p>Bu yakla\u015f\u0131m, olas\u0131 bir hata durumunda \u201cgeri sarma\u201d (rollback) yapman\u0131z\u0131 kolayla\u015ft\u0131r\u0131r. Yanl\u0131\u015f MX\u2019e ge\u00e7ti\u011finizi fark ederseniz TTL d\u00fc\u015f\u00fck oldu\u011fu i\u00e7in birka\u00e7 dakika i\u00e7inde t\u00fcm d\u00fcnya do\u011fru kayda d\u00f6ner.<\/p>\n<h2><span id=\"MX_Kayitlarini_Guvenle_Tasimak_Adim_Adim_Uygulama\">MX Kay\u0131tlar\u0131n\u0131 G\u00fcvenle Ta\u015f\u0131mak: Ad\u0131m Ad\u0131m Uygulama<\/span><\/h2>\n<p>\u015eimdi en kritik par\u00e7aya gelelim: MX taraf\u0131n\u0131 nas\u0131l planl\u0131yoruz? A\u015fa\u011f\u0131daki ad\u0131mlar \u00f6zellikle <strong>DNS sa\u011flay\u0131c\u0131s\u0131 de\u011fi\u015firken, mail sunucusu ayn\u0131 kal\u0131yorsa<\/strong> birebir uygulanabilir; e\u2011posta sunucusunun da de\u011fi\u015fti\u011fi senaryoda ise baz\u0131 ad\u0131mlar\u0131 uyarlayaca\u011f\u0131z.<\/p>\n<h3><span id=\"1_Adim_Mevcut_DNS_Zoneunuzun_Tam_Envanterini_Alin\">1. Ad\u0131m: Mevcut DNS Zone\u2019unuzun Tam Envanterini Al\u0131n<\/span><\/h3>\n<p>\u0130lk i\u015f, mevcut DNS zone\u2019unuzdaki ilgili kay\u0131tlar\u0131 eksiksiz \u00e7\u0131karmak:<\/p>\n<ul>\n<li>T\u00fcm <strong>MX kay\u0131tlar\u0131<\/strong> (priority, hostname)<\/li>\n<li>MX\u2019in i\u015faret etti\u011fi <strong>A\/AAAA kay\u0131tlar\u0131<\/strong><\/li>\n<li>Alan ad\u0131n\u0131za ba\u011fl\u0131 t\u00fcm <strong>TXT kay\u0131tlar\u0131<\/strong> (SPF, DKIM selector\u2019lar\u0131, DMARC vb.)<\/li>\n<\/ul>\n<p>Bunu manuel olarak panelden not edebilir veya zone dosyas\u0131n\u0131 export edebilirsiniz. DCHost DNS altyap\u0131s\u0131na ge\u00e7iyorsan\u0131z, bu export dosyas\u0131n\u0131 teknik ekibimizle payla\u015farak otomatik import s\u00fcrecini h\u0131zland\u0131rabilirsiniz.<\/p>\n<h3><span id=\"2_Adim_Yeni_DNSte_Zoneu_Onden_Hazirlayin\">2. Ad\u0131m: Yeni DNS\u2019te Zone\u2019u \u00d6nden Haz\u0131rlay\u0131n<\/span><\/h3>\n<p>Hen\u00fcz NS kay\u0131tlar\u0131n\u0131 de\u011fi\u015ftirmeden, yeni DNS sa\u011flay\u0131c\u0131n\u0131zda (\u00f6rne\u011fin DCHost DNS) alan ad\u0131n\u0131z i\u00e7in bir zone olu\u015fturun ve az \u00f6nce \u00e7\u0131kard\u0131\u011f\u0131n\u0131z <strong>MX, A\/AAAA ve TXT kay\u0131tlar\u0131n\u0131 birebir ekleyin<\/strong>. Bu a\u015famada:<\/p>\n<ul>\n<li>TTL de\u011ferlerini plan\u0131n\u0131za g\u00f6re (300\u2013600 sn) d\u00fc\u015f\u00fck girin.<\/li>\n<li>Gereksiz veya tarih ge\u00e7mi\u015f kay\u0131tlar\u0131 ta\u015f\u0131madan \u00f6nce mutlaka iki kez d\u00fc\u015f\u00fcn\u00fcn; ama emin de\u011filseniz <strong>silmek yerine aynen ta\u015f\u0131mak daha g\u00fcvenlidir<\/strong>.<\/li>\n<\/ul>\n<h3><span id=\"3_Adim_Yeni_Zoneu_Disaridan_Test_Edin\">3. Ad\u0131m: Yeni Zone\u2019u D\u0131\u015far\u0131dan Test Edin<\/span><\/h3>\n<p>NS ge\u00e7i\u015fi yapmadan \u00f6nce yeni zone\u2019un do\u011fru oldu\u011fundan emin olmak i\u00e7in \u201cdig\u201d veya benzeri ara\u00e7larla <strong>do\u011frudan yeni nameserver\u2019lar\u0131 sorgulay\u0131n<\/strong>. \u00d6rne\u011fin:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">dig @yeni-ns1.ornek.net alanadiniz.com MX\n<\/code><\/pre>\n<p>Bu sorgu, global DNS\u2019ten ba\u011f\u0131ms\u0131z olarak sadece yeni NS \u00fczerinde hangi MX\u2019in tan\u0131ml\u0131 oldu\u011funu g\u00f6sterecektir. Ayn\u0131 testi SPF ve DKIM TXT kay\u0131tlar\u0131 i\u00e7in de yap\u0131n.<\/p>\n<h3><span id=\"4_Adim_NS_Gecisini_Planli_Bir_Zaman_Diliminde_Yapin\">4. Ad\u0131m: NS Ge\u00e7i\u015fini Planl\u0131 Bir Zaman Diliminde Yap\u0131n<\/span><\/h3>\n<p>Yo\u011fun e\u2011posta trafi\u011fi ald\u0131\u011f\u0131n\u0131z saatleri g\u00f6z \u00f6n\u00fcnde bulundurun. Genellikle:<\/p>\n<ul>\n<li>Hafta i\u00e7i mesai saatlerinin d\u0131\u015f\u0131<\/li>\n<li>\u00d6nemli kampanya\/duyuru g\u00f6nderimlerinin olmad\u0131\u011f\u0131 bir g\u00fcn<\/li>\n<\/ul>\n<p>daha g\u00fcvenlidir. NS de\u011fi\u015fikli\u011fini yapt\u0131ktan sonra, d\u00fc\u015f\u00fck TTL sayesinde birka\u00e7 saat i\u00e7erisinde t\u00fcm sorgular yeni DNS\u2019e y\u00f6nlenecektir.<\/p>\n<h3><span id=\"5_Adim_Kisa_Sureli_Cift_Takip_Monitoring\">5. Ad\u0131m: K\u0131sa S\u00fcreli \u00c7ift Takip (Monitoring)<\/span><\/h3>\n<p>Ge\u00e7i\u015ften sonraki 24 saat boyunca:<\/p>\n<ul>\n<li>Hem eski hem yeni mail sunucusunun loglar\u0131n\u0131 (varsa) takip edin.<\/li>\n<li>Farkl\u0131 a\u011flardan test adreslerine mail atarak <strong>mail header\u2019lar\u0131ndan<\/strong> hangi MX\u2019e gitti\u011fini ve hangi SPF\/DKIM kay\u0131tlar\u0131n\u0131n kullan\u0131ld\u0131\u011f\u0131n\u0131 kontrol edin.<\/li>\n<\/ul>\n<p>Bu a\u015famada, bir s\u00fcreli\u011fine <strong>test@alanadiniz.com<\/strong> gibi ek bir adres olu\u015fturup farkl\u0131 sa\u011flay\u0131c\u0131lardan test maili g\u00f6ndermek, t\u00fcm zincirin \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 g\u00f6rsel olarak do\u011frulaman\u0131z\u0131 kolayla\u015ft\u0131r\u0131r.<\/p>\n<h2><span id=\"SPF_Kaydini_Tasirken_Gonderilebilirligi_Bozmamak\">SPF Kayd\u0131n\u0131 Ta\u015f\u0131rken G\u00f6nderilebilirli\u011fi Bozmamak<\/span><\/h2>\n<p>SPF hatalar\u0131, ta\u015f\u0131ma sonras\u0131nda \u201cmailler spam\u2019e d\u00fc\u015f\u00fcyor\u201d \u015fik\u00e2yetlerinin ana sebebi. \u00c7\u00fcnk\u00fc SPF, sizin ad\u0131n\u0131za mail g\u00f6ndermeye yetkili IP veya sunucular\u0131n listesini tutuyor. DNS veya e\u2011posta altyap\u0131s\u0131n\u0131 de\u011fi\u015ftirirken bu listeyi g\u00fcncellemezseniz, al\u0131c\u0131 taraf\u0131nda SPF <code>fail<\/code> sonu\u00e7lar\u0131 almaya ba\u015flars\u0131n\u0131z.<\/p>\n<h3><span id=\"Mevcut_SPF_Kaydinizi_Dogru_Okuyun\">Mevcut SPF Kayd\u0131n\u0131z\u0131 Do\u011fru Okuyun<\/span><\/h3>\n<p>Tipik bir SPF kayd\u0131 \u015f\u00f6yle g\u00f6r\u00fcnebilir:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">v=spf1 ip4:1.2.3.4 include:_spf.ornek.net -all\n<\/code><\/pre>\n<p>Burada:<\/p>\n<ul>\n<li><code>ip4:1.2.3.4<\/code> \u2192 Alan ad\u0131n\u0131z ad\u0131na mail g\u00f6ndermeye yetkili bir sabit IP<\/li>\n<li><code>include:_spf.ornek.net<\/code> \u2192 Ba\u015fka bir SPF kayd\u0131n\u0131n kurallar\u0131n\u0131n da ge\u00e7erli olaca\u011f\u0131n\u0131 s\u00f6yler<\/li>\n<li><code>-all<\/code> \u2192 Listede olmayan her g\u00f6ndereni reddet anlam\u0131na gelir<\/li>\n<\/ul>\n<h3><span id=\"Yeni_Sunucuyu_SPFe_Onden_Ekleyin\">Yeni Sunucuyu SPF\u2019e \u00d6nden Ekleyin<\/span><\/h3>\n<p>E\u2011posta sunucusunu DCHost \u00fczerinde yeni bir IP\u2019ye ta\u015f\u0131yorsan\u0131z, plan \u015fu olmal\u0131:<\/p>\n<ol>\n<li>Yeni mail sunucusu i\u00e7in kullanaca\u011f\u0131n\u0131z IP veya SMTP host\u2019unu netle\u015ftirin.<\/li>\n<li>Mevcut SPF kayd\u0131n\u0131za <strong>bu IP\u2019yi\/host\u2019u da ekleyin<\/strong>. \u00d6rne\u011fin:<br \/><code>v=spf1 ip4:1.2.3.4 ip4:5.6.7.8 include:_spf.ornek.net -all<\/code><\/li>\n<li>Bu de\u011fi\u015fikli\u011fi, MX de\u011fi\u015fiminden <strong>\u00f6nce<\/strong> yap\u0131n ki yeni sunucudan \u00e7\u0131kacak mailler de SPF taraf\u0131ndan yetkili kabul edilsin.<\/li>\n<\/ol>\n<p>Bir s\u00fcre hem eski hem yeni IP\u2019yi SPF\u2019te birlikte tutmakta sak\u0131nca yoktur. Ge\u00e7i\u015f tamamland\u0131ktan ve eski sunucudan mail \u00e7\u0131kmad\u0131\u011f\u0131ndan emin olduktan sonra eski IP\u2019yi kay\u0131ttan kald\u0131rabilirsiniz.<\/p>\n<h3><span id=\"-all_Yerine_Kisa_Sureli_all_Kullanmaya_Deger_mi\">\u201c-all\u201d Yerine K\u0131sa S\u00fcreli \u201c~all\u201d Kullanmaya De\u011fer mi?<\/span><\/h3>\n<p>Ta\u015f\u0131ma s\u0131ras\u0131nda \u00e7ok agresif bir SPF politikas\u0131 (\u00f6rne\u011fin <code>-all<\/code>) bazen istemeden ge\u00e7ici sorunlara yol a\u00e7abilir. Kimi ekipler, ge\u00e7i\u015f s\u0131ras\u0131nda k\u0131sa s\u00fcreli\u011fine <code>-all<\/code> yerine <code>~all<\/code> (soft fail) kullan\u0131p, her \u015feyin oturmas\u0131ndan sonra tekrar <code>-all<\/code>\u2019a d\u00f6nmeyi tercih ediyor.<\/p>\n<p>Bu yakla\u015f\u0131m, \u00f6zellikle karma\u015f\u0131k <code>include:<\/code> zincirleri kullan\u0131yorsan\u0131z mant\u0131kl\u0131 olabilir. SPF\u2019in temel ve geli\u015fmi\u015f kurulum detaylar\u0131n\u0131, ayr\u0131ca <strong>10 lookup s\u0131n\u0131r\u0131na tak\u0131lmamak i\u00e7in flattening tekniklerini<\/strong> \u00f6\u011frenmek isterseniz, <a href=\"https:\/\/www.dchost.com\/blog\/spf-dkim-dmarc-ve-rdns-ile-e-posta-teslim-edilebilirligini-nasil-adim-adim-yukseltirsin\/\">SPF, DKIM, DMARC ve rDNS ile e\u2011posta teslim edilebilirli\u011fini art\u0131rma rehberimize<\/a> ve <a href=\"https:\/\/www.dchost.com\/blog\/spf-flattening-ile-10-lookup-duvarini-nasil-asarsin-ci-cd-ve-workers-ile-yasayan-spf\/\">SPF flattening ile 10 lookup s\u0131n\u0131r\u0131n\u0131 a\u015fma<\/a> yaz\u0131m\u0131za g\u00f6z atabilirsiniz.<\/p>\n<h2><span id=\"DKIM_Selector_ve_Anahtarlarini_Tasirken_Yapmaniz_Gerekenler\">DKIM Selector ve Anahtarlar\u0131n\u0131 Ta\u015f\u0131rken Yapman\u0131z Gerekenler<\/span><\/h2>\n<p>DKIM taraf\u0131nda yanl\u0131\u015f yap\u0131lan ta\u015f\u0131ma genellikle \u015fu sonu\u00e7lar\u0131 do\u011furur: G\u00f6nderdi\u011finiz maillerin header\u2019lar\u0131nda <code>dkim=fail<\/code> g\u00f6r\u00fcn\u00fcr ve DMARC kullan\u0131yorsan\u0131z spam kutusuna d\u00fc\u015fme oran\u0131n\u0131z artar. Bunu \u00f6nlemek i\u00e7in hem eski hem yeni DKIM anahtarlar\u0131n\u0131 bir s\u00fcre <strong>paralel<\/strong> \u00e7al\u0131\u015ft\u0131rmak en g\u00fcvenli yoldur.<\/p>\n<h3><span id=\"1_Mevcut_DKIM_Selectorlarini_Tespit_Edin\">1. Mevcut DKIM Selector\u2019lar\u0131n\u0131 Tespit Edin<\/span><\/h3>\n<p>\u00d6rne\u011fin cPanel kullan\u0131yorsan\u0131z selector genellikle <code>default<\/code> olur ve DNS\u2019te \u015fu isimle bir TXT kayd\u0131 g\u00f6r\u00fcrs\u00fcn\u00fcz:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">default._domainkey.alanadiniz.com\n<\/code><\/pre>\n<p>Ta\u015f\u0131ma \u00f6ncesi t\u00fcm aktif selector isimlerini ve kar\u015f\u0131l\u0131k gelen TXT kay\u0131tlar\u0131n\u0131 not al\u0131n. Baz\u0131 sistemler \u00e7oklu selector kullanabilir (\u00f6rne\u011fin <code>k1._domainkey<\/code>, <code>k2._domainkey<\/code> gibi).<\/p>\n<h3><span id=\"2_Yeni_Sunucuda_DKIMi_Etkinlestirip_Public_Keyi_DNSe_Ekleyin\">2. Yeni Sunucuda DKIM\u2019i Etkinle\u015ftirip Public Key\u2019i DNS\u2019e Ekleyin<\/span><\/h3>\n<p>Yeni e\u2011posta sunucusunu DCHost \u00fczerinde kurduysan\u0131z, kontrol paneli \u00fczerinden ilgili domain i\u00e7in DKIM\u2019i etkinle\u015ftirdi\u011finizde sistem size yeni bir <strong>selector ad\u0131<\/strong> ve <strong>TXT kayd\u0131<\/strong> verecektir. Bu kayd\u0131:<\/p>\n<ul>\n<li>Yeni DNS zone\u2019unuza ekleyin.<\/li>\n<li>M\u00fcmk\u00fcnse selector ad\u0131n\u0131 eskiyle ayn\u0131 tutarak ge\u00e7i\u015fi sadele\u015ftirin; bu m\u00fcmk\u00fcn de\u011filse, bir s\u00fcre her iki selector\u2019\u0131 da (eski ve yeni) DNS\u2019te tutabilirsiniz.<\/li>\n<\/ul>\n<h3><span id=\"3_Eski_Selectori_Hemen_Silmeyin\">3. Eski Selector\u2019\u0131 Hemen Silmeyin<\/span><\/h3>\n<p>\u00d6zellikle karma\u015f\u0131k yap\u0131larda, baz\u0131 arka plan servisleri veya otomatik g\u00f6nderim sistemleri bir s\u00fcre eski sunucuyu kullanmaya devam edebilir. Bu y\u00fczden:<\/p>\n<ul>\n<li>Eski sunucu tamamen devreden \u00e7\u0131kana kadar, ona ait DKIM selector TXT kay\u0131tlar\u0131n\u0131 DNS\u2019te b\u0131rak\u0131n.<\/li>\n<li>Ge\u00e7i\u015ften sonra belirli bir s\u00fcre (\u00f6rne\u011fin 3\u20137 g\u00fcn) mail header\u2019lar\u0131n\u0131 kontrol ederek hangi selector\u2019lar\u0131n fiilen kullan\u0131ld\u0131\u011f\u0131n\u0131 teyit edin.<\/li>\n<\/ul>\n<p>Ba\u015far\u0131l\u0131 bir ta\u015f\u0131ma sonras\u0131nda DKIM header\u2019\u0131nda <code>dkim=pass<\/code> g\u00f6rmeniz gerekir.<\/p>\n<h2><span id=\"DMARC_rDNS_ve_Diger_Ince_Ayarlar_Bonus_Katman\">DMARC, rDNS ve Di\u011fer \u0130nce Ayarlar (Bonus Katman)<\/span><\/h2>\n<p>Makalenin oda\u011f\u0131 MX, SPF, DKIM ve TTL olsa da, e\u2011posta ta\u015f\u0131ma s\u00fcrecinde <strong>DMARC ve rDNS<\/strong> (ters DNS) ayar\u0131n\u0131 da g\u00f6zden ge\u00e7irmek iyi bir pratiktir:<\/p>\n<ul>\n<li><strong>DMARC<\/strong>: E\u011fer zaten DMARC kullan\u0131yorsan\u0131z, yeni SPF ve DKIM d\u00fczeninizle uyumlu olup olmad\u0131\u011f\u0131n\u0131 test edin. \u00c7ok kat\u0131 (<code>p=reject<\/code>) bir politika kullan\u0131yorsan\u0131z, ta\u015f\u0131ma s\u00fcresince k\u0131sa s\u00fcreli <code>p=quarantine<\/code> ile ilerlemeyi d\u00fc\u015f\u00fcnebilirsiniz.<\/li>\n<li><strong>rDNS (PTR)<\/strong>: Yeni IP\u2019lere ge\u00e7ti\u011finizde ters DNS kay\u0131tlar\u0131n\u0131z\u0131n <strong>mail g\u00f6nderdi\u011finiz hostname ile uyumlu<\/strong> oldu\u011fundan emin olun.<\/li>\n<\/ul>\n<p>Bu katmana daha derinlemesine girmek isterseniz, DMARC ve itibar y\u00f6netimi i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/gelismis-dmarc-ve-bimi-rua-ruf-raporlarindan-marka-gostergesine-nasil-yol-alinir\/\">geli\u015fmi\u015f DMARC ve BIMI rehberimizi<\/a> inceleyebilirsiniz.<\/p>\n<h2><span id=\"Ornek_Zaman_Cizelgesi_24_Saatlik_EPosta_Tasima_Plani\">\u00d6rnek Zaman \u00c7izelgesi: 24 Saatlik E\u2011Posta Ta\u015f\u0131ma Plan\u0131<\/span><\/h2>\n<p>A\u015fa\u011f\u0131daki plan, DNS sa\u011flay\u0131c\u0131s\u0131n\u0131 ve e\u2011posta sunucusunu birlikte ta\u015f\u0131d\u0131\u011f\u0131n\u0131z tipik bir senaryoya g\u00f6re haz\u0131rlanm\u0131\u015ft\u0131r. S\u00fcreler \u00f6rnektir; kendi trafi\u011finize g\u00f6re esnetebilirsiniz.<\/p>\n<h3><span id=\"Tasima_Oncesi_4872_Saat\">Ta\u015f\u0131ma \u00d6ncesi 48\u201372 Saat<\/span><\/h3>\n<ul>\n<li>Mevcut DNS\u2019te MX, A\/AAAA ve TXT (SPF, DKIM, DMARC) kay\u0131tlar\u0131n\u0131n TTL\u2019ini 300\u2013600 saniyeye d\u00fc\u015f\u00fcr\u00fcn.<\/li>\n<li>Mevcut SPF kayd\u0131n\u0131za <strong>yeni mail sunucusu IP\u2019sini<\/strong> ekleyin.<\/li>\n<li>Yeni e\u2011posta sunucusunda domain\u2019i tan\u0131mlay\u0131n; test kullan\u0131c\u0131lar\u0131 olu\u015fturun.<\/li>\n<\/ul>\n<h3><span id=\"Tasima_Oncesi_24_Saat\">Ta\u015f\u0131ma \u00d6ncesi 24 Saat<\/span><\/h3>\n<ul>\n<li>Yeni DNS zone\u2019unuzu tamamen haz\u0131rlay\u0131n; t\u00fcm MX, A\/AAAA, SPF, DKIM, DMARC kay\u0131tlar\u0131 birebir girilmi\u015f olsun.<\/li>\n<li><code>dig<\/code> veya benzeri ara\u00e7larla yeni NS \u00fczerinden kay\u0131tlar\u0131n\u0131z\u0131 test edin.<\/li>\n<li>Test adreslerine (<em>test@alanadiniz.com<\/em>) yeni sunucudan mail g\u00f6nderip header\u2019lar\u0131 inceleyin; SPF\/DKIM\u2019in <code>pass<\/code> verdi\u011fini do\u011frulay\u0131n.<\/li>\n<\/ul>\n<h3><span id=\"T0_Gecis_Ani\">T0 \u2013 Ge\u00e7i\u015f An\u0131<\/span><\/h3>\n<ul>\n<li>Alan ad\u0131n\u0131z\u0131n NS kay\u0131tlar\u0131n\u0131 yeni DNS sa\u011flay\u0131c\u0131s\u0131na (\u00f6rne\u011fin DCHost DNS) y\u00f6nlendirin.<\/li>\n<li>MX kay\u0131tlar\u0131n\u0131zda yeni mail sunucusunu i\u015faret edecek de\u011fi\u015fiklikleri uygulay\u0131n (e\u011fer mail sunucusu da de\u011fi\u015fiyorsa).<\/li>\n<\/ul>\n<h3><span id=\"T0_16_Saat\">T0 + 1\u20136 Saat<\/span><\/h3>\n<ul>\n<li>Farkl\u0131 a\u011flardan test mailleri g\u00f6ndererek gelen kutular\u0131na ula\u015f\u0131p ula\u015fmad\u0131\u011f\u0131n\u0131, gecikme s\u00fcresini ve spam\u2019e d\u00fc\u015f\u00fcp d\u00fc\u015fmedi\u011fini kontrol edin.<\/li>\n<li>Gelen ve giden mail loglar\u0131n\u0131 izleyin; bouncelar\u0131 ve hata mesajlar\u0131n\u0131 not al\u0131n.<\/li>\n<li>Gerekirse SPF\/DKIM kay\u0131tlar\u0131nda k\u00fc\u00e7\u00fck d\u00fczeltmeler yap\u0131n.<\/li>\n<\/ul>\n<h3><span id=\"T0_24_Saat\">T0 + 24 Saat<\/span><\/h3>\n<ul>\n<li>Art\u0131k trafi\u011fin b\u00fcy\u00fck \u00e7o\u011funlu\u011fu yeni MX\u2019e y\u00f6nlenmi\u015f olacakt\u0131r.<\/li>\n<li>Eski e\u2011posta sunucusunun h\u00e2l\u00e2 mail al\u0131p almad\u0131\u011f\u0131n\u0131 kontrol edin. Al\u0131yorsa, TTL yay\u0131l\u0131m\u0131 tamamen bitene kadar bir s\u00fcre daha a\u00e7\u0131k b\u0131rak\u0131n.<\/li>\n<li>Her \u015fey stabil ise TTL de\u011ferlerini 3600\u201314400 saniye band\u0131na geri y\u00fckseltin.<\/li>\n<\/ul>\n<h2><span id=\"DCHost_ile_Alan_Adi_ve_EPosta_Tasimada_Is_Akisimiz\">DCHost ile Alan Ad\u0131 ve E\u2011Posta Ta\u015f\u0131mada \u0130\u015f Ak\u0131\u015f\u0131m\u0131z<\/span><\/h2>\n<p>DCHost\u2019ta, hem web sitesi hem de e\u2011posta altyap\u0131s\u0131n\u0131 bize ta\u015f\u0131yan kullan\u0131c\u0131lar i\u00e7in bu s\u00fcreci olabildi\u011fince <strong>operasyonel bir check\u2011list<\/strong> h\u00e2line getirmi\u015f durumday\u0131z. Tipik bir ta\u015f\u0131ma operasyonunda:<\/p>\n<ul>\n<li>\u00d6nce mevcut DNS ve e\u2011posta mimarinizi analiz ediyor, MX, SPF, DKIM, DMARC ve rDNS durumunu netle\u015ftiriyoruz.<\/li>\n<li>Ard\u0131ndan, sizin i\u00e7in \u00f6zel bir <strong>TTL d\u00fc\u015f\u00fcrme ve ge\u00e7i\u015f takvimi<\/strong> planl\u0131yoruz.<\/li>\n<li>Yeni sunucular\u0131n\u0131z (<a href=\"https:\/\/www.dchost.com\/tr\/web-hosting\">payla\u015f\u0131ml\u0131 hosting<\/a>, <a href=\"https:\/\/www.dchost.com\/tr\/vps\">VPS<\/a> veya dedicated) \u00fczerinde e\u2011posta hesaplar\u0131n\u0131, DKIM anahtarlar\u0131n\u0131 ve gerekli DNS kay\u0131tlar\u0131n\u0131 \u00f6nceden haz\u0131rl\u0131yoruz.<\/li>\n<li>NS ve MX ge\u00e7i\u015fini, sizin belirledi\u011finiz d\u00fc\u015f\u00fck riskli zaman diliminde birlikte ger\u00e7ekle\u015ftirip, sonras\u0131nda log ve teslim edilebilirlik kontrollerini yap\u0131yoruz.<\/li>\n<\/ul>\n<p>Kontrol paneli de\u011fi\u015fimlerinin de i\u015fin bir par\u00e7as\u0131 oldu\u011fu durumlarda, \u00f6rne\u011fin <a href=\"https:\/\/www.dchost.com\/blog\/pleskten-cpanele-ve-tersi-kesintisiz-gecis-dns-e%E2%80%91posta-ve-ssl-icin-adim-adim-tasima-plani\/\">Plesk\u2019ten cPanel\u2019e veya tersi ge\u00e7i\u015flerde DNS ve e\u2011postas\u0131z kesintisiz ge\u00e7i\u015f rehberimizde<\/a> anlatt\u0131\u011f\u0131m\u0131z yakla\u015f\u0131mlar\u0131 uyguluyoruz. E\u011fer sadece cPanel\u2019den cPanel\u2019e ta\u015f\u0131ma yap\u0131yorsan\u0131z, <a href=\"https:\/\/www.dchost.com\/blog\/cpanelden-cpanele-canli-tasima-nasil-olur-incremental-rsync-ttl-oyun-plani-ve-whm-live-transfer-ile-sifir-kesinti\/\">canl\u0131 cPanel ta\u015f\u0131ma ve TTL oyun plan\u0131<\/a> yaz\u0131m\u0131zdaki stratejiler de birebir e\u2011posta taraf\u0131na uygulanabilir.<\/p>\n<h2><span id=\"Sonuc_EPosta_Kesintisiz_Alan_Adi_Tasima_Icin_Yol_Haritan\">Sonu\u00e7: E\u2011Posta Kesintisiz Alan Ad\u0131 Ta\u015f\u0131ma \u0130\u00e7in Yol Haritan<\/span><\/h2>\n<p>Alan ad\u0131n\u0131z\u0131, DNS\u2019inizi veya e\u2011posta sunucunuzu de\u011fi\u015ftirirken \u201cbirka\u00e7 saate bir \u015fey olmaz\u201d yakla\u015f\u0131m\u0131, maalesef e\u2011posta taraf\u0131nda pek i\u015flemiyor. MX\u2019in yanl\u0131\u015f yere bakmas\u0131, SPF\u2019e yeni IP\u2019nin eklenmemesi, DKIM selector\u2019\u0131n\u0131n unutulmas\u0131 veya TTL\u2019in y\u00fcksek b\u0131rak\u0131lmas\u0131; t\u00fcm bu k\u00fc\u00e7\u00fck g\u00f6z\u00fcken hatalar bir araya gelince kritik maillerin kaybolmas\u0131na yol a\u00e7abiliyor.<\/p>\n<p>Bu yaz\u0131da \u00f6zetle \u015funu g\u00f6rd\u00fck: <strong>do\u011fru planlanm\u0131\u015f bir TTL stratejisi<\/strong>, <strong>MX kay\u0131tlar\u0131n\u0131n yeni DNS\u2019te \u00f6nceden haz\u0131rlanmas\u0131<\/strong>, <strong>SPF\u2019in eski ve yeni IP\u2019leri birlikte kapsamas\u0131<\/strong> ve <strong>DKIM selector\u2019lar\u0131n\u0131n paralel \u00e7al\u0131\u015ft\u0131r\u0131lmas\u0131<\/strong> ile e\u2011posta kesintisini neredeyse s\u0131f\u0131ra indirebilirsiniz. \u00dczerine DMARC ve rDNS\u2019i de do\u011fru kurgulad\u0131\u011f\u0131n\u0131zda, sadece kesintisiz de\u011fil, ayn\u0131 zamanda <strong>daha g\u00fc\u00e7l\u00fc bir teslim edilebilirlik<\/strong> elde etmi\u015f olursunuz.<\/p>\n<p>Alan ad\u0131n\u0131z\u0131 veya e\u2011posta altyap\u0131n\u0131z\u0131 DCHost\u2019a ta\u015f\u0131may\u0131 d\u00fc\u015f\u00fcn\u00fcyorsan\u0131z, bu rehberi bir <strong>kontrol listesi<\/strong> gibi kullanabilir; teknik ekibimizden ta\u015f\u0131ma \u00f6ncesi mimari de\u011ferlendirme deste\u011fi isteyebilirsiniz. \u0130ster payla\u015f\u0131ml\u0131 hosting, ister VPS, dedicated veya colocation kullan\u0131n; DNS, MX, SPF, DKIM ve TTL planlamas\u0131n\u0131 birlikte kurgulad\u0131\u011f\u0131m\u0131zda, siz i\u015finize odaklan\u0131rken e\u2011posta trafi\u011finiz arka planda sessizce, ama kesintisiz bi\u00e7imde akmaya devam eder.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>\u0130&ccedil;indekiler1 Alan Ad\u0131 Ta\u015f\u0131ma S\u00fcrecinde E\u2011Posta Neden En K\u0131r\u0131lgan Nokta?2 Temel Kavramlar: MX, SPF, DKIM ve TTL Ne \u0130\u015fe Yarar?3 Hangi Ta\u015f\u0131ma Senaryosunda Ne De\u011fi\u015fiyor?3.1 Senaryo 1: Sadece Alan Ad\u0131 Registrar\u2019\u0131 De\u011fi\u015fiyor (DNS Ayn\u0131)3.2 Senaryo 2: DNS Sa\u011flay\u0131c\u0131s\u0131 De\u011fi\u015fiyor (Mail Sunucusu Ayn\u0131)3.3 Senaryo 3: E\u2011Posta Hizmeti de Ba\u015fka Sunucuya Ta\u015f\u0131n\u0131yor4 TTL Stratejisi: MX ve TXT [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":2201,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-2200","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\/2200","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=2200"}],"version-history":[{"count":0,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/2200\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/2201"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=2200"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=2200"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=2200"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}