{"id":57,"date":"2026-06-15T22:16:01","date_gmt":"2026-06-15T19:16:01","guid":{"rendered":"https:\/\/secradar.net\/blog\/dns-cozumleme-nasil-calisir-dns-trace\/"},"modified":"2026-06-15T22:16:01","modified_gmt":"2026-06-15T19:16:01","slug":"dns-cozumleme-nasil-calisir-dns-trace","status":"publish","type":"post","link":"https:\/\/secradar.net\/blog\/dns-cozumleme-nasil-calisir-dns-trace\/","title":{"rendered":"DNS \u00c7\u00f6z\u00fcmleme Nas\u0131l \u00c7al\u0131\u015f\u0131r? K\u00f6k Sunucudan Yetkiliye (DNS Trace)"},"content":{"rendered":"

Taray\u0131c\u0131n\u0131za example.com<\/code> yazd\u0131\u011f\u0131n\u0131z an, arka planda saniyeler i\u00e7inde tamamlanan \u00e7ok ad\u0131ml\u0131 bir yolculuk ba\u015flar. Bilgisayar\u0131n\u0131z bu alan ad\u0131n\u0131n hangi IP adresine ait oldu\u011funu do\u011frudan bilmez; bunu \u00f6\u011frenmek i\u00e7in DNS \u00e7\u00f6z\u00fcmleme<\/strong> (DNS resolution) ad\u0131 verilen, k\u00f6k sunuculardan ba\u015flay\u0131p yetkili name server’a kadar inen bir sorgu zinciri i\u015fletilir. Bu yaz\u0131da o zinciri ad\u0131m ad\u0131m, dig +trace mant\u0131\u011f\u0131yla a\u00e7\u0131kl\u0131yoruz.<\/p>\n

DNS \u00c7\u00f6z\u00fcmleme Ad\u0131m Ad\u0131m<\/h2>\n

Bir alan ad\u0131n\u0131n IP adresine \u00e7evrilmesi tipik olarak \u015fu s\u0131rayla ger\u00e7ekle\u015fir:<\/p>\n

    \n
  1. \u00c7\u00f6z\u00fcmleyici (resolver):<\/strong> \u0130ste\u011finiz \u00f6nce bir \u00f6zyineli \u00e7\u00f6z\u00fcmleyiciye (genelde ISP’niz ya da 1.1.1.1 \/ 8.8.8.8) gider. Cevap \u00f6nbelle\u011finde varsa an\u0131nda d\u00f6ner; yoksa \u00e7\u00f6z\u00fcmleyici sizin ad\u0131n\u0131za ara\u015ft\u0131rmaya ba\u015flar.<\/li>\n
  2. K\u00f6k (root) sunucular:<\/strong> \u00c7\u00f6z\u00fcmleyici, “.com<\/code> uzant\u0131s\u0131na kim bak\u0131yor?” diye k\u00f6k sunuculara sorar. K\u00f6k sunucu cevab\u0131 bilmez ama do\u011fru TLD sunucular\u0131n\u0131 i\u015faret eder (delegasyon).<\/li>\n
  3. TLD sunucular\u0131:<\/strong> .com<\/code> sunucular\u0131, “example.com<\/code>‘un yetkili name server’lar\u0131 \u015funlar” diyerek bir ad\u0131m daha y\u00f6nlendirir.<\/li>\n
  4. Yetkili (authoritative) sunucu:<\/strong> Alan ad\u0131n\u0131n ger\u00e7ek kay\u0131tlar\u0131n\u0131 tutan sunucu nihai cevab\u0131 (\u00f6r. A kayd\u0131 = IP adresi) d\u00f6ner.<\/li>\n<\/ol>\n

    Her ad\u0131m bir \u00f6ncekini daha dar bir alana delege eder<\/em>; bu y\u00fczden s\u00fcrece “delegasyon zinciri” denir.<\/p>\n

    K\u00f6k (Root) Sunucular Nedir?<\/h2>\n

    \u0130nternetin DNS hiyerar\u015fisinin tepesinde, d\u00fcnya genelinde anycast ile da\u011f\u0131t\u0131lm\u0131\u015f 13 mant\u0131ksal k\u00f6k sunucu k\u00fcmesi (a.root-servers.net \u2026 m.root-servers.net) bulunur. K\u00f6k sunucular tek tek alan adlar\u0131n\u0131 bilmez; g\u00f6revleri yaln\u0131zca \u00fcst d\u00fczey uzant\u0131lar\u0131n (TLD) yetkili sunucular\u0131n\u0131 i\u015faret etmektir. \u00c7\u00f6z\u00fcmleme her zaman buradan ba\u015flar.<\/p>\n

    TLD Sunucular\u0131 ve Delegasyon<\/h2>\n

    TLD (Top-Level Domain) sunucular\u0131 .com<\/code>, .net<\/code>, .org<\/code> ya da .com.tr<\/code> gibi uzant\u0131lar\u0131 y\u00f6netir. Bir alan ad\u0131 tescil edildi\u011finde, kaydedici firma o alan ad\u0131n\u0131n NS (name server) kay\u0131tlar\u0131n\u0131<\/strong> TLD’ye bildirir. B\u00f6ylece TLD sunucusu, gelen sorguyu alan ad\u0131n\u0131n yetkili sunucular\u0131na y\u00f6nlendirebilir. NS kay\u0131tlar\u0131 yanl\u0131\u015f ya da eksikse zincir burada kopar. (NS dahil t\u00fcm kay\u0131t tiplerini DNS Kay\u0131t Tipleri rehberimizde<\/a> inceleyebilirsiniz.)<\/p>\n

    Yetkili Sunucu ve Nihai Cevap<\/h2>\n

    Zincirin sonunda, alan ad\u0131n\u0131n kay\u0131tlar\u0131n\u0131 ger\u00e7ekten bar\u0131nd\u0131ran yetkili name server gelir. \u0130stedi\u011finiz kay\u0131t tipi (A, AAAA, MX, TXT\u2026) burada tan\u0131ml\u0131ysa cevap d\u00f6ner; tan\u0131ml\u0131 de\u011filse “kay\u0131t yok” (NODATA) yan\u0131t\u0131 al\u0131n\u0131r. Alan ad\u0131 hi\u00e7 yoksa NXDOMAIN<\/code> d\u00f6ner.<\/p>\n

    dig +trace ve DNS Trace Arac\u0131<\/h2>\n

    Sistem y\u00f6neticileri bu zinciri g\u00f6rmek i\u00e7in klasik olarak dig +trace example.com<\/code> komutunu kullan\u0131r. Bu komut, sizin yerinize \u00f6zyinelemeyi kendisi y\u00fcr\u00fct\u00fcr<\/strong> ve her hop’u (k\u00f6k \u2192 TLD \u2192 yetkili) tek tek g\u00f6sterir; b\u00f6ylece zincirin nerede koptu\u011funu anlars\u0131n\u0131z. \u00d6nemli bir ayr\u0131m: bu i\u015flem bir DNS yay\u0131l\u0131m (propagation) kontrol\u00fc<\/em> de\u011fildir. Yay\u0131l\u0131m kontrol\u00fc bir kayd\u0131n d\u00fcnya genelindeki \u00e7\u00f6z\u00fcmleyicilere ne kadar yay\u0131ld\u0131\u011f\u0131na bakar; DNS Trace ise tek bir \u00e7\u00f6z\u00fcmleme yolunu k\u00f6k sunucudan itibaren izler.<\/p>\n

    Komut sat\u0131r\u0131na ihtiya\u00e7 duymadan ayn\u0131 izi taray\u0131c\u0131dan g\u00f6rmek i\u00e7in SecRadar DNS Trace arac\u0131n\u0131<\/a> kullanabilirsiniz. Ara\u00e7, \u00e7\u00f6z\u00fcmlemeyi k\u00f6k sunuculardan ba\u015flat\u0131r ve her delegasyon ad\u0131m\u0131n\u0131 \u2014 hangi sunucu, IP’si, ge\u00e7en s\u00fcre ve d\u00f6nen yan\u0131t \u2014 ger\u00e7ekle\u015ftik\u00e7e canl\u0131 olarak ekrana d\u00f6ker.<\/p>\n

    Ne Zaman \u0130\u015finize Yarar?<\/h2>\n