{"id":4025,"date":"2026-01-02T21:26:16","date_gmt":"2026-01-02T18:26:16","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/dns-ttl-degerlerini-dogru-ayarlamak-a-mx-cname-ve-txt-kayitlari-icin-stratejik-rehber\/"},"modified":"2026-01-02T21:26:16","modified_gmt":"2026-01-02T18:26:16","slug":"dns-ttl-degerlerini-dogru-ayarlamak-a-mx-cname-ve-txt-kayitlari-icin-stratejik-rehber","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/dns-ttl-degerlerini-dogru-ayarlamak-a-mx-cname-ve-txt-kayitlari-icin-stratejik-rehber\/","title":{"rendered":"DNS TTL De\u011ferlerini Do\u011fru Ayarlamak: A, MX, CNAME ve TXT Kay\u0131tlar\u0131 \u0130\u00e7in Stratejik Rehber"},"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=\"#DNS_TTL_Nedir_ve_Neyi_Kontrol_Eder\"><span class=\"toc_number toc_depth_1\">1<\/span> DNS TTL Nedir ve Neyi Kontrol Eder?<\/a><\/li><li><a href=\"#TTL_DNS_Yayilimi_ve_Kesinti_Riskini_Nasil_Etkiler\"><span class=\"toc_number toc_depth_1\">2<\/span> TTL, DNS Yay\u0131l\u0131m\u0131 ve Kesinti Riskini Nas\u0131l Etkiler?<\/a><\/li><li><a href=\"#A_Kayitlari_Icin_TTL_Stratejisi\"><span class=\"toc_number toc_depth_1\">3<\/span> A Kay\u0131tlar\u0131 \u0130\u00e7in TTL Stratejisi<\/a><ul><li><a href=\"#Kurumsal_web_siteleri_ve_bloglar_icin_onerilen_TTL\"><span class=\"toc_number toc_depth_2\">3.1<\/span> Kurumsal web siteleri ve bloglar i\u00e7in \u00f6nerilen TTL<\/a><\/li><li><a href=\"#Yuksek_trafikli_eticaret_ve_SaaS_uygulamalari_icin_TTL\"><span class=\"toc_number toc_depth_2\">3.2<\/span> Y\u00fcksek trafikli e\u2011ticaret ve SaaS uygulamalar\u0131 i\u00e7in TTL<\/a><\/li><li><a href=\"#IP_degisikligi_tasima_ve_failover_senaryolarinda_TTL_oyunu\"><span class=\"toc_number toc_depth_2\">3.3<\/span> IP de\u011fi\u015fikli\u011fi, ta\u015f\u0131ma ve failover senaryolar\u0131nda TTL oyunu<\/a><\/li><\/ul><\/li><li><a href=\"#MX_Kayitlari_Icin_TTL_Stratejisi\"><span class=\"toc_number toc_depth_1\">4<\/span> MX Kay\u0131tlar\u0131 \u0130\u00e7in TTL Stratejisi<\/a><ul><li><a href=\"#Standart_isletme_eposta_altyapisi_icin_TTL\"><span class=\"toc_number toc_depth_2\">4.1<\/span> Standart i\u015fletme e\u2011posta altyap\u0131s\u0131 i\u00e7in TTL<\/a><\/li><li><a href=\"#Yeni_eposta_saglayicisina_gecis_plani_ve_MX_TTL\"><span class=\"toc_number toc_depth_2\">4.2<\/span> Yeni e\u2011posta sa\u011flay\u0131c\u0131s\u0131na ge\u00e7i\u015f plan\u0131 ve MX TTL<\/a><\/li><li><a href=\"#Backup_MX_ve_coklu_MX_kayitlarinda_TTL\"><span class=\"toc_number toc_depth_2\">4.3<\/span> Backup MX ve \u00e7oklu MX kay\u0131tlar\u0131nda TTL<\/a><\/li><\/ul><\/li><li><a href=\"#CNAME_Kayitlari_Icin_TTL_Stratejisi\"><span class=\"toc_number toc_depth_1\">5<\/span> CNAME Kay\u0131tlar\u0131 \u0130\u00e7in TTL Stratejisi<\/a><ul><li><a href=\"#CDN_statik_icerik_ve_alt_alan_adlari\"><span class=\"toc_number toc_depth_2\">5.1<\/span> CDN, statik i\u00e7erik ve alt alan adlar\u0131<\/a><\/li><li><a href=\"#Ucuncu_taraf_servis_entegrasyonlarinda_CNAME_TTL\"><span class=\"toc_number toc_depth_2\">5.2<\/span> \u00dc\u00e7\u00fcnc\u00fc taraf servis entegrasyonlar\u0131nda CNAME TTL<\/a><\/li><li><a href=\"#Kok_alanda_CNAME_kisiti_ve_alternatifler\"><span class=\"toc_number toc_depth_2\">5.3<\/span> K\u00f6k alanda CNAME k\u0131s\u0131t\u0131 ve alternatifler<\/a><\/li><\/ul><\/li><li><a href=\"#TXT_SPF_DKIM_DMARC_vb_Kayitlari_Icin_TTL_Stratejisi\"><span class=\"toc_number toc_depth_1\">6<\/span> TXT (SPF, DKIM, DMARC vb.) Kay\u0131tlar\u0131 \u0130\u00e7in TTL Stratejisi<\/a><ul><li><a href=\"#SPF_kayitlari_icin_TTL\"><span class=\"toc_number toc_depth_2\">6.1<\/span> SPF kay\u0131tlar\u0131 i\u00e7in TTL<\/a><\/li><li><a href=\"#DKIM_ve_DMARC_icin_TTL\"><span class=\"toc_number toc_depth_2\">6.2<\/span> DKIM ve DMARC i\u00e7in TTL<\/a><\/li><li><a href=\"#Dogrulama_ve_guvenlik_odakli_diger_TXT_kayitlari\"><span class=\"toc_number toc_depth_2\">6.3<\/span> Do\u011frulama ve g\u00fcvenlik odakl\u0131 di\u011fer TXT kay\u0131tlar\u0131<\/a><\/li><\/ul><\/li><li><a href=\"#Farkli_Senaryolar_Icin_Onerilen_TTL_Degerleri\"><span class=\"toc_number toc_depth_1\">7<\/span> Farkl\u0131 Senaryolar \u0130\u00e7in \u00d6nerilen TTL De\u011ferleri<\/a><\/li><li><a href=\"#DCHost_Panelinde_TTL_Yonetimi_Icin_Pratik_Ipuclari\"><span class=\"toc_number toc_depth_1\">8<\/span> DCHost Panelinde TTL Y\u00f6netimi \u0130\u00e7in Pratik \u0130pu\u00e7lar\u0131<\/a><\/li><li><a href=\"#Sonuc_ve_Yol_Haritasi\"><span class=\"toc_number toc_depth_1\">9<\/span> Sonu\u00e7 ve Yol Haritas\u0131<\/a><\/li><\/ul><\/div>\n<h2><span id=\"DNS_TTL_Nedir_ve_Neyi_Kontrol_Eder\">DNS TTL Nedir ve Neyi Kontrol Eder?<\/span><\/h2>\n<p>DNS yap\u0131land\u0131rmas\u0131 yaparken \u00e7o\u011fu zaman A, MX, CNAME veya TXT kay\u0131tlar\u0131n\u0131 ekler, de\u011feri yazar, bir de TTL alan\u0131na h\u0131zl\u0131ca 300 ya da 14400 yaz\u0131p ge\u00e7eriz. Oysa <strong>TTL (Time To Live)<\/strong>, DNS taraf\u0131nda yapt\u0131\u011f\u0131n\u0131z her de\u011fi\u015fikli\u011fin ne kadar s\u00fcrede etkili olaca\u011f\u0131n\u0131, hata yapt\u0131\u011f\u0131n\u0131zda ne kadar s\u00fcre can\u0131n\u0131z\u0131n yanaca\u011f\u0131n\u0131 ve kesinti planlarken elinizde ne kadar manevra alan\u0131 oldu\u011funu belirler. DCHost olarak sahada g\u00f6rd\u00fc\u011f\u00fcm\u00fcz sorunlar\u0131n \u00f6nemli bir k\u0131sm\u0131 yanl\u0131\u015f TTL stratejisinden kaynaklan\u0131yor: Ta\u015f\u0131ma \u00f6ncesi d\u00fc\u015f\u00fcr\u00fclmeyen TTL y\u00fcz\u00fcnden uzayan DNS yay\u0131l\u0131mlar\u0131, e-posta ge\u00e7i\u015flerinde g\u00fcnlerce s\u00fcren kuyruk sorunlar\u0131, gere\u011finden d\u00fc\u015f\u00fck TTL sebebiyle gereksiz DNS trafi\u011fi ve yava\u015flayan resolver yan\u0131tlar\u0131 gibi.<\/p>\n<p>Bu yaz\u0131da TTL kavram\u0131n\u0131 sadece teorik olarak anlatmakla kalmayaca\u011f\u0131z; <strong>A, MX, CNAME ve TXT kay\u0131tlar\u0131 i\u00e7in pratik, senaryo bazl\u0131 TTL stratejileri<\/strong> payla\u015faca\u011f\u0131z. Canl\u0131 site ta\u015f\u0131ma, e-posta altyap\u0131s\u0131 de\u011fi\u015fikli\u011fi, CDN kullan\u0131m\u0131, SPF\/DKIM\/DMARC g\u00fcncellemeleri gibi ger\u00e7ek hayatta s\u0131k ya\u015fanan durumlarda hangi kay\u0131tta, ne kadar s\u00fcreyle, hangi TTL de\u011ferini tercih etmeniz gerekti\u011fini ad\u0131m ad\u0131m netle\u015ftirece\u011fiz. E\u011fer DNS taraf\u0131nda daha temel kavramlar\u0131 da tazelemek isterseniz, \u00f6nce <a href=\"https:\/\/www.dchost.com\/blog\/dns-kayitlari-nedir-a-aaaa-cname-mx-txt-ve-srv-rehberi\/\">DNS kay\u0131tlar\u0131 nedir, A, AAAA, CNAME, MX ve TXT nas\u0131l \u00e7al\u0131\u015f\u0131r<\/a> yaz\u0131m\u0131za g\u00f6z atman\u0131z faydal\u0131 olabilir.<\/p>\n<h2><span id=\"TTL_DNS_Yayilimi_ve_Kesinti_Riskini_Nasil_Etkiler\">TTL, DNS Yay\u0131l\u0131m\u0131 ve Kesinti Riskini Nas\u0131l Etkiler?<\/span><\/h2>\n<p>TTL, bir DNS kayd\u0131n\u0131n resolver ve istemciler taraf\u0131ndan <strong>\u00f6nbellekte ka\u00e7 saniye tutulaca\u011f\u0131n\u0131<\/strong> belirler. \u00d6rne\u011fin TTL de\u011feri 3600 ise, bu kay\u0131t genellikle en fazla 1 saat boyunca cache&#8217;te kal\u0131r. Bir ziyaret\u00e7i ilk iste\u011finde ger\u00e7ek DNS sunucunuza sorar, sonucu al\u0131r, sonraki isteklerde TTL dolana kadar cache&#8217;teki de\u011feri kullan\u0131r.<\/p>\n<p>Bu mekanizma \u00fc\u00e7 kritik sonucu beraberinde getirir:<\/p>\n<ul>\n<li><strong>Y\u00fck azaltma:<\/strong> Y\u00fcksek TTL de\u011ferleri, DNS sunucunuza gelen sorgu say\u0131s\u0131n\u0131 ciddi \u015fekilde azalt\u0131r.<\/li>\n<li><strong>De\u011fi\u015fiklik h\u0131z\u0131:<\/strong> IP, e-posta sa\u011flay\u0131c\u0131s\u0131 veya do\u011frulama kay\u0131tlar\u0131n\u0131 de\u011fi\u015ftirdi\u011finizde, TTL s\u00fcresi boyunca eski de\u011ferler d\u00fcnyada dola\u015fmaya devam eder.<\/li>\n<li><strong>Hata penceresi:<\/strong> Yanl\u0131\u015f kay\u0131t girdi\u011finizde, y\u00fcksek TTL ile bu hata uzun s\u00fcre g\u00f6r\u00fcn\u00fcr olmaya devam eder.<\/li>\n<\/ul>\n<p>TTL, halk aras\u0131nda s\u0131k kullan\u0131lan &#8220;DNS yay\u0131l\u0131m s\u00fcresi&#8221; alg\u0131s\u0131n\u0131n da merkezindedir. \u00c7o\u011fu ki\u015fi, <a href=\"https:\/\/www.dchost.com\/blog\/dns-yayilim-suresi-nedir-neden-24-saat-surer-ve-nasil-hizlandirilir\/\">DNS yay\u0131l\u0131m s\u00fcresi neden 24 saat s\u00fcrer<\/a> diye sordu\u011funda asl\u0131nda <strong>\u00f6nceden ayarlanm\u0131\u015f y\u00fcksek TTL de\u011ferlerinin<\/strong> sonu\u00e7lar\u0131n\u0131 ya\u015f\u0131yordur. \u0130yi haber \u015fu ki, do\u011fru planlama ile bu yay\u0131l\u0131m s\u00fcrelerini y\u00f6netmek m\u00fcmk\u00fcn. Hatta DCHost taraf\u0131nda anlatt\u0131\u011f\u0131m\u0131z gibi, <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<\/a> uygulayarak kesintisiz ge\u00e7i\u015fler bile yapabilirsiniz.<\/p>\n<h2><span id=\"A_Kayitlari_Icin_TTL_Stratejisi\">A Kay\u0131tlar\u0131 \u0130\u00e7in TTL Stratejisi<\/span><\/h2>\n<p>A kayd\u0131 (ve IPv6 i\u00e7in AAAA) genellikle web sitenizi, API&#8217;lar\u0131n\u0131z\u0131 veya uygulama sunucular\u0131n\u0131z\u0131 i\u015faret eder. Yanl\u0131\u015f TTL karar\u0131, \u00f6zellikle trafik yo\u011fun sitelerde do\u011frudan eri\u015filebilirlik ve performans sorunlar\u0131 olarak geri d\u00f6ner.<\/p>\n<h3><span id=\"Kurumsal_web_siteleri_ve_bloglar_icin_onerilen_TTL\">Kurumsal web siteleri ve bloglar i\u00e7in \u00f6nerilen TTL<\/span><\/h3>\n<p>Kurumsal tan\u0131t\u0131m siteleri, bloglar veya s\u0131k s\u0131k IP de\u011fi\u015ftirmedi\u011finiz, klasik <a href=\"https:\/\/www.dchost.com\/tr\/web-hosting\">payla\u015f\u0131ml\u0131 hosting<\/a> ya da sabit IP&#8217;li <a href=\"https:\/\/www.dchost.com\/tr\/vps\">VPS<\/a> \u00fczerinde \u00e7al\u0131\u015fan siteler i\u00e7in TTL&#8217;i <strong>3600\u201314400 saniye (1\u20134 saat)<\/strong> aral\u0131\u011f\u0131nda tutmak genellikle ideal bir dengedir.<\/p>\n<ul>\n<li><strong>3600 sn (1 saat):<\/strong> K\u00fc\u00e7\u00fck IP de\u011fi\u015fikliklerinde makul h\u0131zda yay\u0131l\u0131m, ayn\u0131 zamanda makul DNS sorgu y\u00fck\u00fc.<\/li>\n<li><strong>7200\u201314400 sn (2\u20134 saat):<\/strong> \u00c7ok nadir IP de\u011fi\u015ftiren, son derece stabil altyap\u0131larda tercih edilebilir.<\/li>\n<\/ul>\n<p>Neden 24 saat de\u011fil de 1\u20134 saat? \u00c7\u00fcnk\u00fc IPv4 fiyatlar\u0131n\u0131n ve IP ta\u015f\u0131ma ihtiya\u00e7lar\u0131n\u0131n artt\u0131\u011f\u0131 bu d\u00f6nemde altyap\u0131lar daha s\u0131k de\u011fi\u015fiyor. DCHost m\u00fc\u015fterilerinde de zaman zaman sunucu y\u00fckseltme, farkl\u0131 veri merkezine ta\u015f\u0131ma gibi senaryolar g\u00f6r\u00fcyoruz. TTL&#8217;i 86400 saniye (24 saat) yaparsan\u0131z, bu t\u00fcr operasyonlarda manevra alan\u0131n\u0131z\u0131 gereksiz yere daraltm\u0131\u015f olursunuz.<\/p>\n<h3><span id=\"Yuksek_trafikli_eticaret_ve_SaaS_uygulamalari_icin_TTL\">Y\u00fcksek trafikli e\u2011ticaret ve SaaS uygulamalar\u0131 i\u00e7in TTL<\/span><\/h3>\n<p>E\u2011ticaret, marketplace veya SaaS uygulamalar\u0131nda, arka planda s\u0131k s\u0131k \u00f6l\u00e7eklendirme, node de\u011fi\u015fikli\u011fi veya load balancer IP g\u00fcncellemeleri yap\u0131labiliyor. Bu t\u00fcr senaryolarda <strong>300\u20131800 saniye (5\u201330 dakika)<\/strong> aral\u0131\u011f\u0131 genelde daha ger\u00e7ek\u00e7i:<\/p>\n<ul>\n<li><strong>300 sn (5 dakika):<\/strong> Aktif failover, blue\u2011green deployment veya s\u0131k IP de\u011fi\u015fimi varsa.<\/li>\n<li><strong>900\u20131800 sn (15\u201330 dakika):<\/strong> Ayl\u0131k veya birka\u00e7 ayda bir ya\u015fanan planl\u0131 de\u011fi\u015fiklikler i\u00e7in iyi bir kompromi.<\/li>\n<\/ul>\n<p>TTL&#8217;yi 60 sn gibi \u00e7ok d\u00fc\u015f\u00fck tutmak teoride \u00e7ekici g\u00f6r\u00fcnse de pratikte \u00e7o\u011fu i\u015fletme i\u00e7in gereksiz ve maliyetlidir. Resolver trafi\u011finiz artar, baz\u0131 resolver&#8217;lar agresif cache stratejileri y\u00fcz\u00fcnden TTL&#8217;i tam anlam\u0131yla uygulamayabilir. 300 sn \u00e7o\u011fu ger\u00e7ek d\u00fcnyadaki operasyon i\u00e7in fazlas\u0131yla yeterli, ayn\u0131 zamanda DNS sorgu y\u00fck\u00fcn\u00fc de makul seviyede tutan bir de\u011ferdir.<\/p>\n<h3><span id=\"IP_degisikligi_tasima_ve_failover_senaryolarinda_TTL_oyunu\">IP de\u011fi\u015fikli\u011fi, ta\u015f\u0131ma ve failover senaryolar\u0131nda TTL oyunu<\/span><\/h3>\n<p>A kay\u0131tlar\u0131, ta\u015f\u0131ma ve IP de\u011fi\u015fikli\u011fi senaryolar\u0131n\u0131n ba\u015frol oyuncusu. DCHost taraf\u0131nda canl\u0131 ta\u015f\u0131ma yaparken genelde \u015fu oyunu uyguluyoruz:<\/p>\n<ol>\n<li><strong>Normalde:<\/strong> \u00d6rne\u011fin TTL 3600 sn.<\/li>\n<li><strong>Ta\u015f\u0131madan 24\u201348 saat \u00f6nce:<\/strong> TTL&#8217;i 300\u2013600 sn&#8217;ye d\u00fc\u015f\u00fcr\u00fcyoruz.<\/li>\n<li><strong>Resolver cache&#8217;lerinin yeni TTL&#8217;i benimsemesi i\u00e7in:<\/strong> En az 1\u20132 eski TTL s\u00fcresi kadar bekliyoruz (yani 1\u20132 saat).<\/li>\n<li><strong>Ta\u015f\u0131ma an\u0131nda:<\/strong> A kayd\u0131n\u0131 yeni IP&#8217;ye al\u0131p birka\u00e7 saat trafi\u011fi g\u00f6zl\u00fcyoruz.<\/li>\n<li><strong>Her \u015fey stabil:<\/strong> TTL&#8217;i tekrar 1800\u20133600 sn seviyelerine y\u00fckseltiyoruz.<\/li>\n<\/ol>\n<p>B\u00f6ylece hem <strong>DNS yay\u0131l\u0131m s\u00fcresini fiilen dakikalar seviyesine indiriyor<\/strong>, hem de uzun vadede gereksiz derecede d\u00fc\u015f\u00fck TTL ile DNS altyap\u0131s\u0131n\u0131 yormam\u0131\u015f oluyoruz. Kendi operasyonlar\u0131n\u0131zda da ayn\u0131 mant\u0131\u011f\u0131 uygulayabilirsiniz.<\/p>\n<h2><span id=\"MX_Kayitlari_Icin_TTL_Stratejisi\">MX Kay\u0131tlar\u0131 \u0130\u00e7in TTL Stratejisi<\/span><\/h2>\n<p>MX kay\u0131tlar\u0131, alan ad\u0131n\u0131za gelen e\u2011postalar\u0131n hangi sunuculara teslim edilece\u011fini belirler. E\u2011posta trafi\u011fi do\u011fas\u0131 gere\u011fi daha toleransl\u0131d\u0131r: SMTP sunucular\u0131 ge\u00e7ici hatalarda yeniden deneme yapar, s\u0131raya al\u0131r. Bu y\u00fczden MX i\u00e7in TTL tercihi, A kay\u0131tlar\u0131na g\u00f6re biraz daha farkl\u0131 d\u00fc\u015f\u00fcn\u00fclmelidir.<\/p>\n<h3><span id=\"Standart_isletme_eposta_altyapisi_icin_TTL\">Standart i\u015fletme e\u2011posta altyap\u0131s\u0131 i\u00e7in TTL<\/span><\/h3>\n<p>G\u00fcnl\u00fck e\u2011posta trafi\u011finizin akt\u0131\u011f\u0131, s\u0131k s\u0131k e\u2011posta sa\u011flay\u0131c\u0131s\u0131 de\u011fi\u015ftirmedi\u011finiz bir yap\u0131da MX kay\u0131tlar\u0131 i\u00e7in <strong>3600\u201386400 saniye (1\u201324 saat)<\/strong> aral\u0131\u011f\u0131 uygundur:<\/p>\n<ul>\n<li><strong>3600\u20137200 sn:<\/strong> Altyap\u0131 \u00fczerinde ara s\u0131ra de\u011fi\u015fiklik yapan, IP veya hostname g\u00fcncellemesi ihtimali olan firmalar i\u00e7in.<\/li>\n<li><strong>14400\u201386400 sn:<\/strong> Uzun s\u00fcre stabil kalan, y\u0131llarca ayn\u0131 e\u2011posta altyap\u0131s\u0131n\u0131 kullanan kurumlar i\u00e7in.<\/li>\n<\/ul>\n<p>Burada kritik nokta \u015fu: MX kay\u0131tlar\u0131 genellikle <strong>hostname<\/strong> (\u00f6rne\u011fin mail.ornek.com) g\u00f6sterir, bu hostname&#8217;in arkas\u0131ndaki A kayd\u0131 ise daha k\u0131sa TTL&#8217;e sahip olabilir. B\u00f6ylece MX kay\u0131tlar\u0131n\u0131z nispeten sabit kal\u0131rken, as\u0131l IP de\u011fi\u015fikliklerini A kayd\u0131 \u00fczerinden daha h\u0131zl\u0131 y\u00f6netebilirsiniz.<\/p>\n<h3><span id=\"Yeni_eposta_saglayicisina_gecis_plani_ve_MX_TTL\">Yeni e\u2011posta sa\u011flay\u0131c\u0131s\u0131na ge\u00e7i\u015f plan\u0131 ve MX TTL<\/span><\/h3>\n<p>E\u2011posta sa\u011flay\u0131c\u0131s\u0131 veya kendi mail sunucunuzu de\u011fi\u015ftirirken en s\u0131k yap\u0131lan hata, ge\u00e7i\u015ften hemen \u00f6nce MX kayd\u0131n\u0131 de\u011fi\u015ftirmek ama TTL&#8217;i unutmakt\u0131r. Sa\u011fl\u0131kl\u0131 bir plan \u015f\u00f6yle olmal\u0131:<\/p>\n<ol>\n<li>Ge\u00e7i\u015ften <strong>48\u201372 saat \u00f6nce<\/strong> mevcut MX kay\u0131tlar\u0131n\u0131n TTL&#8217;ini 600\u20131800 sn aral\u0131\u011f\u0131na d\u00fc\u015f\u00fcr\u00fcn.<\/li>\n<li>Bu yeni TTL&#8217;in d\u00fcnya genelinde benimsenmesi i\u00e7in en az 1 eski TTL s\u00fcresi kadar bekleyin.<\/li>\n<li>Yeni e\u2011posta altyap\u0131n\u0131z\u0131 test edin; gerekti\u011finde <a href=\"https:\/\/www.dchost.com\/blog\/e-posta-altyapisinda-yedeklilik-birden-fazla-mx-kaydi-backup-mx-ve-split-delivery-kurulumu\/\">birden fazla MX kayd\u0131 ile split delivery veya backup MX<\/a> senaryosu kurgulay\u0131n.<\/li>\n<li>MX kay\u0131tlar\u0131n\u0131 yeni sa\u011flay\u0131c\u0131ya y\u00f6nlendirin ve SMTP loglar\u0131n\u0131 dikkatle izleyin.<\/li>\n<li>Her \u015fey yolunda ise TTL&#8217;i tekrar 3600\u201314400 sn seviyesine y\u00fckseltin.<\/li>\n<\/ol>\n<p>B\u00f6ylece MX de\u011fi\u015fikli\u011finizin etkisi dakikalar i\u00e7inde hissedilir hale gelir; g\u00fcnlerce s\u00fcren kar\u0131\u015f\u0131k teslim senaryolar\u0131ndan ka\u00e7\u0131nm\u0131\u015f olursunuz.<\/p>\n<h3><span id=\"Backup_MX_ve_coklu_MX_kayitlarinda_TTL\">Backup MX ve \u00e7oklu MX kay\u0131tlar\u0131nda TTL<\/span><\/h3>\n<p>E\u011fer yap\u0131n\u0131zda yedeklilik i\u00e7in birden fazla MX kayd\u0131 kullan\u0131yorsan\u0131z (\u00f6rne\u011fin \u00f6ncelik 10 ana sunucu, \u00f6ncelik 20 backup sunucu), TTL de\u011ferlerini de <strong>tutarl\u0131<\/strong> tutmak \u00f6nemlidir. Genellikle:<\/p>\n<ul>\n<li>T\u00fcm MX kay\u0131tlar\u0131n\u0131n <strong>ayn\u0131 TTL de\u011ferine<\/strong> sahip olmas\u0131 \u00f6nerilir.<\/li>\n<li>Backup MX&#8217;in i\u015faret etti\u011fi A kay\u0131tlar\u0131n\u0131n TTL&#8217;i, ana MX IP&#8217;lerinden bir t\u0131k daha d\u00fc\u015f\u00fck tutulabilir (\u00f6rne\u011fin ana 3600, backup 1800) ki de\u011fi\u015fiklikler daha h\u0131zl\u0131 yans\u0131s\u0131n.<\/li>\n<\/ul>\n<p>Backup MX, felaket senaryolar\u0131nda devreye girer; bu y\u00fczden yanl\u0131\u015f yap\u0131land\u0131r\u0131lm\u0131\u015f bir backup MX, fark edilene kadar sessizce e\u2011postalar\u0131 gereksiz yere geciktirebilir. TTL stratejinizin bu mimariyi destekledi\u011finden emin olun.<\/p>\n<h2><span id=\"CNAME_Kayitlari_Icin_TTL_Stratejisi\">CNAME Kay\u0131tlar\u0131 \u0130\u00e7in TTL Stratejisi<\/span><\/h2>\n<p>CNAME kay\u0131tlar\u0131 genellikle CDN, \u00fc\u00e7\u00fcnc\u00fc taraf servisler, subdomain y\u00f6nlendirmeleri ve \u00e7oklu ortam (blog, ma\u011faza, panel) yap\u0131lar\u0131nda kullan\u0131l\u0131r. Burada hem sizin hem de i\u015faret etti\u011finiz taraf\u0131n de\u011fi\u015fim s\u0131kl\u0131\u011f\u0131 belirleyicidir.<\/p>\n<h3><span id=\"CDN_statik_icerik_ve_alt_alan_adlari\">CDN, statik i\u00e7erik ve alt alan adlar\u0131<\/span><\/h3>\n<p>CDN&#8217;ler ve statik i\u00e7erik servisleri bazen arka plandaki IP adreslerini s\u0131k de\u011fi\u015ftirebilir. Siz alan ad\u0131n\u0131z\u0131 onlar\u0131n size verdi\u011fi hostname&#8217;e CNAME ile y\u00f6nlendirirsiniz. B\u00f6yle bir durumda:<\/p>\n<ul>\n<li>CNAME\u2019in TTL\u2019ini genellikle <strong>300\u20131800 sn<\/strong> aral\u0131\u011f\u0131nda tutmak mant\u0131kl\u0131d\u0131r.<\/li>\n<li>CDN sa\u011flay\u0131c\u0131n\u0131z \u00e7ok s\u0131k dinamik routing yap\u0131yorsa, 300\u2013600 sn daha g\u00fcvenli olabilir.<\/li>\n<\/ul>\n<p>Bu sayede CDN taraf\u0131ndaki de\u011fi\u015fiklikler ziyaret\u00e7ilerinize daha h\u0131zl\u0131 yans\u0131r. Ancak a\u015f\u0131r\u0131 d\u00fc\u015f\u00fck TTL de\u011ferleri CDN&#8217;in size \u00f6nerdi\u011fi s\u0131n\u0131rlar ile \u00e7eli\u015fmemeli; baz\u0131 sa\u011flay\u0131c\u0131lar minimum TTL tavsiyesinde bulunur. DCHost m\u00fc\u015fterilerinde g\u00f6rd\u00fc\u011f\u00fcm\u00fcz iyi pratik, kritik alt alanlar (www, app) i\u00e7in 300\u2013600 sn, daha az kritik statik alanlar i\u00e7in 900\u20131800 sn civar\u0131nda kalmak.<\/p>\n<h3><span id=\"Ucuncu_taraf_servis_entegrasyonlarinda_CNAME_TTL\">\u00dc\u00e7\u00fcnc\u00fc taraf servis entegrasyonlar\u0131nda CNAME TTL<\/span><\/h3>\n<p>CRM, ticket sistemi, analitik ya da benzeri SaaS \u00fcr\u00fcnlerine subdomain y\u00f6nlendirdi\u011finizde (\u00f6rne\u011fin support.ornek.com) altyap\u0131 genellikle \u00e7ok s\u0131k IP de\u011fi\u015ftirmez; de\u011fi\u015fiklik oldu\u011funda da sa\u011flay\u0131c\u0131 taraf\u0131nda \u00e7o\u011funlukla kendi DNS&#8217;inde y\u00f6netilir.<\/p>\n<ul>\n<li>Bu t\u00fcr CNAME kay\u0131tlar\u0131 i\u00e7in <strong>1800\u20137200 sn<\/strong> aral\u0131\u011f\u0131 pratik ve dengeli bir se\u00e7imdir.<\/li>\n<li>Entegrasyonun kritikli\u011fi y\u00fcksek, ancak de\u011fi\u015fim s\u0131kl\u0131\u011f\u0131 d\u00fc\u015f\u00fckse 3600\u20137200 sn iyi \u00e7al\u0131\u015f\u0131r.<\/li>\n<\/ul>\n<p>B\u00f6ylece, sa\u011flay\u0131c\u0131 taraf\u0131ndaki DNS de\u011fi\u015fiklikleri makul s\u00fcrede yans\u0131r; siz de kendi DNS sunucular\u0131n\u0131z\u0131 gere\u011finden fazla sorguyla yormam\u0131\u015f olursunuz.<\/p>\n<h3><span id=\"Kok_alanda_CNAME_kisiti_ve_alternatifler\">K\u00f6k alanda CNAME k\u0131s\u0131t\u0131 ve alternatifler<\/span><\/h3>\n<p>Standart DNS kurallar\u0131na g\u00f6re <strong>k\u00f6kte (\u00f6rnek.com)<\/strong> CNAME kullan\u0131lamaz; burada genellikle A, AAAA ve\/veya ALIAS\/ANAME gibi sa\u011flay\u0131c\u0131ya \u00f6zg\u00fc sanal kay\u0131t t\u00fcrleri kullan\u0131l\u0131r. TTL stratejisi a\u00e7\u0131s\u0131ndan bu \u015fu anlama gelir:<\/p>\n<ul>\n<li>K\u00f6k alan\u0131n A kayd\u0131n\u0131n TTL&#8217;i genellikle 300\u20133600 sn aral\u0131\u011f\u0131nda tutulmal\u0131; a\u015f\u0131r\u0131 y\u00fcksek TTL, IP de\u011fi\u015ftirdi\u011finizde SEO ve eri\u015filebilirlik a\u00e7\u0131s\u0131ndan risklidir.<\/li>\n<li>www gibi CNAME ile i\u015faret edilen alt alan adlar\u0131nda ise 300\u20131800 sn, \u00f6zellikle ta\u015f\u0131ma ve CDN senaryolar\u0131nda ideal dengeyi sa\u011flar.<\/li>\n<\/ul>\n<p>K\u00f6k alan i\u00e7in TTl belirlerken, sadece web trafi\u011fini de\u011fil; ayn\u0131 zamanda API, mobil uygulama ve entegrasyonlar\u0131n da bu domaine ba\u011fl\u0131 olup olmad\u0131\u011f\u0131n\u0131 g\u00f6z \u00f6n\u00fcnde bulundurun.<\/p>\n<h2><span id=\"TXT_SPF_DKIM_DMARC_vb_Kayitlari_Icin_TTL_Stratejisi\">TXT (SPF, DKIM, DMARC vb.) Kay\u0131tlar\u0131 \u0130\u00e7in TTL Stratejisi<\/span><\/h2>\n<p>TXT kay\u0131tlar\u0131 genellikle <strong>e\u2011posta do\u011frulama (SPF, DKIM, DMARC)<\/strong>, <strong>g\u00fcvenlik politikalar\u0131 (MTA\u2011STS, TLS\u2011RPT, BIMI)<\/strong> ve <strong>servis do\u011frulama (Google, Facebook, arama motorlar\u0131 vb.)<\/strong> gibi ama\u00e7larla kullan\u0131l\u0131r. Bu kay\u0131tlar do\u011frudan son kullan\u0131c\u0131 trafi\u011fini de\u011fil, \u00e7o\u011funlukla e\u2011posta teslim edilebilirli\u011fini ve entegrasyon g\u00fcvenilirli\u011fini etkiler.<\/p>\n<h3><span id=\"SPF_kayitlari_icin_TTL\">SPF kay\u0131tlar\u0131 i\u00e7in TTL<\/span><\/h3>\n<p>SPF kayd\u0131, alan ad\u0131n\u0131z\u0131n hangi IP veya sunuculardan e\u2011posta g\u00f6ndermeye yetkili oldu\u011funu tan\u0131mlar. Yanl\u0131\u015f SPF yap\u0131land\u0131rmas\u0131, e\u2011postalar\u0131n\u0131z\u0131n spam klas\u00f6r\u00fcne d\u00fc\u015fmesine veya direkt reddedilmesine yol a\u00e7abilir. Bu nedenle SPF i\u00e7in TTL se\u00e7erken \u015fu denge \u00f6nemli:<\/p>\n<ul>\n<li>G\u00fcnl\u00fck\/haftal\u0131k de\u011fi\u015fiklik yap\u0131yorsan\u0131z: <strong>600\u20131800 sn<\/strong><\/li>\n<li>Nadiren de\u011fi\u015fiklik yap\u0131yorsan\u0131z: <strong>3600\u201314400 sn<\/strong><\/li>\n<\/ul>\n<p>\u00d6zellikle birden fazla e\u2011posta servisi kullan\u0131yorsan\u0131z ve <a href=\"https:\/\/www.dchost.com\/blog\/gelismis-spf-yonetimi-10-dns-lookup-limitine-takilmadan-coklu-e-posta-servisi-kullanmak\/\">geli\u015fmi\u015f SPF y\u00f6netimi ve 10 DNS lookup limitine tak\u0131lmama<\/a> gibi konularla u\u011fra\u015f\u0131yorsan\u0131z, test d\u00f6nemlerinde TTL&#8217;i 600\u2013900 sn gibi daha d\u00fc\u015f\u00fck tutmak, hatal\u0131 yap\u0131land\u0131rmalar\u0131 h\u0131zl\u0131ca d\u00fczeltmenizi sa\u011flar.<\/p>\n<h3><span id=\"DKIM_ve_DMARC_icin_TTL\">DKIM ve DMARC i\u00e7in TTL<\/span><\/h3>\n<p>DKIM public key&#8217;leri ve DMARC politikalar\u0131 genellikle SPF kadar s\u0131k de\u011fi\u015fmez. Buna ra\u011fmen, ilk kurulum ve test s\u00fcrecinde d\u00fc\u015f\u00fck TTL kullanmak, ard\u0131ndan stabil hale gelince art\u0131rmak iyi pratiktir:<\/p>\n<ul>\n<li><strong>\u0130lk kurulum\/test:<\/strong> 900\u20131800 sn<\/li>\n<li><strong>Stabil d\u00f6nem:<\/strong> 3600\u201386400 sn (1\u201324 saat)<\/li>\n<\/ul>\n<p>DMARC politikas\u0131 (\u00f6rne\u011fin p=none \u2192 p=quarantine \u2192 p=reject ge\u00e7i\u015fleri) yaparken, de\u011fi\u015fikli\u011fin etkisini g\u00f6rmek i\u00e7in \u00f6nce 900\u20131800 sn gibi nispeten d\u00fc\u015f\u00fck bir TTL ile ba\u015flay\u0131p, raporlar\u0131 analiz ettikten sonra TTL&#8217;i art\u0131rabilirsiniz. DKIM anahtar rotasyonu planl\u0131, nadir bir i\u015flem oldu\u011fundan, key&#8217;ler oturduktan sonra TTL&#8217;i 14400\u201386400 sn seviyesine \u00e7ekmek genelde sorun \u00e7\u0131karmaz. Ayr\u0131nt\u0131l\u0131 e\u2011posta do\u011frulama stratejisi i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/spf-dkim-ve-dmarc-nedir-ozel-alan-adi-ile-e-posta-dogrulamasini-cpanel-ve-vpste-sifirdan-kurmak\/\">SPF, DKIM ve DMARC nedir ve nas\u0131l kurulur<\/a> yaz\u0131m\u0131z\u0131 da inceleyebilirsiniz.<\/p>\n<h3><span id=\"Dogrulama_ve_guvenlik_odakli_diger_TXT_kayitlari\">Do\u011frulama ve g\u00fcvenlik odakl\u0131 di\u011fer TXT kay\u0131tlar\u0131<\/span><\/h3>\n<p>Google Search Console, Microsoft 365, Facebook, \u00e7e\u015fitli SaaS \u00fcr\u00fcnleri vb. i\u00e7in ekledi\u011finiz TXT do\u011frulama kay\u0131tlar\u0131 genellikle sadece ilk do\u011frulama a\u015famas\u0131nda kritik olur, sonras\u0131nda nadiren dokunulur. Bu senaryoda:<\/p>\n<ul>\n<li><strong>\u0130lk do\u011frulama s\u00fcreci:<\/strong> 300\u2013900 sn (h\u0131zl\u0131 yay\u0131l\u0131m i\u00e7in)<\/li>\n<li><strong>Do\u011frulama tamamland\u0131ktan sonra:<\/strong> 3600\u201386400 sn (hatta isterseniz daha da y\u00fcksek)<\/li>\n<\/ul>\n<p>MTA\u2011STS, TLS\u2011RPT, BIMI gibi g\u00fcvenlik ve g\u00f6r\u00fcn\u00fcrl\u00fck odakl\u0131 TXT kay\u0131tlar\u0131nda da benzer strateji uygulanabilir: \u0130lk kurulumda d\u00fc\u015f\u00fck TTL, stabil ve do\u011frulanm\u0131\u015f politikalar i\u00e7in y\u00fcksek TTL. Bu t\u00fcr kay\u0131tlar da do\u011frudan son kullan\u0131c\u0131 trafi\u011finden \u00e7ok, e\u2011posta g\u00fcvenli\u011fi ve marka g\u00f6r\u00fcn\u00fcrl\u00fc\u011f\u00fc taraf\u0131nda etki yarat\u0131r.<\/p>\n<h2><span id=\"Farkli_Senaryolar_Icin_Onerilen_TTL_Degerleri\">Farkl\u0131 Senaryolar \u0130\u00e7in \u00d6nerilen TTL De\u011ferleri<\/span><\/h2>\n<p>A\u015fa\u011f\u0131daki tablo, DCHost olarak sahada s\u0131k g\u00f6rd\u00fc\u011f\u00fcm\u00fcz senaryolar i\u00e7in pratik TTL \u00f6nerilerini \u00f6zetliyor. Elbette her projenin ihtiya\u00e7lar\u0131 farkl\u0131 olabilir; ancak bu de\u011ferler iyi bir ba\u015flang\u0131\u00e7 noktas\u0131 sa\u011flar.<\/p>\n<table border=\"1\" cellpadding=\"6\" cellspacing=\"0\">\n<tr>\n<th>Senaryo<\/th>\n<th>Kay\u0131t T\u00fcr\u00fc<\/th>\n<th>\u00d6nerilen TTL<\/th>\n<th>A\u00e7\u0131klama<\/th>\n<\/tr>\n<tr>\n<td>Stabil kurumsal site<\/td>\n<td>A<\/td>\n<td>3600\u201314400 sn<\/td>\n<td>Nadiren IP de\u011fi\u015fiyorsa, y\u00fck ve esneklik i\u00e7in dengeli aral\u0131k.<\/td>\n<\/tr>\n<tr>\n<td>Y\u00fcksek trafikli e\u2011ticaret<\/td>\n<td>A<\/td>\n<td>300\u20131800 sn<\/td>\n<td>Failover, scale\u2011up\/down ve h\u0131zl\u0131 ta\u015f\u0131ma senaryolar\u0131na uygun.<\/td>\n<\/tr>\n<tr>\n<td>Payla\u015f\u0131ml\u0131 hosting blog<\/td>\n<td>A<\/td>\n<td>3600\u20137200 sn<\/td>\n<td>Klasik senaryoda genelde yeterli ve stabil.<\/td>\n<\/tr>\n<tr>\n<td>Standart e\u2011posta altyap\u0131s\u0131<\/td>\n<td>MX<\/td>\n<td>3600\u201314400 sn<\/td>\n<td>Hostname \u00fczerinden i\u015faret edilen mail sunucular\u0131 i\u00e7in ideal.<\/td>\n<\/tr>\n<tr>\n<td>E\u2011posta sa\u011flay\u0131c\u0131s\u0131 de\u011fi\u015fikli\u011fi \u00f6ncesi<\/td>\n<td>MX<\/td>\n<td>600\u20131800 sn<\/td>\n<td>Ge\u00e7i\u015ften 48\u201372 saat \u00f6nce d\u00fc\u015f\u00fcr\u00fclmeli.<\/td>\n<\/tr>\n<tr>\n<td>CDN kullan\u0131lan www alt alan\u0131<\/td>\n<td>CNAME<\/td>\n<td>300\u2013900 sn<\/td>\n<td>CDN taraf\u0131ndaki IP\/routing de\u011fi\u015fiklikleri h\u0131zl\u0131 yans\u0131s\u0131n diye.<\/td>\n<\/tr>\n<tr>\n<td>\u00dc\u00e7\u00fcnc\u00fc taraf SaaS entegrasyonu<\/td>\n<td>CNAME<\/td>\n<td>1800\u20137200 sn<\/td>\n<td>Seyrek de\u011fi\u015fen ancak kritik subdomain y\u00f6nlendirmeleri.<\/td>\n<\/tr>\n<tr>\n<td>SPF ilk kurulum\/test d\u00f6nemi<\/td>\n<td>TXT<\/td>\n<td>600\u20131800 sn<\/td>\n<td>Hatalar\u0131 h\u0131zl\u0131 d\u00fczeltmek i\u00e7in d\u00fc\u015f\u00fck TTL.<\/td>\n<\/tr>\n<tr>\n<td>Stabil SPF\/DKIM\/DMARC<\/td>\n<td>TXT<\/td>\n<td>3600\u201386400 sn<\/td>\n<td>Nadiren de\u011fi\u015fen e\u2011posta politikalar\u0131 i\u00e7in ideal.<\/td>\n<\/tr>\n<tr>\n<td>Google \/ di\u011fer do\u011frulama TXT kay\u0131tlar\u0131<\/td>\n<td>TXT<\/td>\n<td>\u0130lk do\u011frulamada 300\u2013900, sonra 3600+ sn<\/td>\n<td>\u0130lk a\u015famada h\u0131zl\u0131 yay\u0131l\u0131m, sonra y\u00fcksek TTL ile stabilite.<\/td>\n<\/tr>\n<\/table>\n<h2><span id=\"DCHost_Panelinde_TTL_Yonetimi_Icin_Pratik_Ipuclari\">DCHost Panelinde TTL Y\u00f6netimi \u0130\u00e7in Pratik \u0130pu\u00e7lar\u0131<\/span><\/h2>\n<p>DCHost altyap\u0131s\u0131nda DNS y\u00f6netimini yaparken TTL&#8217;i her kay\u0131t ekleyi\u015finizde bilin\u00e7li se\u00e7menizi \u00f6neririz. Pratikte uygulayabilece\u011finiz birka\u00e7 ipucu:<\/p>\n<ul>\n<li><strong>Varsay\u0131lan TTL&#8217;i mant\u0131kl\u0131 bir seviyede tutun:<\/strong> \u00d6rne\u011fin 3600 sn; b\u00f6ylece yeni eklenen kay\u0131tlar i\u00e7in fena olmayan bir taban de\u011feri olur.<\/li>\n<li><strong>Ta\u015f\u0131ma ve b\u00fcy\u00fck de\u011fi\u015fikliklerden \u00f6nce TTL&#8217;i planlay\u0131n:<\/strong> Yeni sunucuya ge\u00e7ecekseniz, <a href=\"https:\/\/www.dchost.com\/blog\/zero-downtime-tasima-icin-ttl-stratejileri-dns-yayilimini-gercekten-nasil-hizlandirirsin\/\">zero\u2011downtime ta\u015f\u0131ma rehberimizde<\/a> anlatt\u0131\u011f\u0131m\u0131z gibi birka\u00e7 g\u00fcn \u00f6nce TTL d\u00fc\u015f\u00fcrme plan\u0131 yap\u0131n.<\/li>\n<li><strong>E\u2011posta kay\u0131tlar\u0131n\u0131 grup halinde d\u00fc\u015f\u00fcn\u00fcn:<\/strong> MX, SPF, DKIM ve DMARC kay\u0131tlar\u0131n\u0131z\u0131 ayn\u0131 anda de\u011ferlendirip, \u00f6zellikle test d\u00f6nemlerinde hepsine benzer TTL pencereleri tan\u0131mlay\u0131n.<\/li>\n<li><strong>Ge\u00e7ici kay\u0131tlar i\u00e7in \u00e7ok d\u00fc\u015f\u00fck TTL kullan\u0131n:<\/strong> Sadece test ama\u00e7l\u0131 a\u00e7t\u0131\u011f\u0131n\u0131z alt alanlar veya ge\u00e7ici y\u00f6nlendirmeler i\u00e7in 60\u2013300 sn TTL kullan\u0131p i\u015f bitince kayd\u0131 tamamen silin.<\/li>\n<li><strong>DNS de\u011fi\u015fikliklerini loglay\u0131n:<\/strong> Hangi g\u00fcn, hangi kayd\u0131n TTL\u2019ini de\u011fi\u015ftirdi\u011finizi bir dok\u00fcmana yazmak, sorun an\u0131nda geriye d\u00f6n\u00fcp bakarken b\u00fcy\u00fck kolayl\u0131k sa\u011flar.<\/li>\n<\/ul>\n<p>\u00d6zellikle e\u2011posta taraf\u0131nda sorun ya\u015f\u0131yorsan\u0131z, hem DNS hem SPF\/DKIM\/DMARC hem de MX mimarisini birlikte ele almak gerekir. Bu noktada <a href=\"https:\/\/www.dchost.com\/blog\/e-posta-altyapisinda-yedeklilik-birden-fazla-mx-kaydi-backup-mx-ve-split-delivery-kurulumu\/\">\u00e7oklu MX ve yedekli e\u2011posta altyap\u0131s\u0131 kurulumu<\/a> yaz\u0131m\u0131z ile <a href=\"https:\/\/www.dchost.com\/blog\/spf-dkim-ve-dmarc-nedir-ozel-alan-adi-ile-e-posta-dogrulamasini-cpanel-ve-vpste-sifirdan-kurmak\/\">SPF, DKIM, DMARC rehberimizi<\/a> birlikte okuman\u0131z\u0131 \u00f6neririz.<\/p>\n<h2><span id=\"Sonuc_ve_Yol_Haritasi\">Sonu\u00e7 ve Yol Haritas\u0131<\/span><\/h2>\n<p>TTL, DNS ekran\u0131nda g\u00f6rd\u00fc\u011f\u00fcn\u00fcz k\u00fc\u00e7\u00fck bir say\u0131 gibi dursa da, asl\u0131nda <strong>kesinti riskinizi, hata pencerelerinizi ve operasyonel esnekli\u011finizi<\/strong> do\u011frudan belirleyen kritik bir parametre. A kay\u0131tlar\u0131nda \u00e7ok y\u00fcksek TTL ile IP de\u011fi\u015fikliklerini g\u00fcnlerce s\u00fcr\u00fcncemede b\u0131rakmak da, TXT kay\u0131tlar\u0131nda gereksiz derecede d\u00fc\u015f\u00fck TTL ile DNS altyap\u0131s\u0131n\u0131 yormak da orta ve uzun vadede ba\u015f a\u011fr\u0131s\u0131na d\u00f6n\u00fc\u015febiliyor. Sa\u011flam bir strateji i\u00e7in kayd\u0131 t\u00fcr\u00fcne g\u00f6re d\u00fc\u015f\u00fcnmek, normal d\u00f6nem ve ge\u00e7i\u015f d\u00f6nemleri i\u00e7in farkl\u0131 TTL seviyeleri tan\u0131mlamak en sa\u011fl\u0131kl\u0131 yakla\u015f\u0131m.<\/p>\n<p>DCHost olarak DNS, hosting, VPS, <a href=\"https:\/\/www.dchost.com\/tr\/fiziksel-sunucu\">dedicated sunucu<\/a> ve colocation altyap\u0131lar\u0131m\u0131zda m\u00fc\u015fterilerimize tam da bu bak\u0131\u015f a\u00e7\u0131s\u0131yla yol g\u00f6steriyoruz: <strong>\u00d6nce mimariyi ve de\u011fi\u015fim s\u0131kl\u0131\u011f\u0131n\u0131 anlamak, sonra TTL ve DNS tasar\u0131m\u0131n\u0131 ona g\u00f6re \u015fekillendirmek.<\/strong> Siz de alan ad\u0131n\u0131z\u0131 yeni bir sunucuya ta\u015f\u0131may\u0131 planl\u0131yor, e\u2011posta sa\u011flay\u0131c\u0131n\u0131z\u0131 de\u011fi\u015ftirmek istiyor veya karma\u015f\u0131k bir \u00e7oklu ortam (blog, ma\u011faza, panel, API) mimarisi kuruyorsan\u0131z, DNS ve TTL taraf\u0131nda birlikte detayl\u0131 bir plan \u00e7\u0131karabiliriz. Mevcut DCHost hizmetiniz \u00fczerinden kontrol paneline girip kay\u0131tlar\u0131n\u0131z\u0131 g\u00f6zden ge\u00e7irmeye bug\u00fcn ba\u015flay\u0131n; birka\u00e7 k\u00fc\u00e7\u00fck TTL dokunu\u015funun bile ne kadar fazla rahatl\u0131k sa\u011flad\u0131\u011f\u0131n\u0131 k\u0131sa s\u00fcrede fark edeceksiniz.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>\u0130&ccedil;indekiler1 DNS TTL Nedir ve Neyi Kontrol Eder?2 TTL, DNS Yay\u0131l\u0131m\u0131 ve Kesinti Riskini Nas\u0131l Etkiler?3 A Kay\u0131tlar\u0131 \u0130\u00e7in TTL Stratejisi3.1 Kurumsal web siteleri ve bloglar i\u00e7in \u00f6nerilen TTL3.2 Y\u00fcksek trafikli e\u2011ticaret ve SaaS uygulamalar\u0131 i\u00e7in TTL3.3 IP de\u011fi\u015fikli\u011fi, ta\u015f\u0131ma ve failover senaryolar\u0131nda TTL oyunu4 MX Kay\u0131tlar\u0131 \u0130\u00e7in TTL Stratejisi4.1 Standart i\u015fletme e\u2011posta altyap\u0131s\u0131 i\u00e7in [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":4026,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-4025","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\/4025","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=4025"}],"version-history":[{"count":0,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/4025\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/4026"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=4025"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=4025"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=4025"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}