{"id":52,"title":"Windows Client DNS S\u0131ralamas\u0131: Ger\u00e7ekten S\u0131ral\u0131 m\u0131 \u00c7al\u0131\u015f\u0131r?","content":"DNS (Domain Name System) \u00e7\u00f6z\u00fcmlemesi, modern bilgisayar a\u011flar\u0131n\u0131n en kritik bile\u015fenlerinden biridir. Her g\u00fcn milyarlarca DNS sorgusu yap\u0131l\u0131rken, Windows istemcilerinin bu sorgular\u0131 nas\u0131l i\u015fledi\u011fi ve DNS sunucular\u0131n\u0131 hangi s\u0131rayla kulland\u0131\u011f\u0131 konusu hem sistem y\u00f6neticileri hem de a\u011f uzmanlar\u0131 i\u00e7in kritik \u00f6neme sahiptir. Bu yaz\u0131da, Windows DNS istemcisinin davran\u0131\u015f\u0131n\u0131 derinlemesine inceleyece\u011fiz.

Windows DNS \u0130stemci Davran\u0131\u015f\u0131n\u0131n Tarihsel Geli\u015fimi<\/h2>

Windows XP - Windows 7 D\u00f6nemi: Basit S\u0131ral\u0131 Yakla\u015f\u0131m<\/h3> Windows'un \u00f6nceki s\u00fcr\u00fcmlerinde DNS \u00e7\u00f6z\u00fcmleme olduk\u00e7a basit bir mant\u0131\u011fa sahipti. DNS \u0130stemci Servisi (DNS Client Service), yap\u0131land\u0131r\u0131lan DNS sunucular\u0131n\u0131 belirli bir s\u0131rayla sorguluyordu. Temel \u00c7al\u0131\u015fma Prensibi:<\/strong>
  1. \u0130stemci, tercih edilen a\u011f adapt\u00f6r\u00fcn\u00fcn DNS listesindeki ilk DNS sunucusuna sorgu g\u00f6nderir<\/li>
  2. 1 saniye i\u00e7inde yan\u0131t alamazsa, ayn\u0131 adapt\u00f6rdeki ikinci DNS sunucusunu ve di\u011fer aktif adapt\u00f6rlerdeki ilk DNS sunucular\u0131n\u0131 sorgular<\/li>
  3. Bu s\u00fcre\u00e7, yan\u0131t al\u0131nana kadar artan zaman aral\u0131klar\u0131yla devam eder<\/li> <\/ol>

    Windows 10 ve Sonras\u0131: Paralel DNS Sorgular\u0131<\/h3> Windows 10 ile birlikte DNS \u00e7\u00f6z\u00fcmleme mekanizmas\u0131 k\u00f6kl\u00fc bir de\u011fi\u015fime u\u011frad\u0131. Microsoft, performans\u0131 art\u0131rmak i\u00e7in \"Smart Multi-Homed Name Resolution\" \u00f6zelli\u011fini tan\u0131tt\u0131. Yeni Yakla\u015f\u0131m:<\/strong>
    • DNS sorgular\u0131 paralel olarak g\u00f6nderilir<\/li>
    • \u0130lk yan\u0131t veren sunucunun cevab\u0131 kabul edilir<\/li>
    • LLMNR (Link-Local Multicast Name Resolution) ve NetBIOS sorgular\u0131 da paralel \u00e7al\u0131\u015f\u0131r<\/li> <\/ul>

      DNS Sunucu \u00d6ncelik Belirleme Mekanizmalar\u0131<\/h2>

      1. Interface Metric (Aray\u00fcz Metri\u011fi)<\/h3> Windows 10 ve sonraki s\u00fcr\u00fcmlerde, DNS \u00f6nceli\u011fi interface metric<\/strong> de\u011feri ile belirlenir:
      • En d\u00fc\u015f\u00fck metric de\u011feri = En y\u00fcksek \u00f6ncelik<\/strong><\/li>
      • Her a\u011f adapt\u00f6r\u00fc i\u00e7in IPv4 ve IPv6 i\u00e7in ayr\u0131 metric de\u011ferleri bulunur<\/li>
      • DNS \u00f6nceli\u011fi i\u00e7in bu iki de\u011ferden en d\u00fc\u015f\u00fck olan\u0131 dikkate al\u0131n\u0131r<\/li> <\/ul> PowerShell ile Interface Metric Ayarlama:<\/strong> 
        Set-NetIPInterface -InterfaceAlias \"Ethernet\" -AddressFamily IPv4 -InterfaceMetric 10 Set-NetIPInterface -InterfaceAlias \"Wi-Fi\" -AddressFamily IPv4 -InterfaceMetric 20 <\/code><\/pre> 
        2. DNS Sunucu Listesi \u0130\u00e7indeki S\u0131ralama<\/h3> Ayn\u0131 a\u011f adapt\u00f6r\u00fc \u00fczerinde birden fazla DNS sunucusu tan\u0131mland\u0131\u011f\u0131nda: IPv6 \u00d6nceli\u011fi:<\/strong> Ayn\u0131 adapt\u00f6r i\u00e7inde IPv6 DNS sunucular\u0131 IPv4'ten \u00f6nce sorgulan\u0131r Sunucu S\u0131ralamas\u0131:<\/strong> DNS sunucular\u0131, TCP\/IP \u00f6zelliklerinde belirtilen s\u0131rayla sorgulan\u0131r 
        Timeout ve Yedekleme Davran\u0131\u015f\u0131<\/h2> 
        Tek DNS Sunucusu Senaryosu<\/h3> Yaln\u0131zca bir DNS sunucusu yap\u0131land\u0131r\u0131ld\u0131\u011f\u0131nda: 
           
        • \u0130stemci ayn\u0131 sunucuya 5 kez sorgu g\u00f6nderir<\/li> 
        • Her sorguda timeout s\u00fcresi artar (1, 2, 4, 8, 16 saniye)<\/li> 
        • NXDOMAIN yan\u0131t\u0131 al\u0131rsa s\u00fcre\u00e7 durur<\/li> <\/ul> 
          Birden Fazla DNS Sunucusu Senaryosu<\/h3> Birden fazla DNS sunucusu yap\u0131land\u0131r\u0131ld\u0131\u011f\u0131nda: 
             
          • \u0130lk 3 sunucu 1'er saniye aral\u0131klarla sorgulan\u0131r<\/li> 
          •  
               
            1. ve sonraki sunucular en az 4 saniye gecikmeyle sorgulan\u0131r<\/li> <\/ol> <\/li> 
            2. \u00d6nemli:<\/strong> NXDOMAIN yan\u0131t\u0131 al\u0131nd\u0131\u011f\u0131nda di\u011fer sunucular denenmez<\/li> <\/ul> 
              Multi-Homed Sistemlerde DNS Davran\u0131\u015f\u0131<\/h2> 
              A\u011f Adapt\u00f6r\u00fc \u00d6ncelikleri<\/h3> Birden fazla aktif a\u011f adapt\u00f6r\u00fc olan sistemlerde: 
                 
              1. Interface Metric<\/strong> de\u011feri en d\u00fc\u015f\u00fck olan adapt\u00f6r \u00f6nceliklidir<\/li> 
              2. Windows 10 \u00f6ncesi s\u00fcr\u00fcmlerde NIC Binding Order<\/strong> belirleyiciydi<\/li> 
              3. VPN ba\u011flant\u0131lar\u0131 genellikle en d\u00fc\u015f\u00fck metric de\u011ferine sahiptir<\/li> <\/ol> 
                Smart Name Resolution Problemi<\/h3> Windows 10'daki ak\u0131ll\u0131 isim \u00e7\u00f6z\u00fcmleme bazen beklenmedik sonu\u00e7lar do\u011furabilir: Sorunlar:<\/strong> 
                   
                • VPN DNS'i g\u00fcvenilir \u015fekilde kullan\u0131lmayabilir<\/li> 
                • DNS s\u0131z\u0131nt\u0131lar\u0131 (DNS leaks) olu\u015fabilir<\/li> 
                • Split-DNS yap\u0131land\u0131rmalar\u0131 d\u00fczg\u00fcn \u00e7al\u0131\u015fmayabilir<\/li> <\/ul> \u00c7\u00f6z\u00fcm - Registry D\u00fczenlemeleri:<\/strong> 
                   \"DisableSmartNameResolution\"=dword:00000001 \"DisableParallelAandAAAA\"=dword:00000001 <\/code><\/pre> 
                  Ger\u00e7ek Hayat Senaryolar\u0131 ve Sorun Giderme<\/h2> 
                  Senaryo 1: Yava\u015f DNS \u00c7\u00f6z\u00fcmleme<\/h3> Problem:<\/strong> \u0130nternet eri\u015fimi olan ikinci adapt\u00f6rde DNS sorgular\u0131 10+ saniye s\u00fcr\u00fcyor \u00c7\u00f6z\u00fcm:<\/strong> 
                     
                  1. Root hints'leri kald\u0131r\u0131n (eri\u015filemeyen k\u00f6k sunucular i\u00e7in)<\/li> 
                  2. Interface metric de\u011ferlerini optimize edin<\/li> 
                  3. DNS forwarder'lar\u0131 yap\u0131land\u0131r\u0131n<\/li> <\/ol> 
                    Senaryo 2: VPN Split-DNS Sorunlar\u0131<\/h3> Problem:<\/strong> VPN ba\u011fl\u0131yken i\u00e7 domain sorgular\u0131 ba\u015far\u0131s\u0131z oluyor \u00c7\u00f6z\u00fcm:<\/strong> 
                       
                    1. Smart Name Resolution'\u0131 devre d\u0131\u015f\u0131 b\u0131rak\u0131n<\/li> 
                    2. VPN adapt\u00f6r\u00fcne en d\u00fc\u015f\u00fck metric de\u011ferini verin<\/li> 
                    3. Conditional forwarder'lar\u0131 kullan\u0131n<\/li> <\/ol> 
                      Senaryo 3: Domain Controller DNS Yap\u0131land\u0131rmas\u0131<\/h3> En \u0130yi Pratikler:<\/strong> 
                         
                      • DC'ler kendi IP adreslerini birinci DNS olarak kullanmal\u0131<\/li> 
                      • \u0130kinci DNS olarak ba\u015fka bir DC'yi belirtmeli<\/li> 
                      • ISP DNS sunucular\u0131n\u0131 asla kullanmamal\u0131<\/li> <\/ul> 
                        \u0130leri Seviye Optimizasyon Teknikleri<\/h2> 
                        Registry Tabanl\u0131 Optimizasyonlar<\/h3> DNS Timeout De\u011ferlerini \u00d6zelle\u015ftirme:<\/strong> 
                         \"DNSQueryTimeouts\"=hex:01,00,00,00,02,00,00,00,04,00,00,00 <\/code><\/pre> Round Robin Devre D\u0131\u015f\u0131 B\u0131rakma:<\/strong> 
                         \"RoundRobin\"=dword:00000000 <\/code><\/pre> Sunucu \u00d6ncelik Zaman Limiti:<\/strong> 
                         \"ServerPriorityTimeLimit\"=dword:00000000 <\/code><\/pre> 
                        PowerShell ile DNS Durumu \u0130zleme<\/h3> 
                        # DNS \u00f6ncelik s\u0131ras\u0131n\u0131 g\u00f6r\u00fcnt\u00fcleme Get-DnsClientServerAddress | Sort-Object InterfaceIndex # DNS cache temizleme Clear-DnsClientCache # DNS performans testi Resolve-DnsName google.com -Server 8.8.8.8 -DnsOnly <\/code><\/pre> 
                        PowerShell ile DNS Cevap S\u00fcresi Testi<\/h5> 
                        $dnsList = @(\"10.1.1.1\", \"10.1.2.1\", \"8.8.8.8\", \"1.1.1.1\") $testDomain = \"www.microsoft.com\" foreach ($dns in $dnsList) { Write-Host \"`nTesting DNS Server: $dns\" $time = Measure-Command { try { Resolve-DnsName -Name $testDomain -Server $dns -ErrorAction Stop } catch { Write-Host \"Failed to resolve using $dns\" } } Write-Host \"Time taken: $($time.TotalMilliseconds) ms\" }<\/pre> 
                        <\/code><\/pre> 
                        Netsh ile Trafik \u0130zleme<\/h5> 
                        netsh trace start capture=yes<\/span> scenario=netconnection tracefile=c:\\temp\\dns_trace.etl <\/span><\/pre> 
                        \u0130lgili testleri yapt\u0131ktan sonra:<\/p> 
                        netsh trace stop<\/span><\/span><\/pre> 
                        Windows S\u00fcr\u00fcmlerine G\u00f6re Farkl\u0131l\u0131klar<\/span><\/h3> 
                        Windows Server Versions<\/h3> 
                           
                        • Server 2012 R2 ve \u00f6ncesi:<\/strong> Geleneksel s\u0131ral\u0131 yakla\u015f\u0131m<\/li> 
                        • Server 2016+:<\/strong> Windows 10 benzeri paralel sorgu mekanizmas\u0131<\/li> <\/ul> 
                          Client Versions<\/h3> 
                             
                          • Windows 7\/8.1:<\/strong> NIC binding order tabanl\u0131<\/li> 
                          • Windows 10\/11:<\/strong> Interface metric tabanl\u0131<\/li> 
                          • Windows 11:<\/strong> Ek g\u00fcvenlik optimizasyonlar\u0131<\/li> <\/ul> 
                            G\u00fcvenlik ve Performans \u00d6nerileri<\/h2> 
                            G\u00fcvenlik A\u00e7\u0131s\u0131ndan<\/h3> 
                               
                            1. DNS over HTTPS (DoH)<\/strong> kullan\u0131m\u0131n\u0131 de\u011ferlendirin<\/li> 
                            2. DNSSEC<\/strong> do\u011frulamas\u0131n\u0131 etkinle\u015ftirin<\/li> 
                            3. G\u00fcvenilmeyen a\u011flarda DNS s\u0131z\u0131nt\u0131lar\u0131na dikkat edin<\/li> <\/ol> 
                              Performans A\u00e7\u0131s\u0131ndan<\/h3> 
                                 
                              1. Yerel DNS cache<\/strong> boyutunu optimize edin<\/li> 
                              2. Conditional forwarder'lar\u0131<\/strong> kullan\u0131n<\/li> 
                              3. DNS sunucu yan\u0131t s\u00fcrelerini<\/strong> d\u00fczenli monit\u00f6r edin<\/li> <\/ol> 
                                Sorun Giderme Ara\u00e7lar\u0131<\/h2> 
                                Komut Sat\u0131r\u0131 Ara\u00e7lar\u0131<\/h3> 
                                # DNS konfig\u00fcrasyonunu g\u00f6r\u00fcnt\u00fcleme ipconfig \/all # DNS cache'i temizleme ipconfig \/flushdns # DNS kayd\u0131n\u0131 yenileme ipconfig \/registerdns # DNS sorgu testi nslookup google.com <\/code><\/pre> 
                                PowerShell Ara\u00e7lar\u0131<\/h3> 
                                # Detayl\u0131 DNS sorgu Resolve-DnsName example.com -Type A -DnsOnly # DNS client ayarlar\u0131n\u0131 g\u00f6r\u00fcnt\u00fcleme Get-DnsClient # Interface metric'lerini listeleme Get-NetIPInterface | Select InterfaceAlias,InterfaceMetric,ConnectionState <\/code><\/pre> Windows DNS istemci davran\u0131\u015f\u0131, sistem versiyonuna ba\u011fl\u0131 olarak \u00f6nemli farkl\u0131l\u0131klar g\u00f6stermektedir. Windows 10 ve sonras\u0131nda getirilen paralel sorgu mekanizmas\u0131 performans\u0131 art\u0131r\u0131rken, baz\u0131 senaryolarda beklenmedik sonu\u00e7lar do\u011furabilir. \u00d6zellikle multi-homed sistemlerde ve VPN kullan\u0131m\u0131nda bu davran\u0131\u015flar\u0131 anlamak kritiktir. Ana \u00c7\u0131kar\u0131mlar:<\/strong> 
                                   
                                • Modern Windows s\u00fcr\u00fcmlerinde DNS \"ger\u00e7ekten s\u0131ral\u0131\" \u00e7al\u0131\u015fmaz<\/li> 
                                • Interface metric de\u011feri en \u00f6nemli \u00f6ncelik fakt\u00f6r\u00fcd\u00fcr<\/li> 
                                • Smart Name Resolution baz\u0131 durumlarda devre d\u0131\u015f\u0131 b\u0131rak\u0131lmal\u0131d\u0131r<\/li> 
                                • Do\u011fru DNS yap\u0131land\u0131rmas\u0131 a\u011f performans\u0131n\u0131 \u00f6nemli \u00f6l\u00e7\u00fcde etkiler<\/li> <\/ul> Sistem y\u00f6neticilerinin bu mekanizmalar\u0131 anlamas\u0131 ve uygun optimizasyonlar\u0131 yapmas\u0131, hem g\u00fcvenlik hem de performans a\u00e7\u0131s\u0131ndan kritik \u00f6neme sahiptir.","excerpt":"DNS (Domain Name System) \u00e7\u00f6z\u00fcmlemesi, modern bilgisayar a\u011flar\u0131n\u0131n en kritik bile\u015fenlerinden biridir. Her g\u00fcn milyarlarca DNS sorgusu...","created_at":"2025-06-12 13:05:50","updated_at":"2026-09-06 21:22:00","category_id":6,"view_count":698,"reading_time":6,"status":"published","editor_choice":0,"is_editor_choice":0,"published_at":"2025-06-12 13:05:50","featured_image":"resimyok.jpg","slug":"windows-dns-istemci-davranisi-sistem-versiyonuna-bagli-olarak-onemli-farkliliklar-gostermektedir","category_name":"Sistem","category_slug":"sistem"}