{"id":988,"date":"2026-09-28T16:26:38","date_gmt":"2026-09-28T16:26:38","guid":{"rendered":"https:\/\/www.vps.tc\/blog\/?p=988"},"modified":"2026-10-03T12:20:51","modified_gmt":"2026-10-03T12:20:51","slug":"dns-yayilmasi-ne-kadar-surer","status":"publish","type":"post","link":"https:\/\/www.vps.tc\/blog\/tr\/dns-yayilmasi-ne-kadar-surer\/","title":{"rendered":"DNS Yay\u0131lmas\u0131 Nedir? Ne Kadar S\u00fcrer?"},"content":{"rendered":"<div class=\"aiw-summary\" id=\"aiw-ozet\">\n<p class=\"aiw-summary-title\">H\u0131zl\u0131 \u00d6zet &#8211; DNS Yay\u0131lmas\u0131<\/p>\n<p>DNS yay\u0131lmas\u0131, yeni kayd\u0131n her cihaza tek seferde g\u00f6nderilmesi de\u011fil, resolver \u00f6nbelleklerinin eski cevaplar\u0131 b\u0131rakmas\u0131d\u0131r. S\u00fcreyi TTL, nameserver de\u011fi\u015fikli\u011fi, negatif \u00f6nbellek ve DNSSEC etkiler.<\/p>\n<ul>\n<li><strong>Tipik s\u00fcre<\/strong> \u2014 A ve CNAME kay\u0131tlar\u0131 \u00e7o\u011funlukla TTL s\u00fcresi i\u00e7inde farkl\u0131 a\u011flarda g\u00fcncellenir.<\/li>\n<li><strong>TTL s\u0131n\u0131r\u0131<\/strong> \u2014 300 saniyelik TTL eski cevab\u0131n yakla\u015f\u0131k 5 dakika tutulabilece\u011fini belirtir; kesin g\u00f6r\u00fcn\u00fcrl\u00fck saati vermez.<\/li>\n<li><strong>Nameserver ge\u00e7i\u015fi<\/strong> \u2014 NS delegasyonu de\u011fi\u015fiklikleri birka\u00e7 saat veya daha uzun s\u00fcrebilir ve eski-yeni sunucular birlikte \u00e7al\u0131\u015fmal\u0131d\u0131r.<\/li>\n<li><strong>Kontrol y\u00f6ntemi<\/strong> \u2014 1.1.1.1, 8.8.8.8 ve yetkili nameserver&#039;\u0131 dig ile ayr\u0131 ayr\u0131 sorgulay\u0131n.<\/li>\n<li><strong>Eski site sorunu<\/strong> \u2014 Yerel cache, \u0130SS resolver&#039;\u0131, AAAA kayd\u0131, CDN veya yanl\u0131\u015f DNS b\u00f6lgesi eski i\u00e7eri\u011fe neden olabilir.<\/li>\n<li><strong>DNSSEC istisnas\u0131<\/strong> \u2014 Uyumsuz DS ve imza kay\u0131tlar\u0131 beklemek yerine SERVFAIL ve DNSSEC zinciri incelemesini gerektirir.<\/li>\n<\/ul>\n<\/div>\n<p class=\"aiw-lead\">DNS yay\u0131lmas\u0131 \u00e7o\u011fu zaman birka\u00e7 dakika ile TTL s\u00fcresi aras\u0131nda tamamlan\u0131r; nameserver de\u011fi\u015fikliklerinde s\u00fcre birka\u00e7 saate, baz\u0131 durumlarda daha uzun bir pencereye \u00e7\u0131kabilir. Kesin s\u00fcre TTL, resolver \u00f6nbelle\u011fi, DNSSEC, negatif \u00f6nbellek ve A\/AAAA kay\u0131tlar\u0131n\u0131n tutarl\u0131l\u0131\u011f\u0131na ba\u011fl\u0131d\u0131r. Farkl\u0131 resolver&#039;lar\u0131 sorgulamadan yaln\u0131zca beklemek do\u011fru te\u015fhis de\u011fildir.<\/p>\n<div class=\"aiw-toc\" style=\"border:1px solid #dbe3ea;border-radius:8px;padding:16px 20px;margin:0 0 28px\">\n<p class=\"aiw-toc-head\"><strong>\u0130\u00e7indekiler<\/strong><span class=\"aiw-toc-meta\"> \u00b7 10 dk okuma<\/span><\/p>\n<ol style=\"margin:10px 0 0;padding-left:22px\">\n<li><a href=\"#dns-yayilmasi-aslinda-ne-anlama-gelir\">DNS yay\u0131lmas\u0131 asl\u0131nda ne anlama gelir?<\/a><\/li>\n<li><a href=\"#dns-yayilmasi-ne-kadar-surer\">DNS yay\u0131lmas\u0131 ne kadar s\u00fcrer?<\/a><\/li>\n<li><a href=\"#ttl-degeri-degisikligi-nasil-etkiler\">TTL de\u011feri de\u011fi\u015fikli\u011fi nas\u0131l etkiler?<\/a><\/li>\n<li><a href=\"#dns-kaydi-degisti-neden-hala-eski-site-aciliyor\">DNS kayd\u0131 de\u011fi\u015fti, neden h\u00e2l\u00e2 eski site a\u00e7\u0131l\u0131yor?<\/a><\/li>\n<li><a href=\"#nameserver-degisikligi-neden-daha-uzun-surer\">Nameserver de\u011fi\u015fikli\u011fi neden daha uzun s\u00fcrer?<\/a><\/li>\n<li><a href=\"#dns-yayilmasini-nasil-kontrol-edebilirsiniz\">DNS yay\u0131lmas\u0131n\u0131 nas\u0131l kontrol edebilirsiniz?<\/a><\/li>\n<li><a href=\"#dnssec-negatif-onbellek-ve-diger-istisnalar\">DNSSEC, negatif \u00f6nbellek ve di\u011fer istisnalar<\/a><\/li>\n<li><a href=\"#tasima-oncesi-ve-sonrasi-uygulanacak-yontem\">Ta\u015f\u0131ma \u00f6ncesi ve sonras\u0131 uygulanacak y\u00f6ntem<\/a><\/li>\n<li><a href=\"#dns-degisikliginden-once-ve-sonra-kontrol-edin\">DNS De\u011fi\u015fikli\u011finden \u00d6nce ve Sonra Kontrol Edin<\/a><\/li>\n<li><a href=\"#sik-sorulan-sorular\">S\u0131k Sorulan Sorular<\/a><\/li>\n<li><a href=\"#kaynaklar\">Kaynaklar<\/a><\/li>\n<\/ol>\n<\/div>\n<h2 id=\"dns-yayilmasi-aslinda-ne-anlama-gelir\">DNS yay\u0131lmas\u0131 asl\u0131nda ne anlama gelir?<\/h2>\n<p>Bir alan ad\u0131n\u0131n IP adresi, DNS kay\u0131t t\u00fcr\u00fc veya nameserver bilgisi de\u011fi\u015ftirildi\u011finde tek bir merkezdeki kay\u0131t g\u00fcncellenmez. Yetkili DNS sunucusu yeni cevab\u0131 vermeye ba\u015flar; internet servis sa\u011flay\u0131c\u0131lar\u0131, i\u015fletim sistemleri, taray\u0131c\u0131lar ve kurumsal a\u011flar bu cevab\u0131 TTL s\u00fcreleri boyunca \u00f6nbellekte tutabilir. Bu nedenle ayn\u0131 alan ad\u0131, farkl\u0131 a\u011flardan bir s\u00fcre farkl\u0131 IP adreslerine \u00e7\u00f6z\u00fclebilir.<\/p>\n<p>DNS yay\u0131lmas\u0131, yeni kayd\u0131n d\u00fcnyan\u0131n her noktas\u0131na g\u00f6nderilmesi de\u011fildir. Sorgu yapan \u00e7\u00f6z\u00fcmleyicilerin eski \u00f6nbellekleri b\u0131rak\u0131p yetkili sunucudan yeni cevab\u0131 almas\u0131d\u0131r. DNS \u00e7\u00f6z\u00fcmlemesi; kay\u0131t operat\u00f6r\u00fc, yetkili nameserver ve recursive resolver katmanlar\u0131n\u0131n birlikte \u00e7al\u0131\u015fmas\u0131na dayan\u0131r.<\/p>\n<h3>Yetkili sunucu ile recursive resolver fark\u0131<\/h3>\n<p>Yetkili DNS sunucusu alan ad\u0131n\u0131n ger\u00e7ek kay\u0131tlar\u0131n\u0131 bar\u0131nd\u0131r\u0131r. Recursive resolver ise sizin bilgisayar\u0131n\u0131z veya VPS&#8217;iniz ad\u0131na DNS sorgusunu yapar; internet servis sa\u011flay\u0131c\u0131n\u0131z\u0131n resolver&#8217;\u0131, Google Public DNS ve Cloudflare Resolver bu role \u00f6rnektir.<\/p>\n<p>Bir A kayd\u0131n\u0131n TTL de\u011feri 3.600 saniyeyse resolver, ald\u0131\u011f\u0131 cevab\u0131 normal \u015fartlarda bir saate kadar saklayabilir. TTL dolmadan yeniden sorgu yap\u0131lmayabilir. DNS panelinde kay\u0131t g\u00fcncel g\u00f6r\u00fcn\u00fcrken baz\u0131 kullan\u0131c\u0131lar\u0131n eski IP&#8217;ye gitmesi bu y\u00fczden m\u00fcmk\u00fcnd\u00fcr.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131<\/strong> &#8211; De\u011fi\u015fiklikten \u00f6nce TTL de\u011ferini, yetkili nameserver&#8217;lar\u0131 ve yeni kayd\u0131n do\u011frudan cevap verip vermedi\u011fini kontrol edin.<\/p>\n<h2 id=\"dns-yayilmasi-ne-kadar-surer\">DNS yay\u0131lmas\u0131 ne kadar s\u00fcrer?<\/h2>\n<p>\u00c7o\u011fu A, AAAA veya CNAME kayd\u0131nda de\u011fi\u015fiklik birka\u00e7 dakika ile TTL s\u00fcresi aras\u0131nda farkl\u0131 a\u011flarda g\u00f6r\u00fcn\u00fcr; t\u00fcm internet kullan\u0131c\u0131lar\u0131 i\u00e7in kesin bir saat vermek m\u00fcmk\u00fcn de\u011fildir. 300 saniyelik TTL, de\u011fi\u015fikli\u011fin tam 5 dakikada herkes taraf\u0131ndan g\u00f6r\u00fclece\u011fi anlam\u0131na gelmez. Resolver sorguyu de\u011fi\u015fiklikten hemen \u00f6nce yapt\u0131ysa eski cevap TTL dolana kadar kullan\u0131labilir.<\/p>\n<table>\n<thead>\n<tr>\n<th>Durum<\/th>\n<th>Olas\u0131 g\u00f6r\u00fcn\u00fcrl\u00fck s\u00fcresi<\/th>\n<th>A\u00e7\u0131klama<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>A kayd\u0131, TTL 300<\/td>\n<td>5 dakika ve \u00fczeri<\/td>\n<td>\u00d6nbelle\u011fe alma zaman\u0131 sorgunun yap\u0131ld\u0131\u011f\u0131 ana ba\u011fl\u0131d\u0131r.<\/td>\n<\/tr>\n<tr>\n<td>A kayd\u0131, TTL 3600<\/td>\n<td>1 saate kadar<\/td>\n<td>Resolver eski cevab\u0131 TTL s\u00fcresi dolana kadar d\u00f6nd\u00fcrebilir.<\/td>\n<\/tr>\n<tr>\n<td>Nameserver de\u011fi\u015fikli\u011fi<\/td>\n<td>Birka\u00e7 saat, bazen daha uzun<\/td>\n<td>\u00dcst seviye DNS ve resolver \u00f6nbellekleri devreye girer.<\/td>\n<\/tr>\n<tr>\n<td>NXDOMAIN cevab\u0131<\/td>\n<td>SOA i\u00e7indeki negative TTL kadar<\/td>\n<td>Olmayan kay\u0131t bilgisi de \u00f6nbelle\u011fe al\u0131nabilir.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Nameserver de\u011fi\u015fiklikleri yaln\u0131zca A kayd\u0131 de\u011fi\u015ftirmekten farkl\u0131d\u0131r. Alan ad\u0131n\u0131n \u00fcst b\u00f6lgesindeki NS delegasyonu ve eski nameserver cevaplar\u0131 da devreye girdi\u011fi i\u00e7in ge\u00e7i\u015f s\u00fcresi daha de\u011fi\u015fken olabilir. D\u00fc\u015f\u00fck TTL belirlenmi\u015f olsa bile daha \u00f6nce y\u00fcksek TTL ile \u00f6nbelle\u011fe al\u0131nm\u0131\u015f cevaplar\u0131n s\u00fcresi geriye d\u00f6n\u00fck k\u0131salmaz.<\/p>\n<p>Pratikte kay\u0131t t\u00fcr\u00fcn\u00fc ve TTL de\u011ferini bilmeden saat vermek do\u011fru de\u011fildir. Normal bir kay\u0131t i\u00e7in TTL s\u00fcresini, nameserver de\u011fi\u015fikli\u011finde ise en az birka\u00e7 saatlik ge\u00e7i\u015f penceresini planlay\u0131n. 48 saat boyunca tutarl\u0131 bi\u00e7imde eski kay\u0131t g\u00f6r\u00fcl\u00fcyorsa yaln\u0131zca beklemek yerine delegasyon, DNSSEC ve resolver davran\u0131\u015f\u0131n\u0131 ara\u015ft\u0131r\u0131n.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131<\/strong> &#8211; TTL s\u00fcresini bir son tarih de\u011fil, resolver&#8217;\u0131n eski cevab\u0131 tutabilece\u011fi yakla\u015f\u0131k \u00fcst s\u0131n\u0131r olarak de\u011ferlendirin.<\/p>\n<div class=\"aiw-callout aiw-callout-tip\">\n<p class=\"aiw-callout-label\">\u0130pucu<\/p>\n<p>De\u011fi\u015fiklikten \u00f6nce ve sonra ayn\u0131 sorguyu \u00fc\u00e7 kaynaktan \u00e7al\u0131\u015ft\u0131r\u0131n: yerel resolver, 1.1.1.1 veya 8.8.8.8 ve do\u011frudan yetkili nameserver. Yetkili sunucu yeni cevab\u0131 veriyorsa sorun \u00e7o\u011funlukla \u00f6nbellek s\u00fcrecidir.<\/p>\n<\/div>\n<h2 id=\"ttl-degeri-degisikligi-nasil-etkiler\">TTL de\u011feri de\u011fi\u015fikli\u011fi nas\u0131l etkiler?<\/h2>\n<p>TTL, DNS cevab\u0131n\u0131n saniye cinsinden ne kadar s\u00fcre \u00f6nbellekte tutulabilece\u011fini bildirir. RFC 1035, DNS kaynak kay\u0131tlar\u0131ndaki TTL alan\u0131n\u0131 bu ama\u00e7la tan\u0131mlar. 300 saniye 5 dakikaya, 86.400 saniye ise 24 saate kar\u015f\u0131l\u0131k gelir.<\/p>\n<p>Planl\u0131 bir sunucu ta\u015f\u0131mas\u0131ndan \u00f6nce TTL de\u011ferini 300 veya 600 saniyeye d\u00fc\u015f\u00fcrmek ge\u00e7i\u015fi kolayla\u015ft\u0131rabilir. Fakat bu de\u011fer, ta\u015f\u0131ma ba\u015flamadan \u00f6nce resolver&#8217;lar taraf\u0131ndan g\u00f6r\u00fclmelidir. De\u011fi\u015fiklikten hemen \u00f6nce TTL&#8217;yi d\u00fc\u015f\u00fcr\u00fcrseniz baz\u0131 resolver&#8217;lar h\u00e2l\u00e2 eski, y\u00fcksek TTL&#8217;li cevab\u0131 kullan\u0131yor olabilir.<\/p>\n<pre><code>dig +noall +answer example.com A\n\ndig @1.1.1.1 +noall +answer example.com A\ndig @8.8.8.8 +noall +answer example.com A<\/code><\/pre>\n<p>\u0130lk komut yerel resolver&#8217;\u0131n cevab\u0131n\u0131 g\u00f6sterir. Sonraki iki komut farkl\u0131 public resolver&#8217;lar\u0131n cevab\u0131n\u0131 kar\u015f\u0131la\u015ft\u0131r\u0131r; sat\u0131rdaki say\u0131 kalan TTL de\u011feridir. TTL de\u011feri her sorguda yeniden y\u00fckselmiyorsa \u00f6nbelle\u011fin ya\u015fland\u0131\u011f\u0131n\u0131 g\u00f6rebilirsiniz.<\/p>\n<p>\u00c7ok d\u00fc\u015f\u00fck TTL her zaman iyi de\u011fildir. DNS sorgu say\u0131s\u0131 artar, resolver \u00f6nbellek verimlili\u011fi d\u00fc\u015fer ve yetkili DNS altyap\u0131s\u0131na daha fazla istek gelebilir. S\u0131k de\u011fi\u015fmeyen bir web sitesi i\u00e7in 3.600 saniye veya daha y\u00fcksek de\u011ferler makul olabilir; kritik ge\u00e7i\u015flerde TTL ge\u00e7ici olarak d\u00fc\u015f\u00fcr\u00fcl\u00fcp i\u015flem tamamland\u0131ktan sonra y\u00fckseltilebilir.<\/p>\n<div class=\"aiw-callout aiw-callout-warn\">\n<p class=\"aiw-callout-label\">Dikkat<\/p>\n<p>TTL de\u011ferini DNS de\u011fi\u015fikli\u011finden hemen \u00f6nce d\u00fc\u015f\u00fcrmek ge\u00e7mi\u015fte al\u0131nm\u0131\u015f cevaplar\u0131 k\u0131saltmaz. Resolver 3.600 saniyelik eski TTL ile kay\u0131t ald\u0131ysa sonradan TTL&#039;yi 300 yapmak o \u00f6nbelle\u011fi geriye d\u00f6n\u00fck temizlemez.<\/p>\n<\/div>\n<h2 id=\"dns-kaydi-degisti-neden-hala-eski-site-aciliyor\">DNS kayd\u0131 de\u011fi\u015fti, neden h\u00e2l\u00e2 eski site a\u00e7\u0131l\u0131yor?<\/h2>\n<p>Eski sitenin a\u00e7\u0131lmas\u0131 tek bir nedene i\u015faret etmez. \u00d6nce hangi katman\u0131n eski cevab\u0131 verdi\u011fini ay\u0131r\u0131n:<\/p>\n<ul>\n<li><strong>Yerel \u00f6nbellek:<\/strong> \u0130\u015fletim sistemi veya taray\u0131c\u0131 daha \u00f6nce ald\u0131\u011f\u0131 DNS cevab\u0131n\u0131 sakl\u0131yor olabilir.<\/li>\n<li><strong>\u0130SS resolver&#8217;\u0131:<\/strong> \u0130nternet servis sa\u011flay\u0131c\u0131s\u0131n\u0131n recursive resolver&#8217;\u0131 TTL dolana kadar eski IP&#8217;yi d\u00f6nd\u00fcrebilir.<\/li>\n<li><strong>Yetkili DNS:<\/strong> Paneldeki de\u011fi\u015fiklik yanl\u0131\u015f nameserver \u00fczerinde yap\u0131lm\u0131\u015f veya kay\u0131t yanl\u0131\u015f b\u00f6lgede olu\u015fturulmu\u015f olabilir.<\/li>\n<li><strong>Uygulama katman\u0131:<\/strong> Yeni IP&#8217;ye gidiliyor olsa bile HTTP y\u00f6nlendirmesi, CDN \u00f6nbelle\u011fi veya web sunucusu eski i\u00e7eri\u011fi servis ediyor olabilir.<\/li>\n<li><strong>Hosts dosyas\u0131:<\/strong> Linux&#8217;ta <code>\/etc\/hosts<\/code>, Windows&#8217;ta <code>C:\\Windows\\System32\\drivers\\etc\\hosts<\/code> dosyas\u0131 DNS&#8217;ten \u00f6nce dikkate al\u0131nabilir.<\/li>\n<\/ul>\n<p>Yaln\u0131zca taray\u0131c\u0131y\u0131 yenilemek g\u00fcvenilir test de\u011fildir. \u00d6nce alan ad\u0131n\u0131n hangi IP&#8217;ye \u00e7\u00f6z\u00fcld\u00fc\u011f\u00fcn\u00fc, sonra o IP&#8217;nin hangi HTTP cevab\u0131n\u0131 verdi\u011fini kontrol edin. Alan ad\u0131 \u00e7\u00f6z\u00fcmleme hatas\u0131 i\u00e7in <a href=\"https:\/\/www.vps.tc\/blog\/tr\/dns-probe-finished-nxdomain-hatasi-nasil-cozulur\/\">DNS_PROBE_FINISHED_NXDOMAIN Hatas\u0131 Nas\u0131l \u00c7\u00f6z\u00fcl\u00fcr?<\/a> ba\u015fl\u0131kl\u0131 i\u00e7erikteki yakla\u015f\u0131m da bu ayr\u0131m\u0131 temel al\u0131r.<\/p>\n<pre><code>dig +short NS example.com\ndig +short A example.com\ncurl -I --resolve example.com:443:203.0.113.20 https:\/\/example.com\/<\/code><\/pre>\n<p><code>dig +short NS<\/code> yetkili nameserver listesini, <code>dig +short A<\/code> ise kullan\u0131lan resolver&#8217;\u0131n IP cevab\u0131n\u0131 g\u00f6sterir. <code>curl --resolve<\/code> DNS&#8217;i ge\u00e7ici olarak atlatarak belirli IP&#8217;deki HTTPS servisini test eder. B\u00f6ylece sorunun DNS&#8217;te mi, web sunucusunda m\u0131 oldu\u011fu daha net anla\u015f\u0131l\u0131r.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131<\/strong> &#8211; Taray\u0131c\u0131daki sonucu tek ba\u015f\u0131na kan\u0131t saymay\u0131n; NS, A\/AAAA ve HTTP katmanlar\u0131n\u0131 ayr\u0131 ayr\u0131 sorgulay\u0131n.<\/p>\n<div class=\"aiw-callout aiw-callout-example\">\n<p class=\"aiw-callout-label\">\u00d6rnek<\/p>\n<p>Bir alan ad\u0131n\u0131n A kayd\u0131 yeni VPS&#039;yi, AAAA kayd\u0131 ise eski sunucuyu g\u00f6steriyorsa IPv6 destekli a\u011flardaki kullan\u0131c\u0131lar eski siteye gidebilir. Farkl\u0131 resolver&#039;larda yaln\u0131zca A kayd\u0131n\u0131 de\u011fil, AAAA kayd\u0131n\u0131 da kar\u015f\u0131la\u015ft\u0131r\u0131n.<\/p>\n<\/div>\n<h2 id=\"nameserver-degisikligi-neden-daha-uzun-surer\">Nameserver de\u011fi\u015fikli\u011fi neden daha uzun s\u00fcrer?<\/h2>\n<p>Bir A kayd\u0131n\u0131 de\u011fi\u015ftirdi\u011finizde yetkili DNS b\u00f6lgesindeki tek bir kaynak kayd\u0131 g\u00fcncellenir. Nameserver de\u011fi\u015fikli\u011finde ise alan ad\u0131n\u0131n hangi DNS sunucular\u0131ndan cevap alaca\u011f\u0131n\u0131 belirleyen delegasyon de\u011fi\u015fir. Bu bilgi, alan ad\u0131n\u0131n ba\u011fl\u0131 oldu\u011fu \u00fcst seviye kay\u0131t sisteminde ve resolver \u00f6nbelleklerinde tutulur.<\/p>\n<p>Ge\u00e7i\u015f s\u0131ras\u0131nda eski ve yeni DNS sa\u011flay\u0131c\u0131s\u0131n\u0131n ayn\u0131 kay\u0131tlar\u0131 sunmas\u0131 gerekir. Eski NS delegasyonunu g\u00f6ren bir resolver eski sa\u011flay\u0131c\u0131ya, yeni delegasyonu g\u00f6ren ba\u015fka bir resolver yeni sa\u011flay\u0131c\u0131ya gidebilir. Eski DNS b\u00f6lgesini hemen kapatmak risklidir; ge\u00e7i\u015f tamamlanana kadar eski ve yeni tarafta A, AAAA, MX, TXT ve CNAME kay\u0131tlar\u0131n\u0131 kar\u015f\u0131la\u015ft\u0131r\u0131n.<\/p>\n<p>Alan ad\u0131 ta\u015f\u0131ma s\u00fcre\u00e7lerinde yaln\u0131zca web sitesini d\u00fc\u015f\u00fcnmeyin. MX kayd\u0131 e-posta teslimini, TXT kay\u0131tlar\u0131 SPF, DKIM veya do\u011frulama ak\u0131\u015flar\u0131n\u0131, CAA kayd\u0131 ise sertifika yetkilendirmesini etkileyebilir. Nameserver ge\u00e7i\u015fi \u00f6ncesi DNS b\u00f6lgesini d\u0131\u015fa aktarmak ve kritik kay\u0131tlar\u0131 sat\u0131r sat\u0131r kontrol etmek daha g\u00fcvenlidir.<\/p>\n<p>Bir alan ad\u0131n\u0131 yeni bir sunucuya ta\u015f\u0131rken <a href=\"https:\/\/www.vps.tc\/blog\/tr\/buluta-gecis-10-adimda-tasima-plani\/\">Buluta Ge\u00e7i\u015f Rehberi: 10 Ad\u0131mda Ta\u015f\u0131ma Plan\u0131<\/a> i\u00e7indeki a\u015famal\u0131 ge\u00e7i\u015f yakla\u015f\u0131m\u0131 uygulanabilir: \u00f6nce yeni altyap\u0131y\u0131 haz\u0131rlay\u0131n, d\u00fc\u015f\u00fck riskli testler yap\u0131n ve DNS de\u011fi\u015fikli\u011fini planl\u0131 bak\u0131m penceresinde ger\u00e7ekle\u015ftirin.<\/p>\n<div class=\"aiw-callout aiw-callout-field\">\n<p class=\"aiw-callout-label\">Sahadan not<\/p>\n<p>Bir gece yanl\u0131\u015f sunucuda silme komutunu \u00e7al\u0131\u015ft\u0131rmak \u00fczereydim. Tab&#039;a bast\u0131\u011f\u0131mda prompt&#039;ta bekledi\u011fim hostname yerine ba\u015fka makinenin ad\u0131 g\u00f6r\u00fcnd\u00fc; komutu durdurup hostname ve IP&#039;yi do\u011frulad\u0131m. O g\u00fcnden beri DNS sorgusu veya de\u011fi\u015fikli\u011fi yapmadan \u00f6nce hedef sistemi iki ayr\u0131 komutla kontrol ediyorum.<\/p>\n<\/div>\n<h2 id=\"dns-yayilmasini-nasil-kontrol-edebilirsiniz\">DNS yay\u0131lmas\u0131n\u0131 nas\u0131l kontrol edebilirsiniz?<\/h2>\n<p>Tek bir \u00e7evrim i\u00e7i DNS kontrol sitesine g\u00fcvenmek yerine farkl\u0131 resolver&#8217;lar\u0131 do\u011frudan sorgulay\u0131n. Her ara\u00e7 ayn\u0131 resolver havuzunu kullanmayabilir; baz\u0131 ara\u00e7lar sonucu birka\u00e7 dakika \u00f6nbellekte tutabilir.<\/p>\n<pre><code>dig @1.1.1.1 example.com A +noall +answer\ndig @8.8.8.8 example.com A +noall +answer\ndig @9.9.9.9 example.com A +noall +answer\n\ndig +trace example.com A<\/code><\/pre>\n<p>\u0130lk \u00fc\u00e7 sorgu farkl\u0131 recursive resolver&#8217;lar\u0131 kar\u015f\u0131la\u015ft\u0131r\u0131r. <code>+trace<\/code> k\u00f6k sunuculardan ba\u015flayarak delegasyon zincirini izler; yerel resolver \u00f6nbelle\u011fini do\u011frudan \u00f6l\u00e7mez, fakat yetkili sunucuya giden yolda sorun olup olmad\u0131\u011f\u0131n\u0131 anlamaya yard\u0131mc\u0131 olur.<\/p>\n<p>Yetkili sunucuyu ayr\u0131ca sorgulay\u0131n. \u00d6nce NS listesini al\u0131n, ard\u0131ndan listelenen sunuculardan birine do\u011frudan sorun:<\/p>\n<pre><code>dig +short NS example.com\ndig @ns1.example-dns.com example.com A +noall +answer<\/code><\/pre>\n<p>Yetkili sunucu yeni IP&#8217;yi veriyor, fakat public resolver eski IP&#8217;yi d\u00f6nd\u00fcr\u00fcyorsa de\u011fi\u015fiklik b\u00fcy\u00fck ihtimalle \u00f6nbellek s\u00fcrecindedir. Yetkili sunucu da eski IP&#8217;yi veriyorsa panelde yanl\u0131\u015f b\u00f6lge d\u00fczenlenmi\u015f, kay\u0131t kaydedilmemi\u015f veya DNS sa\u011flay\u0131c\u0131s\u0131 beklenenden farkl\u0131 olabilir.<\/p>\n<p>IPv6 kayd\u0131 da kontrol edilmelidir. A kayd\u0131 yeni sunucuyu, AAAA kayd\u0131 eski sunucuyu g\u00f6steriyorsa IPv6 kullanan istemciler farkl\u0131 bir hedefe gidebilir. Baz\u0131 a\u011flarda g\u00f6r\u00fclen bu durum yanl\u0131\u015f bi\u00e7imde DNS yay\u0131lmas\u0131 sorunu san\u0131labilir.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131<\/strong> &#8211; A ve AAAA kay\u0131tlar\u0131n\u0131 en az iki public resolver ile ve do\u011frudan yetkili nameserver \u00fczerinden kar\u015f\u0131la\u015ft\u0131r\u0131n.<\/p>\n<h2 id=\"dnssec-negatif-onbellek-ve-diger-istisnalar\">DNSSEC, negatif \u00f6nbellek ve di\u011fer istisnalar<\/h2>\n<p>DNSSEC etkin bir alan ad\u0131nda kay\u0131t imzalar\u0131 ve DS bilgileri de uyumlu olmal\u0131d\u0131r. Nameserver de\u011fi\u015fikli\u011fi s\u0131ras\u0131nda eski DS kayd\u0131 ile yeni DNS b\u00f6lgesinin imzalar\u0131 e\u015fle\u015fmezse baz\u0131 resolver&#8217;lar cevab\u0131 do\u011frulayamaz ve <code>SERVFAIL<\/code> d\u00f6nd\u00fcrebilir. Bu, s\u0131radan TTL beklemesinden farkl\u0131d\u0131r.<\/p>\n<p>Bir kay\u0131t mevcut de\u011filken al\u0131nan <code>NXDOMAIN<\/code> cevab\u0131 da \u00f6nbelle\u011fe al\u0131nabilir. RFC 2308, negatif cevaplar\u0131n \u00f6nbelleklenmesinde SOA kayd\u0131ndaki de\u011ferlerin kullan\u0131lmas\u0131n\u0131 tan\u0131mlar. \u00d6nce olmayan bir alt alan ad\u0131n\u0131 sorgulay\u0131p k\u0131sa s\u00fcre sonra bu ad\u0131 olu\u015fturduysan\u0131z, baz\u0131 resolver&#8217;lar kay\u0131t eklenmesine ra\u011fmen bir s\u00fcre daha NXDOMAIN d\u00f6nd\u00fcrebilir.<\/p>\n<pre><code>dig example.com SOA +noall +answer\ndig example.com DNSKEY +dnssec +noall +answer\ndig example.com A +dnssec +noall +answer<\/code><\/pre>\n<p>SOA cevab\u0131ndaki serial de\u011feri DNS b\u00f6lgesinin s\u00fcr\u00fcm\u00fcn\u00fc, minimum TTL ve di\u011fer alanlar ise b\u00f6lge davran\u0131\u015f\u0131n\u0131 de\u011ferlendirmeye yard\u0131mc\u0131 olur. DNSSEC sorgusunda <code>RRSIG<\/code> ve ilgili do\u011frulama kay\u0131tlar\u0131 g\u00f6r\u00fclebilir; sonu\u00e7 <code>SERVFAIL<\/code> ise DNSSEC zinciri ayr\u0131ca incelenmelidir.<\/p>\n<p>CDN kullan\u0131l\u0131yorsa iki ayr\u0131 \u00f6nbellek katman\u0131 bulunur: DNS cevab\u0131 ve CDN&#8217;in HTTP i\u00e7eri\u011fi. DNS yeni IP&#8217;yi g\u00f6sterse bile CDN, <code>Cache-Control<\/code> veya kendi cache s\u00fcresi nedeniyle eski i\u00e7eri\u011fi servis edebilir. <a href=\"https:\/\/www.vps.tc\/blog\/tr\/cdn-nedir-web-sitesini-nasil-hizlandirir\/\">CDN Nedir? Web Sitesini Nas\u0131l H\u0131zland\u0131r\u0131r?<\/a> ba\u015fl\u0131kl\u0131 i\u00e7erikte a\u00e7\u0131klanan edge \u00f6nbelle\u011fi ile DNS \u00f6nbelle\u011fini birbirine kar\u0131\u015ft\u0131rmay\u0131n.<\/p>\n<h2 id=\"tasima-oncesi-ve-sonrasi-uygulanacak-yontem\">Ta\u015f\u0131ma \u00f6ncesi ve sonras\u0131 uygulanacak y\u00f6ntem<\/h2>\n<h3>De\u011fi\u015fiklikten \u00f6nce<\/h3>\n<ol>\n<li>Mevcut A, AAAA, CNAME, MX, TXT, CAA ve NS kay\u0131tlar\u0131n\u0131 d\u0131\u015fa aktar\u0131n.<\/li>\n<li>Yetkili nameserver listesini <code>dig +short NS alanadiniz.tld<\/code> ile do\u011frulay\u0131n.<\/li>\n<li>Yeni sunucuda web, e-posta, TLS ve uygulama eri\u015fimini do\u011frudan IP veya ge\u00e7ici hostname ile test edin.<\/li>\n<li>Planl\u0131 ge\u00e7i\u015ften \u00f6nce kritik kay\u0131tlar\u0131n TTL de\u011ferlerini uygun \u015fekilde d\u00fc\u015f\u00fcr\u00fcn.<\/li>\n<\/ol>\n<h3>De\u011fi\u015fiklikten sonra<\/h3>\n<ol>\n<li>Yetkili DNS sunucusundan yeni cevab\u0131 kontrol edin.<\/li>\n<li>1.1.1.1, 8.8.8.8 ve yerel resolver gibi farkl\u0131 kaynaklar\u0131 kar\u015f\u0131la\u015ft\u0131r\u0131n.<\/li>\n<li>A ve AAAA kay\u0131tlar\u0131n\u0131n ayn\u0131 ge\u00e7i\u015f plan\u0131na uydu\u011fundan emin olun.<\/li>\n<li>E-posta, do\u011frulama TXT kay\u0131tlar\u0131 ve CDN davran\u0131\u015f\u0131n\u0131 ayr\u0131ca test edin.<\/li>\n<\/ol>\n<p>Bir web sunucusunu DNS de\u011fi\u015fiminden \u00f6nce haz\u0131rlamak i\u00e7in <a href=\"https:\/\/www.vps.tc\/blog\/tr\/ubuntu-nginx-kurulumu-ilk-yapilandirma\/\">Ubuntu&#8217;da Nginx Kurulumu ve \u0130lk Yap\u0131land\u0131rma<\/a> rehberindeki temel sanal host ve TLS kontrolleri kullan\u0131labilir. DNS do\u011fru IP&#8217;yi g\u00f6sterse bile Nginx&#8217;te yanl\u0131\u015f <code>server_name<\/code> tan\u0131m\u0131 varsa istemci beklenmeyen siteyi g\u00f6rebilir.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131<\/strong> &#8211; Eski DNS sa\u011flay\u0131c\u0131s\u0131n\u0131, e-posta kay\u0131tlar\u0131n\u0131 ve izleme kontrollerini ge\u00e7i\u015ften hemen sonra silmeyin; en az bir tam TTL d\u00f6ng\u00fcs\u00fc boyunca g\u00f6zlemleyin.<\/p>\n<h2 id=\"dns-degisikliginden-once-ve-sonra-kontrol-edin\">DNS De\u011fi\u015fikli\u011finden \u00d6nce ve Sonra Kontrol Edin<\/h2>\n<ul class=\"aiw-checklist\">\n<li>Mevcut DNS b\u00f6lgesindeki A, AAAA, MX, TXT, CAA ve CNAME kay\u0131tlar\u0131n\u0131 d\u0131\u015fa aktar\u0131n.<\/li>\n<li>Yetkili nameserver listesini dig ile do\u011frulay\u0131n.<\/li>\n<li>Ta\u015f\u0131ma \u00f6ncesinde kritik kay\u0131tlar\u0131n TTL de\u011ferlerini kontrol edin.<\/li>\n<li>Yeni sunucuyu DNS de\u011fi\u015fikli\u011finden \u00f6nce do\u011frudan IP \u00fczerinden test edin.<\/li>\n<li>De\u011fi\u015fiklikten sonra en az iki public resolver&#039;\u0131 kar\u015f\u0131la\u015ft\u0131r\u0131n.<\/li>\n<li>A ve AAAA kay\u0131tlar\u0131n\u0131n ayn\u0131 hedefe veya planlanan hedeflere gitti\u011fini do\u011frulay\u0131n.<\/li>\n<li>DNSSEC, e-posta, CDN ve TLS kontrollerini ayr\u0131 ayr\u0131 tamamlay\u0131n.<\/li>\n<\/ul>\n<div class=\"aiw-cta\">\n<p>Bir sonraki DNS de\u011fi\u015fikli\u011finizden \u00f6nce mevcut kay\u0131tlar\u0131 ve TTL de\u011ferlerini d\u0131\u015fa aktar\u0131n. De\u011fi\u015fiklik sonras\u0131nda tek bir taray\u0131c\u0131 yerine birka\u00e7 resolver ve yetkili nameserver ile \u00f6l\u00e7\u00fcm yap\u0131n.<\/p>\n<p class=\"aiw-cta-action\"><a href=\"https:\/\/www.vps.tc\/tr\/vps\">VPS paketlerini inceleyin<\/a><\/p>\n<\/div>\n<p>DNS yay\u0131lmas\u0131n\u0131 de\u011ferlendirirken domain ile URL kavramlar\u0131n\u0131 kar\u0131\u015ft\u0131rmamak \u00f6nemli; ben bu iki terimin fark\u0131n\u0131 \u00f6rneklerle a\u00e7\u0131klad\u0131\u011f\u0131m <a href=\"https:\/\/www.vps.tc\/blog\/tr\/domain-ve-url-farki\/\">Domain ve URL fark\u0131<\/a> rehberine de g\u00f6z atman\u0131z\u0131 \u00f6neririm.<\/p>\n<h2 id=\"sik-sorulan-sorular\">S\u0131k Sorulan Sorular<\/h2>\n<div class=\"aiw-faq\">\n<details class=\"aiw-faq-item\" open>\n<summary>DNS yay\u0131lmas\u0131 tam olarak ka\u00e7 saat s\u00fcrer?<\/summary>\n<p>Sabit bir saat yoktur. A veya CNAME kayd\u0131nda s\u00fcre \u00e7o\u011funlukla kayd\u0131n TTL de\u011feriyle ili\u015fkilidir; 300 saniyelik TTL i\u00e7in birka\u00e7 dakika, 3.600 saniyelik TTL i\u00e7in bir saate kadar beklemek gerekebilir. Nameserver delegasyonu, negatif \u00f6nbellek veya DNSSEC devredeyse ge\u00e7i\u015f birka\u00e7 saat s\u00fcrebilir. 24-48 saat sonra h\u00e2l\u00e2 tutars\u0131zl\u0131k varsa delegasyon ve kay\u0131tlar\u0131 inceleyin.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>DNS yay\u0131lmas\u0131n\u0131 h\u0131zland\u0131rmak m\u00fcmk\u00fcn m\u00fc?<\/summary>\n<p>Ge\u00e7mi\u015fte resolver&#039;lar\u0131n ald\u0131\u011f\u0131 kay\u0131tlar\u0131 zorla h\u0131zland\u0131rmak m\u00fcmk\u00fcn de\u011fildir. Gelecekteki ge\u00e7i\u015fler i\u00e7in TTL de\u011ferini de\u011fi\u015fiklikten \u00f6nce d\u00fc\u015f\u00fcrmek, eski ve yeni DNS sunucular\u0131nda ayn\u0131 kay\u0131tlar\u0131 tutmak ve DNSSEC zincirini \u00f6nceden do\u011frulamak yard\u0131mc\u0131 olur. Yerel DNS cache temizlemek yaln\u0131zca tek cihaz\u0131 etkiler; internet \u00fczerindeki resolver \u00f6nbelleklerini temizlemez.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>DNS de\u011fi\u015fti\u011fi halde eski site neden a\u00e7\u0131l\u0131yor?<\/summary>\n<p>Eski site; yerel cache, \u0130SS resolver&#039;\u0131, eski TTL, AAAA kayd\u0131, CDN \u00f6nbelle\u011fi veya yanl\u0131\u015f nameserver \u00fczerinde yap\u0131lan de\u011fi\u015fiklik nedeniyle a\u00e7\u0131labilir. dig +short A alanadiniz.tld ve dig +short AAAA alanadiniz.tld ile hedefleri kontrol edin. Ard\u0131ndan public resolver&#039;lar\u0131 ve yetkili nameserver&#039;\u0131 ayr\u0131 ayr\u0131 sorgulay\u0131n.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>TTL 300 yapmak DNS&#039;i 5 dakikada yayar m\u0131?<\/summary>\n<p>Hay\u0131r. TTL 300, resolver&#039;\u0131n yeni ald\u0131\u011f\u0131 cevab\u0131 normal \u015fartlarda en fazla 300 saniye saklamas\u0131n\u0131 belirtir. Resolver de\u011fi\u015fiklikten \u00f6nce kayd\u0131 y\u00fcksek TTL ile ald\u0131ysa eski cevap o s\u00fcrenin tamam\u0131nda kullan\u0131labilir. Nameserver delegasyonu, negatif cache ve CDN katman\u0131 TTL&#039;den ba\u011f\u0131ms\u0131z ek gecikmeler olu\u015fturabilir.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>DNS yay\u0131lmas\u0131n\u0131 hangi komutla kontrol edebilirim?<\/summary>\n<p>Linux ve macOS&#039;ta dig kullanabilirsiniz: dig @1.1.1.1 example.com A +noall +answer. Ayn\u0131 sorguyu @8.8.8.8 ile tekrarlay\u0131n ve yetkili nameserver&#039;\u0131 ayr\u0131ca sorgulay\u0131n. Cevap sat\u0131r\u0131ndaki TTL de\u011ferini, IP adresini ve sorgu yap\u0131lan sunucuyu kar\u015f\u0131la\u015ft\u0131r\u0131n; tek bir \u00e7evrim i\u00e7i kontrol arac\u0131na dayanmay\u0131n.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>Nameserver de\u011fi\u015fikli\u011fi neden A kayd\u0131 de\u011fi\u015fikli\u011finden uzun s\u00fcrer?<\/summary>\n<p>A kayd\u0131 de\u011fi\u015fikli\u011finde yetkili DNS b\u00f6lgesindeki tek bir cevap g\u00fcncellenir. Nameserver de\u011fi\u015fikli\u011finde alan ad\u0131n\u0131n hangi sunuculara sorulaca\u011f\u0131n\u0131 belirleyen delegasyon da de\u011fi\u015fir. \u00dcst seviye kay\u0131tlar, recursive resolver \u00f6nbellekleri ve eski DNS sa\u011flay\u0131c\u0131s\u0131 ayn\u0131 ge\u00e7i\u015fte rol oynar. Bu nedenle eski ve yeni nameserver&#039;lar\u0131 ge\u00e7i\u015f tamamlanana kadar \u00e7al\u0131\u015f\u0131r durumda tutmak gerekir.<\/p>\n<\/details>\n<\/div>\n<h2 id=\"kaynaklar\">Kaynaklar<\/h2>\n<ul class=\"aiw-sources\">\n<li><a href=\"https:\/\/icann.org\/\" target=\"_blank\" rel=\"noopener\">ICANN &#8211; Domain Name System<\/a> \u2014 icann.org<\/li>\n<li><a href=\"https:\/\/www.rfc-editor.org\/rfc\/rfc1035\" target=\"_blank\" rel=\"noopener\">RFC 1035 &#8211; Domain Names: Implementation and Specification<\/a> \u2014 rfc-editor.org<\/li>\n<li><a href=\"https:\/\/www.rfc-editor.org\/rfc\/rfc2308\" target=\"_blank\" rel=\"noopener\">RFC 2308 &#8211; Negative Caching of DNS Queries<\/a> \u2014 rfc-editor.org<\/li>\n<li><a href=\"https:\/\/www.rfc-editor.org\/rfc\/rfc4033\" target=\"_blank\" rel=\"noopener\">RFC 4033 &#8211; DNS Security Introduction and Requirements<\/a> \u2014 rfc-editor.org<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>DNS yay\u0131lmas\u0131 \u00e7o\u011fu kay\u0131tta TTL s\u00fcresi i\u00e7inde ger\u00e7ekle\u015fir; nameserver de\u011fi\u015fiklikleri, negatif \u00f6nbellek ve DNSSEC ge\u00e7i\u015fi uzatabilir. Farkl\u0131 resolver&#8217;lar\u0131 dig ile kar\u015f\u0131la\u015ft\u0131rarak sorunun ger\u00e7ekten \u00f6nbellek kaynakl\u0131 olup olmad\u0131\u011f\u0131n\u0131 anlayabilirsiniz.<\/p>\n","protected":false},"author":2,"featured_media":986,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[111],"tags":[],"class_list":["post-988","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-domain"],"lang":"tr","translations":{"tr":988,"en":989},"pll_sync_post":[],"_links":{"self":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/988","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/comments?post=988"}],"version-history":[{"count":2,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/988\/revisions"}],"predecessor-version":[{"id":1027,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/988\/revisions\/1027"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/media\/986"}],"wp:attachment":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/media?parent=988"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/categories?post=988"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/tags?post=988"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}