{"id":2362,"date":"2025-11-23T17:59:34","date_gmt":"2025-11-23T14:59:34","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/dns-hatalari-yuzunden-site-acilmiyor-dns_probe_finished_nxdomain-teshis-rehberi\/"},"modified":"2025-11-23T17:59:34","modified_gmt":"2025-11-23T14:59:34","slug":"dns-hatalari-yuzunden-site-acilmiyor-dns_probe_finished_nxdomain-teshis-rehberi","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/dns-hatalari-yuzunden-site-acilmiyor-dns_probe_finished_nxdomain-teshis-rehberi\/","title":{"rendered":"DNS Hatalar\u0131 Y\u00fcz\u00fcnden Site A\u00e7\u0131lm\u0131yor: DNS_PROBE_FINISHED_NXDOMAIN Te\u015fhis Rehberi"},"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_hatalari_neden_sitenizi_bir_anda_gorunmez_yapiyor\"><span class=\"toc_number toc_depth_1\">1<\/span> DNS hatalar\u0131 neden sitenizi bir anda g\u00f6r\u00fcnmez yap\u0131yor?<\/a><\/li><li><a href=\"#Tarayicida_gorebileceginiz_yaygin_DNS_hata_mesajlari\"><span class=\"toc_number toc_depth_1\">2<\/span> Taray\u0131c\u0131da g\u00f6rebilece\u011finiz yayg\u0131n DNS hata mesajlar\u0131<\/a><\/li><li><a href=\"#Ilk_adim_Sorun_sizde_mi_sitede_mi_Hizli_kullanici_tarafi_kontrolleri\"><span class=\"toc_number toc_depth_1\">3<\/span> \u0130lk ad\u0131m: Sorun sizde mi, sitede mi? H\u0131zl\u0131 kullan\u0131c\u0131 taraf\u0131 kontrolleri<\/a><ul><li><a href=\"#1_Farkli_cihaz_ve_agdan_test_edin\"><span class=\"toc_number toc_depth_2\">3.1<\/span> 1) Farkl\u0131 cihaz ve a\u011fdan test edin<\/a><\/li><li><a href=\"#2_Tarayici_ve_sistem_onbellegini_temizleyin\"><span class=\"toc_number toc_depth_2\">3.2<\/span> 2) Taray\u0131c\u0131 ve sistem \u00f6nbelle\u011fini temizleyin<\/a><\/li><li><a href=\"#3_DNS_onbellegini_DNS_cache_sifirlayin\"><span class=\"toc_number toc_depth_2\">3.3<\/span> 3) DNS \u00f6nbelle\u011fini (DNS cache) s\u0131f\u0131rlay\u0131n<\/a><\/li><li><a href=\"#4_hosts_dosyasini_kontrol_edin\"><span class=\"toc_number toc_depth_2\">3.4<\/span> 4) hosts dosyas\u0131n\u0131 kontrol edin<\/a><\/li><\/ul><\/li><li><a href=\"#Adim_adim_teknik_teshis_DNS_PROBE_FINISHED_NXDOMAIN_kok_neden_analizi\"><span class=\"toc_number toc_depth_1\">4<\/span> Ad\u0131m ad\u0131m teknik te\u015fhis: DNS_PROBE_FINISHED_NXDOMAIN k\u00f6k neden analizi<\/a><ul><li><a href=\"#1_Alan_adi_gercekten_aktif_mi_Suresi_dolmus_olabilir\"><span class=\"toc_number toc_depth_2\">4.1<\/span> 1) Alan ad\u0131 ger\u00e7ekten aktif mi? S\u00fcresi dolmu\u015f olabilir<\/a><\/li><li><a href=\"#2_Nameserver_kayitlari_dogru_ve_aktif_mi\"><span class=\"toc_number toc_depth_2\">4.2<\/span> 2) Nameserver kay\u0131tlar\u0131 do\u011fru ve aktif mi?<\/a><\/li><li><a href=\"#3_DNS_zone_icinde_AAAAA_ve_diger_kritik_kayitlar_var_mi\"><span class=\"toc_number toc_depth_2\">4.3<\/span> 3) DNS zone i\u00e7inde A\/AAAA ve di\u011fer kritik kay\u0131tlar var m\u0131?<\/a><\/li><li><a href=\"#4_TTL_ve_DNS_yayilimi_Gercekten_sorun_mu_var_yoksa_eski_kayit_mi_gorunuyor\"><span class=\"toc_number toc_depth_2\">4.4<\/span> 4) TTL ve DNS yay\u0131l\u0131m\u0131: Ger\u00e7ekten sorun mu var, yoksa eski kay\u0131t m\u0131 g\u00f6r\u00fcn\u00fcyor?<\/a><\/li><li><a href=\"#5_DNSSEC_yanlis_yapilandirmasi_ve_SERVFAIL_kaynakli_gizli_sorunlar\"><span class=\"toc_number toc_depth_2\">4.5<\/span> 5) DNSSEC yanl\u0131\u015f yap\u0131land\u0131rmas\u0131 ve SERVFAIL kaynakl\u0131 gizli sorunlar<\/a><\/li><\/ul><\/li><li><a href=\"#Komut_satiriyla_DNS_teshisi_nslookup_dig_ve_traceroute\"><span class=\"toc_number toc_depth_1\">5<\/span> Komut sat\u0131r\u0131yla DNS te\u015fhisi: nslookup, dig ve traceroute<\/a><ul><li><a href=\"#1_nslookup_ile_temel_kontrol\"><span class=\"toc_number toc_depth_2\">5.1<\/span> 1) nslookup ile temel kontrol<\/a><\/li><li><a href=\"#2_dig_ile_detayli_cikti_almak\"><span class=\"toc_number toc_depth_2\">5.2<\/span> 2) dig ile detayl\u0131 \u00e7\u0131kt\u0131 almak<\/a><\/li><li><a href=\"#3_traceroute_tracert_ile_ag_yolunu_incelemek\"><span class=\"toc_number toc_depth_2\">5.3<\/span> 3) traceroute \/ tracert ile a\u011f yolunu incelemek<\/a><\/li><\/ul><\/li><li><a href=\"#DCHost_musterileri_icin_tipik_senaryolar_ve_pratik_cozumler\"><span class=\"toc_number toc_depth_1\">6<\/span> DCHost m\u00fc\u015fterileri i\u00e7in tipik senaryolar ve pratik \u00e7\u00f6z\u00fcmler<\/a><ul><li><a href=\"#Senaryo_1_IP_degisti_A_kaydi_guncellenmedi\"><span class=\"toc_number toc_depth_2\">6.1<\/span> Senaryo 1: IP de\u011fi\u015fti, A kayd\u0131 g\u00fcncellenmedi<\/a><\/li><li><a href=\"#Senaryo_2_Farkli_DNS_saglayicisi_kullanirken_nameserver_unutuldu\"><span class=\"toc_number toc_depth_2\">6.2<\/span> Senaryo 2: Farkl\u0131 DNS sa\u011flay\u0131c\u0131s\u0131 kullan\u0131rken nameserver unutuldu<\/a><\/li><li><a href=\"#Senaryo_3_VPS_uzerinde_kendi_DNS_sunucunuzu_yonetirken_yapilandirma_hatasi\"><span class=\"toc_number toc_depth_2\">6.3<\/span> Senaryo 3: VPS \u00fczerinde kendi DNS sunucunuzu y\u00f6netirken yap\u0131land\u0131rma hatas\u0131<\/a><\/li><\/ul><\/li><li><a href=\"#Benzer_hatalar_BAD_CONFIG_SERVFAIL_REFUSED_Ne_anlama_geliyor\"><span class=\"toc_number toc_depth_1\">7<\/span> Benzer hatalar: BAD_CONFIG, SERVFAIL, REFUSED\u2026 Ne anlama geliyor?<\/a><ul><li><a href=\"#DNS_PROBE_FINISHED_BAD_CONFIG\"><span class=\"toc_number toc_depth_2\">7.1<\/span> DNS_PROBE_FINISHED_BAD_CONFIG<\/a><\/li><li><a href=\"#SERVFAIL\"><span class=\"toc_number toc_depth_2\">7.2<\/span> SERVFAIL<\/a><\/li><li><a href=\"#REFUSED\"><span class=\"toc_number toc_depth_2\">7.3<\/span> REFUSED<\/a><\/li><\/ul><\/li><li><a href=\"#Kalici_olarak_DNS_sorunlarindan_kacinmak_icin_iyi_pratikler\"><span class=\"toc_number toc_depth_1\">8<\/span> Kal\u0131c\u0131 olarak DNS sorunlar\u0131ndan ka\u00e7\u0131nmak i\u00e7in iyi pratikler<\/a><\/li><li><a href=\"#Sonuc_DNS_PROBE_FINISHED_NXDOMAIN_hatalarini_sistematik_sekilde_cozmek\"><span class=\"toc_number toc_depth_1\">9<\/span> Sonu\u00e7: DNS_PROBE_FINISHED_NXDOMAIN hatalar\u0131n\u0131 sistematik \u015fekilde \u00e7\u00f6zmek<\/a><\/li><\/ul><\/div>\n<h2><span id=\"DNS_hatalari_neden_sitenizi_bir_anda_gorunmez_yapiyor\">DNS hatalar\u0131 neden sitenizi bir anda g\u00f6r\u00fcnmez yap\u0131yor?<\/span><\/h2>\n<p>Taray\u0131c\u0131ya alan ad\u0131n\u0131z\u0131 yaz\u0131yorsunuz, Enter\u2019a bas\u0131yorsunuz ve kar\u015f\u0131n\u0131za hi\u00e7 ho\u015f olmayan bir ekran \u00e7\u0131k\u0131yor: bo\u015f bir sayfa, taray\u0131c\u0131 uyar\u0131s\u0131 veya \u201cDNS_PROBE_FINISHED_NXDOMAIN\u201d benzeri bir hata. Sunucu taraf\u0131nda her \u015feyin yolunda oldu\u011funu, sitenizin d\u00fcn ak\u015fam \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 biliyorsunuz; ama bug\u00fcn ne siz, ne de m\u00fc\u015fterileriniz eri\u015febiliyor. Bu tablo, DCHost ekibi olarak sahada en s\u0131k kar\u015f\u0131la\u015ft\u0131\u011f\u0131m\u0131z sorunlardan biri.<\/p>\n<p>DNS hatalar\u0131n\u0131n can s\u0131k\u0131c\u0131 taraf\u0131, sorunun kayna\u011f\u0131n\u0131n ilk bak\u0131\u015fta belirsiz olmas\u0131d\u0131r. Problem; bilgisayar\u0131n\u0131zda, modeminizde, ISS\u2019in DNS\u2019inde, alan ad\u0131n\u0131z\u0131n nameserver kay\u0131tlar\u0131nda, DNS zonunda, hatta alan ad\u0131n\u0131z\u0131n s\u00fcresinin dolmu\u015f olmas\u0131nda bile olabilir. \u00dcstelik taray\u0131c\u0131, \u00e7o\u011fu zaman sadece \u201cDNS_PROBE_FINISHED_NXDOMAIN\u201d gibi tek sat\u0131rl\u0131k, yoruma a\u00e7\u0131k bir mesaj g\u00f6sterir.<\/p>\n<p>Bu yaz\u0131da, \u00f6zellikle <strong>DNS_PROBE_FINISHED_NXDOMAIN<\/strong> ve benzeri DNS hatalar\u0131n\u0131 sistematik \u015fekilde te\u015fhis edebilmeniz i\u00e7in ad\u0131m ad\u0131m bir yol haritas\u0131 payla\u015faca\u011f\u0131z. Kullan\u0131c\u0131 taraf\u0131ndaki basit kontrollerden, alan ad\u0131 ya\u015fam d\u00f6ng\u00fcs\u00fc ve DNS kay\u0131tlar\u0131n\u0131n detayl\u0131 incelemesine kadar t\u00fcm katmanlar\u0131 ele alaca\u011f\u0131z. Amac\u0131m\u0131z, sorunun hangi katmanda oldu\u011funu h\u0131zl\u0131ca bulup, do\u011fru noktaya odaklanman\u0131z\u0131 sa\u011flamak ve hem anl\u0131k kesintileri hem de uzun vadeli DNS problemlerini en aza indirmenize yard\u0131mc\u0131 olmak.<\/p>\n<h2><span id=\"Tarayicida_gorebileceginiz_yaygin_DNS_hata_mesajlari\">Taray\u0131c\u0131da g\u00f6rebilece\u011finiz yayg\u0131n DNS hata mesajlar\u0131<\/span><\/h2>\n<p>Taray\u0131c\u0131lar ve i\u015fletim sistemleri, DNS sorunlar\u0131nda farkl\u0131 hata mesajlar\u0131 g\u00f6sterebilir. En s\u0131k kar\u015f\u0131n\u0131za \u00e7\u0131kabilecek mesajlardan baz\u0131lar\u0131 \u015funlard\u0131r:<\/p>\n<ul>\n<li><strong>DNS_PROBE_FINISHED_NXDOMAIN<\/strong> \u2013 Alan ad\u0131n\u0131n DNS taraf\u0131nda bulunamad\u0131\u011f\u0131n\u0131 (NXDOMAIN: Non-Existent Domain) ifade eder.<\/li>\n<li><strong>ERR_NAME_NOT_RESOLVED<\/strong> \u2013 Alan ad\u0131 bir IP adresine \u00e7\u00f6z\u00fcmlenemedi, genellikle NXDOMAIN veya hatal\u0131 DNS yap\u0131land\u0131rmas\u0131 ile ili\u015fkilidir.<\/li>\n<li><strong>DNS_PROBE_FINISHED_BAD_CONFIG<\/strong> \u2013 DNS yap\u0131land\u0131rmas\u0131nda bir sorun oldu\u011funu, \u00e7o\u011fu zaman istemci (bilgisayar\/modem) veya yanl\u0131\u015f DNS sunucusu ayarlar\u0131n\u0131 i\u015faret eder.<\/li>\n<li><strong>DNS_PROBE_STARTED<\/strong> \/ <strong>DNS_PROBE_FINISHED_NO_INTERNET<\/strong> \u2013 \u00c7\u00f6z\u00fcmleme ba\u015flam\u0131\u015f ama internet ba\u011flant\u0131s\u0131 ya yok ya da karars\u0131z.<\/li>\n<li><strong>SERVFAIL<\/strong> \u2013 DNS sunucusu alan ad\u0131n\u0131 \u00e7\u00f6zerken hata ald\u0131; genellikle yetkili DNS sunucusundaki sorunlar, yanl\u0131\u015f yap\u0131land\u0131r\u0131lm\u0131\u015f DNSSEC veya ge\u00e7ersiz kay\u0131tlarla ili\u015fkilidir.<\/li>\n<li><strong>REFUSED<\/strong> \u2013 DNS sunucusu iste\u011fi bilin\u00e7li olarak reddediyor; IP bazl\u0131 k\u0131s\u0131tlama, yanl\u0131\u015f izinler veya firewall kaynakl\u0131 olabilir.<\/li>\n<\/ul>\n<p>Bu hata mesajlar\u0131n\u0131n hepsi ayn\u0131 \u015feyi s\u00f6ylemez, ancak <strong>ortak noktalar\u0131<\/strong>: alan ad\u0131n\u0131n ge\u00e7erli bir IP adresine \u00e7\u00f6z\u00fcmlenememesidir. Dolay\u0131s\u0131yla as\u0131l hedefimiz, DNS\u2019in hangi ad\u0131mda \u201ckoptu\u011funu\u201d bulmak olacakt\u0131r.<\/p>\n<h2><span id=\"Ilk_adim_Sorun_sizde_mi_sitede_mi_Hizli_kullanici_tarafi_kontrolleri\">\u0130lk ad\u0131m: Sorun sizde mi, sitede mi? H\u0131zl\u0131 kullan\u0131c\u0131 taraf\u0131 kontrolleri<\/span><\/h2>\n<p>\u00d6nce, problemi ger\u00e7ekten DNS katman\u0131nda m\u0131 yoksa yerel cihaz\u0131n\u0131zda m\u0131 ya\u015fad\u0131\u011f\u0131n\u0131z\u0131 netle\u015ftirmek gerekir. Hem kendi i\u015finizi hem de destek ekibinizin i\u015fini \u00e7ok kolayla\u015ft\u0131r\u0131r.<\/p>\n<h3><span id=\"1_Farkli_cihaz_ve_agdan_test_edin\">1) Farkl\u0131 cihaz ve a\u011fdan test edin<\/span><\/h3>\n<ul>\n<li>Ayn\u0131 Wi-Fi a\u011f\u0131na ba\u011fl\u0131 ba\u015fka bir telefondan veya bilgisayardan siteye girin.<\/li>\n<li>M\u00fcmk\u00fcnse mobil veriye ge\u00e7erek (4G\/5G) ayn\u0131 alan ad\u0131n\u0131 test edin.<\/li>\n<\/ul>\n<p>Senaryolar:<\/p>\n<ul>\n<li><strong>Sadece sizin bilgisayar\u0131n\u0131zda<\/strong> hata olu\u015fuyorsa: Yerel DNS cache, taray\u0131c\u0131 cache\u2019i, g\u00fcvenlik yaz\u0131l\u0131mlar\u0131 veya hosts dosyas\u0131 \u015f\u00fcpheli.<\/li>\n<li><strong>Ayn\u0131 a\u011fdaki herkeste<\/strong> hata olu\u015fuyorsa: Modem\/Router DNS ayarlar\u0131 veya ISS kaynakl\u0131 bir durum olabilir.<\/li>\n<li><strong>Farkl\u0131 a\u011flarda da<\/strong> ayn\u0131 hata varsa: B\u00fcy\u00fck olas\u0131l\u0131kla sorun alan ad\u0131 taraf\u0131nda (nameserver, DNS zone, alan ad\u0131 durumu vb.).<\/li>\n<\/ul>\n<h3><span id=\"2_Tarayici_ve_sistem_onbellegini_temizleyin\">2) Taray\u0131c\u0131 ve sistem \u00f6nbelle\u011fini temizleyin<\/span><\/h3>\n<p>Taray\u0131c\u0131lar ve i\u015fletim sistemleri, DNS sonu\u00e7lar\u0131n\u0131 bir s\u00fcreli\u011fine \u00f6nbellekte tutar. \u00d6nce en basit ad\u0131mlar\u0131 deneyin:<\/p>\n<ul>\n<li>Taray\u0131c\u0131 gizli sekmede alan ad\u0131n\u0131 a\u00e7may\u0131 deneyin.<\/li>\n<li>Taray\u0131c\u0131 cache\u2019ini ve \u00e7erezleri silin.<\/li>\n<li>Farkl\u0131 bir taray\u0131c\u0131 ile test edin.<\/li>\n<\/ul>\n<h3><span id=\"3_DNS_onbellegini_DNS_cache_sifirlayin\">3) DNS \u00f6nbelle\u011fini (DNS cache) s\u0131f\u0131rlay\u0131n<\/span><\/h3>\n<p>\u0130\u015fletim sisteminin tuttu\u011fu DNS \u00f6nbelle\u011fi bozulmu\u015f veya eski kalm\u0131\u015f olabilir. A\u015fa\u011f\u0131daki komutlar\u0131 terminal\/komut sat\u0131r\u0131nda \u00e7al\u0131\u015ft\u0131rarak DNS cache\u2019i temizleyebilirsiniz:<\/p>\n<ul>\n<li>Windows i\u00e7in:\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">ipconfig \/flushdns<\/code><\/pre>\n<\/li>\n<li>macOS (yeni s\u00fcr\u00fcmler) i\u00e7in:\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">sudo dscacheutil -flushcache\nsudo killall -HUP mDNSResponder<\/code><\/pre>\n<\/li>\n<li>Linux (systemd-resolved kullanan sistemlerde):\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">sudo systemd-resolve --flush-caches<\/code><\/pre>\n<\/li>\n<\/ul>\n<p>Bu i\u015flemlerden sonra taray\u0131c\u0131y\u0131 tamamen kapat\u0131p a\u00e7\u0131n ve tekrar deneyin.<\/p>\n<h3><span id=\"4_hosts_dosyasini_kontrol_edin\">4) hosts dosyas\u0131n\u0131 kontrol edin<\/span><\/h3>\n<p>E\u011fer daha \u00f6nce test ama\u00e7l\u0131 olarak hosts dosyan\u0131za manuel kay\u0131t eklediyseniz, art\u0131k ge\u00e7erli olmayan bir IP\u2019ye i\u015faret ediyor olabilir.<\/p>\n<ul>\n<li>Windows: <code>C:\\Windows\\System32\\drivers\\etc\\hosts<\/code><\/li>\n<li>Linux\/macOS: <code>\/etc\/hosts<\/code><\/li>\n<\/ul>\n<p>\u0130lgili alan ad\u0131n\u0131 eski bir IP\u2019ye zorla y\u00f6nlendiren sat\u0131rlar varsa, ge\u00e7ici olarak yorum sat\u0131r\u0131 haline getirin veya silin. Dosyay\u0131 kaydedip taray\u0131c\u0131y\u0131 yeniden ba\u015flatt\u0131ktan sonra tekrar test edin.<\/p>\n<h2><span id=\"Adim_adim_teknik_teshis_DNS_PROBE_FINISHED_NXDOMAIN_kok_neden_analizi\">Ad\u0131m ad\u0131m teknik te\u015fhis: DNS_PROBE_FINISHED_NXDOMAIN k\u00f6k neden analizi<\/span><\/h2>\n<p>Yerel kontrolleri yapt\u0131ktan ve sorunun ger\u00e7ekten DNS katman\u0131nda oldu\u011funu g\u00f6rd\u00fckten sonra, daha sistematik gitmemiz gerekiyor. A\u015fa\u011f\u0131daki ad\u0131mlar, DCHost taraf\u0131nda da DNS kaynakl\u0131 kesintileri te\u015fhis ederken izledi\u011fimiz tipik yol haritas\u0131n\u0131n sadele\u015ftirilmi\u015f hali.<\/p>\n<h3><span id=\"1_Alan_adi_gercekten_aktif_mi_Suresi_dolmus_olabilir\">1) Alan ad\u0131 ger\u00e7ekten aktif mi? S\u00fcresi dolmu\u015f olabilir<\/span><\/h3>\n<p>\u0130nanmas\u0131 zor gelse de, \u201cDNS_PROBE_FINISHED_NXDOMAIN\u201d hatalar\u0131n\u0131n \u00f6nemli bir k\u0131sm\u0131 <strong>alan ad\u0131 s\u00fcresi doldu\u011fu<\/strong> i\u00e7in ortaya \u00e7\u0131k\u0131yor. M\u00fc\u015fteri taraf\u0131nda fatura e-postas\u0131 g\u00f6zden ka\u00e7\u0131yor, otomatik yenileme kapal\u0131 oluyor ve alan ad\u0131 grace\/redemption d\u00f6nemine giriyor.<\/p>\n<p>\u00d6nce basit bir WHOIS sorgusu ile:<\/p>\n<ul>\n<li>Alan ad\u0131n\u0131n <strong>sona erme tarihini<\/strong>,<\/li>\n<li>Registrar bilgisini,<\/li>\n<li>Alan ad\u0131n\u0131n kilitli (transfere kapal\u0131) olup olmad\u0131\u011f\u0131n\u0131<\/li>\n<\/ul>\n<p>kontrol edin. Alan ad\u0131n\u0131n ya\u015fam d\u00f6ng\u00fcs\u00fcn\u00fcn nas\u0131l i\u015fledi\u011fini daha iyi anlamak i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/alan-adi-yasam-dongusu-ve-dusen-domain-yakalama-rehberi\/\">alan ad\u0131 ya\u015fam d\u00f6ng\u00fcs\u00fc ve d\u00fc\u015fen domain yakalama rehberimizi<\/a> mutlaka g\u00f6zden ge\u00e7irmenizi \u00f6neririz.<\/p>\n<p>Alan ad\u0131n\u0131z ger\u00e7ekten grace veya redemption d\u00f6nemindeyse, \u00f6nce yenileme sorununu \u00e7\u00f6zmeden DNS taraf\u0131nda yapaca\u011f\u0131n\u0131z hi\u00e7bir d\u00fczeltme tek ba\u015f\u0131na i\u015fe yaramayacakt\u0131r.<\/p>\n<h3><span id=\"2_Nameserver_kayitlari_dogru_ve_aktif_mi\">2) Nameserver kay\u0131tlar\u0131 do\u011fru ve aktif mi?<\/span><\/h3>\n<p>Alan ad\u0131n\u0131n aktif oldu\u011funu do\u011frulad\u0131ktan sonra ikinci ad\u0131m, <strong>NS (nameserver) kay\u0131tlar\u0131n\u0131<\/strong> kontrol etmek olmal\u0131. \u00c7\u00fcnk\u00fc taray\u0131c\u0131, alan ad\u0131n\u0131z\u0131n hangi DNS sunucular\u0131na sorulaca\u011f\u0131n\u0131 bu kay\u0131tlardan \u00f6\u011frenir.<\/p>\n<ul>\n<li>Alan ad\u0131n\u0131z\u0131n kay\u0131tl\u0131 oldu\u011fu registar paneline girin.<\/li>\n<li>NS\/nameserver b\u00f6l\u00fcm\u00fcnde yazan sunucu adreslerini not edin (\u00f6rne\u011fin, <code>ns1.ornekns.com<\/code>, <code>ns2.ornekns.com<\/code> gibi).<\/li>\n<li>Bu nameserver\u2019lar\u0131n ger\u00e7ekten var olup olmad\u0131\u011f\u0131n\u0131 ve cevap verip vermedi\u011fini <code>dig<\/code> veya <code>nslookup<\/code> ile test edin.<\/li>\n<\/ul>\n<p>\u00d6rne\u011fin:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">dig NS ornekalanadi.com<\/code><\/pre>\n<p>Bu komutla yetkili NS kay\u0131tlar\u0131n\u0131 g\u00f6rebilirsiniz. Komut \u00e7\u0131kt\u0131s\u0131nda hi\u00e7 NS kayd\u0131 yoksa veya bekledi\u011finizden farkl\u0131 NS\u2019ler geliyorsa, alan ad\u0131 taraf\u0131nda yanl\u0131\u015f veya eksik nameserver tan\u0131mlanm\u0131\u015f demektir.<\/p>\n<p>Kendi \u00f6zel ad sunucular\u0131n\u0131z\u0131 kullan\u0131yorsan\u0131z (\u00f6rne\u011fin <code>ns1.sizinmarka.com<\/code> gibi), <strong>glue record<\/strong> yap\u0131land\u0131rmas\u0131n\u0131n da do\u011fru oldu\u011fundan emin olman\u0131z gerekir. Bu konuyu detayl\u0131 anlatt\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/ozel-ad-sunucusu-ve-glue-record-nasil-kurulur-kendi-dnsine-adim-adim-yolculuk\/\">\u00f6zel ad sunucusu ve glue record rehberimizi<\/a> incelemeniz, ileride olu\u015fabilecek karma\u015f\u0131k DNS sorunlar\u0131n\u0131n \u00f6n\u00fcne ge\u00e7menize yard\u0131mc\u0131 olacakt\u0131r.<\/p>\n<h3><span id=\"3_DNS_zone_icinde_AAAAA_ve_diger_kritik_kayitlar_var_mi\">3) DNS zone i\u00e7inde A\/AAAA ve di\u011fer kritik kay\u0131tlar var m\u0131?<\/span><\/h3>\n<p>Nameserver\u2019lar do\u011fru ise, s\u0131radaki ad\u0131m <strong>DNS zone<\/strong> i\u00e7eri\u011fini kontrol etmektir. En kritik kay\u0131tlar genellikle \u015funlard\u0131r:<\/p>\n<ul>\n<li><strong>A kayd\u0131<\/strong> \u2013 Alan ad\u0131n\u0131 IPv4 adrese y\u00f6nlendirir (\u00f6r. <code>203.0.113.10<\/code>).<\/li>\n<li><strong>AAAA kayd\u0131<\/strong> \u2013 Alan ad\u0131n\u0131 IPv6 adrese y\u00f6nlendirir.<\/li>\n<li><strong>CNAME kayd\u0131<\/strong> \u2013 Bir alan ad\u0131n\u0131 ba\u015fka bir alan ad\u0131na y\u00f6nlendirir.<\/li>\n<li><strong>MX kayd\u0131<\/strong> \u2013 E-posta teslimat\u0131 i\u00e7in posta sunucular\u0131n\u0131 tan\u0131mlar.<\/li>\n<\/ul>\n<p>\u00d6zellikle <strong>ana alan ad\u0131n\u0131z<\/strong> (\u00f6r. <code>ornekalanadi.com<\/code>) ve varsa <code>www<\/code> alt alan ad\u0131n\u0131z i\u00e7in A\/AAAA veya CNAME kayd\u0131 <strong>yoksa<\/strong>, taray\u0131c\u0131 \u201cDNS_PROBE_FINISHED_NXDOMAIN\u201d hatas\u0131 verebilir.<\/p>\n<p>DNS kay\u0131tlar\u0131n\u0131n do\u011fru t\u00fcrde ve do\u011fru formatta olup olmad\u0131\u011f\u0131n\u0131 ad\u0131m ad\u0131m \u00f6\u011frenmek i\u00e7in haz\u0131rlad\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/dns-kayitlari-adan-zye-a-aaaa-cname-mx-txt-srv-caa-ve-sizi-yakan-o-kucuk-hatalar\/\">DNS kay\u0131tlar\u0131 A\u2019dan Z\u2019ye rehberine<\/a> mutlaka g\u00f6z at\u0131n. \u00d6zellikle yanl\u0131\u015f kullan\u0131lm\u0131\u015f CNAME kay\u0131tlar\u0131 veya k\u00f6k alan ad\u0131nda istenen ama teknik olarak sak\u0131ncal\u0131 CNAME\u2019ler, uzun s\u00fcre fark edilmeyen sorunlar yaratabiliyor.<\/p>\n<h3><span id=\"4_TTL_ve_DNS_yayilimi_Gercekten_sorun_mu_var_yoksa_eski_kayit_mi_gorunuyor\">4) TTL ve DNS yay\u0131l\u0131m\u0131: Ger\u00e7ekten sorun mu var, yoksa eski kay\u0131t m\u0131 g\u00f6r\u00fcn\u00fcyor?<\/span><\/h3>\n<p>DNS de\u011fi\u015fikli\u011fi yapt\u0131ysan\u0131z (IP de\u011fi\u015ftirdiniz, nameserver ta\u015f\u0131d\u0131n\u0131z, A kayd\u0131n\u0131 g\u00fcncellediniz vb.), <strong>TTL (Time To Live)<\/strong> de\u011ferleri nedeniyle baz\u0131 kullan\u0131c\u0131lar bir s\u00fcre eski kay\u0131tlar\u0131 g\u00f6rmeye devam edebilir. Bu durum, sizde site a\u00e7\u0131l\u0131rken ba\u015fka bir b\u00f6lgede \u201cDNS_PROBE_FINISHED_NXDOMAIN\u201d al\u0131nmas\u0131na yol a\u00e7abilir.<\/p>\n<p>B\u00fcy\u00fck ge\u00e7i\u015fler ve ta\u015f\u0131malarda TTL de\u011ferlerini nas\u0131l planlaman\u0131z gerekti\u011fini, ad\u0131m ad\u0131m \u00f6rneklerle <a href=\"https:\/\/www.dchost.com\/blog\/zero-downtime-tasima-icin-ttl-stratejileri-dns-yayilimini-gercekten-nasil-hizlandirirsin\/\">zero-downtime ta\u015f\u0131ma i\u00e7in TTL stratejileri rehberimizde<\/a> anlatt\u0131k. K\u0131saca:<\/p>\n<ul>\n<li>Ta\u015f\u0131ma \u00f6ncesinde TTL\u2019leri yava\u015f yava\u015f d\u00fc\u015f\u00fcrmek,<\/li>\n<li>Ge\u00e7i\u015fi yapt\u0131ktan sonra bir s\u00fcre d\u00fc\u015f\u00fck TTL\u2019le devam etmek,<\/li>\n<li>Her \u015fey stabil olduktan sonra TTL\u2019leri tekrar y\u00fckseltmek<\/li>\n<\/ul>\n<p>en sa\u011fl\u0131kl\u0131 yakla\u015f\u0131md\u0131r. Aksi halde, farkl\u0131 b\u00f6lgelerde farkl\u0131 DNS cevaplar\u0131 g\u00f6rmek ka\u00e7\u0131n\u0131lmaz olur.<\/p>\n<h3><span id=\"5_DNSSEC_yanlis_yapilandirmasi_ve_SERVFAIL_kaynakli_gizli_sorunlar\">5) DNSSEC yanl\u0131\u015f yap\u0131land\u0131rmas\u0131 ve SERVFAIL kaynakl\u0131 gizli sorunlar<\/span><\/h3>\n<p>DNSSEC, DNS kay\u0131tlar\u0131n\u0131z\u0131n b\u00fct\u00fcnl\u00fc\u011f\u00fcn\u00fc kriptografik olarak do\u011frulayan bir g\u00fcvenlik katman\u0131d\u0131r. Ancak yanl\u0131\u015f yap\u0131land\u0131r\u0131ld\u0131\u011f\u0131nda, alan ad\u0131n\u0131z baz\u0131 resolver\u2019lar i\u00e7in tamamen ula\u015f\u0131lamaz hale gelebilir. \u00d6rne\u011fin:<\/p>\n<ul>\n<li>DNSSEC etkin ama <strong>DS kay\u0131tlar\u0131<\/strong> yanl\u0131\u015f veya g\u00fcncel de\u011filse,<\/li>\n<li>KSK\/ZSK anahtar d\u00f6nd\u00fcrme (key rollover) i\u015flemi hatal\u0131 yap\u0131ld\u0131ysa,<\/li>\n<li>DNS sa\u011flay\u0131c\u0131n\u0131z\u0131 de\u011fi\u015ftirdi\u011finiz halde eski DS kayd\u0131 registrar taraf\u0131nda kald\u0131ysa<\/li>\n<\/ul>\n<p>baz\u0131 kullan\u0131c\u0131lar SERVFAIL veya NXDOMAIN benzeri hatalar g\u00f6rebilir, baz\u0131lar\u0131 ise hi\u00e7 sorun ya\u015famayabilir.<\/p>\n<p>DNSSEC\u2019in ne i\u015fe yarad\u0131\u011f\u0131n\u0131 ve nas\u0131l g\u00fcvenli \u015fekilde etkin tutulaca\u011f\u0131n\u0131 anlatt\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/dnssec-nedir-web-sitenizi-nasil-daha-guvenli-hale-getirir\/\">DNSSEC rehberimize<\/a> mutlaka g\u00f6z at\u0131n. Daha ileri seviye ihtiya\u00e7lar i\u00e7in haz\u0131rlad\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/dnssec-key-rollover-ksk-zsk-ve-ds-kayit-guncelleme-sifir-kesintiyle-anahtar-dondurme-nasil-yapilir\/\">DNSSEC key rollover yaz\u0131s\u0131<\/a> da \u00f6zellikle b\u00fcy\u00fck projelerde hayat kurtar\u0131c\u0131 olabilir.<\/p>\n<h2><span id=\"Komut_satiriyla_DNS_teshisi_nslookup_dig_ve_traceroute\">Komut sat\u0131r\u0131yla DNS te\u015fhisi: nslookup, dig ve traceroute<\/span><\/h2>\n<p>Bir noktadan sonra, taray\u0131c\u0131daki tek sat\u0131rl\u0131k hata mesajlar\u0131 yetersiz kal\u0131r. O an devreye klasik a\u011f ara\u00e7lar\u0131 girer: <code>nslookup<\/code>, <code>dig<\/code>, <code>traceroute<\/code>.<\/p>\n<h3><span id=\"1_nslookup_ile_temel_kontrol\">1) nslookup ile temel kontrol<\/span><\/h3>\n<p>Windows, macOS ve Linux\u2019ta kullanabilece\u011finiz basit bir ara\u00e7t\u0131r. \u00d6rne\u011fin:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">nslookup ornekalanadi.com<\/code><\/pre>\n<p>Burada dikkat etmeniz gerekenler:<\/p>\n<ul>\n<li><strong>Non-existent domain<\/strong> gibi bir \u00e7\u0131kt\u0131 g\u00f6r\u00fcyorsan\u0131z: Resolver, alan ad\u0131n\u0131z i\u00e7in hi\u00e7 kay\u0131t bulamam\u0131\u015f demektir (NXDOMAIN).<\/li>\n<li>Cevap veren DNS sunucusunun adresi (genelde ISS DNS\u2019i) ve d\u00f6nen IP adresleri.<\/li>\n<\/ul>\n<h3><span id=\"2_dig_ile_detayli_cikti_almak\">2) dig ile detayl\u0131 \u00e7\u0131kt\u0131 almak<\/span><\/h3>\n<p><code>dig<\/code>, \u00f6zellikle Linux ve macOS taraf\u0131nda daha detayl\u0131 \u00e7\u0131kt\u0131lar sunar. \u00d6rne\u011fin:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">dig ornekalanadi.com A<\/code><\/pre>\n<p>Komut \u00e7\u0131kt\u0131s\u0131nda:<\/p>\n<ul>\n<li><strong>ANSWER SECTION<\/strong> k\u0131sm\u0131nda IP adresi g\u00f6rmeniz gerekir.<\/li>\n<li><strong>status: NXDOMAIN<\/strong> g\u00f6r\u00fcyorsan\u0131z, DNS sunucusu bu alan ad\u0131n\u0131n mevcut olmad\u0131\u011f\u0131n\u0131 d\u00fc\u015f\u00fcn\u00fcyor demektir.<\/li>\n<li><strong>status: SERVFAIL<\/strong> ise, genellikle DNSSEC veya yetkili DNS sunucusu kaynakl\u0131 daha derin bir hata vard\u0131r.<\/li>\n<\/ul>\n<p>Yetkili nameserver\u2019\u0131 do\u011frudan sorgulamak i\u00e7in:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">dig @ns1.ornekns.com ornekalanadi.com A<\/code><\/pre>\n<p>Bu sayede, aradaki resolver\u2019lar\u0131 atlayarak sorunun yetkili DNS sunucusundaki kay\u0131tlardan m\u0131, yoksa aradaki zincirden mi kaynakland\u0131\u011f\u0131n\u0131 ay\u0131rt edebilirsiniz.<\/p>\n<h3><span id=\"3_traceroute_tracert_ile_ag_yolunu_incelemek\">3) traceroute \/ tracert ile a\u011f yolunu incelemek<\/span><\/h3>\n<p>DNS sorunlar\u0131n\u0131n bir k\u0131sm\u0131, asl\u0131nda a\u011f seviyesindeki eri\u015fim problemlerinin semptomu olabilir. \u00d6rne\u011fin, yetkili DNS sunucunuzun bulundu\u011fu IP blo\u011fu baz\u0131 ISS\u2019ler taraf\u0131ndan ge\u00e7ici olarak eri\u015filemez durumdad\u0131r.<\/p>\n<ul>\n<li>Windows: <code>tracert ornekalanadi.com<\/code><\/li>\n<li>Linux\/macOS: <code>traceroute ornekalanadi.com<\/code><\/li>\n<\/ul>\n<p>E\u011fer traceroute \u00e7\u0131k\u0131\u015f\u0131 belirli bir noktada kesiliyor veya time-out veriyorsa, sorun DNS kay\u0131tlar\u0131n\u0131zdan ziyade network rotas\u0131nda olabilir. Bu durumda DCHost destek ekibimizle veya a\u011f y\u00f6neticinizle birlikte daha derin bir analiz yapmak gerekir.<\/p>\n<h2><span id=\"DCHost_musterileri_icin_tipik_senaryolar_ve_pratik_cozumler\">DCHost m\u00fc\u015fterileri i\u00e7in tipik senaryolar ve pratik \u00e7\u00f6z\u00fcmler<\/span><\/h2>\n<p>DCHost taraf\u0131nda, hem <a href=\"https:\/\/www.dchost.com\/tr\/web-hosting\">payla\u015f\u0131ml\u0131 hosting<\/a> hem de <a href=\"https:\/\/www.dchost.com\/tr\/vps\">VPS<\/a>\/<a href=\"https:\/\/www.dchost.com\/tr\/fiziksel-sunucu\">dedicated sunucu<\/a> m\u00fc\u015fterilerimizde DNS kaynakl\u0131 benzer senaryolar\u0131 s\u0131k\u00e7a g\u00f6r\u00fcyoruz. Bunlar\u0131n bir k\u0131sm\u0131 birka\u00e7 dakikal\u0131k d\u00fczenlemeyle \u00e7\u00f6z\u00fclebilirken, baz\u0131lar\u0131 daha planl\u0131 bir mimari gerektiriyor.<\/p>\n<h3><span id=\"Senaryo_1_IP_degisti_A_kaydi_guncellenmedi\">Senaryo 1: IP de\u011fi\u015fti, A kayd\u0131 g\u00fcncellenmedi<\/span><\/h3>\n<p>En s\u0131k kar\u015f\u0131la\u015ft\u0131\u011f\u0131m\u0131z senaryolardan biri: M\u00fc\u015fteri, farkl\u0131 bir sunucuya ge\u00e7iyor veya yeni bir VPS\u2019e ta\u015f\u0131n\u0131yor, ancak alan ad\u0131n\u0131n A kayd\u0131 eski IP\u2019yi g\u00f6stermeye devam ediyor. Sonu\u00e7: \u201cDNS_PROBE_FINISHED_NXDOMAIN\u201d ya da farkl\u0131 IP\u2019de \u00e7al\u0131\u015fan, art\u0131k ge\u00e7erli olmayan bir eski site.<\/p>\n<p>\u00c7\u00f6z\u00fcm ad\u0131mlar\u0131:<\/p>\n<ul>\n<li>Yeni sunucunun IP adresini kesin olarak do\u011frulamak.<\/li>\n<li>Alan ad\u0131n\u0131z\u0131n DNS zonunda A\/AAAA kay\u0131tlar\u0131n\u0131 do\u011fru IP\u2019ye g\u00fcncellemek.<\/li>\n<li>TTL de\u011ferlerini ge\u00e7ici olarak d\u00fc\u015f\u00fcrerek ge\u00e7i\u015f s\u00fcrecini h\u0131zland\u0131rmak.<\/li>\n<\/ul>\n<p>DNS yay\u0131l\u0131m\u0131n\u0131 beklerken, farkl\u0131 b\u00f6lgelerden sorgu yaparak hangi resolver\u2019lar\u0131n yeni IP\u2019yi g\u00f6rmeye ba\u015flad\u0131\u011f\u0131n\u0131 takip edebilirsiniz.<\/p>\n<h3><span id=\"Senaryo_2_Farkli_DNS_saglayicisi_kullanirken_nameserver_unutuldu\">Senaryo 2: Farkl\u0131 DNS sa\u011flay\u0131c\u0131s\u0131 kullan\u0131rken nameserver unutuldu<\/span><\/h3>\n<p>Bazen m\u00fc\u015fterilerimiz, performans veya \u00f6zellik nedeniyle \u00fc\u00e7\u00fcnc\u00fc parti bir DNS hizmetine ge\u00e7iyor; ancak alan ad\u0131n\u0131n registrar panelindeki nameserver kay\u0131tlar\u0131n\u0131 g\u00fcncellemeyi atlayabiliyor. Taray\u0131c\u0131, eski nameserver\u2019lara bakmaya devam etti\u011fi i\u00e7in, DNS kay\u0131tlar\u0131 ile ger\u00e7ekte kullan\u0131lan DNS paneli birbirini tutmuyor.<\/p>\n<p>Bu durumda kontrol listesi:<\/p>\n<ul>\n<li>Hangi DNS panelini ger\u00e7ekten kulland\u0131\u011f\u0131n\u0131z\u0131 netle\u015ftirin.<\/li>\n<li>Registrar panelindeki NS kay\u0131tlar\u0131n\u0131 bu panele ait nameserver\u2019larla hizalay\u0131n.<\/li>\n<li>Eski DNS panelinde kalan \u201cart\u0131k\u201d kay\u0131tlar\u0131 temizleyin; ileride kafa kar\u0131\u015f\u0131kl\u0131\u011f\u0131 ya\u015famay\u0131n.<\/li>\n<\/ul>\n<p>Farkl\u0131 DNS \u00e7\u00f6z\u00fcmleri aras\u0131nda se\u00e7im yaparken dikkat edilmesi gereken noktalar\u0131, <a href=\"https:\/\/www.dchost.com\/blog\/cloudflare-dns-mi-hosting-dnsi-mi-en-dogru-nameserver-stratejisi\/\">nameserver stratejisi \u00fczerine haz\u0131rlad\u0131\u011f\u0131m\u0131z yaz\u0131da<\/a> detayl\u0131 olarak anlatt\u0131k. DCHost \u00fczerinde bar\u0131nan projeleriniz i\u00e7in de benzer prensipler ge\u00e7erli.<\/p>\n<h3><span id=\"Senaryo_3_VPS_uzerinde_kendi_DNS_sunucunuzu_yonetirken_yapilandirma_hatasi\">Senaryo 3: VPS \u00fczerinde kendi DNS sunucunuzu y\u00f6netirken yap\u0131land\u0131rma hatas\u0131<\/span><\/h3>\n<p>VPS veya dedicated sunucu \u00fczerinde kendi DNS sunucunuzu (\u00f6rne\u011fin BIND, PowerDNS vb.) y\u00f6netiyorsan\u0131z, ufak bir konfig\u00fcrasyon hatas\u0131 bile NXDOMAIN veya SERVFAIL hatalar\u0131na sebep olabilir:<\/p>\n<ul>\n<li>Zone dosyas\u0131nda syntax hatas\u0131,<\/li>\n<li>SOA\/NS kay\u0131tlar\u0131nda eksiklik,<\/li>\n<li>Yanl\u0131\u015f seri numaras\u0131 (serial) veya hatal\u0131 increment,<\/li>\n<li>Master\/Slave replikasyon problemleri<\/li>\n<\/ul>\n<p>DCHost \u00fczerinde kendi DNS altyap\u0131s\u0131n\u0131 y\u00f6neten m\u00fc\u015fterilerimiz i\u00e7in, test ortam\u0131nda de\u011fi\u015fiklik yapmak, staging zone\u2019lar kullanmak ve konfig\u00fcrasyonlar\u0131 s\u00fcr\u00fcm kontroll\u00fc bir depo ile y\u00f6netmek en g\u00fcvenli yakla\u015f\u0131m oluyor. B\u00f6ylece sorun \u00e7\u0131kt\u0131\u011f\u0131nda \u201c\u00f6nceki \u00e7al\u0131\u015fan\u201d s\u00fcr\u00fcme h\u0131zl\u0131ca d\u00f6nebilmek m\u00fcmk\u00fcn.<\/p>\n<h2><span id=\"Benzer_hatalar_BAD_CONFIG_SERVFAIL_REFUSED_Ne_anlama_geliyor\">Benzer hatalar: BAD_CONFIG, SERVFAIL, REFUSED\u2026 Ne anlama geliyor?<\/span><\/h2>\n<p>Her DNS hatas\u0131 NXDOMAIN de\u011fildir. Taray\u0131c\u0131lar\u0131n g\u00f6sterdi\u011fi baz\u0131 hata kodlar\u0131, sorunun k\u00f6keni hakk\u0131nda ipucu verir.<\/p>\n<h3><span id=\"DNS_PROBE_FINISHED_BAD_CONFIG\">DNS_PROBE_FINISHED_BAD_CONFIG<\/span><\/h3>\n<p>Genellikle istemci taraf\u0131ndaki (bilgisayar\u0131n\u0131z, modeminiz veya kulland\u0131\u011f\u0131n\u0131z DNS sunucusu) hatal\u0131 yap\u0131land\u0131rmay\u0131 i\u015faret eder:<\/p>\n<ul>\n<li>Modemde yanl\u0131\u015f DNS sunucusu IP\u2019leri tan\u0131mlanm\u0131\u015f olabilir.<\/li>\n<li>Bilgisayar\u0131n\u0131zda manuel olarak girilmi\u015f, art\u0131k \u00e7al\u0131\u015fmayan DNS adresleri olabilir.<\/li>\n<li>Yerel firewall veya g\u00fcvenlik yaz\u0131l\u0131mlar\u0131, DNS trafi\u011fini engelliyor olabilir.<\/li>\n<\/ul>\n<p>Bu durumda a\u011f ayarlar\u0131ndaki DNS alan\u0131n\u0131 \u201cotomatik\u201de \u00e7ekip, modemi yeniden ba\u015flatmak ve alternatif bir a\u011fda test etmek iyi bir ba\u015flang\u0131\u00e7t\u0131r.<\/p>\n<h3><span id=\"SERVFAIL\">SERVFAIL<\/span><\/h3>\n<p>SERVFAIL, yetkili DNS sunucusunun soru kar\u015f\u0131s\u0131nda hata verdi\u011fini g\u00f6sterir. Nedenleri aras\u0131nda:<\/p>\n<ul>\n<li>Yanl\u0131\u015f yap\u0131land\u0131r\u0131lm\u0131\u015f DNSSEC,<\/li>\n<li>Yetkili DNS sunucusuna a\u011f seviyesinde ula\u015f\u0131lamamas\u0131,<\/li>\n<li>DNS sunucusunun i\u00e7 hata (konfig\u00fcrasyon, yaz\u0131l\u0131m) \u00fcretmesi<\/li>\n<\/ul>\n<p>say\u0131labilir. E\u011fer <code>dig<\/code> \u00e7\u0131kt\u0131s\u0131nda <strong>status: SERVFAIL<\/strong> g\u00f6r\u00fcyorsan\u0131z, sorunun k\u00f6k\u00fcne inmek i\u00e7in yetkili DNS sunucusunun loglar\u0131n\u0131 da incelemek gerekir.<\/p>\n<h3><span id=\"REFUSED\">REFUSED<\/span><\/h3>\n<p>REFUSED, DNS sunucusunun iste\u011finizi bilerek reddetti\u011fi anlam\u0131na gelir. S\u0131k g\u00f6r\u00fclen sebepler:<\/p>\n<ul>\n<li>DNS sunucusu sadece belirli IP bloklar\u0131ndan gelen isteklere izin veriyor olabilir.<\/li>\n<li>Recursion (\u00f6zyinelemeli sorgu) yetkisi k\u0131s\u0131tlanm\u0131\u015f olabilir.<\/li>\n<li>Firewall, belirli portlardan (genellikle 53\/UDP, 53\/TCP) gelen istekleri kesiyor olabilir.<\/li>\n<\/ul>\n<p>Bu t\u00fcr durumlar, \u00f6zellikle kendi DNS sunucunuzu \u00e7al\u0131\u015ft\u0131r\u0131yorsan\u0131z yanl\u0131\u015f firewall kural\u0131 veya yanl\u0131\u015f \u201callow-query\u201d yap\u0131land\u0131rmas\u0131ndan kaynaklanabilir.<\/p>\n<h2><span id=\"Kalici_olarak_DNS_sorunlarindan_kacinmak_icin_iyi_pratikler\">Kal\u0131c\u0131 olarak DNS sorunlar\u0131ndan ka\u00e7\u0131nmak i\u00e7in iyi pratikler<\/span><\/h2>\n<p>DNS sorunlar\u0131n\u0131 sadece \u201cyang\u0131n \u00e7\u0131kt\u0131\u011f\u0131nda\u201d \u00e7\u00f6zmeye \u00e7al\u0131\u015fmak yerine, ba\u015ftan do\u011fru tasarlamak \u00e7ok daha az maliyetli ve streslidir. DCHost olarak \u00e7o\u011fu projede \u00f6nerdi\u011fimiz baz\u0131 pratikler:<\/p>\n<ul>\n<li><strong>Alan ad\u0131 yenileme takvimi<\/strong> olu\u015fturun, otomatik yenileme ve hat\u0131rlat\u0131c\u0131lar\u0131 aktif tutun. \u00d6zellikle kritik projeler i\u00e7in birden fazla ki\u015fiye uyar\u0131 gitmesini sa\u011flay\u0131n.<\/li>\n<li><strong>DNS de\u011fi\u015fikliklerini belgeleyin<\/strong>. Hangi tarihte hangi kayd\u0131 de\u011fi\u015ftirdi\u011finizi, eski ve yeni de\u011ferleri not edin; gerekirse bir de\u011fi\u015fiklik g\u00fcnl\u00fc\u011f\u00fc (changelog) tutun.<\/li>\n<li><strong>TTl stratejisi<\/strong> geli\u015ftirin. Ta\u015f\u0131ma veya IP de\u011fi\u015fimi yapacaksan\u0131z, TTL\u2019leri \u00f6nceden d\u00fc\u015f\u00fcr\u00fcn; her \u015feyi test ettikten sonra y\u00fckseltin.<\/li>\n<li><strong>Staging\/test ortam\u0131<\/strong> kullan\u0131n. \u00d6zellikle kendi DNS sunucusunu y\u00f6neten ekipler i\u00e7in, canl\u0131ya almadan \u00f6nce test zone\u2019lar\u0131nda de\u011fi\u015fiklikleri denemek \u00e7ok \u00f6nemli.<\/li>\n<li><strong>DNSSEC ve g\u00fcvenlik yap\u0131land\u0131rmalar\u0131n\u0131<\/strong> bilin\u00e7li y\u00f6netin. Ne yapt\u0131\u011f\u0131n\u0131zdan emin de\u011filseniz, \u00f6nce test domain\u2019lerinde deneme yap\u0131n.<\/li>\n<\/ul>\n<p>Daha b\u00fcy\u00fck mimarilerde, kesintisiz eri\u015filebilirlik hedefliyorsan\u0131z, <a href=\"https:\/\/www.dchost.com\/blog\/hic-kesilmeden-yayinda-kalmak-mumkun-mu-anycast-dns-ve-otomatik-failover-ile-nasil-saglanir\/\">Anycast DNS ve otomatik failover \u00fczerine haz\u0131rlad\u0131\u011f\u0131m\u0131z rehber<\/a> de size yol g\u00f6sterebilir.<\/p>\n<h2><span id=\"Sonuc_DNS_PROBE_FINISHED_NXDOMAIN_hatalarini_sistematik_sekilde_cozmek\">Sonu\u00e7: DNS_PROBE_FINISHED_NXDOMAIN hatalar\u0131n\u0131 sistematik \u015fekilde \u00e7\u00f6zmek<\/span><\/h2>\n<p>\u201cDNS_PROBE_FINISHED_NXDOMAIN\u201d ve benzeri DNS hatalar\u0131, ilk bak\u0131\u015fta gizemli ve sinir bozucu g\u00f6r\u00fcnebilir. Ancak sorunu katmanlara ay\u0131rd\u0131\u011f\u0131n\u0131zda; \u00f6nce <strong>kullan\u0131c\u0131 taraf\u0131n\u0131<\/strong> (cache, hosts, modem), ard\u0131ndan <strong>alan ad\u0131 durumunu<\/strong> (WHOIS, sona erme tarihi), sonra <strong>nameserver ve DNS zone\u2019unu<\/strong> (NS, A\/AAAA, CNAME, MX kay\u0131tlar\u0131), gerekirse de <strong>DNSSEC ve a\u011f rotas\u0131n\u0131<\/strong> inceledi\u011finizde, \u00e7o\u011fu problemi birka\u00e7 net ad\u0131mda te\u015fhis etmek m\u00fcmk\u00fcnd\u00fcr.<\/p>\n<p>DCHost olarak hem payla\u015f\u0131ml\u0131 hosting hem de VPS\/dedicated altyap\u0131lar\u0131m\u0131zda, DNS yap\u0131land\u0131rman\u0131z\u0131 m\u00fcmk\u00fcn oldu\u011funca sade, anla\u015f\u0131l\u0131r ve dok\u00fcmante \u015fekilde tutmaya \u00e7al\u0131\u015f\u0131yoruz. Yine de bazen alan ad\u0131 taraf\u0131ndaki paneller, harici DNS servisleri veya manuel m\u00fcdahaleler i\u015fleri kar\u0131\u015ft\u0131rabiliyor. B\u00f6yle durumlarda, yukar\u0131daki kontrol listesini izleyerek sorunun hangi halkada koptu\u011funu tespit edebilir, ard\u0131ndan do\u011fru noktaya odaklanabilirsiniz.<\/p>\n<p>E\u011fer hala nereden ba\u015flayaca\u011f\u0131n\u0131za emin de\u011filseniz veya b\u00fcy\u00fck bir ta\u015f\u0131ma, IP de\u011fi\u015fikli\u011fi ya da DNS mimarisi planl\u0131yorsan\u0131z, DCHost destek ekibiyle ileti\u015fime ge\u00e7mekten \u00e7ekinmeyin. Alan ad\u0131, DNS ve hosting taraf\u0131ndaki birikimimizi projenize uyarlayarak, hem bug\u00fcnk\u00fc DNS_PROBE_FINISHED_NXDOMAIN benzeri hatalar\u0131 gidermenize hem de gelecekteki kesintileri en aza indirmenize yard\u0131mc\u0131 olabiliriz.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>\u0130&ccedil;indekiler1 DNS hatalar\u0131 neden sitenizi bir anda g\u00f6r\u00fcnmez yap\u0131yor?2 Taray\u0131c\u0131da g\u00f6rebilece\u011finiz yayg\u0131n DNS hata mesajlar\u01313 \u0130lk ad\u0131m: Sorun sizde mi, sitede mi? H\u0131zl\u0131 kullan\u0131c\u0131 taraf\u0131 kontrolleri3.1 1) Farkl\u0131 cihaz ve a\u011fdan test edin3.2 2) Taray\u0131c\u0131 ve sistem \u00f6nbelle\u011fini temizleyin3.3 3) DNS \u00f6nbelle\u011fini (DNS cache) s\u0131f\u0131rlay\u0131n3.4 4) hosts dosyas\u0131n\u0131 kontrol edin4 Ad\u0131m ad\u0131m teknik te\u015fhis: DNS_PROBE_FINISHED_NXDOMAIN [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":2363,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-2362","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\/2362","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=2362"}],"version-history":[{"count":0,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/2362\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/2363"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=2362"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=2362"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=2362"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}