{"id":3026,"date":"2025-12-06T20:11:08","date_gmt":"2025-12-06T17:11:08","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/dns-yayilim-suresi-nedir-neden-24-saat-surer-ve-nasil-hizlandirilir\/"},"modified":"2025-12-06T20:11:08","modified_gmt":"2025-12-06T17:11:08","slug":"dns-yayilim-suresi-nedir-neden-24-saat-surer-ve-nasil-hizlandirilir","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/dns-yayilim-suresi-nedir-neden-24-saat-surer-ve-nasil-hizlandirilir\/","title":{"rendered":"DNS Yay\u0131l\u0131m S\u00fcresi Nedir, Neden 24 Saat S\u00fcrer ve Nas\u0131l H\u0131zland\u0131r\u0131l\u0131r?"},"content":{"rendered":"<div class=\"dchost-blog-content-wrapper\"><p>Alan ad\u0131n\u0131z\u0131 yeni bir sunucuya ta\u015f\u0131d\u0131\u011f\u0131n\u0131zda, A kayd\u0131n\u0131 g\u00fcncelledi\u011finizde ya da e\u2011posta altyap\u0131n\u0131z\u0131 ba\u015fka bir servise y\u00f6nlendirdi\u011finizde ilk kar\u015f\u0131n\u0131za \u00e7\u0131kan soru genelde ayn\u0131d\u0131r: \u201cDNS yay\u0131l\u0131m\u0131 ne zaman bitecek, neden h\u00e2l\u00e2 eski sunucuya gidiyor?\u201d Bu belirsizlik, \u00f6zellikle canl\u0131ya ge\u00e7i\u015f anlar\u0131nda hem teknik ekipleri hem de i\u015f taraf\u0131n\u0131 gereksiz strese sokar.<\/p>\n<p>Bu yaz\u0131da sahada en \u00e7ok kar\u015f\u0131la\u015ft\u0131\u011f\u0131m\u0131z sorular\u0131 temel alarak DNS yay\u0131l\u0131m s\u00fcresini ad\u0131m ad\u0131m netle\u015ftirece\u011fiz. \u201c24 saat s\u00fcrer\u201d kli\u015fesinin nereden geldi\u011fini, ger\u00e7ekte ne anlama geldi\u011fini, hangi de\u011fi\u015fikli\u011fin yakla\u015f\u0131k ne kadar s\u00fcrede t\u00fcm d\u00fcnyaya yay\u0131ld\u0131\u011f\u0131n\u0131 ve bu s\u00fcreyi pratikte nas\u0131l ciddi \u015fekilde k\u0131saltabilece\u011finizi konu\u015faca\u011f\u0131z. TTL stratejilerinden yerel \u00f6nbellek temizlemeye, nameserver de\u011fi\u015fikliklerinden kesintisiz ta\u015f\u0131ma senaryolar\u0131na kadar t\u00fcm kritik ba\u015fl\u0131klar\u0131 tek yerde toparlayaca\u011f\u0131z.<\/p>\n<p>DCHost altyap\u0131s\u0131nda g\u00fcnl\u00fck operasyonlar\u0131m\u0131zda onlarca DNS de\u011fi\u015fikli\u011fini planl\u0131yoruz; makaleyi de tam bu pratik tecr\u00fcbeyle yaz\u0131yoruz. Amac\u0131m\u0131z, \u201cDNS yay\u0131l\u0131m s\u00fcresi\u201d kavram\u0131n\u0131 g\u00f6z\u00fcn\u00fczde b\u00fcy\u00fcten sis perdesini kald\u0131rmak ve sonraki ta\u015f\u0131ma ya da yay\u0131n s\u00fcre\u00e7lerinizi \u00e7ok daha sakin ve kontroll\u00fc y\u00f6netmenizi sa\u011flamak.<\/p>\n<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_yayilim_suresi_nedir\"><span class=\"toc_number toc_depth_1\">1<\/span> DNS yay\u0131l\u0131m s\u00fcresi nedir?<\/a><\/li><li><a href=\"#DNS_nasil_calisir_Yayilimi_etkileyen_katmanlar\"><span class=\"toc_number toc_depth_1\">2<\/span> DNS nas\u0131l \u00e7al\u0131\u015f\u0131r? Yay\u0131l\u0131m\u0131 etkileyen katmanlar<\/a><\/li><li><a href=\"#Neden_herkes_24_saat_surer_diyor_Gercekte_ne_kadar_surer\"><span class=\"toc_number toc_depth_1\">3<\/span> Neden herkes \u201c24 saat s\u00fcrer\u201d diyor? Ger\u00e7ekte ne kadar s\u00fcrer?<\/a><\/li><li><a href=\"#Hangi_DNS_degisiklikleri_ne_kadar_surede_yayilir\"><span class=\"toc_number toc_depth_1\">4<\/span> Hangi DNS de\u011fi\u015fiklikleri ne kadar s\u00fcrede yay\u0131l\u0131r?<\/a><ul><li><a href=\"#A_AAAA_kaydi_degisikligi_IP_adresi_degisimi\"><span class=\"toc_number toc_depth_2\">4.1<\/span> A \/ AAAA kayd\u0131 de\u011fi\u015fikli\u011fi (IP adresi de\u011fi\u015fimi)<\/a><\/li><li><a href=\"#MX_kaydi_degisikligi_eposta_altyapisi\"><span class=\"toc_number toc_depth_2\">4.2<\/span> MX kayd\u0131 de\u011fi\u015fikli\u011fi (e\u2011posta altyap\u0131s\u0131)<\/a><\/li><li><a href=\"#Nameserver_NS_degisikligi\"><span class=\"toc_number toc_depth_2\">4.3<\/span> Nameserver (NS) de\u011fi\u015fikli\u011fi<\/a><\/li><li><a href=\"#TXT_CNAME_ve_diger_kayitlar\"><span class=\"toc_number toc_depth_2\">4.4<\/span> TXT, CNAME ve di\u011fer kay\u0131tlar<\/a><\/li><\/ul><\/li><li><a href=\"#DNS_yayilim_suresini_gercekten_nasil_hizlandirirsiniz\"><span class=\"toc_number toc_depth_1\">5<\/span> DNS yay\u0131l\u0131m s\u00fcresini ger\u00e7ekten nas\u0131l h\u0131zland\u0131r\u0131rs\u0131n\u0131z?<\/a><ul><li><a href=\"#1_TTL_stratejisini_dogru_kullanmak\"><span class=\"toc_number toc_depth_2\">5.1<\/span> 1. TTL stratejisini do\u011fru kullanmak<\/a><\/li><li><a href=\"#2_Yerel_DNS_onbellegini_temizlemek_siz_ve_musterileriniz_icin\"><span class=\"toc_number toc_depth_2\">5.2<\/span> 2. Yerel DNS \u00f6nbelle\u011fini temizlemek (siz ve m\u00fc\u015fterileriniz i\u00e7in)<\/a><\/li><li><a href=\"#3_Dogru_DNS_altyapisini_kullanmak\"><span class=\"toc_number toc_depth_2\">5.3<\/span> 3. Do\u011fru DNS altyap\u0131s\u0131n\u0131 kullanmak<\/a><\/li><li><a href=\"#4_Yanlis_kayit_ve_konfigurasyon_hatalarindan_kacinmak\"><span class=\"toc_number toc_depth_2\">5.4<\/span> 4. Yanl\u0131\u015f kay\u0131t ve konfig\u00fcrasyon hatalar\u0131ndan ka\u00e7\u0131nmak<\/a><\/li><\/ul><\/li><li><a href=\"#DNS_yayilimi_sirasinda_dikkat_etmeniz_gereken_operasyonel_ipuclari\"><span class=\"toc_number toc_depth_1\">6<\/span> DNS yay\u0131l\u0131m\u0131 s\u0131ras\u0131nda dikkat etmeniz gereken operasyonel ipu\u00e7lar\u0131<\/a><ul><li><a href=\"#1_Eski_ve_yeni_sunucuyu_bir_sure_paralel_calistirin\"><span class=\"toc_number toc_depth_2\">6.1<\/span> 1. Eski ve yeni sunucuyu bir s\u00fcre paralel \u00e7al\u0131\u015ft\u0131r\u0131n<\/a><\/li><li><a href=\"#2_hosts_dosyasi_ile_once_kendiniz_test_edin\"><span class=\"toc_number toc_depth_2\">6.2<\/span> 2. hosts dosyas\u0131 ile \u00f6nce kendiniz test edin<\/a><\/li><li><a href=\"#3_Eposta_gecislerinde_MX_kayitlarini_asamali_degistirin\"><span class=\"toc_number toc_depth_2\">6.3<\/span> 3. E\u2011posta ge\u00e7i\u015flerinde MX kay\u0131tlar\u0131n\u0131 a\u015famal\u0131 de\u011fi\u015ftirin<\/a><\/li><li><a href=\"#4_SEO_ve_yonlendirmeleri_dogru_kurgulayin\"><span class=\"toc_number toc_depth_2\">6.4<\/span> 4. SEO ve y\u00f6nlendirmeleri do\u011fru kurgulay\u0131n<\/a><\/li><\/ul><\/li><li><a href=\"#DCHost_uzerinde_DNS_yayilimini_yonetmek\"><span class=\"toc_number toc_depth_1\">7<\/span> DCHost \u00fczerinde DNS yay\u0131l\u0131m\u0131n\u0131 y\u00f6netmek<\/a><\/li><li><a href=\"#Ozet_ve_sonraki_adimlar\"><span class=\"toc_number toc_depth_1\">8<\/span> \u00d6zet ve sonraki ad\u0131mlar<\/a><\/li><\/ul><\/div>\n<h2><span id=\"DNS_yayilim_suresi_nedir\">DNS yay\u0131l\u0131m s\u00fcresi nedir?<\/span><\/h2>\n<p>DNS yay\u0131l\u0131m s\u00fcresi, DNS kay\u0131tlar\u0131n\u0131zda yapt\u0131\u011f\u0131n\u0131z bir de\u011fi\u015fikli\u011fin internet \u00fczerindeki t\u00fcm DNS \u00f6nbelleklerine yans\u0131y\u0131p \u201cherkes i\u00e7in ge\u00e7erli\u201d hale gelmesine kadar ge\u00e7en zamand\u0131r. \u00d6rne\u011fin:<\/p>\n<ul>\n<li>Alan ad\u0131n\u0131z\u0131n <strong>A kayd\u0131n\u0131<\/strong> de\u011fi\u015ftirirsiniz (IP de\u011fi\u015fimi),<\/li>\n<li><strong>MX kay\u0131tlar\u0131n\u0131<\/strong> g\u00fcncelleyip e\u2011posta trafi\u011fini yeni bir sunucuya y\u00f6nlendirirsiniz,<\/li>\n<li>Alan ad\u0131n\u0131z\u0131n <strong>nameserver<\/strong> (NS) adreslerini de\u011fi\u015ftirirsiniz.<\/li>\n<\/ul>\n<p>Bu de\u011fi\u015fiklikler teknik olarak yetkili DNS sunucunuzda an\u0131nda kaydolur; ancak d\u00fcnya \u00fczerindeki milyonlarca DNS \u00e7\u00f6z\u00fcmleyicinin (resolver) eski bilgiyi \u00f6nbelleklerinde tuttu\u011funu unutmay\u0131n. \u0130\u015fte bu \u00f6nbelleklerin tek tek g\u00fcncellenmesi s\u00fcrecine pratikte \u201cDNS yay\u0131l\u0131m\u0131\u201d diyoruz.<\/p>\n<p>DNS kay\u0131t t\u00fcrleriyle ilgili temel bilgilere h\u00e2kim de\u011filseniz, \u00f6nce <a href=\"https:\/\/www.dchost.com\/blog\/dns-kayitlari-nedir-a-aaaa-cname-mx-txt-ve-srv-rehberi\/\">DNS kay\u0131t t\u00fcrleri rehberi<\/a> yaz\u0131m\u0131za g\u00f6z atman\u0131z faydal\u0131 olur. Ayr\u0131ca yeni bir alan ad\u0131n\u0131 ilk kez sunucuya ba\u011flama a\u015famas\u0131ndaysan\u0131z, <a href=\"https:\/\/www.dchost.com\/blog\/yeni-aldiginiz-alan-adini-hosting-hesabina-baglamak-adim-adim-nameserver-dns-ve-ssl-rehberi\/\">alan ad\u0131n\u0131 hosting hesab\u0131na ba\u011flama ad\u0131mlar\u0131n\u0131 anlatt\u0131\u011f\u0131m\u0131z detayl\u0131 rehber<\/a> bu yaz\u0131yla birlikte okununca tablo iyice netle\u015fir.<\/p>\n<h2><span id=\"DNS_nasil_calisir_Yayilimi_etkileyen_katmanlar\">DNS nas\u0131l \u00e7al\u0131\u015f\u0131r? Yay\u0131l\u0131m\u0131 etkileyen katmanlar<\/span><\/h2>\n<p>DNS yay\u0131l\u0131m\u0131n\u0131 anlaman\u0131n en pratik yolu, DNS \u00e7\u00f6z\u00fcmleme s\u00fcrecini katman katman d\u00fc\u015f\u00fcnmekten ge\u00e7er. Bir kullan\u0131c\u0131 taray\u0131c\u0131ya alan ad\u0131n\u0131z\u0131 yazd\u0131\u011f\u0131nda \u015fu ad\u0131mlar\u0131n bir k\u0131sm\u0131 ya da tamam\u0131 devreye girer:<\/p>\n<ol>\n<li><strong>Taray\u0131c\u0131 \u00f6nbelle\u011fi<\/strong>: Taray\u0131c\u0131 daha \u00f6nce bu alan ad\u0131na gitti ise, k\u0131sa s\u00fcreli bir DNS \u00f6nbelle\u011fi tutuyor olabilir.<\/li>\n<li><strong>\u0130\u015fletim sistemi \u00f6nbelle\u011fi<\/strong>: Windows, macOS ve Linux, DNS sonu\u00e7lar\u0131n\u0131 belirli bir s\u00fcre kendi i\u00e7inde cache\u2019ler.<\/li>\n<li><strong>Modem \/ router \u00f6nbelle\u011fi<\/strong>: Baz\u0131 modemler, s\u0131k kullan\u0131lan alan adlar\u0131n\u0131 \u00f6nbelle\u011fe al\u0131r.<\/li>\n<li><strong>\u0130SS ya da kulland\u0131\u011f\u0131n\u0131z DNS hizmetinin recursive resolver\u2019\u0131<\/strong>: \u0130nternete \u00e7\u0131kt\u0131\u011f\u0131n\u0131z yerdeki DNS sunucusu (\u00f6rne\u011fin internet sa\u011flay\u0131c\u0131n\u0131z\u0131n DNS\u2019i) cevaplar\u0131 belli bir s\u00fcre saklar.<\/li>\n<li><strong>Yetkili (authoritative) DNS sunucusu<\/strong>: Alan ad\u0131n\u0131z i\u00e7in \u201cdo\u011fru cevab\u0131\u201d tutan as\u0131l kaynakt\u0131r. DCHost \u00fczerindeki DNS y\u00f6netim ekranlar\u0131n\u0131z, i\u015fte bu yetkili sunuculara kay\u0131t yazar.<\/li>\n<\/ol>\n<p>Pratikte \u201cyay\u0131l\u0131m\u201d, bu zincirin orta ve \u00fcst katmanlar\u0131ndaki \u00f6nbelleklerin (\u00f6zellikle de \u0130SS DNS sunucular\u0131n\u0131n) eski kayd\u0131 b\u0131rak\u0131p yeni cevab\u0131 almaya ba\u015flamas\u0131d\u0131r. Siz yetkili DNS \u00fczerinde kayd\u0131 de\u011fi\u015ftirdi\u011finiz anda teknik olarak <strong>do\u011fru cevap tek bir yerde haz\u0131rd\u0131r<\/strong>; geri kalan her \u015fey \u00f6nbellek s\u00fcresiyle ilgilidir.<\/p>\n<p>DNS\u2019in bu katmanl\u0131 yap\u0131s\u0131n\u0131n, hosting ve DNS taraf\u0131nda nas\u0131l b\u00fct\u00fcnle\u015fti\u011fini daha geni\u015f bir \u00e7er\u00e7evede g\u00f6rmek isterseniz, <a href=\"https:\/\/www.dchost.com\/blog\/web-hosting-nedir-domain-dns-sunucu-ve-ssl-nasil-birlikte-calisir\/\">domain, DNS, sunucu ve SSL\u2019in birlikte nas\u0131l \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 anlatt\u0131\u011f\u0131m\u0131z rehber<\/a> size iyi bir arka plan sunar.<\/p>\n<h2><span id=\"Neden_herkes_24_saat_surer_diyor_Gercekte_ne_kadar_surer\">Neden herkes \u201c24 saat s\u00fcrer\u201d diyor? Ger\u00e7ekte ne kadar s\u00fcrer?<\/span><\/h2>\n<p>\u201cDNS yay\u0131l\u0131m\u0131 24 saat s\u00fcrer\u201d c\u00fcmlesi asl\u0131nda teknik bir zorunluluktan de\u011fil, y\u0131llar i\u00e7inde olu\u015fmu\u015f muhafazak\u00e2r bir beklenti y\u00f6netimi c\u00fcmlesinden do\u011fuyor. Temel belirleyici, her DNS kayd\u0131n\u0131n \u00fczerinde tan\u0131ml\u0131 olan <strong>TTL (Time To Live)<\/strong> de\u011feridir.<\/p>\n<p>TTL, bir DNS cevab\u0131n\u0131n \u00f6nbellekte <strong>en fazla ka\u00e7 saniye tutulabilece\u011fini<\/strong> s\u00f6yler. \u00d6rne\u011fin TTL de\u011feri 3600 ise, recursive resolver teoride cevab\u0131 1 saat saklayabilir. Yeni kay\u0131t gelse bile, bu 1 saat dolana kadar eski cevab\u0131 d\u00f6nd\u00fcrmeye devam edebilir.<\/p>\n<p>Dolay\u0131s\u0131yla DNS yay\u0131l\u0131m s\u00fcresini belirleyen ana fakt\u00f6rler \u015funlard\u0131r:<\/p>\n<ul>\n<li>\u0130lgili kayd\u0131n TTL de\u011feri (\u00f6rne\u011fin 300 saniye, 3600 saniye, 86400 saniye vb.),<\/li>\n<li>Bu kayd\u0131n ne zaman kimler taraf\u0131ndan \u00e7\u00f6z\u00fcl\u00fcp \u00f6nbelle\u011fe al\u0131nd\u0131\u011f\u0131,<\/li>\n<li>\u0130SS\u2019lerin ve baz\u0131 DNS sunucular\u0131n\u0131n TTL\u2019e birebir uyup uymamalar\u0131 (baz\u0131lar\u0131 minimum TTL uygular, baz\u0131lar\u0131 TTL\u2019den uzun s\u00fcre cache\u2019ler).<\/li>\n<\/ul>\n<p>Uygulamada s\u0131k g\u00f6rd\u00fc\u011f\u00fcm\u00fcz tipik TTL de\u011ferleri \u015f\u00f6yledir:<\/p>\n<ul>\n<li><strong>300 sn (5 dk)<\/strong>: Canl\u0131 ta\u015f\u0131ma, deneme ortamlar\u0131, h\u0131zl\u0131 de\u011fi\u015fmesi gereken kay\u0131tlar.<\/li>\n<li><strong>1800\u20133600 sn (30\u201360 dk)<\/strong>: \u00c7o\u011fu web sitesi i\u00e7in makul varsay\u0131lan.<\/li>\n<li><strong>14400\u201386400 sn (4\u201324 saat)<\/strong>: Daha az de\u011fi\u015fen, oturmu\u015f prod ortamlar.<\/li>\n<\/ul>\n<p>Bu y\u00fczden \u201c24 saat s\u00fcrer\u201d ifadesi, asl\u0131nda <strong>TTL\u2019i 86400 saniye (24 saat) olan kay\u0131tlar i\u00e7in, en k\u00f6t\u00fc senaryoda<\/strong> kullan\u0131lan bir yuvarlamad\u0131r. Ger\u00e7ekte \u00e7o\u011fu modern DNS yap\u0131land\u0131rmas\u0131nda:<\/p>\n<ul>\n<li>A\/AAAA kay\u0131tlar\u0131 i\u00e7in de\u011fi\u015fiklikler 5\u201360 dakika i\u00e7inde b\u00fcy\u00fck oranda yay\u0131l\u0131r,<\/li>\n<li>MX ve TXT gibi kay\u0131tlar genelde 1\u20134 saat i\u00e7inde b\u00fcy\u00fck \u00e7o\u011funlu\u011fa ula\u015f\u0131r,<\/li>\n<li>Nameserver de\u011fi\u015fiklikleri ise TLD \u00f6nbellekleri devreye girdi\u011fi i\u00e7in 4\u201324 saat aras\u0131nda dalgalanabilir.<\/li>\n<\/ul>\n<p>Ancak her zaman baz\u0131 \u0130SS\u2019lerin veya eski cihazlar\u0131n \u00f6nbellekleri <strong>uzun s\u00fcre \u0131srarla eski kayd\u0131 tutabilir<\/strong>. Bu y\u00fczden kritik ge\u00e7i\u015flerde 24 saati tamamen g\u00f6zden \u00e7\u0131karmak yerine, planlaman\u0131z\u0131 \u201c\u00e7o\u011funluk h\u0131zl\u0131, az\u0131nl\u0131k yava\u015f\u201d mant\u0131\u011f\u0131yla yapman\u0131z en sa\u011fl\u0131kl\u0131s\u0131d\u0131r.<\/p>\n<h2><span id=\"Hangi_DNS_degisiklikleri_ne_kadar_surede_yayilir\">Hangi DNS de\u011fi\u015fiklikleri ne kadar s\u00fcrede yay\u0131l\u0131r?<\/span><\/h2>\n<p>DNS yay\u0131l\u0131m s\u00fcresi de\u011fi\u015fikli\u011fin t\u00fcr\u00fcne g\u00f6re de farkl\u0131l\u0131k g\u00f6sterir. Sahada g\u00f6rd\u00fc\u011f\u00fcm\u00fcz ortalama senaryolar\u0131 kabaca \u015f\u00f6yle \u00f6zetleyebiliriz (do\u011fru TTL ve d\u00fczg\u00fcn yap\u0131land\u0131rma varsay\u0131m\u0131yla):<\/p>\n<h3><span id=\"A_AAAA_kaydi_degisikligi_IP_adresi_degisimi\">A \/ AAAA kayd\u0131 de\u011fi\u015fikli\u011fi (IP adresi de\u011fi\u015fimi)<\/span><\/h3>\n<p>Web sitenizi yeni bir sunucuya ta\u015f\u0131d\u0131\u011f\u0131n\u0131zda en s\u0131k yapt\u0131\u011f\u0131n\u0131z i\u015flem, alan ad\u0131n\u0131z\u0131n A (IPv4) ya da AAAA (IPv6) kayd\u0131n\u0131 de\u011fi\u015ftirmektir. Bu durumda:<\/p>\n<ul>\n<li>Yay\u0131l\u0131m s\u00fcresi b\u00fcy\u00fck oranda <strong>kayd\u0131n TTL\u2019ine e\u015fittir<\/strong>. TTL 300 ise, pratikte 5\u201330 dakika i\u00e7inde \u00e7o\u011fu yerde yenilenir.<\/li>\n<li>Eski IP\u2019ye giden az\u0131nl\u0131k kullan\u0131c\u0131lar olabilir; bu y\u00fczden ta\u015f\u0131ma d\u00f6neminde eski sunucuyu tamamen kapatmadan \u00f6nce birka\u00e7 saat beklemek ak\u0131ll\u0131cad\u0131r.<\/li>\n<li>Y\u00fcksek trafikli sitelerde kesintisiz ge\u00e7i\u015f i\u00e7in genelde TTL\u2019yi \u00f6nceden d\u00fc\u015f\u00fcr\u00fcp sonra cutover yapmak en sa\u011flam stratejidir (a\u015fa\u011f\u0131da detayland\u0131raca\u011f\u0131z).<\/li>\n<\/ul>\n<h3><span id=\"MX_kaydi_degisikligi_eposta_altyapisi\">MX kayd\u0131 de\u011fi\u015fikli\u011fi (e\u2011posta altyap\u0131s\u0131)<\/span><\/h3>\n<p>MX kay\u0131tlar\u0131, e\u2011postalar\u0131n\u0131z\u0131n hangi sunucuya teslim edilece\u011fini belirler. MX de\u011fi\u015fimleri, web trafi\u011fi kadar g\u00f6r\u00fcn\u00fcr olmayabilir ama <strong>yanl\u0131\u015f planland\u0131\u011f\u0131nda ciddi e\u2011posta kay\u0131plar\u0131na<\/strong> yol a\u00e7abilir.<\/p>\n<ul>\n<li>Yay\u0131l\u0131m s\u00fcresi yine b\u00fcy\u00fck \u00f6l\u00e7\u00fcde TTL\u2019e ba\u011fl\u0131d\u0131r; \u00e7o\u011fu senaryoda 1\u20134 saat i\u00e7inde b\u00fcy\u00fck \u00e7o\u011funluk yeni MX\u2019e d\u00f6ner.<\/li>\n<li>Eski MX sunucunuz bir s\u00fcre daha ayakta kalmal\u0131 ve m\u00fcmk\u00fcnse yeni sisteme <strong>forward<\/strong> etmelidir.<\/li>\n<li>Ta\u015f\u0131ma s\u0131ras\u0131nda baz\u0131 g\u00f6nderici sunucular <strong>eski MX\u2019i<\/strong> kullanmaya devam edebilir; bu y\u00fczden \u201ckaybolan e\u2011posta var m\u0131?\u201d sorusunun cevab\u0131, ge\u00e7i\u015f mimarisine ba\u011fl\u0131d\u0131r.<\/li>\n<\/ul>\n<p>E\u2011posta altyap\u0131 ge\u00e7i\u015flerinde DNS yay\u0131l\u0131m\u0131n\u0131 do\u011fru y\u00f6netmek i\u00e7in, <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 rehberi<\/a> ve <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 i\u00e7in haz\u0131rlad\u0131\u011f\u0131m\u0131z yaz\u0131<\/a> ile birlikte bu makaleyi okuman\u0131z\u0131 \u00f6zellikle \u00f6neririz.<\/p>\n<h3><span id=\"Nameserver_NS_degisikligi\">Nameserver (NS) de\u011fi\u015fikli\u011fi<\/span><\/h3>\n<p>Alan ad\u0131n\u0131z\u0131 farkl\u0131 bir DNS sa\u011flay\u0131c\u0131s\u0131na ya da yeni bir hosting firmas\u0131na ge\u00e7irirken genelde nameserver\u2019lar\u0131 de\u011fi\u015ftirirsiniz. Bu, daha derin bir de\u011fi\u015fikliktir; \u00e7\u00fcnk\u00fc TLD (\u00f6rne\u011fin .com, .net, .org) seviyesinde tutulan \u201cbu alan ad\u0131 i\u00e7in yetkili DNS \u015funlard\u0131r\u201d bilgisini g\u00fcncellemi\u015f olursunuz.<\/p>\n<ul>\n<li>TLD taraf\u0131nda TTL\u2019ler devreye girdi\u011fi i\u00e7in tipik yay\u0131l\u0131m s\u00fcresi <strong>4\u201324 saat<\/strong> aral\u0131\u011f\u0131ndad\u0131r.<\/li>\n<li>Bir\u00e7ok kullan\u0131c\u0131 1\u20134 saat i\u00e7inde yeni NS \u00fczerinden \u00e7\u00f6z\u00fcmlemeye ba\u015flasa da, baz\u0131 \u0130SS\u2019ler TLD yan\u0131tlar\u0131n\u0131 agresif \u015fekilde cache\u2019leyebilir.<\/li>\n<li>Bu nedenle kritik ta\u015f\u0131malar\u0131 yo\u011fun trafi\u011fin daha az oldu\u011fu saatlere almak genelde daha az risklidir.<\/li>\n<\/ul>\n<h3><span id=\"TXT_CNAME_ve_diger_kayitlar\">TXT, CNAME ve di\u011fer kay\u0131tlar<\/span><\/h3>\n<p>TXT kay\u0131tlar\u0131 (SPF, DKIM, do\u011frulama kay\u0131tlar\u0131 vb.), CNAME kay\u0131tlar\u0131 ve SRV gibi \u00f6zel kay\u0131tlar da yay\u0131l\u0131m a\u00e7\u0131s\u0131ndan TTL\u2019e tabidir. Genelde bu kay\u0131tlar i\u00e7in daha k\u0131sa TTL\u2019ler kullan\u0131l\u0131r ve yay\u0131l\u0131m 5\u201360 dakika aral\u0131\u011f\u0131nda tamamlan\u0131r. Ancak e\u2011posta teslim edilebilirli\u011fi gibi hassas konularda yanl\u0131\u015f konfig\u00fcrasyon yaparsan\u0131z, DNS sadece \u201cyava\u015f\u201d de\u011fil, <strong>yanl\u0131\u015f<\/strong> da \u00e7al\u0131\u015fabilir.<\/p>\n<p>\u00d6rne\u011fin, SPF\/DKIM\/TXT taraf\u0131ndaki bir hata y\u00fcz\u00fcnden e\u2011postalar\u0131n\u0131z\u0131n spam klas\u00f6r\u00fcne d\u00fc\u015ft\u00fc\u011f\u00fcn\u00fc \u00e7ok s\u0131k g\u00f6r\u00fcyoruz. Bu konuyu derinlemesine ele ald\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/e-postalar-neden-spam-klasorune-dusuyor-paylasimli-hosting-ve-vps-icin-teslim-edilebilirlik-kontrol-listesi\/\">e\u2011postalar\u0131n neden spam klas\u00f6r\u00fcne d\u00fc\u015ft\u00fc\u011f\u00fcn\u00fc ve teslim edilebilirli\u011fi nas\u0131l iyile\u015ftirebilece\u011finizi anlatan rehber<\/a>, DNS kay\u0131tlar\u0131n\u0131z\u0131 d\u00fczenlerken ba\u015fucunuzda durmal\u0131.<\/p>\n<h2><span id=\"DNS_yayilim_suresini_gercekten_nasil_hizlandirirsiniz\">DNS yay\u0131l\u0131m s\u00fcresini ger\u00e7ekten nas\u0131l h\u0131zland\u0131r\u0131rs\u0131n\u0131z?<\/span><\/h2>\n<p>Gelelim en kritik soruya: DNS yay\u0131l\u0131m\u0131 \u201ckader\u201d midir, yoksa ak\u0131ll\u0131 planlamayla b\u00fcy\u00fck \u00f6l\u00e7\u00fcde y\u00f6netilebilir mi? Deneyimimiz, iyi bir stratejiyle hem s\u00fcreyi hem de riskleri ciddi oranda d\u00fc\u015f\u00fcrebilece\u011finiz y\u00f6n\u00fcnde.<\/p>\n<h3><span id=\"1_TTL_stratejisini_dogru_kullanmak\">1. TTL stratejisini do\u011fru kullanmak<\/span><\/h3>\n<p>Yay\u0131l\u0131m\u0131 h\u0131zland\u0131rman\u0131n en g\u00fc\u00e7l\u00fc ve en temiz yolu <strong>TTL de\u011ferlerini planl\u0131 bir \u015fekilde y\u00f6netmektir<\/strong>. \u00d6nerdi\u011fimiz tipik yakla\u015f\u0131m \u015f\u00f6yle:<\/p>\n<ol>\n<li><strong>Ge\u00e7i\u015ften 24\u201348 saat \u00f6nce:<\/strong> Ta\u015f\u0131may\u0131 planlad\u0131\u011f\u0131n\u0131z A, AAAA, MX vb. kay\u0131tlar\u0131n TTL\u2019ini d\u00fc\u015f\u00fcr\u00fcn (\u00f6rne\u011fin 3600 \u2192 300 saniye).<\/li>\n<li><strong>Bekleme a\u015famas\u0131:<\/strong> D\u00fc\u015f\u00fck TTL, eski \u00f6nbelleklerin kendini yenilemesini sa\u011flar. Bu s\u00fcre zarf\u0131nda h\u00e2l\u00e2 eski kayda i\u015faret ediyorsunuz.<\/li>\n<li><strong>Cutover an\u0131:<\/strong> Yeni IP\u2019ye, yeni MX\u2019e veya yeni hedefe ge\u00e7i\u015f yap\u0131n. Art\u0131k DNS \u00e7\u00f6z\u00fcmleyiciler, en fazla 300 sn i\u00e7inde yeni kayd\u0131 alm\u0131\u015f olacak.<\/li>\n<li><strong>Stabil olduktan sonra:<\/strong> Gerekiyorsa TTL\u2019i tekrar makul bir seviyeye (\u00f6rne\u011fin 1800\u20133600) y\u00fckseltebilirsiniz.<\/li>\n<\/ol>\n<p>Bu konuya \u00f6zel, senaryo bazl\u0131 bir yaz\u0131m\u0131z da var: <a href=\"https:\/\/www.dchost.com\/blog\/zero-downtime-tasima-icin-ttl-stratejileri-dns-yayilimini-gercekten-nasil-hizlandirirsin\/\">TTL stratejileriyle DNS yay\u0131l\u0131m\u0131n\u0131 h\u0131zland\u0131rma rehberi<\/a>. Bu makaledeki genel prensipleri oradaki pratik oyun planlar\u0131yla birle\u015ftirdi\u011finizde, s\u0131f\u0131ra \u00e7ok yak\u0131n kesintiyle ta\u015f\u0131ma yapmak gayet m\u00fcmk\u00fcn.<\/p>\n<h3><span id=\"2_Yerel_DNS_onbellegini_temizlemek_siz_ve_musterileriniz_icin\">2. Yerel DNS \u00f6nbelle\u011fini temizlemek (siz ve m\u00fc\u015fterileriniz i\u00e7in)<\/span><\/h3>\n<p>TTL stratejisi global yay\u0131l\u0131m\u0131 h\u0131zland\u0131r\u0131rken, kendi bilgisayar\u0131n\u0131zda h\u00e2l\u00e2 eski kayd\u0131 g\u00f6r\u00fcyor olabilirsiniz. Bu durumda <strong>yerel DNS cache\u2019i temizlemek<\/strong> i\u015fe yarar:<\/p>\n<ul>\n<li><strong>Windows<\/strong>: Komut istemini y\u00f6netici olarak a\u00e7\u0131p <code>ipconfig \/flushdns<\/code> komutunu \u00e7al\u0131\u015ft\u0131r\u0131n.<\/li>\n<li><strong>macOS<\/strong> (yeni s\u00fcr\u00fcmler): Terminal\u2019de <code>sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder<\/code>.<\/li>\n<li><strong>Linux<\/strong>: Kulland\u0131\u011f\u0131n\u0131z DNS cache servisine g\u00f6re (systemd-resolved, nscd, dnsmasq) ilgili servisi yeniden ba\u015flat\u0131n.<\/li>\n<li><strong>Taray\u0131c\u0131<\/strong>: Baz\u0131 durumlarda taray\u0131c\u0131 \u00f6nbelle\u011fini temizlemek veya farkl\u0131 bir taray\u0131c\u0131yla test etmek de fark yarat\u0131r.<\/li>\n<\/ul>\n<p>Bu ad\u0131mlar <strong>sadece sizin cihaz\u0131n\u0131z<\/strong> i\u00e7in ge\u00e7erlidir; t\u00fcm internetin yay\u0131l\u0131m h\u0131z\u0131n\u0131 etkilemez. Ancak \u00f6zellikle ge\u00e7i\u015f sonras\u0131 testlerde, \u201casl\u0131nda DNS de\u011fi\u015fmi\u015f ama siz h\u00e2l\u00e2 eski cache\u2019i g\u00f6r\u00fcyorsunuz\u201d yan\u0131lg\u0131s\u0131n\u0131 ortadan kald\u0131r\u0131r.<\/p>\n<h3><span id=\"3_Dogru_DNS_altyapisini_kullanmak\">3. Do\u011fru DNS altyap\u0131s\u0131n\u0131 kullanmak<\/span><\/h3>\n<p>Yetkili DNS sunucular\u0131n\u0131z\u0131n bulundu\u011fu altyap\u0131 da, DNS yan\u0131t s\u00fcrelerini ve dolayl\u0131 olarak yay\u0131l\u0131m\u0131n \u201chissedili\u015fini\u201d etkiler. Anycast mimarisiyle \u00e7al\u0131\u015fan, d\u00fcnya geneline yay\u0131lm\u0131\u015f DNS sunucular\u0131, kullan\u0131c\u0131lara en yak\u0131n noktadan cevap d\u00f6nd\u00fc\u011f\u00fc i\u00e7in daha d\u00fc\u015f\u00fck gecikme (latency) sunar.<\/p>\n<p>DCHost b\u00fcnyesinde sundu\u011fumuz DNS hizmetlerinde, hosting ve <a href=\"https:\/\/www.dchost.com\/tr\/vps\">VPS<\/a> m\u00fc\u015fterilerimizin kay\u0131tlar\u0131 performans ve s\u00fcreklilik odakl\u0131 bir altyap\u0131da tutulur. Bu sayede:<\/p>\n<ul>\n<li>DNS yan\u0131t s\u00fcreleri istikrarl\u0131 ve d\u00fc\u015f\u00fck kal\u0131r,<\/li>\n<li>Olas\u0131 a\u011f ya da donan\u0131m sorunlar\u0131na kar\u015f\u0131 yedekli bir yap\u0131 kullan\u0131l\u0131r,<\/li>\n<li>Yo\u011fun trafik d\u00f6nemlerinde bile DNS katman\u0131 darbo\u011faz olmadan i\u015fini yapar.<\/li>\n<\/ul>\n<p>\u0130yi bir DNS altyap\u0131s\u0131 yay\u0131l\u0131m s\u00fcresini \u201cmucizevi \u015fekilde s\u0131f\u0131ra indirmez\u201d, ancak <strong>h\u0131zl\u0131 ve tutarl\u0131 yan\u0131t<\/strong> sayesinde de\u011fi\u015fikliklerin etkisini \u00e7ok daha p\u00fcr\u00fczs\u00fcz hissetmenizi sa\u011flar.<\/p>\n<h3><span id=\"4_Yanlis_kayit_ve_konfigurasyon_hatalarindan_kacinmak\">4. Yanl\u0131\u015f kay\u0131t ve konfig\u00fcrasyon hatalar\u0131ndan ka\u00e7\u0131nmak<\/span><\/h3>\n<p>Bazen sorun yay\u0131l\u0131m s\u00fcresinde de\u011fil, <strong>yanl\u0131\u015f girilmi\u015f bir kay\u0131tta<\/strong> olur. A kayd\u0131n\u0131 hatal\u0131 IP\u2019ye, MX kayd\u0131n\u0131 yanl\u0131\u015f hostname\u2019e veya SPF kayd\u0131n\u0131 hatal\u0131 bir s\u00f6zdizimiyle girdiyseniz; yay\u0131l\u0131m beklemekle zaman kaybedersiniz, \u00e7\u00fcnk\u00fc en sonunda yay\u0131lacak \u015fey yine <strong>yanl\u0131\u015f<\/strong> bir cevapt\u0131r.<\/p>\n<p>\u00d6zellikle \u015fu senaryolar\u0131 s\u0131k g\u00f6r\u00fcyoruz:<\/p>\n<ul>\n<li>Alan ad\u0131n\u0131n sonuna gereksiz nokta (.) konmas\u0131 veya tam tersi, konulmas\u0131 gerekirken unutulmas\u0131,<\/li>\n<li>Apex (k\u00f6k) alanda CNAME kullan\u0131m hatalar\u0131,<\/li>\n<li>TXT\/SPF kay\u0131tlar\u0131nda t\u0131rnak ve bo\u015fluk hatalar\u0131,<\/li>\n<li>NS kay\u0131tlar\u0131n\u0131n eksik ya da yanl\u0131\u015f yaz\u0131lmas\u0131.<\/li>\n<\/ul>\n<p>Bu tip durumlarda taray\u0131c\u0131n\u0131zda <code>DNS_PROBE_FINISHED_NXDOMAIN<\/code> gibi hatalarla kar\u015f\u0131la\u015fman\u0131z m\u00fcmk\u00fcn. Bu noktada <a href=\"https:\/\/www.dchost.com\/blog\/dns-hatalari-yuzunden-site-acilmiyor-dns_probe_finished_nxdomain-teshis-rehberi\/\">DNS_PROBE_FINISHED_NXDOMAIN ve benzeri DNS hatalar\u0131n\u0131 te\u015fhis etme rehberimiz<\/a> \u00fczerinden giderek, problemin yay\u0131l\u0131mdan m\u0131 yoksa yanl\u0131\u015f konfig\u00fcrasyondan m\u0131 kaynakland\u0131\u011f\u0131n\u0131 h\u0131zl\u0131ca ay\u0131rt edebilirsiniz.<\/p>\n<h2><span id=\"DNS_yayilimi_sirasinda_dikkat_etmeniz_gereken_operasyonel_ipuclari\">DNS yay\u0131l\u0131m\u0131 s\u0131ras\u0131nda dikkat etmeniz gereken operasyonel ipu\u00e7lar\u0131<\/span><\/h2>\n<p>DNS de\u011fi\u015fikli\u011fini teknik olarak do\u011fru yapmak kadar, <strong>operasyonel s\u00fcre\u00e7leri do\u011fru kurgulamak<\/strong> da \u00f6nemli. \u00d6zellikle y\u00fcksek trafikli sitelerde, e\u2011ticaret projelerinde veya kritik e\u2011posta altyap\u0131lar\u0131nda \u015fu pratikleri \u00f6neriyoruz:<\/p>\n<h3><span id=\"1_Eski_ve_yeni_sunucuyu_bir_sure_paralel_calistirin\">1. Eski ve yeni sunucuyu bir s\u00fcre paralel \u00e7al\u0131\u015ft\u0131r\u0131n<\/span><\/h3>\n<p>\u00d6zellikle IP de\u011fi\u015fimlerinde (A\/AAAA kayd\u0131), DNS yay\u0131l\u0131m\u0131n\u0131n \u201ctam bitti\u011fi an\u0131\u201d y\u00fczde y\u00fcz yakalamak m\u00fcmk\u00fcn de\u011fildir. Bu y\u00fczden:<\/p>\n<ul>\n<li>Yeni sunucuyu tamamen haz\u0131r h\u00e2le getirdikten sonra DNS\u2019i yeni IP\u2019ye \u00e7evirin,<\/li>\n<li>Eski sunucuyu <strong>en az birka\u00e7 saat, tercihen 24 saat<\/strong> daha kapatmadan ayakta tutun,<\/li>\n<li>Statik sitelerde bu neredeyse s\u0131f\u0131r \u00e7ak\u0131\u015fma ile \u00e7al\u0131\u015f\u0131r; dinamik uygulamalarda ise veritaban\u0131 replikasyonu gibi ilave mimari ad\u0131mlar gerekebilir.<\/li>\n<\/ul>\n<p>Daha karma\u015f\u0131k (\u00e7ok b\u00f6lgeli, replikasyonlu) mimariler planl\u0131yorsan\u0131z, <a href=\"https:\/\/www.dchost.com\/blog\/cok-bolgeli-mimariler-nasil-kurulur-dns-geo%e2%80%91routing-ve-veritabani-replikasyonu-ile-korkusuz-felaket-dayanikliligi\/\">\u00e7ok b\u00f6lgeli mimarilerde DNS y\u00f6nlendirme ve veritaban\u0131 replikasyonu ile kesintisizli\u011fi anlatt\u0131\u011f\u0131m\u0131z rehber<\/a> size ileri seviye fikirler verebilir.<\/p>\n<h3><span id=\"2_hosts_dosyasi_ile_once_kendiniz_test_edin\">2. hosts dosyas\u0131 ile \u00f6nce kendiniz test edin<\/span><\/h3>\n<p>DNS\u2019ye dokunmadan \u00f6nce, yeni sunucunun ger\u00e7ekten sorunsuz \u00e7al\u0131\u015ft\u0131\u011f\u0131ndan emin olman\u0131n en pratik yollar\u0131ndan biri <strong>hosts dosyas\u0131<\/strong> ile ge\u00e7ici y\u00f6nlendirme yapmakt\u0131r. B\u00f6ylece:<\/p>\n<ul>\n<li>Sadece kendi bilgisayar\u0131n\u0131z alan ad\u0131n\u0131 yeni IP\u2019ye \u00e7\u00f6zer,<\/li>\n<li>Ger\u00e7ek kullan\u0131c\u0131lar h\u00e2l\u00e2 eski, stabil sunucuya gitmeye devam eder,<\/li>\n<li>T\u00fcm testleri (SSL, oturumlar, \u00f6deme ad\u0131mlar\u0131, e\u2011posta g\u00f6nderimi vb.) DNS\u2019e dokunmadan tamamlayabilirsiniz.<\/li>\n<\/ul>\n<p>Bu sayede DNS yay\u0131l\u0131m\u0131na ge\u00e7ti\u011finizde \u201cs\u00fcrprizlerle\u201d kar\u015f\u0131la\u015fma ihtimaliniz ciddi oranda azal\u0131r.<\/p>\n<h3><span id=\"3_Eposta_gecislerinde_MX_kayitlarini_asamali_degistirin\">3. E\u2011posta ge\u00e7i\u015flerinde MX kay\u0131tlar\u0131n\u0131 a\u015famal\u0131 de\u011fi\u015ftirin<\/span><\/h3>\n<p>E\u2011posta altyap\u0131s\u0131n\u0131 ta\u015f\u0131rken en \u00e7ok yap\u0131lan hata, tek seferde MX de\u011fi\u015ftirip eski sunucuyu hemen kapatmakt\u0131r. Bunun yerine:<\/p>\n<ul>\n<li>Yeni e\u2011posta altyap\u0131n\u0131z\u0131 haz\u0131r h\u00e2le getirin ve test edin,<\/li>\n<li>MX kay\u0131tlar\u0131n\u0131 \u00f6ncelik de\u011ferleriyle oynayarak <strong>a\u015famal\u0131<\/strong> ge\u00e7i\u015f yap\u0131n (\u00f6rne\u011fin yeni MX\u2019i daha d\u00fc\u015f\u00fck say\u0131 ile daha \u00f6ncelikli h\u00e2le getirmek),<\/li>\n<li>Eski sunucudan yeniye <strong>forward<\/strong> kural\u0131 ekleyin; b\u00f6ylece yay\u0131l\u0131m s\u00fcresince gelen posta kaybolmaz.<\/li>\n<\/ul>\n<p>DNS yay\u0131l\u0131m\u0131 ve e\u2011posta ge\u00e7i\u015flerini ayn\u0131 potada eritmek i\u00e7in, bu yaz\u0131n\u0131n yan\u0131 s\u0131ra e\u2011posta odakl\u0131 rehberlerimize g\u00f6z atman\u0131z operasyonel a\u00e7\u0131dan ciddi rahatl\u0131k sa\u011flar.<\/p>\n<h3><span id=\"4_SEO_ve_yonlendirmeleri_dogru_kurgulayin\">4. SEO ve y\u00f6nlendirmeleri do\u011fru kurgulay\u0131n<\/span><\/h3>\n<p>Alan ad\u0131 de\u011fi\u015fikli\u011fi, HTTP\u2192HTTPS ge\u00e7i\u015fi veya URL yap\u0131s\u0131 de\u011fi\u015fiklikleri gibi SEO hassas konularda, DNS yay\u0131l\u0131m\u0131 tek ba\u015f\u0131na yetmez; <strong>301 y\u00f6nlendirmeleri<\/strong> ve sunucu taraf\u0131 ayarlar da kritik rol oynar.<\/p>\n<ul>\n<li>Yeni sunucuya ge\u00e7ti\u011finizde, eski alan ad\u0131ndan yenisine 301 y\u00f6nlendirmeleri mutlaka do\u011fru kurulmal\u0131,<\/li>\n<li>HTTPS\u2019e ge\u00e7erken HSTS, sertifika ve y\u00f6nlendirme zincirleri temiz olmal\u0131,<\/li>\n<li>DNS ve HTTP d\u00fczeyindeki t\u00fcm ge\u00e7i\u015fler bir b\u00fct\u00fcn olarak planlanmal\u0131.<\/li>\n<\/ul>\n<p>Bu noktada <a href=\"https:\/\/www.dchost.com\/blog\/httpden-httpse-gecis-rehberi-301-yonlendirme-hsts-ve-seoyu-korumak\/\">HTTP\u2019den HTTPS\u2019e ge\u00e7i\u015fte 301 y\u00f6nlendirme ve HSTS ayarlar\u0131n\u0131 anlatt\u0131\u011f\u0131m\u0131z rehber<\/a> ile <a href=\"https:\/\/www.dchost.com\/blog\/alan-adi-degistirirken-seo-kaybetmemek\/\">alan ad\u0131 de\u011fi\u015ftirirken SEO kaybetmemek i\u00e7in haz\u0131rlad\u0131\u011f\u0131m\u0131z yaz\u0131<\/a>, DNS taraf\u0131ndaki bu makaleyle birlikte d\u00fc\u015f\u00fcn\u00fcld\u00fc\u011f\u00fcnde size u\u00e7tan uca bir yol haritas\u0131 verir.<\/p>\n<h2><span id=\"DCHost_uzerinde_DNS_yayilimini_yonetmek\">DCHost \u00fczerinde DNS yay\u0131l\u0131m\u0131n\u0131 y\u00f6netmek<\/span><\/h2>\n<p>DCHost m\u00fc\u015fterileri i\u00e7in DNS, g\u00fcnl\u00fck operasyonlarda en s\u0131k dokunulan katmanlardan biri. <a href=\"https:\/\/www.dchost.com\/tr\/web-hosting\">payla\u015f\u0131ml\u0131 hosting<\/a>, VPS ya da <a href=\"https:\/\/www.dchost.com\/tr\/fiziksel-sunucu\">dedicated sunucu<\/a> kullan\u0131yor olun; kontrol paneliniz \u00fczerinden alan ad\u0131n\u0131z\u0131n DNS kay\u0131tlar\u0131n\u0131 y\u00f6netebilir, TTL de\u011ferlerini g\u00fcncelleyebilir ve gerekti\u011finde ge\u00e7i\u015flerinizi planlayabilirsiniz.<\/p>\n<p>Genel olarak \u015fu prensipleri \u00f6neriyoruz:<\/p>\n<ul>\n<li>Canl\u0131 ta\u015f\u0131madan <strong>en az 24 saat \u00f6nce<\/strong> kritik kay\u0131tlar\u0131n TTL\u2019ini d\u00fc\u015f\u00fcr\u00fcn,<\/li>\n<li>DNS de\u011fi\u015fikli\u011fini d\u00fc\u015f\u00fck trafikli bir zaman dilimine konumland\u0131r\u0131n,<\/li>\n<li>\u0130lk 1\u20132 saat boyunca izlemeyi s\u0131k\u0131 tutun; loglar\u0131 ve hata bildirimlerini takip edin,<\/li>\n<li>Her \u015fey stabil olduktan sonra TTL\u2019leri tekrar mant\u0131kl\u0131 ve dengeli bir seviyeye y\u00fckseltin.<\/li>\n<\/ul>\n<p>Altyap\u0131 olarak DCHost; domain, hosting, VPS, dedicated sunucu ve colocation hizmetlerini ayn\u0131 \u00e7at\u0131 alt\u0131nda sundu\u011fu i\u00e7in, DNS taraf\u0131ndaki kararlar\u0131n\u0131z\u0131 da genel bar\u0131nd\u0131rma stratejinizle uyumlu \u015fekilde kurgulaman\u0131z m\u00fcmk\u00fcn. Soru i\u015faretleriniz oldu\u011funda teknik ekibimize senaryonuzu \u00f6nden anlatman\u0131z, birlikte en do\u011fru TTL ve ge\u00e7i\u015f plan\u0131n\u0131 \u00e7\u0131karmam\u0131z\u0131 kolayla\u015ft\u0131r\u0131r.<\/p>\n<h2><span id=\"Ozet_ve_sonraki_adimlar\">\u00d6zet ve sonraki ad\u0131mlar<\/span><\/h2>\n<p>DNS yay\u0131l\u0131m s\u00fcresi, \u00e7o\u011fu zaman gizemli ve kontrol edilemez bir s\u00fcre\u00e7 gibi anlat\u0131l\u0131r; oysa i\u015fin kalbinde son derece net bir mekanizma var: <strong>\u00f6nbellekler ve TTL de\u011ferleri<\/strong>. Siz yetkili DNS sunucunuzda kayd\u0131 de\u011fi\u015ftirdi\u011finiz anda, do\u011fru cevab\u0131n tek kayna\u011f\u0131 haz\u0131rd\u0131r; geri kalan t\u00fcm gecikme, d\u00fcnyan\u0131n d\u00f6rt bir yan\u0131ndaki DNS \u00e7\u00f6z\u00fcmleyicilerin bu yeni cevab\u0131 ne kadar s\u00fcrede alaca\u011f\u0131yla ilgilidir.<\/p>\n<p>Bu yaz\u0131da, \u201c24 saat s\u00fcrer\u201d kli\u015fesinin nereden geldi\u011fini, farkl\u0131 kay\u0131t t\u00fcrleri i\u00e7in ortalama yay\u0131l\u0131m s\u00fcrelerini, TTL stratejileriyle bu s\u00fcreyi nas\u0131l ciddi \u015fekilde k\u0131saltabilece\u011finizi ve ge\u00e7i\u015f s\u0131ras\u0131nda operasyonel a\u00e7\u0131dan nelere dikkat etmeniz gerekti\u011fini konu\u015ftuk. Art\u0131k yeni bir sunucuya ge\u00e7erken, MX kayd\u0131n\u0131 g\u00fcncellerken veya nameserver de\u011fi\u015ftirirken neyle kar\u015f\u0131la\u015faca\u011f\u0131n\u0131z\u0131 \u00e7ok daha net \u00f6ng\u00f6rebilirsiniz.<\/p>\n<p>\u00d6n\u00fcn\u00fczde bir ta\u015f\u0131ma, alan ad\u0131 de\u011fi\u015fikli\u011fi ya da e\u2011posta altyap\u0131s\u0131 yenileme projesi varsa; DCHost \u00fczerinde kullanaca\u011f\u0131n\u0131z domain ve hosting hizmetleriyle birlikte, bu yaz\u0131daki ad\u0131mlar\u0131 ve ba\u011flant\u0131 verdi\u011fimiz di\u011fer detayl\u0131 rehberleri bir plan h\u00e2line getirmenizi \u00f6neririz. Do\u011fru TTL, temiz DNS kay\u0131tlar\u0131 ve iyi tasarlanm\u0131\u015f bir ge\u00e7i\u015f penceresiyle, \u201cDNS yay\u0131l\u0131m\u0131 y\u00fcz\u00fcnden saatlerce bekledik\u201d c\u00fcmlesini b\u00fcy\u00fck \u00f6l\u00e7\u00fcde tarihe g\u00f6mebilirsiniz.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>Alan ad\u0131n\u0131z\u0131 yeni bir sunucuya ta\u015f\u0131d\u0131\u011f\u0131n\u0131zda, A kayd\u0131n\u0131 g\u00fcncelledi\u011finizde ya da e\u2011posta altyap\u0131n\u0131z\u0131 ba\u015fka bir servise y\u00f6nlendirdi\u011finizde ilk kar\u015f\u0131n\u0131za \u00e7\u0131kan soru genelde ayn\u0131d\u0131r: \u201cDNS yay\u0131l\u0131m\u0131 ne zaman bitecek, neden h\u00e2l\u00e2 eski sunucuya gidiyor?\u201d Bu belirsizlik, \u00f6zellikle canl\u0131ya ge\u00e7i\u015f anlar\u0131nda hem teknik ekipleri hem de i\u015f taraf\u0131n\u0131 gereksiz strese sokar. Bu yaz\u0131da sahada en \u00e7ok kar\u015f\u0131la\u015ft\u0131\u011f\u0131m\u0131z [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":3027,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-3026","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\/3026","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=3026"}],"version-history":[{"count":0,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/3026\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/3027"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=3026"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=3026"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=3026"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}