{"id":966,"date":"2026-09-27T09:46:49","date_gmt":"2026-09-27T09:46:49","guid":{"rendered":"https:\/\/www.vps.tc\/blog\/?p=966"},"modified":"2026-09-27T09:21:12","modified_gmt":"2026-09-27T09:21:12","slug":"ubuntu-statik-ip-ayarlama-netplan","status":"publish","type":"post","link":"https:\/\/www.vps.tc\/blog\/tr\/ubuntu-statik-ip-ayarlama-netplan\/","title":{"rendered":"Ubuntu&#8217;da Statik IP Ayarlama: Netplan Rehberi"},"content":{"rendered":"<div class=\"aiw-summary\" id=\"aiw-ozet\">\n<p class=\"aiw-summary-title\">H\u0131zl\u0131 \u00d6zet &#8211; Ubuntu Statik IP Ayarlama<\/p>\n<p>Netplan, Ubuntu&#039;da a\u011f adresi, varsay\u0131lan rota ve DNS ayarlar\u0131n\u0131 YAML dosyalar\u0131 \u00fczerinden y\u00f6netir. De\u011fi\u015fikli\u011fi uygulamadan \u00f6nce aray\u00fcz ad\u0131n\u0131 ve sa\u011flay\u0131c\u0131n\u0131n verdi\u011fi a\u011f bilgilerini do\u011frulay\u0131n.<\/p>\n<ul>\n<li><strong>Dosyay\u0131 bulun<\/strong> \u2014 Yap\u0131land\u0131rma dosyalar\u0131 \u00e7o\u011funlukla \/etc\/netplan\/ dizinindedir.<\/li>\n<li><strong>Aray\u00fcz\u00fc do\u011frulay\u0131n<\/strong> \u2014 ip -br link \u00e7\u0131kt\u0131s\u0131ndaki ger\u00e7ek aray\u00fcz ad\u0131n\u0131 YAML i\u00e7inde kullan\u0131n.<\/li>\n<li><strong>Prefix yaz\u0131n<\/strong> \u2014 IP adresini 192.168.1.50\/24 gibi a\u011f prefix&#039;iyle birlikte tan\u0131mlay\u0131n.<\/li>\n<li><strong>Rotay\u0131 ekleyin<\/strong> \u2014 Varsay\u0131lan gateway&#039;i routes alt\u0131nda to: default ve via ile belirtin.<\/li>\n<li><strong>G\u00fcvenli uygulay\u0131n<\/strong> \u2014 Uzak SSH oturumlar\u0131nda \u00f6nce netplan try, ard\u0131ndan do\u011frulama testleri kullan\u0131n.<\/li>\n<li><strong>Ba\u011flant\u0131y\u0131 s\u0131nay\u0131n<\/strong> \u2014 IP, gateway, d\u0131\u015f adres, DNS ve servis portlar\u0131n\u0131 birbirinden ayr\u0131 test edin.<\/li>\n<\/ul>\n<\/div>\n<p class=\"aiw-lead\">Ubuntu&#039;da statik IP ayarlamak i\u00e7in \/etc\/netplan\/ alt\u0131nda bir YAML dosyas\u0131nda DHCP&#039;yi kapat\u0131p adres, prefix, varsay\u0131lan rota ve DNS sunucular\u0131n\u0131 tan\u0131mlay\u0131n. \u00d6nce netplan generate ile dosyay\u0131 do\u011frulay\u0131n, uzak ba\u011flant\u0131da netplan try kullan\u0131n ve IP, gateway ile DNS&#039;i ayr\u0131 komutlarla test edin.<\/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 11 dk okuma<\/span><\/p>\n<ol style=\"margin:10px 0 0;padding-left:22px\">\n<li><a href=\"#ubuntuda-statik-ip-neden-kullanilir\">Ubuntu&#039;da Statik IP Neden Kullan\u0131l\u0131r?<\/a><\/li>\n<li><a href=\"#netplan-dosyasi-nerede-bulunur\">Netplan Dosyas\u0131 Nerede Bulunur?<\/a><\/li>\n<li><a href=\"#ubuntuda-statik-ip-nasil-ayarlanir\">Ubuntu&#039;da Statik IP Nas\u0131l Ayarlan\u0131r?<\/a><\/li>\n<li><a href=\"#netplan-degisikligi-nasil-guvenli-uygulanir\">Netplan De\u011fi\u015fikli\u011fi Nas\u0131l G\u00fcvenli Uygulan\u0131r?<\/a><\/li>\n<li><a href=\"#statik-ip-ayarindan-sonra-baglanti-nasil-test-edilir\">Statik IP Ayar\u0131ndan Sonra Ba\u011flant\u0131 Nas\u0131l Test Edilir?<\/a><\/li>\n<li><a href=\"#ipv6-icin-netplan-yapilandirmasi\">IPv6 \u0130\u00e7in Netplan Yap\u0131land\u0131rmas\u0131<\/a><\/li>\n<li><a href=\"#yaygin-netplan-hatalari-ve-cozumleri\">Yayg\u0131n Netplan Hatalar\u0131 ve \u00c7\u00f6z\u00fcmleri<\/a><\/li>\n<li><a href=\"#statik-ip-degisikligini-geri-alma\">Statik IP De\u011fi\u015fikli\u011fini Geri Alma<\/a><\/li>\n<li><a href=\"#ubuntu-statik-ip-ayarlama-icin-saglam-is-akisi\">Ubuntu Statik IP Ayarlama \u0130\u00e7in Sa\u011flam \u0130\u015f Ak\u0131\u015f\u0131<\/a><\/li>\n<li><a href=\"#statik-ip-uygulamadan-once-kontrol-edin\">Statik IP Uygulamadan \u00d6nce 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=\"ubuntuda-statik-ip-neden-kullanilir\">Ubuntu&#8217;da Statik IP Neden Kullan\u0131l\u0131r?<\/h2>\n<p>Ubuntu Server, a\u011f yap\u0131land\u0131rmas\u0131n\u0131 s\u00fcr\u00fcme ve kurulum y\u00f6ntemine g\u00f6re farkl\u0131 ara\u00e7larla y\u00f6netebilir. Ubuntu 18.04 ve sonraki bir\u00e7ok kurulumda bu g\u00f6rev Netplan taraf\u0131ndan \u00fcstlenilir. Netplan, YAML dosyas\u0131n\u0131 okuyarak NetworkManager veya systemd-networkd i\u00e7in yap\u0131land\u0131rma \u00fcretir. Bu nedenle Ubuntu statik IP ayarlama i\u015fleminde do\u011fru dosyay\u0131 bulmak kadar YAML girintisini ve aray\u00fcz ad\u0131n\u0131 do\u011fru yazmak da gerekir.<\/p>\n<p>Statik IP, sunucunun her yeniden ba\u015flatmada ayn\u0131 yerel veya genel IP adresini kullanmas\u0131n\u0131 sa\u011flar. Web sunucusu, DNS, VPN, izleme sistemi ve uzak y\u00f6netim servislerinde bu kararl\u0131l\u0131k gerekir. DHCP ile al\u0131nan adres de\u011fi\u015fti\u011finde SSH eri\u015fimi, DNS kay\u0131tlar\u0131 veya g\u00fcvenlik duvar\u0131 kurallar\u0131 beklenmedik bi\u00e7imde bozulabilir.<\/p>\n<p>Ev a\u011f\u0131 ya da veri merkezi i\u00e7indeki \u00f6zel adresler i\u00e7in RFC 1918&#8217;de tan\u0131mlanan <code>10.0.0.0\/8<\/code>, <code>172.16.0.0\/12<\/code> ve <code>192.168.0.0\/16<\/code> aral\u0131klar\u0131 kullan\u0131l\u0131r. \u0130nternete do\u011frudan \u00e7\u0131kan bir sunucuda ise sa\u011flay\u0131c\u0131n\u0131n tahsis etti\u011fi IP, a\u011f ge\u00e7idi ve prefix de\u011feri esas al\u0131nmal\u0131d\u0131r.<\/p>\n<table>\n<thead>\n<tr>\n<th>Yap\u0131land\u0131rma<\/th>\n<th>Adres kayna\u011f\u0131<\/th>\n<th>Uygun kullan\u0131m<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>DHCP<\/td>\n<td>Router veya DHCP sunucusu<\/td>\n<td>Ge\u00e7ici makineler, istemciler<\/td>\n<\/tr>\n<tr>\n<td>Statik IP<\/td>\n<td>YAML dosyas\u0131nda sabit tan\u0131m<\/td>\n<td>VPS, web, DNS ve VPN sunucular\u0131<\/td>\n<\/tr>\n<tr>\n<td>DHCP rezervasyonu<\/td>\n<td>MAC adresine ba\u011fl\u0131 DHCP kayd\u0131<\/td>\n<td>Ev ve k\u00fc\u00e7\u00fck ofis a\u011flar\u0131<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><strong>Ne yap\u0131lmal\u0131<\/strong> &#8211; Statik adres vermeden \u00f6nce sa\u011flay\u0131c\u0131n\u0131zdan IP, prefix, gateway ve DNS bilgilerini ayn\u0131 formatta teyit edin.<\/p>\n<h2 id=\"netplan-dosyasi-nerede-bulunur\">Netplan Dosyas\u0131 Nerede Bulunur?<\/h2>\n<p>Netplan yap\u0131land\u0131rmalar\u0131 genellikle <code>\/etc\/netplan\/<\/code> dizininde yer al\u0131r. Dosya ad\u0131 da\u011f\u0131t\u0131ma ve kurulum arac\u0131na g\u00f6re de\u011fi\u015febilir; <code>00-installer-config.yaml<\/code>, <code>50-cloud-init.yaml<\/code> ve <code>99-netcfg.yaml<\/code> gibi adlar g\u00f6r\u00fclebilir. \u00d6nce mevcut dosyalar\u0131 ve i\u00e7erikleri inceleyin:<\/p>\n<pre><code>ls -l \/etc\/netplan\/\nsudo sed -n '1,160p' \/etc\/netplan\/*.yaml<\/code><\/pre>\n<p>Birden fazla YAML dosyas\u0131 varsa ayarlar\u0131n \u00e7ak\u0131\u015fma ihtimali vard\u0131r. Netplan yap\u0131land\u0131rma dosyalar\u0131n\u0131 adlar\u0131na g\u00f6re i\u015fler; daha sonra gelen dosya, ayn\u0131 anahtarlar i\u00e7in \u00f6nceki tan\u0131mlar\u0131 etkileyebilir. Cloud-init taraf\u0131ndan \u00fcretilen dosyalarda do\u011frudan de\u011fi\u015fiklik yapmak, sonraki a\u00e7\u0131l\u0131\u015fta ayar\u0131n \u00fczerine yaz\u0131lmas\u0131na yol a\u00e7abilir.<\/p>\n<p>De\u011fi\u015fiklikten \u00f6nce dosyalar\u0131n yede\u011fini al\u0131n ve etkin yap\u0131land\u0131rmay\u0131 kontrol edin:<\/p>\n<pre><code>sudo cp -a \/etc\/netplan \/etc\/netplan.backup.$(date +%F-%H%M)\nnetplan get\nnetworkctl status 2&gt;\/dev\/null || true<\/code><\/pre>\n<p><code>netplan get<\/code>, birden fazla dosyadan olu\u015fan etkin yap\u0131land\u0131rmay\u0131 daha anla\u015f\u0131l\u0131r bi\u00e7imde g\u00f6sterir. <code>networkctl<\/code> \u00e7\u0131kt\u0131s\u0131 systemd-networkd kullan\u0131l\u0131yorsa anlaml\u0131d\u0131r; NetworkManager kullan\u0131lan kurulumlarda <code>nmcli device status<\/code> daha yararl\u0131 olur.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131<\/strong> &#8211; De\u011fi\u015fiklikten \u00f6nce <code>\/etc\/netplan\/<\/code> dizinini yedekleyin ve etkin dosyan\u0131n cloud-init taraf\u0131ndan y\u00f6netilip y\u00f6netilmedi\u011fini kontrol edin.<\/p>\n<h2 id=\"ubuntuda-statik-ip-nasil-ayarlanir\">Ubuntu&#8217;da Statik IP Nas\u0131l Ayarlan\u0131r?<\/h2>\n<p>A\u015fa\u011f\u0131daki \u00f6rnekte aray\u00fcz ad\u0131 <code>ens18<\/code>, IPv4 adresi <code>192.168.1.50<\/code>, a\u011f prefix&#8217;i <code>\/24<\/code> ve a\u011f ge\u00e7idi <code>192.168.1.1<\/code> kabul edilmi\u015ftir. Bu de\u011ferleri kopyalamak yerine kendi a\u011f\u0131n\u0131za ait bilgilerle de\u011fi\u015ftirin. \u00d6nce ger\u00e7ek aray\u00fcz ad\u0131n\u0131 bulun:<\/p>\n<pre><code>ip -br link\nip -br address<\/code><\/pre>\n<p>\u00c7\u0131kt\u0131da <code>ens18<\/code>, <code>enp1s0<\/code> veya <code>eth0<\/code> gibi bir ad g\u00f6rebilirsiniz. <code>lo<\/code> loopback aray\u00fcz\u00fcd\u00fcr; statik IP i\u00e7in onu se\u00e7meyin. YAML dosyas\u0131n\u0131 d\u00fczenlemek i\u00e7in sunucuda bulunma ihtimali y\u00fcksek olan <code>vim<\/code> veya <code>nano<\/code> kullan\u0131labilir:<\/p>\n<pre><code>sudo vim \/etc\/netplan\/50-static-ip.yaml<\/code><\/pre>\n<p>Netplan&#8217;\u0131n ikinci s\u00fcr\u00fcm s\u00f6zdizimiyle temel bir IPv4 yap\u0131land\u0131rmas\u0131 \u015f\u00f6yledir:<\/p>\n<pre><code>network:\n  version: 2\n  ethernets:\n    ens18:\n      dhcp4: false\n      addresses:\n        - 192.168.1.50\/24\n      routes:\n        - to: default\n          via: 192.168.1.1\n      nameservers:\n        addresses:\n          - 1.1.1.1\n          - 9.9.9.9<\/code><\/pre>\n<p><code>version: 2<\/code> Netplan yap\u0131land\u0131rma bi\u00e7iminin s\u00fcr\u00fcm\u00fcn\u00fc belirtir. <code>dhcp4: false<\/code> IPv4 adresinin DHCP&#8217;den al\u0131nmas\u0131n\u0131 kapat\u0131r. <code>addresses<\/code> alt\u0131nda adres prefix ile birlikte yaz\u0131l\u0131r; <code>192.168.1.50\/24<\/code>, <code>255.255.255.0<\/code> maskesine kar\u015f\u0131l\u0131k gelir. Varsay\u0131lan rota, eski \u00f6rneklerde g\u00f6r\u00fclen <code>gateway4<\/code> yerine <code>routes<\/code> alt\u0131nda tan\u0131mlanabilir.<\/p>\n<p>Netplan belgelerinde varsay\u0131lan rota i\u00e7in <code>to: default<\/code> ve <code>via:<\/code> bi\u00e7imi g\u00f6sterilir. Baz\u0131 Ubuntu s\u00fcr\u00fcmlerinde <code>gateway4<\/code> h\u00e2l\u00e2 \u00e7al\u0131\u015fsa da yeni yap\u0131land\u0131rmalarda rota tan\u0131m\u0131 tercih edilmelidir. DNS adresleri yaln\u0131zca isim \u00e7\u00f6z\u00fcmlemesi i\u00e7indir; DNS sunucusu yazmak, varsay\u0131lan a\u011f ge\u00e7idini tan\u0131mlamaz.<\/p>\n<h3>YAML girintisi neden bu kadar \u00f6nemli?<\/h3>\n<p>YAML&#8217;de blok yap\u0131s\u0131 bo\u015fluklarla belirlenir. Tab karakteri kullanmak veya ayn\u0131 seviyedeki anahtarlar\u0131 farkl\u0131 girintilemek s\u00f6zdizimi hatas\u0131na neden olur. \u00d6rnekte her seviye iki bo\u015flukla ilerler. <code>ens18<\/code> sat\u0131r\u0131 <code>ethernets<\/code> alt\u0131nda, <code>dhcp4<\/code> ve <code>addresses<\/code> ise <code>ens18<\/code> alt\u0131nda olmal\u0131d\u0131r.<\/p>\n<pre><code>sudo netplan generate<\/code><\/pre>\n<p>Bu komut yap\u0131land\u0131rmay\u0131 do\u011frular ve ilgili backend i\u00e7in dosyalar\u0131 \u00fcretir; do\u011frudan a\u011f ba\u011flant\u0131s\u0131n\u0131 de\u011fi\u015ftirmez. Hata al\u0131rsan\u0131z iki noktaya bak\u0131n: aray\u00fcz ad\u0131n\u0131n <code>ip -br link<\/code> \u00e7\u0131kt\u0131s\u0131yla e\u015fle\u015fmesi ve YAML&#8217;de tab kullan\u0131lmamas\u0131.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131<\/strong> &#8211; Aray\u00fcz ad\u0131n\u0131 sistemden do\u011frulay\u0131n, adresi prefix ile yaz\u0131n ve de\u011fi\u015fiklikten \u00f6nce <code>netplan generate<\/code> ile s\u00f6zdizimini test edin.<\/p>\n<div class=\"aiw-callout aiw-callout-warn\">\n<p class=\"aiw-callout-label\">Dikkat<\/p>\n<p>YAML i\u00e7inde tab karakteri kullanmay\u0131n ve aray\u00fcz ad\u0131n\u0131 tahmin etmeyin. ip -br link \u00e7\u0131kt\u0131s\u0131nda olmayan bir ad yazmak, do\u011fru g\u00f6r\u00fcnen dosyan\u0131n hi\u00e7bir cihaza uygulanmamas\u0131na neden olur.<\/p>\n<\/div>\n<h2 id=\"netplan-degisikligi-nasil-guvenli-uygulanir\">Netplan De\u011fi\u015fikli\u011fi Nas\u0131l G\u00fcvenli Uygulan\u0131r?<\/h2>\n<p>Uzak SSH oturumunda do\u011frudan <code>netplan apply<\/code> \u00e7al\u0131\u015ft\u0131rmak risklidir. Yanl\u0131\u015f gateway veya aray\u00fcz ad\u0131 ba\u011flant\u0131y\u0131 an\u0131nda kesebilir. Etkile\u015fimli <code>netplan try<\/code> komutu yap\u0131land\u0131rmay\u0131 ge\u00e7ici olarak uygular ve belirli s\u00fcre i\u00e7inde onay verilmezse \u00f6nceki ayara d\u00f6nmeye \u00e7al\u0131\u015f\u0131r.<\/p>\n<pre><code>sudo netplan try<\/code><\/pre>\n<p>Yeni ayar do\u011fruysa komutun istedi\u011fi onay\u0131 verin. SSH oturumu koparsa sa\u011flay\u0131c\u0131n\u0131n VNC, serial console veya web tabanl\u0131 kurtarma konsoluna ge\u00e7in. <code>netplan try<\/code> her senaryoda kurtarma garantisi de\u011fildir; konsol eri\u015fimi bulunmayan kritik VPS&#8217;lerde sa\u011flay\u0131c\u0131n\u0131n out-of-band eri\u015fimini \u00f6nceden do\u011frulamak gerekir.<\/p>\n<p>Yerel konsol veya eri\u015fimin garanti oldu\u011fu bir ortamda son uygulama \u015fu \u015fekilde yap\u0131labilir:<\/p>\n<pre><code>sudo netplan apply\nip -4 address show dev ens18\nip route\nresolvectl status<\/code><\/pre>\n<p><code>ip -4 address<\/code> do\u011fru IP&#8217;nin aray\u00fcze eklendi\u011fini, <code>ip route<\/code> varsay\u0131lan rotay\u0131, <code>resolvectl status<\/code> ise DNS sunucular\u0131n\u0131 g\u00f6sterir. Sadece ping ba\u015far\u0131l\u0131 diye yap\u0131land\u0131rmay\u0131 tamamlanm\u0131\u015f saymay\u0131n; IP&#8217;ye eri\u015fmek ile alan ad\u0131 \u00e7\u00f6z\u00fcmlemek farkl\u0131 testlerdir.<\/p>\n<div class=\"aiw-callout aiw-callout-tip\">\n<p class=\"aiw-callout-label\">\u0130pucu<\/p>\n<p>De\u011fi\u015fiklikten \u00f6nce ikinci bir SSH oturumu veya sa\u011flay\u0131c\u0131n\u0131n web konsolunu haz\u0131r tutun. Uzak sunucuda netplan try kullanmak, onay verilmedi\u011finde \u00f6nceki a\u011f ayar\u0131na d\u00f6nme \u015fans\u0131 sa\u011flar.<\/p>\n<\/div>\n<h2 id=\"statik-ip-ayarindan-sonra-baglanti-nasil-test-edilir\">Statik IP Ayar\u0131ndan Sonra Ba\u011flant\u0131 Nas\u0131l Test Edilir?<\/h2>\n<p>Testleri katmanl\u0131 yap\u0131n. \u00d6nce yerel adresi, ard\u0131ndan gateway&#8217;i, sonra d\u0131\u015f IP&#8217;yi ve en son DNS \u00e7\u00f6z\u00fcmlemesini kontrol edin:<\/p>\n<pre><code>ip -4 addr show dev ens18\nip route get 192.168.1.1\nping -c 4 192.168.1.1\nping -c 4 1.1.1.1\ndig +short A example.com<\/code><\/pre>\n<p>Gateway&#8217;e ping ba\u015far\u0131s\u0131zsa sorun \u00e7o\u011funlukla prefix, VLAN, kablo, sanal switch veya gateway de\u011ferindedir. <code>1.1.1.1<\/code> yan\u0131t veriyor ancak <code>dig +short A example.com<\/code> bo\u015f d\u00f6n\u00fcyorsa IP y\u00f6nlendirmesi \u00e7al\u0131\u015f\u0131yor, DNS yap\u0131land\u0131rmas\u0131 \u00e7al\u0131\u015fm\u0131yor olabilir. ICMP g\u00fcvenlik duvar\u0131 taraf\u0131ndan engellenebilece\u011fi i\u00e7in tek ba\u015f\u0131na ping sonucunu kesin karar gibi yorumlamay\u0131n.<\/p>\n<p>Varsay\u0131lan rotay\u0131 daha ayr\u0131nt\u0131l\u0131 g\u00f6rmek i\u00e7in:<\/p>\n<pre><code>ip route show default\nresolvectl query example.com\nsudo ss -tulpen<\/code><\/pre>\n<p>Sunucuya SSH ile eri\u015fim de ayr\u0131ca test edilmelidir. SSH varsay\u0131lan olarak TCP <code>22<\/code> portunu kullan\u0131r, fakat sisteminizde farkl\u0131 bir port tan\u0131ml\u0131 olabilir. Uzak bir makineden <code>nc -vz 192.168.1.50 22<\/code> komutuyla port eri\u015fimini kontrol edebilirsiniz. SSH portunu de\u011fi\u015ftirmek tek ba\u015f\u0131na g\u00fcvenlik politikas\u0131 de\u011fildir; eri\u015fimi kaynak IP&#8217;lerle s\u0131n\u0131rlamak ve loglar\u0131 izlemek daha anlaml\u0131d\u0131r.<\/p>\n<p>Yerel a\u011fdaki adres plan\u0131n\u0131 hesaplarken <a href=\"#\">CIDR Nedir? IP Aral\u0131\u011f\u0131 Hesaplama Rehberi<\/a> ba\u015fl\u0131kl\u0131 i\u00e7erikteki prefix a\u00e7\u0131klamalar\u0131ndan yararlanabilirsiniz. B\u00f6ylece <code>\/24<\/code> ile <code>\/32<\/code> aras\u0131ndaki fark\u0131, kullan\u0131labilir host aral\u0131\u011f\u0131n\u0131 ve gateway&#8217;in hangi a\u011fda bulunmas\u0131 gerekti\u011fini kar\u0131\u015ft\u0131rmazs\u0131n\u0131z.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131<\/strong> &#8211; Gateway, d\u0131\u015f IP ve DNS \u00e7\u00f6z\u00fcmlemesini ayr\u0131 komutlarla test edin; tek bir ba\u015far\u0131l\u0131 ping sonucuna g\u00fcvenmeyin.<\/p>\n<div class=\"aiw-callout aiw-callout-example\">\n<p class=\"aiw-callout-label\">\u00d6rnek<\/p>\n<p>192.168.1.50\/24 adresi i\u00e7in 192.168.1.1 gateway&#039;i ayn\u0131 \/24 a\u011f\u0131nda bulunur. Gateway&#039;i 192.168.2.1 yazmak, adres do\u011fru olsa bile varsay\u0131lan rotan\u0131n eri\u015filememesine yol a\u00e7ar.<\/p>\n<\/div>\n<h2 id=\"ipv6-icin-netplan-yapilandirmasi\">IPv6 \u0130\u00e7in Netplan Yap\u0131land\u0131rmas\u0131<\/h2>\n<p>Sa\u011flay\u0131c\u0131n\u0131z IPv6 veriyorsa IPv4 tan\u0131m\u0131n\u0131n yan\u0131na IPv6 adresi ekleyebilirsiniz. \u00d6rnekte <code>2001:db8::50\/64<\/code> dok\u00fcmantasyon i\u00e7in ayr\u0131lm\u0131\u015f \u00f6rnek bir adrestir; internette kullan\u0131labilir ger\u00e7ek bir adres de\u011fildir. IPv6 i\u00e7in gateway, sa\u011flay\u0131c\u0131n\u0131n verdi\u011fi de\u011fer olmal\u0131d\u0131r.<\/p>\n<pre><code>network:\n  version: 2\n  ethernets:\n    ens18:\n      dhcp4: false\n      dhcp6: false\n      addresses:\n        - 192.168.1.50\/24\n        - 2001:db8::50\/64\n      routes:\n        - to: default\n          via: 192.168.1.1\n        - to: ::\/0\n          via: 2001:db8::1\n      nameservers:\n        addresses:\n          - 1.1.1.1\n          - 2606:4700:4700::1111<\/code><\/pre>\n<p>IPv6 adresi, prefix&#8217;i ve gateway&#8217;i sa\u011flay\u0131c\u0131dan ba\u011f\u0131ms\u0131z olarak tahmin etmeyin. Baz\u0131 veri merkezleri router advertisement veya DHCPv6 kullan\u0131r; bu durumda <code>dhcp6<\/code> ve <code>accept-ra<\/code> se\u00e7enekleri sa\u011flay\u0131c\u0131n\u0131n tasar\u0131m\u0131na g\u00f6re de\u011fi\u015febilir. Yanl\u0131\u015f IPv6 varsay\u0131lan rotas\u0131, IPv4 d\u00fczg\u00fcn \u00e7al\u0131\u015f\u0131rken baz\u0131 uygulamalar\u0131n ba\u011flant\u0131y\u0131 geciktirmesine yol a\u00e7abilir.<\/p>\n<h2 id=\"yaygin-netplan-hatalari-ve-cozumleri\">Yayg\u0131n Netplan Hatalar\u0131 ve \u00c7\u00f6z\u00fcmleri<\/h2>\n<h3>&#8220;Invalid YAML&#8221; veya girinti hatas\u0131<\/h3>\n<p>Tab karakteri, eksik iki nokta veya yanl\u0131\u015f seviyedeki liste i\u015fareti en s\u0131k g\u00f6r\u00fclen nedenlerdir. Dosyay\u0131 bir YAML do\u011frulay\u0131c\u0131ya y\u00fcklemek yerine \u00f6nce sunucuda <code>netplan generate<\/code> \u00e7al\u0131\u015ft\u0131r\u0131n; gizli bilgiler i\u00e7eren dosyalar\u0131 \u00fc\u00e7\u00fcnc\u00fc taraf ara\u00e7lara g\u00f6ndermeyin.<\/p>\n<h3>&#8220;Cannot find device&#8221; hatas\u0131<\/h3>\n<p>YAML&#8217;deki aray\u00fcz ad\u0131 sistemde yoktur. <code>ip -br link<\/code> ile ger\u00e7ek ad\u0131 bulun. Cloud imajlar\u0131nda aray\u00fcz ad\u0131 yeniden \u00fcretilebildi\u011fi i\u00e7in MAC e\u015flemesi veya cloud-init ayarlar\u0131 da kontrol edilmelidir.<\/p>\n<h3>Gateway eri\u015filemiyor<\/h3>\n<p>IP adresi ile gateway ayn\u0131 subnet i\u00e7inde olmayabilir. \u00d6rne\u011fin <code>192.168.1.50\/24<\/code> adresi i\u00e7in <code>192.168.2.1<\/code> gateway&#8217;i do\u011frudan eri\u015filebilir de\u011fildir. VLAN etiketi, sanal switch ba\u011flant\u0131s\u0131 ve sa\u011flay\u0131c\u0131n\u0131n ek route gerektirip gerektirmedi\u011fi incelenmelidir.<\/p>\n<h3>DNS \u00e7al\u0131\u015fm\u0131yor<\/h3>\n<p><code>ip route<\/code> do\u011fru oldu\u011fu h\u00e2lde alan adlar\u0131 \u00e7\u00f6z\u00fclm\u00fcyorsa <code>resolvectl status<\/code> ve <code>\/etc\/resolv.conf<\/code> ba\u011flant\u0131s\u0131n\u0131 kontrol edin. Ubuntu&#8217;da <code>\/etc\/resolv.conf<\/code> \u00e7o\u011fu kurulumda systemd-resolved taraf\u0131ndan y\u00f6netilen bir sembolik ba\u011flant\u0131d\u0131r; dosyay\u0131 elle ezmek kal\u0131c\u0131 \u00e7\u00f6z\u00fcm olmayabilir.<\/p>\n<h3>Cloud-init ayar\u0131 geri yaz\u0131yor<\/h3>\n<p>Bulut sunucular\u0131nda yeniden ba\u015flatma sonras\u0131 ayar\u0131n eski h\u00e2line d\u00f6nmesi cloud-init kaynakl\u0131 olabilir. <code>cloud-init status --long<\/code> ve <code>\/var\/log\/cloud-init.log<\/code> \u00e7\u0131kt\u0131lar\u0131 incelenmelidir. Sa\u011flay\u0131c\u0131n\u0131n imaj politikas\u0131 bilinmeden cloud-init&#8217;i tamamen devre d\u0131\u015f\u0131 b\u0131rakmak ba\u015fka ilk a\u00e7\u0131l\u0131\u015f i\u015flemlerini bozabilir.<\/p>\n<p>Ubuntu VPS \u00fczerinde web servisi \u00e7al\u0131\u015ft\u0131racaksan\u0131z a\u011f do\u011frulamas\u0131ndan sonra uygulama katman\u0131n\u0131 kontrol edin. \u00d6rne\u011fin <a href=\"#\">Ubuntu&#8217;da Nginx Kurulumu ve \u0130lk Yap\u0131land\u0131rma<\/a> i\u00e7eri\u011findeki <code>ss<\/code>, site dosyas\u0131 ve servis kontrol ad\u0131mlar\u0131 statik IP testinin devam\u0131nda uygulanabilir.<\/p>\n<div class=\"aiw-callout aiw-callout-field\">\n<p class=\"aiw-callout-label\">Sahadan not<\/p>\n<p>Bir m\u00fc\u015fteri VPS&#039;inde sa\u011flay\u0131c\u0131n\u0131n verdi\u011fi gateway&#039;i yanl\u0131\u015f prefix ile tan\u0131mlad\u0131m. sudo netplan generate hata vermedi; fakat ip route \u00e7\u0131kt\u0131s\u0131nda beklenen varsay\u0131lan rota \u00e7al\u0131\u015fmad\u0131 ve d\u0131\u015f IP&#039;ye eri\u015filemedi. Gateway ile adres blo\u011funu sa\u011flay\u0131c\u0131n\u0131n panelindeki bilgilerle kar\u015f\u0131la\u015ft\u0131r\u0131p rotay\u0131 d\u00fczelttim.<\/p>\n<\/div>\n<h2 id=\"statik-ip-degisikligini-geri-alma\">Statik IP De\u011fi\u015fikli\u011fini Geri Alma<\/h2>\n<p>Yeni ayar ba\u011flant\u0131y\u0131 bozduysa \u00f6nce sa\u011flay\u0131c\u0131n\u0131n konsoluna girin. Yedek dosyay\u0131 geri kopyalay\u0131p yap\u0131land\u0131rmay\u0131 yeniden \u00fcretin:<\/p>\n<pre><code>sudo cp -a \/etc\/netplan.backup.2026-09-27-1200\/* \/etc\/netplan\/\nsudo netplan generate\nsudo netplan apply\nip -br address\nip route<\/code><\/pre>\n<p>Yedek klas\u00f6r ad\u0131n\u0131 kendi \u00e7\u0131kt\u0131n\u0131za g\u00f6re de\u011fi\u015ftirin; \u00f6rnekteki tarih yaln\u0131zca g\u00f6sterim i\u00e7indir. Sorun bir dosyan\u0131n di\u011ferini ezmesinden kaynaklan\u0131yorsa <code>\/etc\/netplan\/<\/code> i\u00e7indeki t\u00fcm YAML dosyalar\u0131n\u0131 listeleyin. Kullan\u0131lmayan eski dosyalar\u0131 silmeden \u00f6nce kopyas\u0131n\u0131 saklay\u0131n.<\/p>\n<p>VPS sa\u011flay\u0131c\u0131n\u0131z snapshot sunuyorsa, a\u011f de\u011fi\u015fikli\u011finden \u00f6nce snapshot almak geri d\u00f6n\u00fc\u015f s\u00fcresini k\u0131saltabilir. Yine de snapshot, yap\u0131land\u0131rma yede\u011finin ve konsol eri\u015fiminin yerine ge\u00e7mez. <a href=\"#\">VPS Snapshot Nedir? Anl\u0131k Yedekleme Rehberi<\/a> i\u00e7eri\u011finde snapshot&#8217;\u0131n neyi korudu\u011fu ve neyi garanti etmedi\u011fi a\u00e7\u0131klan\u0131r.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131<\/strong> &#8211; \u00dcretim VPS&#8217;inde de\u011fi\u015fiklikten \u00f6nce YAML yede\u011fi, sa\u011flay\u0131c\u0131 konsolu ve geri d\u00f6n\u00fc\u015f komutlar\u0131n\u0131 haz\u0131r tutun.<\/p>\n<h2 id=\"ubuntu-statik-ip-ayarlama-icin-saglam-is-akisi\">Ubuntu Statik IP Ayarlama \u0130\u00e7in Sa\u011flam \u0130\u015f Ak\u0131\u015f\u0131<\/h2>\n<p>\u0130\u015flem birka\u00e7 komuttan olu\u015fsa da g\u00fcvenli s\u0131ra \u00f6nemlidir. \u00d6nce a\u011f bilgilerini do\u011frulay\u0131n, sonra aray\u00fcz\u00fc ve mevcut Netplan dosyalar\u0131n\u0131 inceleyin. Dosyay\u0131 yedekleyip de\u011fi\u015fikli\u011fi yaz\u0131n; <code>netplan generate<\/code> ile s\u00f6z dizimini, <code>netplan try<\/code> ile ba\u011flant\u0131y\u0131 s\u0131nay\u0131n. Son ad\u0131mda adres, rota, DNS ve uygulama portlar\u0131n\u0131 ayr\u0131 ayr\u0131 kontrol edin.<\/p>\n<p>SSH ile ba\u011fl\u0131yken ayn\u0131 sunucuya ikinci bir oturum a\u00e7mak da faydal\u0131d\u0131r. \u0130lk oturum koparsa ikinci oturum mevcut durumu g\u00f6rmenizi sa\u011flar; bu, konsol eri\u015fiminin yerini tutmaz ama k\u00fc\u00e7\u00fck bir yaz\u0131m hatas\u0131n\u0131n te\u015fhisini kolayla\u015ft\u0131r\u0131r. Kritik makinelerde de\u011fi\u015fikli\u011fi bak\u0131m penceresine ta\u015f\u0131y\u0131n ve izleme sisteminde eri\u015filebilirlik alarm\u0131n\u0131n \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 \u00f6nceden do\u011frulay\u0131n.<\/p>\n<p>Netplan&#8217;\u0131n resmi dok\u00fcmantasyonu s\u00f6zdizimi, backend se\u00e7imi ve rota tan\u0131mlar\u0131 i\u00e7in temel ba\u015fvuru kayna\u011f\u0131d\u0131r. Ubuntu Server belgeleri ise da\u011f\u0131t\u0131m\u0131n cloud-init ve a\u011f servisleriyle ili\u015fkisini a\u00e7\u0131klar. S\u00fcr\u00fcm y\u00fckseltmelerinde eski bir blog komutunu aynen ta\u015f\u0131mak yerine i\u015fletim sisteminizin belgeleriyle kar\u015f\u0131la\u015ft\u0131r\u0131n.<\/p>\n<p>Bir statik IP yap\u0131land\u0131rmas\u0131 ancak yeniden ba\u015flatmadan sonra da do\u011fru \u00e7al\u0131\u015f\u0131yor, DNS \u00e7\u00f6z\u00fcl\u00fcyor ve servisler beklenen portlarda dinliyorsa tamamlanm\u0131\u015f say\u0131l\u0131r. De\u011fi\u015fiklikten sonra kontroll\u00fc bir yeniden ba\u015flatma planlay\u0131n; bunu acil bir ba\u011flant\u0131 kesintisinin ortas\u0131nda denemek yerine bak\u0131m penceresinde yap\u0131n.<\/p>\n<h2 id=\"statik-ip-uygulamadan-once-kontrol-edin\">Statik IP Uygulamadan \u00d6nce Kontrol Edin<\/h2>\n<ul class=\"aiw-checklist\">\n<li>IP adresini, prefix de\u011ferini ve gateway&#039;i sa\u011flay\u0131c\u0131n\u0131zdan do\u011frulay\u0131n.<\/li>\n<li>Ger\u00e7ek a\u011f aray\u00fcz\u00fcn\u00fc ip -br link ile bulun.<\/li>\n<li>\/etc\/netplan\/ dizininin yede\u011fini al\u0131n.<\/li>\n<li>YAML dosyas\u0131nda yaln\u0131zca bo\u015fluk kullan\u0131n.<\/li>\n<li>netplan generate ile s\u00f6zdizimini do\u011frulay\u0131n.<\/li>\n<li>Uzak oturumda netplan try komutunu tercih edin.<\/li>\n<li>IP, gateway, DNS ve servis portlar\u0131n\u0131 ayr\u0131 ayr\u0131 test edin.<\/li>\n<\/ul>\n<div class=\"aiw-cta\">\n<p>Bir sonraki a\u011f de\u011fi\u015fikli\u011finizde \u00f6nce netplan try ile g\u00fcvenli do\u011frulama yap\u0131n; ard\u0131ndan kulland\u0131\u011f\u0131n\u0131z IP, rota ve DNS testlerini k\u0131sa bir bak\u0131m notuna kaydedin. Ayn\u0131 i\u015flemi tekrar etmeniz gerekti\u011finde bu not, tahminden daha h\u0131zl\u0131 yol g\u00f6sterir.<\/p>\n<p class=\"aiw-cta-action\"><a href=\"https:\/\/www.vps.tc\/tr\/vps\">VPS paketlerini inceleyin<\/a><\/p>\n<\/div>\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>Ubuntu&#039;da statik IP hangi dosyaya yaz\u0131l\u0131r?<\/summary>\n<p>Statik IP tan\u0131m\u0131 \u00e7o\u011fu Ubuntu kurulumunda \/etc\/netplan\/ dizinindeki .yaml dosyalar\u0131ndan birine yaz\u0131l\u0131r. Dosyan\u0131n ad\u0131 kurulum bi\u00e7imine g\u00f6re 00-installer-config.yaml veya 50-cloud-init.yaml olabilir. \u00d6nce ls -l \/etc\/netplan\/ ve sed -n komutlar\u0131yla mevcut dosyalar\u0131 inceleyin. Cloud-init y\u00f6netimi varsa elle yap\u0131lan de\u011fi\u015fiklik yeniden ba\u015flatma sonras\u0131nda \u00fczerine yaz\u0131labilir.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>Netplan ile statik IP nas\u0131l verilir?<\/summary>\n<p>YAML dosyas\u0131nda ilgili ethernet aray\u00fcz\u00fc alt\u0131nda dhcp4: false, addresses, routes ve nameservers alanlar\u0131n\u0131 tan\u0131mlay\u0131n. Adresi prefix ile yaz\u0131n; \u00f6rne\u011fin 192.168.1.50\/24. Ard\u0131ndan sudo netplan generate ile s\u00f6zdizimini, sudo netplan try ile ba\u011flant\u0131y\u0131 test edin. Gateway de\u011ferini sa\u011flay\u0131c\u0131n\u0131n verdi\u011fi rota bilgisine g\u00f6re belirleyin.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>Netplan try ile netplan apply aras\u0131ndaki fark nedir?<\/summary>\n<p>netplan apply yap\u0131land\u0131rmay\u0131 do\u011frudan etkinle\u015ftirir ve uzak SSH oturumunu yanl\u0131\u015f ayarlarda kesebilir. netplan try ise yap\u0131land\u0131rmay\u0131 ge\u00e7ici olarak uygular ve belirli s\u00fcre i\u00e7inde onay verilmezse \u00f6nceki ayara d\u00f6nmeyi dener. Yine de netplan try mutlak kurtarma garantisi de\u011fildir; kritik VPS&#039;lerde web konsolu veya serial console eri\u015fimi bulunmal\u0131d\u0131r.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>Ubuntu statik IP ayar\u0131ndan sonra internet \u00e7al\u0131\u015fm\u0131yorsa ne yap\u0131l\u0131r?<\/summary>\n<p>\u00d6nce ip -4 address show ile adresi, ip route ile varsay\u0131lan rotay\u0131 kontrol edin. Gateway&#039;e ping ba\u015far\u0131s\u0131zsa prefix, VLAN veya gateway de\u011ferini inceleyin. D\u0131\u015f IP&#039;ye eri\u015filiyor ancak alan adlar\u0131 \u00e7\u00f6z\u00fclm\u00fcyorsa resolvectl status ve DNS tan\u0131mlar\u0131n\u0131 kontrol edin. Sa\u011flay\u0131c\u0131n\u0131n \u00f6zel route veya sanal a\u011f gereksinimleri de g\u00f6zden ge\u00e7irilmelidir.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>Netplan&#039;da gateway4 m\u00fc, routes mu kullan\u0131lmal\u0131?<\/summary>\n<p>Yeni Netplan yap\u0131land\u0131rmalar\u0131nda varsay\u0131lan rota i\u00e7in routes alt\u0131nda to: default ve via kullanmak daha uygun yakla\u015f\u0131md\u0131r. Baz\u0131 Ubuntu s\u00fcr\u00fcmleri gateway4 anahtar\u0131n\u0131 desteklemeye devam edebilir, ancak s\u00fcr\u00fcm ve backend davran\u0131\u015f\u0131 de\u011fi\u015febilir. Sa\u011flay\u0131c\u0131n\u0131n dok\u00fcmantasyonunu ve kurulu Netplan s\u00fcr\u00fcm\u00fcn\u00fc kontrol ederek yap\u0131land\u0131rmay\u0131 buna g\u00f6re yaz\u0131n.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>Ubuntu&#039;da statik IP verdikten sonra DNS neden \u00e7al\u0131\u015fmaz?<\/summary>\n<p>IP adresi ve rota do\u011fru olsa bile nameservers tan\u0131m\u0131 eksik veya systemd-resolved yap\u0131land\u0131rmas\u0131 bozuksa DNS \u00e7al\u0131\u015fmayabilir. resolvectl status ile etkin DNS sunucular\u0131n\u0131, resolvectl query example.com ile \u00e7\u00f6z\u00fcmlemeyi test edin. \/etc\/resolv.conf dosyas\u0131n\u0131 elle ezmeden \u00f6nce bunun systemd-resolved taraf\u0131ndan y\u00f6netilen bir sembolik ba\u011flant\u0131 olup olmad\u0131\u011f\u0131n\u0131 kontrol edin.<\/p>\n<\/details>\n<\/div>\n<h2 id=\"kaynaklar\">Kaynaklar<\/h2>\n<ul class=\"aiw-sources\">\n<li><a href=\"https:\/\/ubuntu.com\/server\/docs\/network-configuration\" target=\"_blank\" rel=\"noopener\">Ubuntu Server &#8211; Network Configuration<\/a> \u2014 ubuntu.com<\/li>\n<li><a href=\"https:\/\/www.rfc-editor.org\/rfc\/rfc1918.html\" target=\"_blank\" rel=\"noopener\">RFC 1918 &#8211; Address Allocation for Private Internets<\/a> \u2014 rfc-editor.org<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Ubuntu&#8217;da Netplan kullanarak statik IPv4 ve IPv6 adresi tan\u0131mlama, gateway ve DNS yap\u0131land\u0131rma, ba\u011flant\u0131 testi ve geri alma ad\u0131mlar\u0131.<\/p>\n","protected":false},"author":2,"featured_media":964,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[383],"tags":[],"class_list":["post-966","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-linux"],"lang":"tr","translations":{"tr":966,"en":967},"pll_sync_post":[],"_links":{"self":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/966","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=966"}],"version-history":[{"count":1,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/966\/revisions"}],"predecessor-version":[{"id":968,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/966\/revisions\/968"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/media\/964"}],"wp:attachment":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/media?parent=966"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/categories?post=966"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/tags?post=966"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}