{"id":2972,"date":"2026-10-21T15:00:00","date_gmt":"2026-10-21T12:00:00","guid":{"rendered":"https:\/\/narhost.com\/destek\/?p=2972"},"modified":"2026-10-21T15:00:00","modified_gmt":"2026-10-21T12:00:00","slug":"temporary-failure-in-name-resolution","status":"publish","type":"post","link":"https:\/\/narhost.com\/destek\/temporary-failure-in-name-resolution\/","title":{"rendered":"Temporary Failure in Name Resolution Hatas\u0131 Nas\u0131l \u00c7\u00f6z\u00fcl\u00fcr (Ubuntu 24.04)"},"content":{"rendered":"<p class=\"kb-dogrulama\">Son g\u00f6zden ge\u00e7irme: Ekim 2026 \u00b7 Ubuntu 24.04 systemd-resolved ve Netplan resm\u00ee belgelerine g\u00f6re<\/p>\n<div id=\"hizli-cozum\" class=\"ai-box ai-box--cozum\">\n<p class=\"ai-box-title\">H\u0131zl\u0131 \u00e7\u00f6z\u00fcm<\/p>\n<p><strong>Temporary failure in name resolution<\/strong> hatas\u0131, sunucunun alan adlar\u0131n\u0131 IP adresine \u00e7eviremedi\u011fini g\u00f6sterir; a\u011f ba\u011flant\u0131s\u0131 \u00e7o\u011fu zaman \u00e7al\u0131\u015f\u0131r, bozuk olan DNS ayar\u0131d\u0131r. Ubuntu 24.04&#8217;te \u015fu s\u0131rayla ilerleyin:<\/p>\n<ol>\n<li><code>ping -c 3 1.1.1.1<\/code> ile a\u011f\u0131n \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131, <code>ping -c 3 ubuntu.com<\/code> ile sorunun DNS&#8217;te oldu\u011funu ay\u0131r\u0131n.<\/li>\n<li><code>resolvectl status<\/code> ile sunucunun hangi DNS sunucular\u0131n\u0131 kulland\u0131\u011f\u0131na bak\u0131n.<\/li>\n<li><code>\/etc\/resolv.conf<\/code> dosyas\u0131n\u0131n systemd-resolved&#8217;a ba\u011fl\u0131 oldu\u011funu do\u011frulay\u0131n.<\/li>\n<li>Netplan yap\u0131land\u0131rmas\u0131na <code>nameservers<\/code> ekleyip <code>sudo netplan try<\/code> ile uygulay\u0131n.<\/li>\n<\/ol>\n<\/div>\n<table class=\"kb-uyg\">\n<tr>\n<th>Panel<\/th>\n<td>SSH (komut sat\u0131r\u0131)<\/td>\n<\/tr>\n<tr>\n<th>Sistem<\/th>\n<td>Ubuntu 24.04 ve 22.04 (systemd-resolved, Netplan)<\/td>\n<\/tr>\n<tr>\n<th>Yetki<\/th>\n<td>root ya da sudo<\/td>\n<\/tr>\n<tr>\n<th>Narhost \u00fcr\u00fcn\u00fc<\/th>\n<td><a href=\"https:\/\/narhost.com\/vps-sunucu\" title=\"Narhost VPS Sunucu paketleri\">VPS Sunucu<\/a>, VDS Sunucu<\/td>\n<\/tr>\n<\/table>\n<div class=\"kb-once\">\n<p class=\"label\">Ba\u015flamadan \u00f6nce<\/p>\n<ul>\n<li>Sunucuya konsol eri\u015fiminiz oldu\u011fundan emin olun; a\u011f ayar\u0131ndaki bir hata SSH ba\u011flant\u0131s\u0131n\u0131 koparabilir.<\/li>\n<li><code>\/etc\/netplan\/<\/code> klas\u00f6r\u00fcndeki dosyan\u0131n yede\u011fini al\u0131n.<\/li>\n<li>Hatan\u0131n hangi komutta \u00e7\u0131kt\u0131\u011f\u0131n\u0131 not edin: <code>apt update<\/code>, <code>ping<\/code>, <code>curl<\/code> ya da bir uygulama.<\/li>\n<\/ul>\n<\/div>\n<h2>Temporary failure in name resolution neden olur<\/h2>\n<p>Ubuntu&#8217;da alan ad\u0131 \u00e7\u00f6z\u00fcmlemesini <code>systemd-resolved<\/code> hizmeti yapar. Programlar <code>\/etc\/resolv.conf<\/code> dosyas\u0131na bakar; bu dosya normalde hizmetin yerel adresini, <code>127.0.0.53<\/code>&#8216;\u00fc g\u00f6sterir ve hizmet iste\u011fi as\u0131l DNS sunucular\u0131na iletir. Zincirin bir halkas\u0131 koptu\u011funda sorgu yan\u0131ts\u0131z kal\u0131r ve bu hata \u00e7\u0131kar. Hizmetin \u00e7al\u0131\u015fma bi\u00e7imi <a href=\"https:\/\/manpages.ubuntu.com\/manpages\/noble\/man8\/systemd-resolved.service.8.html\" title=\"Ubuntu k\u0131lavuz sayfas\u0131 \u2014 systemd-resolved hizmeti\" target=\"_blank\" rel=\"noopener\">systemd-resolved k\u0131lavuz sayfas\u0131nda<\/a> anlat\u0131l\u0131r.<\/p>\n<p>En s\u0131k nedenler: Netplan yap\u0131land\u0131rmas\u0131nda DNS sunucusu tan\u0131ml\u0131 olmamas\u0131, <code>\/etc\/resolv.conf<\/code> dosyas\u0131n\u0131n elle de\u011fi\u015ftirilip ba\u011f\u0131n\u0131n kopmas\u0131, <code>systemd-resolved<\/code> hizmetinin durmas\u0131 ve giden 53 numaral\u0131 port trafi\u011fini engelleyen bir g\u00fcvenlik duvar\u0131 kural\u0131.<\/p>\n<figure class=\"nh-sema\"><img src=\"https:\/\/narhost.com\/destek\/wp-content\/uploads\/2026\/10\/temporary-failure-in-name-resolution-sema-narhost.webp\" alt=\"temporary failure in name resolution \u00e7\u00f6z\u00fcm \u015femas\u0131 \u2014 ping, resolvectl, resolv.conf ve Netplan\" width=\"1200\" height=\"500\" loading=\"lazy\" decoding=\"async\"><figcaption>IP&#x27;ye ping at\u0131l\u0131p ada at\u0131lam\u0131yorsa sorun DNS ayar\u0131ndad\u0131r.<\/figcaption><\/figure>\n<h2>Ad\u0131m ad\u0131m \u00e7\u00f6z\u00fcm<\/h2>\n<ol class=\"kb-adimlar\">\n<li><strong>A\u011f\u0131 ve DNS&#8217;i ay\u0131r\u0131n.<\/strong>\n<pre><code class=\"language-bash\">ping -c 3 1.1.1.1\nping -c 3 ubuntu.com<\/code><\/pre>\n<p class=\"kb-cikti\">Beklenen sonu\u00e7: ilk komut yan\u0131t al\u0131p ikincisi ad \u00e7\u00f6z\u00fcmleme hatas\u0131 veriyorsa a\u011f \u00e7al\u0131\u015f\u0131yor, sorun DNS&#8217;tedir. \u0130lk komut da yan\u0131t alm\u0131yorsa sorun a\u011f ba\u011flant\u0131s\u0131ndad\u0131r.<\/p>\n<\/li>\n<li><strong>Kullan\u0131lan DNS sunucular\u0131na bak\u0131n.<\/strong>\n<pre><code class=\"language-bash\">resolvectl status<\/code><\/pre>\n<p class=\"kb-cikti\">Beklenen sonu\u00e7: a\u011f aray\u00fcz\u00fcn\u00fcn alt\u0131nda <code>DNS Servers:<\/code> sat\u0131r\u0131nda en az bir adres g\u00f6r\u00fcn\u00fcr. Sat\u0131r yoksa sunucuya DNS tan\u0131mlanmam\u0131\u015ft\u0131r.<\/p>\n<\/li>\n<li><strong>resolv.conf ba\u011f\u0131n\u0131 kontrol edin.<\/strong>\n<pre><code class=\"language-bash\">ls -l \/etc\/resolv.conf<\/code><\/pre>\n<p class=\"kb-cikti\">Beklenen sonu\u00e7: dosya <code>..\/run\/systemd\/resolve\/stub-resolv.conf<\/code> dosyas\u0131na ba\u011flant\u0131 olarak g\u00f6r\u00fcn\u00fcr. Ba\u011f kopmu\u015fsa \u015fu komutla yeniden kurun:<\/p>\n<pre><code class=\"language-bash\">sudo ln -sf \/run\/systemd\/resolve\/stub-resolv.conf \/etc\/resolv.conf<\/code><\/pre>\n<\/li>\n<li><strong>Netplan&#8217;a DNS sunucusu ekleyin.<\/strong><code>\/etc\/netplan\/<\/code> alt\u0131ndaki yap\u0131land\u0131rma dosyas\u0131n\u0131 a\u00e7\u0131n ve a\u011f aray\u00fcz\u00fcn\u00fcn alt\u0131na <code>nameservers<\/code> b\u00f6l\u00fcm\u00fcn\u00fc ekleyin. Girintiler bo\u015flukla yaz\u0131l\u0131r:\n<pre><code class=\"language-bash\">network:\n  version: 2\n  ethernets:\n    eth0:\n      nameservers:\n        addresses: [1.1.1.1, 8.8.8.8]<\/code><\/pre>\n<p>Aray\u00fcz ad\u0131n\u0131z farkl\u0131ysa (<code>ens3<\/code> gibi) dosyadaki mevcut ad\u0131 kullan\u0131n. Alanlar\u0131n a\u00e7\u0131klamas\u0131 <a href=\"https:\/\/netplan.readthedocs.io\/en\/stable\/netplan-yaml\/\" title=\"Netplan belgesi \u2014 YAML yap\u0131land\u0131rma alanlar\u0131\" target=\"_blank\" rel=\"noopener\">Netplan belgesinde<\/a>.<\/p>\n<\/li>\n<li><strong>Ayar\u0131 g\u00fcvenli bi\u00e7imde uygulay\u0131n.<\/strong>\n<pre><code class=\"language-bash\">sudo netplan try<\/code><\/pre>\n<p class=\"kb-cikti\">Beklenen sonu\u00e7: Netplan ayar\u0131 uygular ve onay ister. Onay vermezseniz ayar bekleme s\u00fcresi dolunca kendili\u011finden geri al\u0131n\u0131r; b\u00f6ylece hatal\u0131 bir ayar ba\u011flant\u0131n\u0131z\u0131 kal\u0131c\u0131 olarak koparmaz.<\/p>\n<\/li>\n<li><strong>Hizmeti yeniden ba\u015flat\u0131n.<\/strong>\n<pre><code class=\"language-bash\">sudo systemctl restart systemd-resolved\nresolvectl status<\/code><\/pre>\n<\/li>\n<\/ol>\n<div class=\"warn-box\">\n<p class=\"label\">Dikkat<\/p>\n<p>Netplan dosyas\u0131nda IP adresi ve a\u011f ge\u00e7idi sat\u0131rlar\u0131n\u0131 de\u011fi\u015ftirmeyin; yaln\u0131z <code>nameservers<\/code> b\u00f6l\u00fcm\u00fcn\u00fc ekleyin. Yanl\u0131\u015f bir adres ya da girinti hatas\u0131 sunucuyu a\u011fdan koparabilir. <code>netplan apply<\/code> yerine <code>netplan try<\/code> kullanman\u0131z bu y\u00fczden \u00f6nemlidir.<\/p>\n<\/div>\n<h2>Do\u011frulama<\/h2>\n<div class=\"success-box\">\n<p class=\"label\">Sonu\u00e7<\/p>\n<p><code>resolvectl query ubuntu.com<\/code> bir IP adresi d\u00f6nd\u00fcr\u00fcyor ve <code>sudo apt update<\/code> depo adreslerine hatas\u0131z ba\u011flan\u0131yorsa temporary failure in name resolution hatas\u0131 giderilmi\u015ftir.<\/p>\n<\/div>\n<h2>H\u00e2l\u00e2 \u00e7\u00f6z\u00fclmediyse<\/h2>\n<ul>\n<li><strong>A\u011f hi\u00e7 \u00e7al\u0131\u015fm\u0131yor.<\/strong><code>ping 1.1.1.1<\/code> de yan\u0131t alm\u0131yorsa sorun DNS&#8217;ten \u00f6nce a\u011f yap\u0131land\u0131rmas\u0131ndad\u0131r; dosyan\u0131n yeri <a href=\"https:\/\/narhost.com\/destek\/ubuntu-network-konfigurasyon-dosya-yolu\/\" title=\"Ubuntu A\u011f Yap\u0131land\u0131rma Dosya Yolu \u2014 Narhost Destek Merkezi\">Ubuntu a\u011f yap\u0131land\u0131rma dosya yolu<\/a> kart\u0131nda.<\/li>\n<li><strong>sudo komutu &#8220;unable to resolve host&#8221; diyor.<\/strong> Bu farkl\u0131 bir sorundur: sunucunun kendi ad\u0131 <code>\/etc\/hosts<\/code> dosyas\u0131nda tan\u0131ml\u0131 de\u011fildir. Dosyaya <code>127.0.1.1<\/code> sat\u0131r\u0131yla sunucu ad\u0131n\u0131 ekleyin.<\/li>\n<li><strong>Yaln\u0131z tek bir alan ad\u0131 \u00e7\u00f6z\u00fclm\u00fcyor.<\/strong> Sorun sunucuda de\u011fil o alan ad\u0131n\u0131n kay\u0131tlar\u0131ndad\u0131r; <a href=\"https:\/\/narhost.com\/destek\/nslookup-ile-dns-sorgulama\/\" title=\"nslookup ile DNS Sorgulama \u2014 Narhost Destek Merkezi\">nslookup ile DNS sorgulama<\/a> kart\u0131yla kontrol edin.<\/li>\n<\/ul>\n<div class=\"cta-box\">\n<p class=\"label\">Narhost deste\u011fi<\/p>\n<p>VPS ve VDS sunucular y\u00f6netimsizdir; sunucu i\u00e7indeki ayar sizin sorumlulu\u011funuzdad\u0131r. A\u011f ya da konsol eri\u015fiminde sorun varsa talebe \u015funlar\u0131 ekleyin: sunucu ad\u0131, <code>resolvectl status<\/code> \u00e7\u0131kt\u0131s\u0131, hatan\u0131n ba\u015flad\u0131\u011f\u0131 tarih ve son yapt\u0131\u011f\u0131n\u0131z de\u011fi\u015fiklik.<\/p>\n<p><a class=\"cta-btn\" href=\"https:\/\/narhost.com\/submitticket.php\" title=\"Narhost destek talebi a\u00e7\">Destek talebi a\u00e7<\/a><\/div>\n<div class=\"kb-ilgili\">\n<p class=\"label\">Sonraki ad\u0131mlar<\/p>\n<ul>\n<li><a href=\"https:\/\/narhost.com\/destek\/sunucuya-ping-atilamiyorsa-ne-yapilmali\/\" title=\"Sunucuya Ping At\u0131lam\u0131yorsa Ne Yap\u0131lmal\u0131 \u2014 Narhost Destek Merkezi\">Sunucuya ping at\u0131lam\u0131yorsa ne yap\u0131lmal\u0131<\/a><\/li>\n<li><a href=\"https:\/\/narhost.com\/destek\/dns-sunucusu-yanit-vermiyor-hatasi\/\" title=\"DNS Sunucusu Yan\u0131t Vermiyor Hatas\u0131 \u2014 Narhost Destek Merkezi\">DNS sunucusu yan\u0131t vermiyor hatas\u0131<\/a><\/li>\n<li><a href=\"https:\/\/narhost.com\/destek\/linux-kullanici-ekleme-sudo-yetkisi\/\" title=\"Linux&#039;ta Kullan\u0131c\u0131 Ekleme ve Sudo Yetkisi \u2014 Narhost Destek Merkezi\">Linux&#8217;ta kullan\u0131c\u0131 ekleme ve sudo yetkisi<\/a><\/li>\n<\/ul>\n<\/div>\n<div class=\"kb-faq\">\n<h2>S\u0131k\u00e7a sorulan sorular<\/h2>\n<h3>resolv.conf dosyas\u0131n\u0131 do\u011frudan d\u00fczenleyebilir miyim?<\/h3>\n<p>D\u00fczenleyebilirsiniz ama kal\u0131c\u0131 olmaz; dosya systemd-resolved taraf\u0131ndan y\u00f6netildi\u011fi i\u00e7in yeniden ba\u015flatmada ya da a\u011f de\u011fi\u015fikli\u011finde \u00fczerine yaz\u0131l\u0131r. Kal\u0131c\u0131 DNS ayar\u0131 Netplan yap\u0131land\u0131rmas\u0131nda yap\u0131l\u0131r.<\/p>\n<h3>Hata yaln\u0131z apt update s\u0131ras\u0131nda \u00e7\u0131k\u0131yor, neden?<\/h3>\n<p>Paket deposu adresleri \u00e7\u00f6z\u00fclemiyordur ve ayn\u0131 sorun di\u011fer komutlarda da vard\u0131r, yaln\u0131z ilk orada fark edilir. DNS d\u00fczeldi\u011finde apt da \u00e7al\u0131\u015f\u0131r. Proxy kullanan sunucularda apt&#8217;nin proxy ayar\u0131n\u0131 da kontrol edin.<\/p>\n<h3>Docker konteynerinde ayn\u0131 hata \u00e7\u0131k\u0131yor, ne yapmal\u0131y\u0131m?<\/h3>\n<p>Konteyner DNS ayar\u0131n\u0131 sunucudan al\u0131r. \u00d6nce sunucuda \u00e7\u00f6z\u00fcmlemenin \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 do\u011frulay\u0131n; sunucuda \u00e7al\u0131\u015f\u0131yor ama konteynerde \u00e7al\u0131\u015fm\u0131yorsa Docker&#8217;\u0131n DNS ayar\u0131 ayr\u0131ca yap\u0131land\u0131r\u0131lmal\u0131d\u0131r.<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>Ubuntu 24.04&#8217;te temporary failure in name resolution hatas\u0131n\u0131n nedeni ve \u00e7\u00f6z\u00fcm\u00fc: a\u011f ile DNS&#8217;i ay\u0131rma, resolvectl status, resolv.conf ba\u011f\u0131, Netplan&#8217;a nameservers ekleme ve netplan try ile g\u00fcvenli uygulama.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[12,13],"tags":[190],"class_list":["post-2972","post","type-post","status-publish","format-standard","hentry","category-vds-server","category-vps-server","tag-netplan"],"meta_box":[],"_links":{"self":[{"href":"https:\/\/narhost.com\/destek\/wp-json\/wp\/v2\/posts\/2972","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/narhost.com\/destek\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/narhost.com\/destek\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/narhost.com\/destek\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/narhost.com\/destek\/wp-json\/wp\/v2\/comments?post=2972"}],"version-history":[{"count":1,"href":"https:\/\/narhost.com\/destek\/wp-json\/wp\/v2\/posts\/2972\/revisions"}],"predecessor-version":[{"id":3030,"href":"https:\/\/narhost.com\/destek\/wp-json\/wp\/v2\/posts\/2972\/revisions\/3030"}],"wp:attachment":[{"href":"https:\/\/narhost.com\/destek\/wp-json\/wp\/v2\/media?parent=2972"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/narhost.com\/destek\/wp-json\/wp\/v2\/categories?post=2972"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/narhost.com\/destek\/wp-json\/wp\/v2\/tags?post=2972"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}