{"id":4145,"date":"2026-01-04T18:54:55","date_gmt":"2026-01-04T15:54:55","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/vps-sunucunuzda-ipv6-kurulum-ve-yapilandirma-rehberi-3\/"},"modified":"2026-01-04T18:54:55","modified_gmt":"2026-01-04T15:54:55","slug":"vps-sunucunuzda-ipv6-kurulum-ve-yapilandirma-rehberi-3","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/vps-sunucunuzda-ipv6-kurulum-ve-yapilandirma-rehberi-3\/","title":{"rendered":"VPS Sunucunuzda IPv6 Kurulum ve Yap\u0131land\u0131rma 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=\"#IPv68217yi_VPS_Sunucunuza_Tasimak_Neden_Artik_Ertelenmemeli\"><span class=\"toc_number toc_depth_1\">1<\/span> IPv6&#8217;y\u0131 VPS Sunucunuza Ta\u015f\u0131mak Neden Art\u0131k Ertelenmemeli?<\/a><\/li><li><a href=\"#Temel_Kavramlar_IPv6_Adres_Yapisi_64_Gateway_ve_DNS\"><span class=\"toc_number toc_depth_1\">2<\/span> Temel Kavramlar: IPv6 Adres Yap\u0131s\u0131, \/64, Gateway ve DNS<\/a><ul><li><a href=\"#IPv6_adres_tipleri_ve_yazim_bicimi\"><span class=\"toc_number toc_depth_2\">2.1<\/span> IPv6 adres tipleri ve yaz\u0131m bi\u00e7imi<\/a><\/li><li><a href=\"#Onek_prefix_ve_64_mantigi\"><span class=\"toc_number toc_depth_2\">2.2<\/span> \u00d6nek (prefix) ve \/64 mant\u0131\u011f\u0131<\/a><\/li><li><a href=\"#DNS_tarafi_AAAA_ve_PTR_reverse_kayitlari\"><span class=\"toc_number toc_depth_2\">2.3<\/span> DNS taraf\u0131: AAAA ve PTR (reverse) kay\u0131tlar\u0131<\/a><\/li><\/ul><\/li><li><a href=\"#VPS_Ortaminda_IPv6_Planlamasi_Dual-Stack_IPv6-Only_ve_Senaryolar\"><span class=\"toc_number toc_depth_1\">3<\/span> VPS Ortam\u0131nda IPv6 Planlamas\u0131: Dual-Stack, IPv6-Only ve Senaryolar<\/a><ul><li><a href=\"#Dual-stack_mi_IPv6-only_mi\"><span class=\"toc_number toc_depth_2\">3.1<\/span> Dual-stack mi, IPv6-only mi?<\/a><\/li><li><a href=\"#VPS_saglayicinizdan_almaniz_gereken_bilgiler\"><span class=\"toc_number toc_depth_2\">3.2<\/span> VPS sa\u011flay\u0131c\u0131n\u0131zdan alman\u0131z gereken bilgiler<\/a><\/li><\/ul><\/li><li><a href=\"#DebianUbuntu_Tabanli_VPS8217te_IPv6_Kurulumu\"><span class=\"toc_number toc_depth_1\">4<\/span> Debian\/Ubuntu Tabanl\u0131 VPS&#8217;te IPv6 Kurulumu<\/a><ul><li><a href=\"#Netplan_ile_IPv6_yapilandirmasi_Ubuntu_1804_ve_yeni_Debian_surumleri\"><span class=\"toc_number toc_depth_2\">4.1<\/span> Netplan ile IPv6 yap\u0131land\u0131rmas\u0131 (Ubuntu 18.04+ ve yeni Debian s\u00fcr\u00fcmleri)<\/a><\/li><li><a href=\"#Eski_ifupdown_ile_IPv6_Debian_ve_eski_Ubuntu_surumleri\"><span class=\"toc_number toc_depth_2\">4.2<\/span> Eski ifupdown ile IPv6 (Debian ve eski Ubuntu s\u00fcr\u00fcmleri)<\/a><\/li><li><a href=\"#IPv68217nin_gercekten_calistigini_dogrulama\"><span class=\"toc_number toc_depth_2\">4.3<\/span> IPv6&#8217;n\u0131n ger\u00e7ekten \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 do\u011frulama<\/a><\/li><\/ul><\/li><li><a href=\"#CentOS_AlmaLinux_ve_Rocky_Linux8217ta_IPv6_Kurulumu\"><span class=\"toc_number toc_depth_1\">5<\/span> CentOS, AlmaLinux ve Rocky Linux&#8217;ta IPv6 Kurulumu<\/a><ul><li><a href=\"#nmcli_ile_IPv6_adresi_eklemek\"><span class=\"toc_number toc_depth_2\">5.1<\/span> nmcli ile IPv6 adresi eklemek<\/a><\/li><li><a href=\"#ifcfg_dosyalari_ile_manuel_IPv6_yapilandirmasi\"><span class=\"toc_number toc_depth_2\">5.2<\/span> ifcfg dosyalar\u0131 ile manuel IPv6 yap\u0131land\u0131rmas\u0131<\/a><\/li><\/ul><\/li><li><a href=\"#Guvenlik_Duvari_ve_IPv6_Adres_Eklemek_Tek_Basina_Yeterli_Degil\"><span class=\"toc_number toc_depth_1\">6<\/span> G\u00fcvenlik Duvar\u0131 ve IPv6: Adres Eklemek Tek Ba\u015f\u0131na Yeterli De\u011fil<\/a><ul><li><a href=\"#ufw_ile_IPv6_trafigini_acmak\"><span class=\"toc_number toc_depth_2\">6.1<\/span> ufw ile IPv6 trafi\u011fini a\u00e7mak<\/a><\/li><li><a href=\"#firewalld_ile_IPv6_servislerini_acmak\"><span class=\"toc_number toc_depth_2\">6.2<\/span> firewalld ile IPv6 servislerini a\u00e7mak<\/a><\/li><li><a href=\"#Dogrudan_ip6tablesnftables_kullanan_yapilar\"><span class=\"toc_number toc_depth_2\">6.3<\/span> Do\u011frudan ip6tables\/nftables kullanan yap\u0131lar<\/a><\/li><\/ul><\/li><li><a href=\"#DNS_Web_Sunucusu_ve_Uygulama_Katmaninda_IPv68217yi_Tamamlama\"><span class=\"toc_number toc_depth_1\">7<\/span> DNS, Web Sunucusu ve Uygulama Katman\u0131nda IPv6&#8217;y\u0131 Tamamlama<\/a><ul><li><a href=\"#Alan_adiniza_AAAA_kaydi_eklemek\"><span class=\"toc_number toc_depth_2\">7.1<\/span> Alan ad\u0131n\u0131za AAAA kayd\u0131 eklemek<\/a><\/li><li><a href=\"#Nginx_ve_Apache8217yi_IPv6_uzerinde_dinleyecek_sekilde_ayarlamak\"><span class=\"toc_number toc_depth_2\">7.2<\/span> Nginx ve Apache&#8217;yi IPv6 \u00fczerinde dinleyecek \u015fekilde ayarlamak<\/a><\/li><li><a href=\"#SEO_performans_ve_kullanici_deneyimi_etkileri\"><span class=\"toc_number toc_depth_2\">7.3<\/span> SEO, performans ve kullan\u0131c\u0131 deneyimi etkileri<\/a><\/li><\/ul><\/li><li><a href=\"#E-posta_Reverse_DNS_ve_IPv6_ile_Teslim_Edilebilirlik\"><span class=\"toc_number toc_depth_1\">8<\/span> E-posta, Reverse DNS ve IPv6 ile Teslim Edilebilirlik<\/a><ul><li><a href=\"#IPv6_PTR_reverse_DNS_kaydi\"><span class=\"toc_number toc_depth_2\">8.1<\/span> IPv6 PTR (reverse DNS) kayd\u0131<\/a><\/li><li><a href=\"#SPF_DKIM_DMARC_ve_IPv6\"><span class=\"toc_number toc_depth_2\">8.2<\/span> SPF, DKIM, DMARC ve IPv6<\/a><\/li><li><a href=\"#Gercekci_bir_strateji_Web_trafiginde_agresif_e-postada_temkinli_IPv6\"><span class=\"toc_number toc_depth_2\">8.3<\/span> Ger\u00e7ek\u00e7i bir strateji: Web trafi\u011finde agresif, e-postada temkinli IPv6<\/a><\/li><\/ul><\/li><li><a href=\"#Sorun_Giderme_En_Sik_Karsilastigimiz_IPv6_Hatalari\"><span class=\"toc_number toc_depth_1\">9<\/span> Sorun Giderme: En S\u0131k Kar\u015f\u0131la\u015ft\u0131\u011f\u0131m\u0131z IPv6 Hatalar\u0131<\/a><\/li><li><a href=\"#DCHost_Ortaminda_Pratik_Bir_IPv6_Gecis_Plani\"><span class=\"toc_number toc_depth_1\">10<\/span> DCHost Ortam\u0131nda Pratik Bir IPv6 Ge\u00e7i\u015f Plan\u0131<\/a><\/li><li><a href=\"#Sonuc_IPv68217yi_Sadece_Acmayin_Bilincli_Sekilde_Hayata_Gecirin\"><span class=\"toc_number toc_depth_1\">11<\/span> Sonu\u00e7: IPv6&#8217;y\u0131 Sadece A\u00e7may\u0131n, Bilin\u00e7li \u015eekilde Hayata Ge\u00e7irin<\/a><\/li><\/ul><\/div>\n<h2><span id=\"IPv68217yi_VPS_Sunucunuza_Tasimak_Neden_Artik_Ertelenmemeli\">IPv6&#8217;y\u0131 <a href=\"https:\/\/www.dchost.com\/tr\/vps\">VPS<\/a> Sunucunuza Ta\u015f\u0131mak Neden Art\u0131k Ertelenmemeli?<\/span><\/h2>\n<p>VPS altyap\u0131s\u0131 planlarken \u00e7o\u011fu ekip h\u00e2l\u00e2 IPv4 adreslerini merkeze al\u0131yor. Ancak hem adres k\u0131tl\u0131\u011f\u0131 hem de maliyetler, bu yakla\u015f\u0131m\u0131n s\u00fcrd\u00fcr\u00fclemez oldu\u011funu art\u0131k \u00e7ok net g\u00f6steriyor. \u00d6zellikle son y\u0131llarda IPv4 kiralama ve sat\u0131n alma maliyetlerindeki ciddi art\u0131\u015flar\u0131 biz de DCHost taraf\u0131nda g\u00fcnl\u00fck operasyonlar\u0131m\u0131zda yak\u0131ndan hissediyoruz. Bu tabloyu daha teknik y\u00f6nden incelemek isterseniz, <a href=\"https:\/\/www.dchost.com\/blog\/ipv4-tukenmesi-ve-fiyat-artislari-teknik-arka-plan-ve-somut-cikis-yollari\/\">IPv4 t\u00fckenmesi ve fiyat art\u0131\u015flar\u0131n\u0131n teknik arka plan\u0131n\u0131 anlatt\u0131\u011f\u0131m\u0131z rehbere<\/a> mutlaka g\u00f6z at\u0131n.<\/p>\n<p>IPv6, sadece daha \u00e7ok adres sunan yeni bir protokol de\u011fil; mobil a\u011flarda performans, modern ISP altyap\u0131lar\u0131yla uyum, baz\u0131 \u00fclkelerde daha d\u00fc\u015f\u00fck gecikme ve orta\u2013uzun vadede maliyet avantaj\u0131 anlam\u0131na geliyor. G\u00fcn\u00fcm\u00fczde ciddi bir k\u0131sm\u0131 mobil olan ziyaret\u00e7ileriniz zaten \u00e7o\u011fu zaman IPv6 \u00fczerinden internete \u00e7\u0131k\u0131yor. Sunucunuz IPv6 desteklemiyorsa, a\u011f \u00fczerinde gereksiz \u00e7eviri katmanlar\u0131 (NAT, CGNAT vb.) devreye giriyor ve bu da hem gecikme hem de karma\u015f\u0131kl\u0131k anlam\u0131na geliyor.<\/p>\n<p>Bu rehberde DCHost \u00fczerinde kulland\u0131\u011f\u0131n\u0131z Linux tabanl\u0131 VPS sunucularda IPv6&#8217;y\u0131 ad\u0131m ad\u0131m nas\u0131l etkinle\u015ftirece\u011finizi, DNS ve web sunucusu taraf\u0131nda hangi ek ayarlar\u0131n gerekti\u011fini, g\u00fcvenlik duvar\u0131 ve e-posta gibi pratik konular\u0131 da kapsayacak \u015fekilde, ger\u00e7ek saha senaryolar\u0131na dayanarak anlataca\u011f\u0131m. Hedefim, IPv6&#8217;y\u0131 sadece etkinle\u015ftirip b\u0131rakman\u0131z de\u011fil; ger\u00e7ekten \u00f6l\u00e7\u00fclebilir \u015fekilde fayda sa\u011flayacak, s\u00fcrd\u00fcr\u00fclebilir bir yap\u0131 kurman\u0131z.<\/p>\n<h2><span id=\"Temel_Kavramlar_IPv6_Adres_Yapisi_64_Gateway_ve_DNS\">Temel Kavramlar: IPv6 Adres Yap\u0131s\u0131, \/64, Gateway ve DNS<\/span><\/h2>\n<h3><span id=\"IPv6_adres_tipleri_ve_yazim_bicimi\">IPv6 adres tipleri ve yaz\u0131m bi\u00e7imi<\/span><\/h3>\n<p>IPv6 adresleri 128 bit uzunlu\u011fundad\u0131r ve sekiz adet 16 bitlik bloktan olu\u015fur. Her blok, hex (16&#8217;l\u0131k) sistemde yaz\u0131l\u0131r ve iki nokta ile ayr\u0131l\u0131r. \u00d6rnek bir global IPv6 adresi \u015f\u00f6yle g\u00f6r\u00fcnebilir:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">2001:db8:1234:10::2<\/code><\/pre>\n<p>Genel olarak \u00fc\u00e7 ana IPv6 adres tipini bilmek yeterli olacakt\u0131r:<\/p>\n<ul>\n<li><strong>Global unicast<\/strong>: \u0130nternet \u00fczerinde y\u00f6nlendirilen, VPS&#8217;iniz i\u00e7in as\u0131l kullanaca\u011f\u0131n\u0131z adresler (\u00f6rnek: 2001:db8::\/32 gibi bloklardan gelen adresler).<\/li>\n<li><strong>Link-local<\/strong>: Sadece yerel a\u011f segmentinde ge\u00e7erli adresler; her aray\u00fczde otomatik olu\u015fur (fe80::\/64 ile ba\u015flar). Genelde gateway tan\u0131mlarken kar\u015f\u0131n\u0131za \u00e7\u0131kabilir.<\/li>\n<li><strong>Loopback<\/strong>: IPv4&#8217;teki 127.0.0.1&#8217;e kar\u015f\u0131l\u0131k gelen ::1 adresi.<\/li>\n<\/ul>\n<h3><span id=\"Onek_prefix_ve_64_mantigi\">\u00d6nek (prefix) ve \/64 mant\u0131\u011f\u0131<\/span><\/h3>\n<p>IPv6 taraf\u0131nda en s\u0131k g\u00f6rece\u011finiz \u00f6nek uzunlu\u011fu \/64 olacakt\u0131r. \u00d6rne\u011fin size \u015fu bilgiler verilmi\u015f olabilir:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">IPv6 adresiniz: 2001:db8:1234:10::2\nPrefix:        \/64\nGateway:       2001:db8:1234:10::1<\/code><\/pre>\n<p>Burada \/64, ilk 64 bitin a\u011f k\u0131sm\u0131 oldu\u011funu g\u00f6sterir. Geriye kalan 64 bit host k\u0131sm\u0131d\u0131r. Bir \/64 a\u011f, 2^64 adet adres i\u00e7erir; yani tek bir \/64 bile pratikte <strong>bir sunucu i\u00e7in fazlas\u0131yla b\u00fcy\u00fck<\/strong> bir bloktur. Pek \u00e7ok VPS ortam\u0131nda size tek bir IPv6 adresi ya da \/64 verilir ve siz sadece bu adresi aray\u00fcze statik olarak tan\u0131mlars\u0131n\u0131z.<\/p>\n<h3><span id=\"DNS_tarafi_AAAA_ve_PTR_reverse_kayitlari\">DNS taraf\u0131: AAAA ve PTR (reverse) kay\u0131tlar\u0131<\/span><\/h3>\n<p>IPv4 i\u00e7in A kayd\u0131 neyse, IPv6 i\u00e7in de AAAA kayd\u0131 odur. \u00d6rne\u011fin:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">www.ornek.com.   300   IN   A    198.51.100.10\nwww.ornek.com.   300   IN   AAAA 2001:db8:1234:10::2<\/code><\/pre>\n<p>IPv6&#8217;y\u0131 tam anlam\u0131yla devreye almak i\u00e7in yaln\u0131zca AAAA kayd\u0131 eklemek yetmez; e-posta gibi servisler i\u00e7in reverse DNS (PTR) de kritik \u00f6neme sahiptir. PTR kayd\u0131, IP &rarr; alan ad\u0131 e\u015fle\u015fmesini sa\u011flar ve \u00f6zellikle spam filtrelerinde olumlu bir sinyaldir. DNS kay\u0131tlar\u0131n\u0131n genel mant\u0131\u011f\u0131n\u0131 tazelemek isterseniz, <a href=\"https:\/\/www.dchost.com\/blog\/dns-kayitlari-nedir-a-aaaa-cname-mx-txt-ve-srv-rehberi\/\">A, AAAA, CNAME, MX, TXT ve di\u011fer DNS kay\u0131tlar\u0131n\u0131 anlatt\u0131\u011f\u0131m\u0131z kapsaml\u0131 rehbere<\/a> de g\u00f6z atabilirsiniz.<\/p>\n<h2><span id=\"VPS_Ortaminda_IPv6_Planlamasi_Dual-Stack_IPv6-Only_ve_Senaryolar\">VPS Ortam\u0131nda IPv6 Planlamas\u0131: Dual-Stack, IPv6-Only ve Senaryolar<\/span><\/h2>\n<h3><span id=\"Dual-stack_mi_IPv6-only_mi\">Dual-stack mi, IPv6-only mi?<\/span><\/h3>\n<p>Pratikte bug\u00fcn i\u00e7in en ger\u00e7ek\u00e7i yakla\u015f\u0131m <strong>dual-stack<\/strong> modelidir: Sunucunuzda hem IPv4 hem IPv6 ayn\u0131 anda \u00e7al\u0131\u015f\u0131r. B\u00f6ylece:<\/p>\n<ul>\n<li>IPv4-only a\u011flardan gelen ziyaret\u00e7ileriniz IPv4 ile,<\/li>\n<li>IPv6 destekli a\u011flardan gelenler ise direkt IPv6 ile<\/li>\n<\/ul>\n<p>eri\u015fmeye devam eder. Uygulamay\u0131, firewall&#8217;u ve DNS&#8217;i buna g\u00f6re tasarlars\u0131n\u0131z.<\/p>\n<p>Daha ileri bir ad\u0131m olarak <strong>IPv6-only VPS<\/strong> mimarileri de m\u00fcmk\u00fcn. Bu durumda sunucunuzda hi\u00e7 IPv4 yoktur; IPv4-only ziyaret\u00e7ilere ula\u015fmak i\u00e7in de NAT64\/DNS64 gibi k\u00f6pr\u00fc teknolojileri kullan\u0131l\u0131r. Bu yakla\u015f\u0131m\u0131 daha derin incelemek isterseniz, <a href=\"https:\/\/www.dchost.com\/blog\/ipv6%e2%80%91only-vps-uzerinde-web-sitesi-yayinlamak-nat64-dns64-ile-ipv4e-nasil-kopru-kurulur\/\">IPv6-only VPS \u00fczerinde web sitesi yay\u0131nlama ve NAT64\/DNS64 ile IPv4&#8217;e k\u00f6pr\u00fc kurma rehberimizi<\/a> inceleyebilirsiniz.<\/p>\n<h3><span id=\"VPS_saglayicinizdan_almaniz_gereken_bilgiler\">VPS sa\u011flay\u0131c\u0131n\u0131zdan alman\u0131z gereken bilgiler<\/span><\/h3>\n<p>DCHost \u00fczerinde yeni bir VPS olu\u015fturdu\u011funuzda, y\u00f6netim panelinde genellikle \u015fu bilgileri g\u00f6r\u00fcrs\u00fcn\u00fcz:<\/p>\n<ul>\n<li>Atanm\u0131\u015f IPv6 adresiniz (ya da adresleriniz)<\/li>\n<li>IPv6 prefix (\u00e7o\u011fu zaman \/64)<\/li>\n<li>IPv6 gateway<\/li>\n<li>Varsay\u0131lan DNS sunucular\u0131 (\u00e7o\u011fu zaman hem IPv4 hem IPv6 adresleri listelenir)<\/li>\n<\/ul>\n<p>Bu rehberde kullanaca\u011f\u0131m\u0131z \u00f6rneklerde, bu bilgileri elinizin alt\u0131nda tuttu\u011funuzu varsay\u0131yorum. E\u011fer panelde g\u00f6remiyorsan\u0131z ya da emin de\u011filseniz, DCHost destek ekibine bir ticket a\u00e7arak IPv6 tan\u0131mlamalar\u0131n\u0131z\u0131 netle\u015ftirmeniz iyi bir ba\u015flang\u0131\u00e7 olur.<\/p>\n<h2><span id=\"DebianUbuntu_Tabanli_VPS8217te_IPv6_Kurulumu\">Debian\/Ubuntu Tabanl\u0131 VPS&#8217;te IPv6 Kurulumu<\/span><\/h2>\n<p>Debian ve Ubuntu, DCHost m\u00fc\u015fterilerimizin en s\u0131k tercih etti\u011fi iki da\u011f\u0131t\u0131m. \u00d6zellikle yeni Ubuntu s\u00fcr\u00fcmlerinde <strong>netplan<\/strong>, Debian ve baz\u0131 eski Ubuntu s\u00fcr\u00fcmlerinde ise klasik <strong>\/etc\/network\/interfaces<\/strong> yap\u0131s\u0131n\u0131 g\u00f6rebilirsiniz.<\/p>\n<h3><span id=\"Netplan_ile_IPv6_yapilandirmasi_Ubuntu_1804_ve_yeni_Debian_surumleri\">Netplan ile IPv6 yap\u0131land\u0131rmas\u0131 (Ubuntu 18.04+ ve yeni Debian s\u00fcr\u00fcmleri)<\/span><\/h3>\n<p>Tipik bir netplan dosyas\u0131 \u015f\u00f6yle g\u00f6r\u00fcnebilir:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">sudo nano \/etc\/netplan\/01-netcfg.yaml<\/code><\/pre>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">network:\n  version: 2\n  renderer: networkd\n  ethernets:\n    eth0:\n      addresses:\n        - 198.51.100.10\/24        # IPv4 adresiniz\n        - 2001:db8:1234:10::2\/64  # IPv6 adresiniz\n      gateway4: 198.51.100.1\n      gateway6: 2001:db8:1234:10::1\n      nameservers:\n        addresses:\n          - 1.1.1.1\n          - 8.8.8.8\n          - 2606:4700:4700::1111\n          - 2001:4860:4860::8888<\/code><\/pre>\n<p>Burada \u00f6nemli noktalar:<\/p>\n<ul>\n<li>IPv6 adresini \/64 prefix ile birlikte yazman\u0131z gerekir.<\/li>\n<li>gateway6 alan\u0131na panelde g\u00f6rd\u00fc\u011f\u00fcn\u00fcz IPv6 gateway&#8217;i yazmal\u0131s\u0131n\u0131z.<\/li>\n<li>nameservers alt\u0131nda hem IPv4 hem IPv6 DNS sunucular\u0131n\u0131 tan\u0131mlayabilirsiniz.<\/li>\n<\/ul>\n<p>Dosyay\u0131 kaydettikten sonra ayarlar\u0131 uygulay\u0131n:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">sudo netplan apply<\/code><\/pre>\n<h3><span id=\"Eski_ifupdown_ile_IPv6_Debian_ve_eski_Ubuntu_surumleri\">Eski ifupdown ile IPv6 (Debian ve eski Ubuntu s\u00fcr\u00fcmleri)<\/span><\/h3>\n<p>E\u011fer \/etc\/network\/interfaces dosyas\u0131 kullan\u0131l\u0131yorsa, tipik bir yap\u0131land\u0131rma \u015f\u00f6yle olabilir:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">auto eth0\niface eth0 inet static\n    address 198.51.100.10\n    netmask 255.255.255.0\n    gateway 198.51.100.1\n\niface eth0 inet6 static\n    address 2001:db8:1234:10::2\n    netmask 64\n    gateway 2001:db8:1234:10::1<\/code><\/pre>\n<p>De\u011fi\u015fiklik sonras\u0131nda a\u011f servisini yeniden ba\u015flat\u0131n:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">sudo systemctl restart networking<\/code><\/pre>\n<h3><span id=\"IPv68217nin_gercekten_calistigini_dogrulama\">IPv6&#8217;n\u0131n ger\u00e7ekten \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 do\u011frulama<\/span><\/h3>\n<p>A\u015fa\u011f\u0131daki komutlarla IPv6 konfig\u00fcrasyonunuzu test edebilirsiniz:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\"># IPv6 adreslerini ve rotalar\u0131 kontrol et\nip -6 addr show\nip -6 route show\n\n# IPv6 \u00fczerinden ping testi\nping -6 2001:4860:4860::8888\nping -6 google.com\n\n# Sadece IPv6 kullanarak HTTP iste\u011fi atmak\ncurl -6 https:\/\/ifconfig.co<\/code><\/pre>\n<p>ping -6 ile domain&#8217;e ping atarken sadece IPv6 kullan\u0131laca\u011f\u0131ndan, DNS&#8217;te AAAA kayd\u0131n\u0131z yoksa ya da rota hatal\u0131ysa sorunlar\u0131 h\u0131zl\u0131ca fark edebilirsiniz.<\/p>\n<h2><span id=\"CentOS_AlmaLinux_ve_Rocky_Linux8217ta_IPv6_Kurulumu\">CentOS, AlmaLinux ve Rocky Linux&#8217;ta IPv6 Kurulumu<\/span><\/h2>\n<p>RHEL tabanl\u0131 da\u011f\u0131t\u0131mlarda varsay\u0131lan olarak <strong>NetworkManager<\/strong> kullan\u0131l\u0131r. Ayarlar\u0131 ister nmcli komut sat\u0131r\u0131 ile ister ifcfg dosyalar\u0131 \u00fczerinden yapabilirsiniz.<\/p>\n<h3><span id=\"nmcli_ile_IPv6_adresi_eklemek\">nmcli ile IPv6 adresi eklemek<\/span><\/h3>\n<p>\u00d6nce ba\u011flant\u0131 ad\u0131n\u0131 tespit edin:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">nmcli connection show<\/code><\/pre>\n<p>Diyelim ki ba\u011flant\u0131n\u0131z\u0131n ad\u0131 &#8216;eth0&#8217; olsun. \u015eu \u015fekilde IPv6 adresi ve gateway ekleyebilirsiniz:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">sudo nmcli connection modify eth0 ipv6.method manual \n  ipv6.addresses 2001:db8:1234:10::2\/64 \n  ipv6.gateway 2001:db8:1234:10::1 \n  ipv6.dns &quot;2606:4700:4700::1111,2001:4860:4860::8888&quot;<\/code><\/pre>\n<p>Sonras\u0131nda ba\u011flant\u0131y\u0131 yeniden ba\u015flat\u0131n:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">sudo nmcli connection down eth0\nsudo nmcli connection up eth0<\/code><\/pre>\n<h3><span id=\"ifcfg_dosyalari_ile_manuel_IPv6_yapilandirmasi\">ifcfg dosyalar\u0131 ile manuel IPv6 yap\u0131land\u0131rmas\u0131<\/span><\/h3>\n<p>Baz\u0131 ortamlarda h\u00e2l\u00e2 klasik ifcfg format\u0131 tercih ediliyor. \u00d6rne\u011fin:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">sudo nano \/etc\/sysconfig\/network-scripts\/ifcfg-eth0<\/code><\/pre>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">DEVICE=eth0\nBOOTPROTO=none\nONBOOT=yes\n\nIPADDR=198.51.100.10\nPREFIX=24\nGATEWAY=198.51.100.1\n\nIPV6INIT=yes\nIPV6_AUTOCONF=no\nIPV6ADDR=2001:db8:1234:10::2\/64\nIPV6_DEFAULTGW=2001:db8:1234:10::1<\/code><\/pre>\n<p>De\u011fi\u015fiklikten sonra a\u011f servisini yeniden ba\u015flat\u0131n:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">sudo systemctl restart network<\/code><\/pre>\n<p>Ard\u0131ndan yine <code>ip -6 addr<\/code> ve <code>ping -6<\/code> ile ba\u011flant\u0131y\u0131 do\u011frulayabilirsiniz.<\/p>\n<h2><span id=\"Guvenlik_Duvari_ve_IPv6_Adres_Eklemek_Tek_Basina_Yeterli_Degil\">G\u00fcvenlik Duvar\u0131 ve IPv6: Adres Eklemek Tek Ba\u015f\u0131na Yeterli De\u011fil<\/span><\/h2>\n<p>IPv6 taraf\u0131nda sahada g\u00f6rd\u00fc\u011f\u00fcm\u00fcz en yayg\u0131n hata \u015fu: Sunucuya IPv6 adresi ekleniyor, DNS&#8217;e AAAA kayd\u0131 yaz\u0131l\u0131yor ama IPv4 i\u00e7in yaz\u0131lm\u0131\u015f firewall kurallar\u0131 IPv6 i\u00e7in g\u00fcncellenmiyor. Sonu\u00e7; elinizde var olan ama d\u0131\u015far\u0131dan eri\u015filemeyen bir IPv6 adresi.<\/p>\n<h3><span id=\"ufw_ile_IPv6_trafigini_acmak\">ufw ile IPv6 trafi\u011fini a\u00e7mak<\/span><\/h3>\n<p>Ubuntu&#8217;da s\u0131k\u00e7a kullan\u0131lan ufw, varsay\u0131lan ayarlar\u0131nda IPv6 deste\u011fini kapal\u0131 getirebilir. \u00d6nce \u015funu kontrol edin:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">sudo nano \/etc\/ufw\/ufw.conf<\/code><\/pre>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">IPV6=yes<\/code><\/pre>\n<p>Bu sat\u0131r &#8216;yes&#8217; de\u011filse, de\u011fi\u015ftirip ufw&#8217;yi yeniden ba\u015flat\u0131n:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">sudo ufw disable\nsudo ufw enable<\/code><\/pre>\n<p>Sonras\u0131nda tan\u0131mlad\u0131\u011f\u0131n\u0131z kurallar hem IPv4 hem IPv6&#8217;ya uygulanacakt\u0131r. \u00d6rne\u011fin:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">sudo ufw allow 80\/tcp comment 'HTTP'\nsudo ufw allow 443\/tcp comment 'HTTPS'<\/code><\/pre>\n<p>G\u00fcvenlik duvar\u0131n\u0131 daha detayl\u0131 sertle\u015ftirmek isterseniz, IPv6 odakl\u0131 nftables kurallar\u0131n\u0131 da i\u015fin i\u00e7ine dahil eden <a href=\"https:\/\/www.dchost.com\/blog\/nftables-ile-vps-guvenlik-duvari-rehberi-rate-limit-port-knocking-ve-ipv6-kurallari-nasil-tatli-tatli-kurulur\/\">nftables ile VPS g\u00fcvenlik duvar\u0131 rehberimizi<\/a> mutlaka inceleyin.<\/p>\n<h3><span id=\"firewalld_ile_IPv6_servislerini_acmak\">firewalld ile IPv6 servislerini a\u00e7mak<\/span><\/h3>\n<p>RHEL tabanl\u0131 sistemlerde firewalld kullan\u0131yorsan\u0131z, IPv4 ve IPv6 i\u00e7in ayn\u0131 zone ve servis tan\u0131mlar\u0131n\u0131 kullan\u0131rs\u0131n\u0131z. \u00d6rne\u011fin:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">sudo firewall-cmd --zone=public --add-service=http --permanent\nsudo firewall-cmd --zone=public --add-service=https --permanent\nsudo firewall-cmd --reload<\/code><\/pre>\n<p>E\u011fer \u00f6zel kurallar yaz\u0131yorsan\u0131z, IPv6&#8217;ya \u00f6zg\u00fc adres ailelerini de unutmay\u0131n:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">sudo firewall-cmd --permanent \n  --add-rich-rule='rule family=&quot;ipv6&quot; service name=&quot;http&quot; accept'<\/code><\/pre>\n<h3><span id=\"Dogrudan_ip6tablesnftables_kullanan_yapilar\">Do\u011frudan ip6tables\/nftables kullanan yap\u0131lar<\/span><\/h3>\n<p>Daha geli\u015fmi\u015f VPS kurulumlar\u0131nda iptables yerine nftables kullan\u0131m\u0131 h\u0131zla yayg\u0131nla\u015f\u0131yor. Mant\u0131k basit: IPv4 i\u00e7in yazd\u0131\u011f\u0131n\u0131z kurallar\u0131n bir muadilini IPv6 i\u00e7in de tan\u0131mlaman\u0131z gerekiyor. \u00d6rne\u011fin sadece belirli portlar\u0131 a\u00e7\u0131p geri kalan her \u015feyi drop ediyorsan\u0131z, IPv6 zincirinizde de ayn\u0131 politikay\u0131 uygulamal\u0131s\u0131n\u0131z. Aksi halde ya t\u00fcm IPv6 trafi\u011fini engellemi\u015f olursunuz ya da tam tersi, IPv4&#8217;te kapatt\u0131\u011f\u0131n\u0131z bir port IPv6 \u00fczerinden a\u00e7\u0131k kal\u0131r.<\/p>\n<h2><span id=\"DNS_Web_Sunucusu_ve_Uygulama_Katmaninda_IPv68217yi_Tamamlama\">DNS, Web Sunucusu ve Uygulama Katman\u0131nda IPv6&#8217;y\u0131 Tamamlama<\/span><\/h2>\n<h3><span id=\"Alan_adiniza_AAAA_kaydi_eklemek\">Alan ad\u0131n\u0131za AAAA kayd\u0131 eklemek<\/span><\/h3>\n<p>Sunucuda IPv6 adresi \u00e7al\u0131\u015f\u0131r h\u00e2le geldikten sonra s\u0131ra DNS taraf\u0131na gelir. \u00d6rne\u011fin \u015f\u00f6yle bir yap\u0131land\u0131rman\u0131z olabilir:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">ornek.com.        300 IN A    198.51.100.10\nornek.com.        300 IN AAAA 2001:db8:1234:10::2\nwww.ornek.com.    300 IN CNAME ornek.com.<\/code><\/pre>\n<p>CDN ya da harici DNS sa\u011flay\u0131c\u0131s\u0131 kullan\u0131yorsan\u0131z, oradaki panelden de AAAA kayd\u0131n\u0131 eklemeyi unutmay\u0131n. Sadece A kayd\u0131n\u0131 g\u00fcncelleyip AAAA&#8217;y\u0131 ihmal etmek, IPv6 kullan\u0131c\u0131lar\u0131n\u0131n IPv4&#8217;e geri d\u00fc\u015fmesine neden olur; bu da asl\u0131nda kurdu\u011funuz yeni altyap\u0131n\u0131n faydas\u0131n\u0131 k\u0131smen bo\u015fa \u00e7\u0131kar\u0131r.<\/p>\n<h3><span id=\"Nginx_ve_Apache8217yi_IPv6_uzerinde_dinleyecek_sekilde_ayarlamak\">Nginx ve Apache&#8217;yi IPv6 \u00fczerinde dinleyecek \u015fekilde ayarlamak<\/span><\/h3>\n<p>Unix soket ya da sadece 0.0.0.0:80 \u00fczerinde dinleyen konfig\u00fcrasyonlarda web sunucusu zaten hem IPv4 hem IPv6 \u00fczerinden \u00e7al\u0131\u015f\u0131yor olabilir, fakat konfig\u00fcrasyonu netle\u015ftirmek iyi bir pratiktir.<\/p>\n<p>Nginx \u00f6rne\u011fi:<\/p>\n<pre class=\"language-nginx line-numbers\"><code class=\"language-nginx\">server {\n    listen 80 default_server;\n    listen [::]:80 default_server;\n\n    server_name ornek.com www.ornek.com;\n    root \/var\/www\/ornek.com\/public;\n}<\/code><\/pre>\n<p>HTTPS i\u00e7in:<\/p>\n<pre class=\"language-nginx line-numbers\"><code class=\"language-nginx\">server {\n    listen 443 ssl http2;\n    listen [::]:443 ssl http2;\n\n    server_name ornek.com www.ornek.com;\n    ssl_certificate     \/etc\/letsencrypt\/live\/ornek.com\/fullchain.pem;\n    ssl_certificate_key \/etc\/letsencrypt\/live\/ornek.com\/privkey.pem;\n}<\/code><\/pre>\n<p>Apache taraf\u0131nda ise genellikle Listen direktifini hem IPv4 hem IPv6&#8217;y\u0131 kapsayacak \u015fekilde yazman\u0131z yeterlidir:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">Listen 80\nListen [::]:80<\/code><\/pre>\n<p>VirtualHost tan\u0131mlar\u0131n\u0131zda da benzer \u015fekilde hem IPv4 hem IPv6&#8217;y\u0131 kapsayan yap\u0131 kullanabilirsiniz.<\/p>\n<h3><span id=\"SEO_performans_ve_kullanici_deneyimi_etkileri\">SEO, performans ve kullan\u0131c\u0131 deneyimi etkileri<\/span><\/h3>\n<p>Google ve di\u011fer arama motorlar\u0131, sitenizin IPv6 \u00fczerinden eri\u015filebilir olup olmad\u0131\u011f\u0131n\u0131 kontrol eder. \u00c7o\u011fu zaman IPv6 yaln\u0131zca do\u011frudan bir SEO s\u0131ralama fakt\u00f6r\u00fc de\u011fildir; ancak kullan\u0131c\u0131lar\u0131n\u0131za daha yak\u0131n IPv6 rotalar\u0131 sunuyorsan\u0131z, <strong>daha d\u00fc\u015f\u00fck gecikme ve daha stabil bir deneyim<\/strong> sunars\u0131n\u0131z. Bu da dolayl\u0131 olarak hemen \u00e7\u0131kma oran\u0131, sayfa y\u00fckleme s\u00fcresi ve kullan\u0131c\u0131 davran\u0131\u015f\u0131 metrikleri \u00fczerinden SEO&#8217;ya katk\u0131 sa\u011flar.<\/p>\n<h2><span id=\"E-posta_Reverse_DNS_ve_IPv6_ile_Teslim_Edilebilirlik\">E-posta, Reverse DNS ve IPv6 ile Teslim Edilebilirlik<\/span><\/h2>\n<p>E\u011fer VPS&#8217;iniz \u00fczerinden SMTP ile e-posta g\u00f6nderimi yap\u0131yorsan\u0131z, IPv6&#8217;y\u0131 devreye al\u0131rken bu alan\u0131 \u00f6zellikle dikkatli ele alman\u0131z gerekir. Pek \u00e7ok al\u0131c\u0131 MTA, IPv6&#8217;dan gelen ba\u011flant\u0131lara kar\u015f\u0131 daha kat\u0131 kurallar uygulayabiliyor.<\/p>\n<h3><span id=\"IPv6_PTR_reverse_DNS_kaydi\">IPv6 PTR (reverse DNS) kayd\u0131<\/span><\/h3>\n<p>PTR kayd\u0131 genellikle IP blo\u011funu size tahsis eden taraf\u0131ndan y\u00f6netilir; yani DCHost taraf\u0131nda tan\u0131mlan\u0131r. IPv6 adresinizin reverse DNS&#8217;ini alan ad\u0131n\u0131zla e\u015fle\u015ftirmek i\u00e7in destek talebi a\u00e7arak \u015fu bilgileri iletmeniz yeterlidir:<\/p>\n<ul>\n<li>IPv6 adresiniz (\u00f6rnek: 2001:db8:1234:10::2)<\/li>\n<li>Bu IP i\u00e7in kullan\u0131lacak hostname (\u00f6rnek: mail.ornek.com)<\/li>\n<\/ul>\n<p>Sonras\u0131nda <code>dig -x 2001:db8:1234:10::2<\/code> ya da benzeri ara\u00e7larla PTR kayd\u0131n\u0131 kontrol edebilirsiniz.<\/p>\n<h3><span id=\"SPF_DKIM_DMARC_ve_IPv6\">SPF, DKIM, DMARC ve IPv6<\/span><\/h3>\n<p>SPF kayd\u0131 olu\u015ftururken, g\u00f6nderen IP&#8217;niz IPv6 ise buna g\u00f6re &#8216;ip6:&#8217; mekanizmas\u0131n\u0131 kullanman\u0131z gerekir. \u00d6rne\u011fin:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">ornek.com.  300 IN TXT &quot;v=spf1 ip6:2001:db8:1234:10::2 -all&quot;<\/code><\/pre>\n<p>DKIM ve DMARC kay\u0131tlar\u0131 IPv4\/IPv6&#8217;dan ba\u011f\u0131ms\u0131zd\u0131r; alan ad\u0131n\u0131z i\u00e7in do\u011fru \u015fekilde kurulu olmalar\u0131 yeterlidir. IPv6 \u00fczerinden e-posta g\u00f6nderimini daha detayl\u0131 ele ald\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/ipv6-ile-e-posta-gonderimi-reverse-dns-spf-ve-teslim-edilebilirlik-rehberi\/\">IPv6 ile e-posta g\u00f6nderimi, reverse DNS, SPF ve teslim edilebilirlik rehberimize<\/a> g\u00f6z atman\u0131z, bu konuyu sahadaki iyi ve k\u00f6t\u00fc \u00f6rneklerle birlikte g\u00f6rmenizi sa\u011flayacakt\u0131r.<\/p>\n<h3><span id=\"Gercekci_bir_strateji_Web_trafiginde_agresif_e-postada_temkinli_IPv6\">Ger\u00e7ek\u00e7i bir strateji: Web trafi\u011finde agresif, e-postada temkinli IPv6<\/span><\/h3>\n<p>Saha deneyimimiz \u015funu g\u00f6steriyor: Web trafi\u011finde IPv6&#8217;y\u0131 h\u0131zl\u0131ca ve agresif \u015fekilde devreye almak \u00e7o\u011fu zaman ciddi fayda sa\u011fl\u0131yor. E-posta taraf\u0131nda ise baz\u0131 al\u0131c\u0131 sistemlerin IPv6&#8217;ya h\u00e2l\u00e2 \u00e7ekingen yakla\u015ft\u0131\u011f\u0131n\u0131 g\u00f6r\u00fcyoruz. Bu nedenle:<\/p>\n<ul>\n<li>Web siteniz i\u00e7in IPv6&#8217;y\u0131 mutlaka a\u00e7\u0131n.<\/li>\n<li>E-posta taraf\u0131nda ise PTR, SPF ve di\u011fer ayarlar\u0131 titizlikle kurup teslim edilebilirlik metriklerinizi g\u00f6zlemleyin.<\/li>\n<li>Gerekirse bir s\u00fcre daha SMTP \u00e7\u0131k\u0131\u015f\u0131n\u0131 sadece IPv4 \u00fczerinden b\u0131rak\u0131p, IPv6&#8217;y\u0131 yava\u015f yava\u015f devreye al\u0131n.<\/li>\n<\/ul>\n<h2><span id=\"Sorun_Giderme_En_Sik_Karsilastigimiz_IPv6_Hatalari\">Sorun Giderme: En S\u0131k Kar\u015f\u0131la\u015ft\u0131\u011f\u0131m\u0131z IPv6 Hatalar\u0131<\/span><\/h2>\n<p>IPv6 taraf\u0131nda DCHost destek ekibine en s\u0131k gelen vakalar\u0131 \u00f6zetlemek, kendi kurulumunuzda da h\u0131zl\u0131 te\u015fhis koyman\u0131za yard\u0131mc\u0131 olacakt\u0131r.<\/p>\n<ul>\n<li><strong>Sunucudan d\u0131\u015far\u0131ya ping -6 \u00e7al\u0131\u015f\u0131yor ama site d\u0131\u015far\u0131dan a\u00e7\u0131lm\u0131yor:<\/strong> \u00c7o\u011funlukla firewall&#8217;da IPv6 i\u00e7in 80\/443 portlar\u0131n\u0131n a\u00e7\u0131k olmamas\u0131ndan kaynaklan\u0131r. ufw\/firewalld ya da nftables kurallar\u0131n\u0131z\u0131 kontrol edin.<\/li>\n<li><strong>Sunucuya SSH ile IPv6 \u00fczerinden hi\u00e7 eri\u015filemiyor:<\/strong> G\u00fcvenlik duvar\u0131nda 22\/tcp i\u00e7in IPv6 kural\u0131 yoktur veya gateway yanl\u0131\u015f yaz\u0131lm\u0131\u015ft\u0131r. <code>ip -6 route<\/code> \u00e7\u0131kt\u0131s\u0131n\u0131 mutlaka kontrol edin.<\/li>\n<li><strong>baz\u0131 a\u011flardan IPv6 ile eri\u015filirken baz\u0131 ISP&#8217;lerden eri\u015filememesi:<\/strong> Genelde rota sorunlar\u0131 ya da ilgili ISP taraf\u0131ndaki peering problemleriyle ilgilidir. Bu durumda traceroute6 \u00e7\u0131kt\u0131lar\u0131yla birlikte destek birimine ba\u015fvurmak gerekir.<\/li>\n<li><strong>AAAA kayd\u0131 var ama taray\u0131c\u0131 IPv4 \u00fczerinden ba\u011flan\u0131yor:<\/strong> Kullan\u0131c\u0131n\u0131n ISP&#8217;si IPv6 desteklemiyor olabilir. Ayr\u0131ca taray\u0131c\u0131lar genelde Happy Eyeballs algoritmas\u0131n\u0131 kullanarak IPv4\/IPv6 aras\u0131nda en h\u0131zl\u0131 yan\u0131t vereni se\u00e7er; bu nedenle IPv6 rotan\u0131z\u0131n performans\u0131 da \u00f6nemlidir.<\/li>\n<li><strong>IPv6 adresi ekledikten sonra a\u011f tamamen gitti:<\/strong> Yanl\u0131\u015f prefix (\/64 yerine \/128 gibi), gateway adresinin hatal\u0131 yaz\u0131lmas\u0131 ya da netplan\/interfaces dosyas\u0131nda s\u00f6zdizimi hatalar\u0131 buna yol a\u00e7abilir. Konfig\u00fcrasyonu dikkatle g\u00f6zden ge\u00e7irin.<\/li>\n<\/ul>\n<h2><span id=\"DCHost_Ortaminda_Pratik_Bir_IPv6_Gecis_Plani\">DCHost Ortam\u0131nda Pratik Bir IPv6 Ge\u00e7i\u015f Plan\u0131<\/span><\/h2>\n<p>\u015eimdiye kadar par\u00e7a par\u00e7a ele ald\u0131\u011f\u0131m\u0131z konular\u0131, DCHost \u00fczerinde kullan\u0131lan tipik bir VPS senaryosu i\u00e7in somut bir yol haritas\u0131nda toplayal\u0131m. \u00d6zellikle staging ve canl\u0131 ortam ayr\u0131m\u0131 olan projelerde bu ad\u0131mlar\u0131 s\u0131rayla izlemek ciddi rahatl\u0131k sa\u011flayacakt\u0131r.<\/p>\n<ol>\n<li><strong>Panelden IPv6 bilgilerinizi netle\u015ftirin:<\/strong> VPS y\u00f6netim ekran\u0131nda IPv6 adresi, prefix ve gateway bilgilerinizi not al\u0131n. Emin de\u011filseniz destek ile teyit edin.<\/li>\n<li><strong>\u00d6nce staging\/deneme bir VPS&#8217;te uygulay\u0131n:<\/strong> Canl\u0131 sitenizi riske atmadan, ayn\u0131 imaja sahip test bir VPS \u00fczerinde IPv6 adresini ekleyin ve t\u00fcm ad\u0131mlar\u0131 deneyin.<\/li>\n<li><strong>\u0130\u015fletim sistemi konfig\u00fcrasyonunu yap\u0131n:<\/strong> Debian\/Ubuntu&#8217;da netplan ya da interfaces, RHEL tabanl\u0131 sistemlerde nmcli\/ifcfg ile statik IPv6 adresi ve gateway tan\u0131mlay\u0131n.<\/li>\n<li><strong>G\u00fcvenlik duvar\u0131n\u0131 g\u00fcncelleyin:<\/strong> IPv4 i\u00e7in tan\u0131ml\u0131 kritik portlar\u0131n (22, 80, 443, gerekliyse 25 vb.) IPv6 i\u00e7in de a\u00e7\u0131k oldu\u011fundan emin olun. Gerekirse nftables gibi daha geli\u015fmi\u015f bir katmana ge\u00e7in.<\/li>\n<li><strong>DNS taraf\u0131nda AAAA kayd\u0131n\u0131 ekleyin:<\/strong> Alan ad\u0131n\u0131z i\u00e7in web trafi\u011fini y\u00f6nlendiren kay\u0131tlara mutlaka AAAA kar\u015f\u0131l\u0131klar\u0131 ekleyin. CDN ya da harici DNS kullan\u0131yorsan\u0131z oradaki paneli de g\u00fcncelleyin.<\/li>\n<li><strong>Web sunucusu ve uygulamay\u0131 test edin:<\/strong> Nginx\/Apache konfig\u00fcrasyonlar\u0131nda IPv6 dinleme ayarlar\u0131n\u0131 kontrol edin, curl -6 ve farkl\u0131 a\u011flardan ger\u00e7ek taray\u0131c\u0131 testleri yap\u0131n.<\/li>\n<li><strong>E-posta ve reverse DNS&#8217;i planlay\u0131n:<\/strong> SMTP trafi\u011finiz varsa PTR, SPF ve di\u011fer e-posta g\u00fcvenlik ayarlar\u0131n\u0131 IPv6&#8217;y\u0131 da kapsayacak \u015fekilde g\u00f6zden ge\u00e7irin. \u0130lk a\u015famada sadece web trafi\u011fi i\u00e7in IPv6 a\u00e7mak da makul bir strateji olabilir.<\/li>\n<\/ol>\n<p>Bu s\u00fcre\u00e7te, IPv6 ge\u00e7i\u015finizi i\u015fletmenizin genel IP stratejisiyle uyumlu h\u00e2le getirmek isterseniz, <a href=\"https:\/\/www.dchost.com\/blog\/ipv4-tukenmesi-ve-fiyat-artislari-teknik-arka-plan-ve-somut-cikis-yollari\/\">IPv4 t\u00fckenmesi ve \u00e7\u00f6z\u00fcm stratejilerini detayland\u0131rd\u0131\u011f\u0131m\u0131z rehber<\/a> ile birlikte d\u00fc\u015f\u00fcnmek uzun vadede ciddi avantaj sa\u011flar.<\/p>\n<h2><span id=\"Sonuc_IPv68217yi_Sadece_Acmayin_Bilincli_Sekilde_Hayata_Gecirin\">Sonu\u00e7: IPv6&#8217;y\u0131 Sadece A\u00e7may\u0131n, Bilin\u00e7li \u015eekilde Hayata Ge\u00e7irin<\/span><\/h2>\n<p>IPv6, uzun y\u0131llar boyunca &#8216;ileride mutlaka ge\u00e7eriz&#8217; denilen ama bir t\u00fcrl\u00fc \u00f6ncelik listesinde yukar\u0131 \u00e7\u0131kamayan bir konuydu. Bug\u00fcn ise IPv4 maliyetleri, yeni a\u011flar\u0131n b\u00fcy\u00fck k\u0131sm\u0131n\u0131n do\u011frudan IPv6 ile kurulmas\u0131 ve mobil trafi\u011fin a\u011f\u0131rl\u0131\u011f\u0131 nedeniyle bu l\u00fcks yava\u015f yava\u015f ortadan kalk\u0131yor. DCHost taraf\u0131nda da hem veri merkezi hem de VPS platformlar\u0131m\u0131z\u0131 IPv6&#8217;y\u0131 bir yan \u00f6zellik de\u011fil, varsay\u0131lan kabul eden bir noktaya ta\u015f\u0131mak i\u00e7in ciddi yat\u0131r\u0131mlar yap\u0131yoruz.<\/p>\n<p>Bu rehberde VPS sunucunuzda IPv6 kurulumunu i\u015fletim sistemi, g\u00fcvenlik duvar\u0131, DNS, web sunucusu ve e-posta katmanlar\u0131yla birlikte ele ald\u0131k. Art\u0131k elinizde sadece &#8216;IPv6&#8217;y\u0131 a\u00e7t\u0131m&#8217; demekle kalmayan, ger\u00e7ekten \u00f6l\u00e7\u00fclebilir fayda sa\u011flayabilecek bir yol haritas\u0131 var. Bir sonraki ad\u0131m olarak, daha ileri senaryolar (\u00f6rne\u011fin IPv6-only VPS mimarileri, NAT64\/DNS64, ileri seviye firewall kurallar\u0131) i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/ipv6%e2%80%91only-vps-uzerinde-web-sitesi-yayinlamak-nat64-dns64-ile-ipv4e-nasil-kopru-kurulur\/\">IPv6-only hosting rehberimizi<\/a> ve IPv6 ile e-posta taraf\u0131n\u0131 ayr\u0131nt\u0131l\u0131 anlatan <a href=\"https:\/\/www.dchost.com\/blog\/ipv6-ile-e-posta-gonderimi-reverse-dns-spf-ve-teslim-edilebilirlik-rehberi\/\">teslim edilebilirlik odakl\u0131 makalemizi<\/a> okuman\u0131z\u0131 tavsiye ederim.<\/p>\n<p>E\u011fer DCHost \u00fczerinde h\u00e2lihaz\u0131rda \u00e7al\u0131\u015fan bir VPS&#8217;iniz varsa ve IPv6 ge\u00e7i\u015fini planl\u0131, kontroll\u00fc \u015fekilde yapmak istiyorsan\u0131z, altyap\u0131 ekibimizle birlikte proje bazl\u0131 bir ge\u00e7i\u015f plan\u0131 \u00e7\u0131karmaktan memnuniyet duyar\u0131z. Yeni bir proje i\u00e7in VPS, <a href=\"https:\/\/www.dchost.com\/tr\/fiziksel-sunucu\">dedicated sunucu<\/a> ya da colocation d\u00fc\u015f\u00fcn\u00fcyorsan\u0131z da, ilk g\u00fcnden itibaren IPv6&#8217;y\u0131 mimarinin do\u011fal bir par\u00e7as\u0131 olacak \u015fekilde tasarlaman\u0131z uzun vadede hem maliyet hem de operasyonel sadele\u015fme a\u00e7\u0131s\u0131ndan b\u00fcy\u00fck avantaj sa\u011flayacakt\u0131r.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>\u0130&ccedil;indekiler1 IPv6&#8217;y\u0131 VPS Sunucunuza Ta\u015f\u0131mak Neden Art\u0131k Ertelenmemeli?2 Temel Kavramlar: IPv6 Adres Yap\u0131s\u0131, \/64, Gateway ve DNS2.1 IPv6 adres tipleri ve yaz\u0131m bi\u00e7imi2.2 \u00d6nek (prefix) ve \/64 mant\u0131\u011f\u01312.3 DNS taraf\u0131: AAAA ve PTR (reverse) kay\u0131tlar\u01313 VPS Ortam\u0131nda IPv6 Planlamas\u0131: Dual-Stack, IPv6-Only ve Senaryolar3.1 Dual-stack mi, IPv6-only mi?3.2 VPS sa\u011flay\u0131c\u0131n\u0131zdan alman\u0131z gereken bilgiler4 Debian\/Ubuntu Tabanl\u0131 VPS&#8217;te [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":4146,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-4145","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\/4145","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=4145"}],"version-history":[{"count":0,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/4145\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/4146"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=4145"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=4145"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=4145"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}