{"id":3376,"date":"2025-12-25T23:55:31","date_gmt":"2025-12-25T20:55:31","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/ripe-ncc-ip-tahsislerinde-yeni-kurallar-ipv4-kitligi-ve-ipv6-stratejisi-nasil-yeniden-sekilleniyor\/"},"modified":"2025-12-25T23:55:31","modified_gmt":"2025-12-25T20:55:31","slug":"ripe-ncc-ip-tahsislerinde-yeni-kurallar-ipv4-kitligi-ve-ipv6-stratejisi-nasil-yeniden-sekilleniyor","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/ripe-ncc-ip-tahsislerinde-yeni-kurallar-ipv4-kitligi-ve-ipv6-stratejisi-nasil-yeniden-sekilleniyor\/","title":{"rendered":"RIPE NCC IP Tahsislerinde Yeni Kurallar: IPv4 K\u0131tl\u0131\u011f\u0131 ve IPv6 Stratejisi Nas\u0131l Yeniden \u015eekilleniyor?"},"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=\"#RIPE_NCC_IP_Tahsislerinde_Yeni_Donem_Neden_Bu_Kadar_Onemli\"><span class=\"toc_number toc_depth_1\">1<\/span> RIPE NCC IP Tahsislerinde Yeni D\u00f6nem: Neden Bu Kadar \u00d6nemli?<\/a><\/li><li><a href=\"#RIPE_NCC_ve_IP_Tahsis_Surecinin_Yeni_Gercegi\"><span class=\"toc_number toc_depth_1\">2<\/span> RIPE NCC ve IP Tahsis S\u00fcrecinin Yeni Ger\u00e7e\u011fi<\/a><\/li><li><a href=\"#Yeni_RIPE_NCC_IP_Tahsis_Kurallarinin_Ana_Hatlari\"><span class=\"toc_number toc_depth_1\">3<\/span> Yeni RIPE NCC IP Tahsis Kurallar\u0131n\u0131n Ana Hatlar\u0131<\/a><ul><li><a href=\"#1_Yeni_IPv4_Tahsisleri_Son_24_Mantigi\"><span class=\"toc_number toc_depth_2\">3.1<\/span> 1) Yeni IPv4 Tahsisleri: \u201cSon \/24\u201d Mant\u0131\u011f\u0131<\/a><\/li><li><a href=\"#2_Bekleme_Listesi_ve_Kitlik_Yonetimi\"><span class=\"toc_number toc_depth_2\">3.2<\/span> 2) Bekleme Listesi ve K\u0131tl\u0131k Y\u00f6netimi<\/a><\/li><li><a href=\"#3_Transfer_Kurallarinin_Sikilasmasi_ve_Spekulasyon_Engeli\"><span class=\"toc_number toc_depth_2\">3.3<\/span> 3) Transfer Kurallar\u0131n\u0131n S\u0131k\u0131la\u015fmas\u0131 ve Spek\u00fclasyon Engeli<\/a><\/li><li><a href=\"#4_IPv6_Tahsisleri_ve_Artik_Kacis_Yok_Noktasi\"><span class=\"toc_number toc_depth_2\">3.4<\/span> 4) IPv6 Tahsisleri ve \u201cArt\u0131k Ka\u00e7\u0131\u015f Yok\u201d Noktas\u0131<\/a><\/li><li><a href=\"#5_RIPE_Database_RPKI_ve_Seffaflik_Beklentisi\"><span class=\"toc_number toc_depth_2\">3.5<\/span> 5) RIPE Database, RPKI ve \u015eeffafl\u0131k Beklentisi<\/a><\/li><\/ul><\/li><li><a href=\"#IPv4_Kitligi_Maliyet_Baskisi_ve_Operasyonel_Etkiler\"><span class=\"toc_number toc_depth_1\">4<\/span> IPv4 K\u0131tl\u0131\u011f\u0131, Maliyet Bask\u0131s\u0131 ve Operasyonel Etkiler<\/a><ul><li><a href=\"#IPv4_Adresi_Artik_Stratejik_Bir_Kaynak\"><span class=\"toc_number toc_depth_2\">4.1<\/span> IPv4 Adresi Art\u0131k Stratejik Bir Kaynak<\/a><\/li><li><a href=\"#Fiyat_Artislari_Butce_Planlamasinda_Yeni_Satir\"><span class=\"toc_number toc_depth_2\">4.2<\/span> Fiyat Art\u0131\u015flar\u0131: B\u00fct\u00e7e Planlamas\u0131nda Yeni Sat\u0131r<\/a><\/li><li><a href=\"#Ag_Tasariminda_NAT_Proxy_ve_Coklu_Kiraci_Mimariler\"><span class=\"toc_number toc_depth_2\">4.3<\/span> A\u011f Tasar\u0131m\u0131nda NAT, Proxy ve \u00c7oklu Kirac\u0131 Mimariler<\/a><\/li><\/ul><\/li><li><a href=\"#IPv6_Zorunluluguna_Dogru_Stratejinizi_Nasil_Kaydirmalisiniz\"><span class=\"toc_number toc_depth_1\">5<\/span> IPv6 Zorunlulu\u011funa Do\u011fru: Stratejinizi Nas\u0131l Kayd\u0131rmal\u0131s\u0131n\u0131z?<\/a><ul><li><a href=\"#1_Mevcut_IPv4_Envanterinizi_Gercekci_Sekilde_Cikarin\"><span class=\"toc_number toc_depth_2\">5.1<\/span> 1) Mevcut IPv4 Envanterinizi Ger\u00e7ek\u00e7i \u015eekilde \u00c7\u0131kar\u0131n<\/a><\/li><li><a href=\"#2_Yeni_Projeleri_IPv6-First_Mantigiyla_Tasarlayin\"><span class=\"toc_number toc_depth_2\">5.2<\/span> 2) Yeni Projeleri \u201cIPv6-First\u201d Mant\u0131\u011f\u0131yla Tasarlay\u0131n<\/a><\/li><li><a href=\"#3_Uygulama_ve_Veritabani_Katmaninda_Hazirlik\"><span class=\"toc_number toc_depth_2\">5.3<\/span> 3) Uygulama ve Veritaban\u0131 Katman\u0131nda Haz\u0131rl\u0131k<\/a><\/li><li><a href=\"#4_Hosting_ve_Veri_Merkezi_Stratejinizi_Gozden_Gecirin\"><span class=\"toc_number toc_depth_2\">5.4<\/span> 4) Hosting ve Veri Merkezi Stratejinizi G\u00f6zden Ge\u00e7irin<\/a><\/li><\/ul><\/li><li><a href=\"#LIRler_Kurumsal_Aglar_ve_Hosting_Musterileri_Icin_Uygulanabilir_Kontrol_Listesi\"><span class=\"toc_number toc_depth_1\">6<\/span> LIR\u2019ler, Kurumsal A\u011flar ve Hosting M\u00fc\u015fterileri \u0130\u00e7in Uygulanabilir Kontrol Listesi<\/a><ul><li><a href=\"#Adim_1_Politika_ve_Sozlesmelerinizi_Guncelleyin\"><span class=\"toc_number toc_depth_2\">6.1<\/span> Ad\u0131m 1: Politika ve S\u00f6zle\u015fmelerinizi G\u00fcncelleyin<\/a><\/li><li><a href=\"#Adim_2_Ag_Tasariminizi_IP_Kitligina_Gore_Revize_Edin\"><span class=\"toc_number toc_depth_2\">6.2<\/span> Ad\u0131m 2: A\u011f Tasar\u0131m\u0131n\u0131z\u0131 IP K\u0131tl\u0131\u011f\u0131na G\u00f6re Revize Edin<\/a><\/li><li><a href=\"#Adim_3_IPv6_Yayginlastirma_Plani_Hazirlayin\"><span class=\"toc_number toc_depth_2\">6.3<\/span> Ad\u0131m 3: IPv6 Yayg\u0131nla\u015ft\u0131rma Plan\u0131 Haz\u0131rlay\u0131n<\/a><\/li><li><a href=\"#Adim_4_RIPE_Database_ve_RPKI_Temizligini_Yapin\"><span class=\"toc_number toc_depth_2\">6.4<\/span> Ad\u0131m 4: RIPE Database ve RPKI Temizli\u011fini Yap\u0131n<\/a><\/li><li><a href=\"#Adim_5_Izleme_Loglama_ve_Guvenlik\"><span class=\"toc_number toc_depth_2\">6.5<\/span> Ad\u0131m 5: \u0130zleme, Loglama ve G\u00fcvenlik<\/a><\/li><\/ul><\/li><li><a href=\"#DCHost_ile_Yeni_RIPE_NCC_Kurallarina_Uyum_Nasil_Yardimci_Oluyoruz\"><span class=\"toc_number toc_depth_1\">7<\/span> DCHost ile Yeni RIPE NCC Kurallar\u0131na Uyum: Nas\u0131l Yard\u0131mc\u0131 Oluyoruz?<\/a><\/li><\/ul><\/div>\n<h2><span id=\"RIPE_NCC_IP_Tahsislerinde_Yeni_Donem_Neden_Bu_Kadar_Onemli\">RIPE NCC IP Tahsislerinde Yeni D\u00f6nem: Neden Bu Kadar \u00d6nemli?<\/span><\/h2>\n<p>A\u011f tasar\u0131m\u0131, kapasite planlama veya maliyet analizi yapt\u0131\u011f\u0131n\u0131z her toplant\u0131da ayn\u0131 soru art\u0131k daha sert bi\u00e7imde kar\u015f\u0131m\u0131za \u00e7\u0131k\u0131yor: \u201cYeni projeler i\u00e7in nereden IP bulaca\u011f\u0131z ve bu bize ne kadara mal olacak?\u201d Avrupa, Orta Do\u011fu ve baz\u0131 Orta Asya \u00fclkelerini kapsayan b\u00f6lgesel adres kay\u0131t otoritesi RIPE NCC, tam da bu bask\u0131lar\u0131n ortas\u0131nda IP tahsis kurallar\u0131n\u0131 son y\u0131llarda ciddi \u015fekilde s\u0131k\u0131la\u015ft\u0131rd\u0131. \u00d6zellikle IPv4 adresleri neredeyse tamamen t\u00fckendi\u011fi i\u00e7in, bug\u00fcn art\u0131k IP blo\u011fu almak birka\u00e7 form doldurup beklemekten \u00e7ok daha karma\u015f\u0131k bir s\u00fcrece d\u00f6n\u00fc\u015fm\u00fc\u015f durumda.<\/p>\n<p>Bu makalede, RIPE NCC IP tahsislerindeki yeni kurallar\u0131 sade bir dille \u00f6zetleyip; LIR\u2019ler (Local Internet Registry), hosting \u015firketleri, kurumsal a\u011flar ve SaaS projeleri a\u00e7\u0131s\u0131ndan ne anlama geldi\u011fini netle\u015ftirece\u011fiz. DCHost taraf\u0131nda kendi altyap\u0131m\u0131z\u0131 planlarken ve m\u00fc\u015fterilerimize IP haz\u0131rl\u0131\u011f\u0131 yaparken ya\u015fad\u0131\u011f\u0131m\u0131z pratik deneyimleri de araya serpi\u015ftirerek konu\u015faca\u011f\u0131z. Amac\u0131m\u0131z; \u201cpolitika metni\u201d okumak zorunda kalmadan, IPv4 k\u0131tl\u0131\u011f\u0131 ve IPv6 ge\u00e7i\u015fi ba\u011flam\u0131nda \u00f6n\u00fcm\u00fczdeki 3\u20135 y\u0131l\u0131 mant\u0131kl\u0131 bi\u00e7imde planlayabilmenizi sa\u011flamak.<\/p>\n<h2><span id=\"RIPE_NCC_ve_IP_Tahsis_Surecinin_Yeni_Gercegi\">RIPE NCC ve IP Tahsis S\u00fcrecinin Yeni Ger\u00e7e\u011fi<\/span><\/h2>\n<p>\u00d6nce tabloyu netle\u015ftirelim: RIPE NCC, b\u00f6lgemizdeki IP adreslerini ve AS numaralar\u0131n\u0131 da\u011f\u0131tan b\u00f6lgesel internet kay\u0131t kurumu (RIR). \u00dcyeleri genellikle LIR stat\u00fcs\u00fcndeki operat\u00f6rler, ISP\u2019ler, veri merkezi ve hosting sa\u011flay\u0131c\u0131lar\u0131 ile b\u00fcy\u00fck kurumsal a\u011flar. Yani siz de bir hosting m\u00fc\u015fterisi, kurumsal IT ekibi veya SaaS geli\u015ftiricisi olarak, asl\u0131nda bu zincirin bir par\u00e7as\u0131s\u0131n\u0131z.<\/p>\n<p>IPv4 adresleri uzun s\u00fcredir \u201ct\u00fckeniyor\u201d diyoruz; ama RIPE b\u00f6lgesinde bu art\u0131k teorik bir risk de\u011fil, pratik bir ger\u00e7ek. IPv4 adreslerinin k\u0131tl\u0131\u011f\u0131 ve <a href=\"https:\/\/www.dchost.com\/blog\/ipv4-adreslerinin-tukenmesi-ve-fiyat-artisi\/\">IPv4 fiyatlar\u0131n\u0131n h\u0131zla artmas\u0131<\/a> y\u00fcz\u00fcnden RIPE NCC, tahsis politikas\u0131n\u0131 \u00fc\u00e7 ana eksende s\u0131k\u0131la\u015ft\u0131rd\u0131:<\/p>\n<ul>\n<li>Yeni IPv4 tahsisleri i\u00e7in \u00e7ok s\u0131n\u0131rl\u0131 ve k\u00fc\u00e7\u00fck bloklar (tipik olarak tek bir \/24),<\/li>\n<li>Bekleme listesi ve tahsis \u00f6nceli\u011finin yeniden tan\u0131mlanmas\u0131,<\/li>\n<li>Transfer ve \u00e7oklu LIR a\u00e7arak \u201cadres avc\u0131l\u0131\u011f\u0131\u201d yap\u0131lmas\u0131n\u0131 \u00f6nlemeye d\u00f6n\u00fck kurallar.<\/li>\n<\/ul>\n<p>Buna paralel olarak IPv6 taraf\u0131nda ise te\u015fvik edici, hatta baz\u0131 durumlarda fiilen zorlay\u0131c\u0131 diyebilece\u011fimiz ad\u0131mlar g\u00f6r\u00fcyoruz: Yeni LIR\u2019lerin IPv6 blo\u011fu almadan a\u011f kurmas\u0131 pratikte anlams\u0131z hale geliyor; operat\u00f6rler ve hosting \u015firketleri ise projeleri giderek \u201cIPv6-first\u201d d\u00fc\u015f\u00fcnmeye zorlan\u0131yor. Bu e\u011filimin daha geni\u015f resmini merak ediyorsan\u0131z, <a href=\"https:\/\/www.dchost.com\/blog\/ipv6-benimseme-oranlarindaki-artis-performans-guvenlik-ve-maliyet-dengesi\/\">IPv6 benimseme oranlar\u0131ndaki art\u0131\u015f\u0131n performans ve maliyet dengesine etkilerini anlatt\u0131\u011f\u0131m\u0131z yaz\u0131m\u0131z<\/a> iyi bir tamamlay\u0131c\u0131 olacakt\u0131r.<\/p>\n<h2><span id=\"Yeni_RIPE_NCC_IP_Tahsis_Kurallarinin_Ana_Hatlari\">Yeni RIPE NCC IP Tahsis Kurallar\u0131n\u0131n Ana Hatlar\u0131<\/span><\/h2>\n<p>Politika dok\u00fcmanlar\u0131n\u0131n t\u00fcm maddelerini tek tek saymak yerine, sahada ger\u00e7ekten i\u015finizi de\u011fi\u015ftiren ba\u015fl\u0131klara odaklanal\u0131m.<\/p>\n<h3><span id=\"1_Yeni_IPv4_Tahsisleri_Son_24_Mantigi\">1) Yeni IPv4 Tahsisleri: \u201cSon \/24\u201d Mant\u0131\u011f\u0131<\/span><\/h3>\n<p>Art\u0131k RIPE NCC\u2019den yeni IPv4 blo\u011fu istemek, \u201cgereksinim formu doldurup \/22 almak\u201d gibi eski d\u00fczen de\u011fil. Son d\u00f6nemde uygulanan yakla\u015f\u0131m, LIR ba\u015f\u0131na en fazla tek bir k\u00fc\u00e7\u00fck blok mant\u0131\u011f\u0131yla ilerliyor; pratikte bu genellikle bir <strong>\/24 (256 IP)<\/strong> anlam\u0131na geliyor. Bunun da ad\u0131 \u00fczerinde \u201cson\u201d tahsis oldu\u011fu a\u00e7\u0131k\u00e7a belirtiliyor; yani \u201cbiraz daha b\u00fcy\u00fcd\u00fck, ikinci \/24 gelir mi?\u201d beklentisi ger\u00e7ek\u00e7i de\u011fil.<\/p>\n<p>Bu ne demek?<\/p>\n<ul>\n<li>Yeni kurulan LIR\u2019ler, sadece k\u00fc\u00e7\u00fck \u00f6l\u00e7ekli bir IPv4 blo\u011funa sahip olabiliyor.<\/li>\n<li>B\u00fcy\u00fck projeler i\u00e7in gereken IPv4 adresleri, ya ikincil piyasa (transferler) ya da mevcut bloklar\u0131n optimize edilmesiyle sa\u011flanmak zorunda.<\/li>\n<li>Hosting m\u00fc\u015fterisi olarak do\u011frudan RIPE\u2019den blok almak yerine, \u00e7o\u011fu zaman sa\u011flay\u0131c\u0131n\u0131z \u00fczerinden IPv4 kiralama yoluna gideceksiniz.<\/li>\n<\/ul>\n<p>DCHost olarak biz de kendi IP envanterimizi planlarken, yeni \/24 tahsislerini \u201cstratejik tampon\u201d gibi de\u011ferlendiriyor, as\u0131l kapasiteyi ise elimizdeki bloklar\u0131n verimli kullan\u0131m\u0131 ve IPv6\u2019ya agresif ge\u00e7i\u015fle \u00e7\u00f6z\u00fcyoruz.<\/p>\n<h3><span id=\"2_Bekleme_Listesi_ve_Kitlik_Yonetimi\">2) Bekleme Listesi ve K\u0131tl\u0131k Y\u00f6netimi<\/span><\/h3>\n<p>IPv4 sto\u011fu bitmi\u015f bir kaynak oldu\u011fu i\u00e7in RIPE NCC, zaman zaman geri d\u00f6nen (geri verilen veya iptal edilen) bloklar\u0131 yeniden da\u011f\u0131tmak zorunda kal\u0131yor. Bu da\u011f\u0131t\u0131m da <strong>bekleme listesi<\/strong> \u00fczerinden yap\u0131l\u0131yor. Temel mant\u0131k \u015f\u00f6yle:<\/p>\n<ul>\n<li>Yeni (veya baz\u0131 durumlarda daha \u00f6nce tahsis almam\u0131\u015f) LIR\u2019ler ba\u015fvuru yapt\u0131ktan sonra s\u0131raya giriyor.<\/li>\n<li>Bo\u015fa \u00e7\u0131kan k\u00fc\u00e7\u00fck IPv4 bloklar\u0131, bu s\u0131radaki LIR\u2019lere belirlenmi\u015f kurallar \u00e7er\u00e7evesinde tahsis ediliyor.<\/li>\n<li>Bekleme s\u00fcresi; ba\u015fvuru yo\u011funlu\u011fu, geri d\u00f6nen adres miktar\u0131 ve b\u00f6lgesel talebe g\u00f6re de\u011fi\u015fiyor.<\/li>\n<\/ul>\n<p>Ger\u00e7ek hayatta bu ne anlama geliyor? Bir projeye alt\u0131 ay sonra ba\u015flayaca\u011f\u0131n\u0131z\u0131 biliyorsan\u0131z, IP plan\u0131n\u0131 da alt\u0131 ay \u00f6nceden d\u00fc\u015f\u00fcnmek zorundas\u0131n\u0131z. \u201cSunucu haz\u0131r, IP\u2019yi yar\u0131n al\u0131r\u0131z\u201d yakla\u015f\u0131m\u0131 art\u0131k i\u015flemez hale geldi. Biz DCHost taraf\u0131nda, b\u00fcy\u00fck projeler i\u00e7in kapasite planlarken IP ihtiyac\u0131n\u0131 en ba\u015ftan konu\u015fuyor; gerekirse projeyi kademeli devreye alarak IP kullan\u0131m\u0131n\u0131 zamana yay\u0131yoruz.<\/p>\n<h3><span id=\"3_Transfer_Kurallarinin_Sikilasmasi_ve_Spekulasyon_Engeli\">3) Transfer Kurallar\u0131n\u0131n S\u0131k\u0131la\u015fmas\u0131 ve Spek\u00fclasyon Engeli<\/span><\/h3>\n<p>IPv4 k\u0131tl\u0131\u011f\u0131 ortaya \u00e7\u0131kt\u0131\u011f\u0131nda, piyasada do\u011fal olarak \u201cIP ticareti\u201d canland\u0131. Baz\u0131 akt\u00f6rler sadece adres al\u0131p satarak gelir elde etmeye \u00e7al\u0131\u015ft\u0131. RIPE toplulu\u011fu, bu t\u00fcr spek\u00fclasyonu s\u0131n\u0131rlamak i\u00e7in transfer kurallar\u0131n\u0131 s\u0131k\u0131la\u015ft\u0131rd\u0131. Ana maddeleri sadele\u015ftirirsek:<\/p>\n<ul>\n<li>Tahsis edilmi\u015f bir IPv4 blo\u011funu hemen transfer etmek m\u00fcmk\u00fcn de\u011fil; <strong>belirli bir elde tutma s\u00fcresi<\/strong> (holding period) s\u00f6z konusu.<\/li>\n<li>S\u0131rf daha fazla IPv4 kapmak i\u00e7in ayn\u0131 ki\u015fi veya kurumun birden fazla LIR a\u00e7arak sistemi \u201cbypass etmesi\u201d politikalarla a\u00e7\u0131k\u00e7a hedefleniyor.<\/li>\n<li>Transferlerde \u015feffafl\u0131k, kay\u0131tlar\u0131n do\u011fru tutulmas\u0131 ve RIPE Database \u00fczerinde g\u00fcncel whois bilgilerinin olmas\u0131 zorunlu.<\/li>\n<\/ul>\n<p>Bu kurallar, bir anda \u201chadi ba\u015fka bir LIR a\u00e7\u0131p ikinci \/24\u2019\u00fc kapal\u0131m\u201d gibi planlar\u0131 b\u00fcy\u00fck oranda anlams\u0131z hale getirdi. Uzun vadede IP\u2019yi \u201cfinansal yat\u0131r\u0131m arac\u0131\u201d de\u011fil, a\u011f kayna\u011f\u0131 olarak g\u00f6rmeye zorlayan bir yakla\u015f\u0131m bu. IPv4 transfer piyasas\u0131n\u0131n i\u015fleyi\u015fini ve di\u011fer RIR b\u00f6lgesindeki (\u00f6rne\u011fin ARIN) yakla\u015f\u0131mlar\u0131 merak ediyorsan\u0131z, <a href=\"https:\/\/www.dchost.com\/blog\/arin-ip-tahsis-degisiklikleri-ipv4-kitligi-ipv6-stratejisi-ve-operasyonel-etkiler\/\">ARIN IP tahsis de\u011fi\u015fikliklerini anlatt\u0131\u011f\u0131m\u0131z yaz\u0131<\/a> kar\u015f\u0131la\u015ft\u0131rma yapmak i\u00e7in faydal\u0131 olabilir.<\/p>\n<h3><span id=\"4_IPv6_Tahsisleri_ve_Artik_Kacis_Yok_Noktasi\">4) IPv6 Tahsisleri ve \u201cArt\u0131k Ka\u00e7\u0131\u015f Yok\u201d Noktas\u0131<\/span><\/h3>\n<p>IPv4 taraf\u0131 s\u0131k\u0131la\u015f\u0131rken, IPv6 i\u00e7in tablo farkl\u0131: RIPE NCC IPv6 adreslerini olduk\u00e7a c\u00f6mert ve gelece\u011fe d\u00f6n\u00fck \u015fekilde tahsis ediyor. Yeni kurallar ve pratik uygulama \u015fu mesaj\u0131 veriyor: \u201cGer\u00e7ek b\u00fcy\u00fcmeyi IPv6 \u00fczerinde planlay\u0131n.\u201d<\/p>\n<p>Tipik olarak bir LIR, tek bir IPv6 blo\u011fu ile milyonlarca, hatta milyarlarca son kullan\u0131c\u0131 cihaz\u0131n\u0131 numaraland\u0131rabilecek kadar geni\u015f bir adres alan\u0131 alabiliyor. Buradaki kritik nokta; IPv6 blo\u011funa sahip olman\u0131n tek ba\u015f\u0131na yeterli olmad\u0131\u011f\u0131, <strong>operasyonel olarak IPv6\u2019y\u0131 ger\u00e7ekten yay\u0131na alman\u0131z gerekti\u011fi<\/strong>. Yani:<\/p>\n<ul>\n<li>Sunucular\u0131n\u0131zda ve router\u2019lar\u0131n\u0131zda IPv6 konfig\u00fcrasyonu,<\/li>\n<li>Firewall kurallar\u0131n\u0131z\u0131n IPv6\u2019y\u0131 kapsamas\u0131,<\/li>\n<li>DNS\u2019te AAAA kay\u0131tlar\u0131n\u0131n a\u00e7\u0131lmas\u0131,<\/li>\n<li>Uygulama katman\u0131nda IPv6 fark\u0131ndal\u0131\u011f\u0131 (log formatlar\u0131, rate-limit, eri\u015fim kontrol\u00fc vb.).<\/li>\n<\/ul>\n<p>DCHost altyap\u0131s\u0131nda yeni projeleri tasarlarken, art\u0131k subnet \u015femas\u0131n\u0131 \u00f6nce IPv6 i\u00e7in kuruyor, IPv4\u2019\u00fc ise \u00e7o\u011fu zaman NAT ve payla\u015f\u0131ml\u0131 kullan\u0131m senaryolar\u0131 \u00fczerinden d\u00fc\u015f\u00fcn\u00fcyoruz. Benzer bir yolu sizin a\u011f\u0131n\u0131z i\u00e7in de \u00e7izmek istiyorsan\u0131z, daha teknik bir ba\u015flang\u0131\u00e7 noktas\u0131 olarak <a href=\"https:\/\/www.dchost.com\/blog\/vps-sunucunuzda-ipv6-kurulum-ve-yapilandirma-rehberi-2\/\">VPS sunucunuzda IPv6 kurulum ve yap\u0131land\u0131rma rehberimize<\/a> g\u00f6z atabilirsiniz.<\/p>\n<h3><span id=\"5_RIPE_Database_RPKI_ve_Seffaflik_Beklentisi\">5) RIPE Database, RPKI ve \u015eeffafl\u0131k Beklentisi<\/span><\/h3>\n<p>Yeni tahsis ve transfer kurallar\u0131 kadar \u00f6nemli bir di\u011fer eksen de <strong>\u015feffafl\u0131k ve y\u00f6nlendirme g\u00fcvenli\u011fi<\/strong>. RIPE NCC ekosisteminde art\u0131k \u015fu beklentiler standart hale geliyor:<\/p>\n<ul>\n<li>IP ve ASN kay\u0131tlar\u0131n\u0131n RIPE Database \u00fczerinde g\u00fcncel tutulmas\u0131,<\/li>\n<li>Her blok i\u00e7in do\u011fru <code>abuse-c<\/code> ve ileti\u015fim bilgilerinin tan\u0131mlanmas\u0131,<\/li>\n<li>BGP\u2019de IP\u2019nizi kimin hangi AS ile anons edebilece\u011fini belirleyen RPKI (ROA kay\u0131tlar\u0131) kullan\u0131m\u0131,<\/li>\n<li>Route object\u2019lerin yarat\u0131lmas\u0131 ve d\u00fczenli g\u00fcncellenmesi.<\/li>\n<\/ul>\n<p>G\u00fcvenlik denetimleri ve siber sald\u0131r\u0131lardaki art\u0131\u015f da bu e\u011filimi g\u00fc\u00e7lendiriyor. \u00d6zellikle DDoS ve BGP hijacking gibi tehditler ba\u011flam\u0131nda, RIPE NCC\u2019nin de te\u015fvik etti\u011fi RPKI s\u00fcre\u00e7leri giderek \u201copsiyonel iyi uygulama\u201d olmaktan \u00e7\u0131k\u0131p fiili bir gereklilik haline geliyor. Bu y\u00f6n\u00fcyle bak\u0131nca, <a href=\"https:\/\/www.dchost.com\/blog\/siber-guvenlik-tehditleri-artiyor-aginizi-ve-sunucularinizi-gercekci-sekilde-nasil-korursunuz\/\">a\u011f ve sunucu g\u00fcvenli\u011fi i\u00e7in ger\u00e7ek\u00e7i yol haritas\u0131n\u0131 anlatt\u0131\u011f\u0131m\u0131z yaz\u0131daki<\/a> tavsiyelerle RIPE taraf\u0131ndaki beklentiler asl\u0131nda ayn\u0131 noktada bulu\u015fuyor.<\/p>\n<h2><span id=\"IPv4_Kitligi_Maliyet_Baskisi_ve_Operasyonel_Etkiler\">IPv4 K\u0131tl\u0131\u011f\u0131, Maliyet Bask\u0131s\u0131 ve Operasyonel Etkiler<\/span><\/h2>\n<p>Politika ba\u015fl\u0131klar\u0131n\u0131 anlad\u0131k; \u015fimdi i\u015fin can yakan k\u0131sm\u0131na gelelim: Bu de\u011fi\u015fiklikler pratikte a\u011f mimarisi, maliyet ve i\u015f planlamas\u0131 a\u00e7\u0131s\u0131ndan ne ifade ediyor?<\/p>\n<h3><span id=\"IPv4_Adresi_Artik_Stratejik_Bir_Kaynak\">IPv4 Adresi Art\u0131k Stratejik Bir Kaynak<\/span><\/h3>\n<p>Eskiden bir\u00e7ok projede IP adreslerini neredeyse s\u0131n\u0131rs\u0131zm\u0131\u015f gibi da\u011f\u0131t\u0131yorduk: Her servise ayr\u0131 IP, her k\u00fc\u00e7\u00fck m\u00fc\u015fteri grubuna \/29, kimi zaman bo\u015fta duran onlarca IP\u2026 IPv4\u2019\u00fcn fiilen t\u00fckenmesi ve <a href=\"https:\/\/www.dchost.com\/blog\/ipv4-adres-fiyatlari-rekor-seviyelere-ulasti\/\">IPv4 adres fiyatlar\u0131n\u0131n rekor seviyelere \u00e7\u0131kmas\u0131<\/a> ile bu rahat d\u00f6nemin kapand\u0131\u011f\u0131n\u0131 kabul etmek zorunday\u0131z.<\/p>\n<p>Bug\u00fcn orta \u00f6l\u00e7ekli bir proje planlarken bile \u015fu sorular\u0131 sormam\u0131z gerekiyor:<\/p>\n<ul>\n<li>Ger\u00e7ekten her node i\u00e7in ayr\u0131 public IP\u2019ye ihtiyac\u0131m\u0131z var m\u0131?<\/li>\n<li>Load balancer ve reverse proxy mimarisiyle tek IP \u00fczerinden birden \u00e7ok servisi sunabilir miyiz?<\/li>\n<li>CGNAT veya 1:N NAT ile son kullan\u0131c\u0131lar\u0131 daha az public IP ile d\u0131\u015far\u0131 \u00e7\u0131karabilir miyiz?<\/li>\n<li>Mail, web ve API trafi\u011fini ayn\u0131 IP \u00fczerinde y\u00f6netmek m\u00fcmk\u00fcn m\u00fc?<\/li>\n<\/ul>\n<p>DCHost taraf\u0131nda yapt\u0131\u011f\u0131m\u0131z yeni projelerde, neredeyse her tasar\u0131m dok\u00fcman\u0131nda \u201cIP b\u00fct\u00e7esi\u201d diye ayr\u0131 bir b\u00f6l\u00fcm a\u00e7\u0131yoruz. CPU ve RAM kadar IP adreslerinin de bir kaynak oldu\u011funu, hatta bir\u00e7ok durumda en pahal\u0131 kaynak oldu\u011funu kabullenmi\u015f durumday\u0131z.<\/p>\n<h3><span id=\"Fiyat_Artislari_Butce_Planlamasinda_Yeni_Satir\">Fiyat Art\u0131\u015flar\u0131: B\u00fct\u00e7e Planlamas\u0131nda Yeni Sat\u0131r<\/span><\/h3>\n<p>IPv4 transfer piyasas\u0131ndaki fiyat art\u0131\u015flar\u0131, do\u011frudan proje maliyetlerine yans\u0131yor. Eskiden donan\u0131m veya lisans kalemleri aras\u0131nda kaybolan IP maliyeti, art\u0131k kendi ba\u015f\u0131na sat\u0131r a\u00e7\u0131lmas\u0131 gereken bir kalem. \u00dcstelik bu maliyet sadece \u201cadres sat\u0131n alma\u201d ile bitmiyor:<\/p>\n<ul>\n<li>RIPE \u00fcye (LIR) \u00fccretleri,<\/li>\n<li>Adres bloklar\u0131n\u0131n y\u00f6netimi, audit s\u00fcre\u00e7leri,<\/li>\n<li>RPKI, route-policy ve g\u00fcvenlik i\u00e7in ayr\u0131lan i\u015f g\u00fcc\u00fc,<\/li>\n<li>IP temelli rate-limit, siyah liste y\u00f6netimi, k\u00f6t\u00fcye kullan\u0131m \u015fikayetlerine yan\u0131t.<\/li>\n<\/ul>\n<p>Buna kar\u015f\u0131l\u0131k, IPv6 taraf\u0131nda adres maliyeti neredeyse s\u0131f\u0131r denecek seviyede. Tam da bu nedenle, <strong>uzun vadeli b\u00fct\u00e7e planlamas\u0131nda b\u00fcy\u00fcmeyi IPv6 \u00fczerinde konumland\u0131rmak<\/strong> neredeyse tek makul se\u00e7enek. IPv4 ise \u201cge\u00e7i\u015f ve uyumluluk katman\u0131\u201d gibi d\u00fc\u015f\u00fcn\u00fclmeli.<\/p>\n<h3><span id=\"Ag_Tasariminda_NAT_Proxy_ve_Coklu_Kiraci_Mimariler\">A\u011f Tasar\u0131m\u0131nda NAT, Proxy ve \u00c7oklu Kirac\u0131 Mimariler<\/span><\/h3>\n<p>IPv4 k\u0131tl\u0131\u011f\u0131, a\u011f tasar\u0131m\u0131n\u0131 da de\u011fi\u015ftiriyor. Daha az say\u0131da public IP ile daha fazla i\u015f yapmak zorunda oldu\u011fumuz i\u00e7in a\u015fa\u011f\u0131daki desenler \u00f6ne \u00e7\u0131k\u0131yor:<\/p>\n<ul>\n<li><strong>Reverse proxy ve load balancer:<\/strong> Tek IP \u00fczerinden birden fazla domain ve uygulama yay\u0131n\u0131.<\/li>\n<li><strong>CGNAT \/ PAT:<\/strong> \u00c7ok say\u0131da i\u00e7 IP\u2019nin birka\u00e7 d\u0131\u015f IP \u00fczerinden internete \u00e7\u0131kmas\u0131.<\/li>\n<li><strong>\u00c7ok kirac\u0131l\u0131 (multi-tenant) uygulama mimarileri:<\/strong> Tek IP \u00fczerinden y\u00fczlerce m\u00fc\u015fteri hesab\u0131 bar\u0131nd\u0131ran SaaS yap\u0131lar\u0131.<\/li>\n<li><strong>\u0130\u00e7 a\u011fda RFC1918 + IPv6, d\u0131\u015fa \u00e7\u0131k\u0131\u015fta minimum IPv4:<\/strong> \u00d6zellikle ofis a\u011flar\u0131nda ve IoT senaryolar\u0131nda yayg\u0131n bir model.<\/li>\n<\/ul>\n<p>DCHost altyap\u0131s\u0131nda da, \u00f6zellikle yo\u011fun trafik alan projelerde \u201cIP ba\u015f\u0131na d\u00fc\u015fen ba\u011flant\u0131\u201d say\u0131s\u0131n\u0131 art\u0131ran bu yakla\u015f\u0131mlar\u0131 tercih ediyoruz. B\u00f6ylece hem IP maliyetini a\u015fa\u011f\u0131 \u00e7ekiyor, hem de y\u00f6nlendirme tablosunu sade tutarak performans ve y\u00f6netilebilirli\u011fi art\u0131r\u0131yoruz.<\/p>\n<h2><span id=\"IPv6_Zorunluluguna_Dogru_Stratejinizi_Nasil_Kaydirmalisiniz\">IPv6 Zorunlulu\u011funa Do\u011fru: Stratejinizi Nas\u0131l Kayd\u0131rmal\u0131s\u0131n\u0131z?<\/span><\/h2>\n<p>RIPE NCC\u2019nin yeni IP tahsis kurallar\u0131n\u0131n arka plan\u0131nda tek bir b\u00fcy\u00fck hedef var: IPv4\u2019\u00fc verimli kullan\u0131rken, ger\u00e7ek geni\u015flemeyi IPv6\u2019ya ta\u015f\u0131mak. Peki pratikte ne yapmal\u0131s\u0131n\u0131z?<\/p>\n<h3><span id=\"1_Mevcut_IPv4_Envanterinizi_Gercekci_Sekilde_Cikarin\">1) Mevcut IPv4 Envanterinizi Ger\u00e7ek\u00e7i \u015eekilde \u00c7\u0131kar\u0131n<\/span><\/h3>\n<p>\u0130lk ad\u0131m, neye sahip oldu\u011funuzu ve nas\u0131l kulland\u0131\u011f\u0131n\u0131z\u0131 netle\u015ftirmek. Biz bir\u00e7ok firmayla \u00e7al\u0131\u015f\u0131rken \u015fu tabloyu g\u00f6r\u00fcyoruz:<\/p>\n<ul>\n<li>Y\u0131llar \u00f6nce al\u0131nm\u0131\u015f ama art\u0131k kullan\u0131lmayan \/29\u2013\/28 bloklar,<\/li>\n<li>Sunuculara atanm\u0131\u015f ama hi\u00e7bir servisin dinlemedi\u011fi IP\u2019ler,<\/li>\n<li>Firewall kurallar\u0131nda \u201ctarihi nedenlerle\u201d b\u0131rak\u0131lm\u0131\u015f ancak bug\u00fcn anlam\u0131n\u0131 yitirmi\u015f tan\u0131mlar.<\/li>\n<\/ul>\n<p>Somut bir egzersiz \u00f6nerisi:<\/p>\n<ol>\n<li>T\u00fcm IPv4 bloklar\u0131n\u0131z\u0131 ve VLAN\/subnet \u015feman\u0131z\u0131 \u00e7\u0131kar\u0131n.<\/li>\n<li>Her IP i\u00e7in: hangi sunucu\/servis, hangi portlar, hangi trafi\u011fi ta\u015f\u0131yor, tek tek etiketleyin.<\/li>\n<li>Kullan\u0131lmayan IP\u2019leri tespit edip ya geri verin ya da yeni projeler i\u00e7in planlay\u0131n.<\/li>\n<li>Gere\u011finden geni\u015f atanm\u0131\u015f subnet\u2019leri b\u00f6lmeyi d\u00fc\u015f\u00fcn\u00fcn.<\/li>\n<\/ol>\n<p>Bu \u00e7al\u0131\u015fma genelde toplam IPv4 havuzunuzun %10\u201320\u2019sini geri kazanman\u0131z\u0131 sa\u011flar; yeni bir blok almaktan \u00f6nce denenmesi gereken en ucuz y\u00f6ntem budur.<\/p>\n<h3><span id=\"2_Yeni_Projeleri_IPv6-First_Mantigiyla_Tasarlayin\">2) Yeni Projeleri \u201cIPv6-First\u201d Mant\u0131\u011f\u0131yla Tasarlay\u0131n<\/span><\/h3>\n<p>Art\u0131k yeni bir uygulama veya servis tasarlarken \u015fu soruyu sormak gerekiyor: \u201cBu sistemi sadece IPv4 ile de\u011fil, ba\u015ftan IPv6 destekli olarak nas\u0131l kurar\u0131z?\u201d DCHost ekibi olarak kendi mimarilerimizde \u015fu prensipleri uyguluyoruz:<\/p>\n<ul>\n<li>Her <a href=\"https:\/\/www.dchost.com\/tr\/vps\">VPS<\/a> veya <a href=\"https:\/\/www.dchost.com\/tr\/fiziksel-sunucu\">dedicated sunucu<\/a>ya hem IPv4 hem IPv6 adresi atamak.<\/li>\n<li>DNS taraf\u0131nda A ve AAAA kay\u0131tlar\u0131n\u0131 birlikte yay\u0131nlamak.<\/li>\n<li>Uygulama log\u2019lar\u0131n\u0131 IPv6 adreslerini do\u011fru g\u00f6sterecek \u015fekilde ayarlamak.<\/li>\n<li>Firewall ve WAF kurallar\u0131n\u0131 IPv6\u2019y\u0131 kapsayacak \u015fekilde tasarlamak.<\/li>\n<\/ul>\n<p>E\u011fer IPv6 ge\u00e7i\u015fi size hala \u201criskli ve karma\u015f\u0131k\u201d geliyorsa, <a href=\"https:\/\/www.dchost.com\/blog\/ipv6-benimseme-oranlarindaki-artis-isletmeler-icin-gercekci-yol-haritasi\/\">IPv6 benimseme oranlar\u0131 ve i\u015fletmeler i\u00e7in ger\u00e7ek\u00e7i yol haritas\u0131n\u0131 anlatt\u0131\u011f\u0131m\u0131z yaz\u0131<\/a> a\u015fama a\u015fama plan \u00e7\u0131karman\u0131za yard\u0131mc\u0131 olabilir.<\/p>\n<h3><span id=\"3_Uygulama_ve_Veritabani_Katmaninda_Hazirlik\">3) Uygulama ve Veritaban\u0131 Katman\u0131nda Haz\u0131rl\u0131k<\/span><\/h3>\n<p>IPv6\u2019y\u0131 sadece a\u011f taraf\u0131 meselesi gibi g\u00f6rmek b\u00fcy\u00fck hata. Uygulama ve veritaban\u0131 katman\u0131nda da haz\u0131rl\u0131k yapmak gerekiyor:<\/p>\n<ul>\n<li>IP adresi saklad\u0131\u011f\u0131n\u0131z alanlar\u0131n veri tipleri (\u00f6rne\u011fin <code>VARCHAR(15)<\/code> yerine <code>INET6<\/code> veya daha geni\u015f string alanlar),<\/li>\n<li>IP bazl\u0131 rate-limit ve g\u00fcvenlik kurallar\u0131 (IPv6 aral\u0131\u011f\u0131 \u00e7ok geni\u015f oldu\u011fu i\u00e7in daha ak\u0131ll\u0131 kurallar gerekli),<\/li>\n<li>Log analizi ve raporlamada IPv6 format\u0131n\u0131 desteklemek.<\/li>\n<\/ul>\n<p>Bu d\u00f6n\u00fc\u015f\u00fcm\u00fc par\u00e7a par\u00e7a yapmak m\u00fcmk\u00fcn. \u00d6rne\u011fin \u00f6nce sadece admin panelini IPv6 \u00fczerinden eri\u015filebilir hale getirip, ard\u0131ndan API ve son kullan\u0131c\u0131 trafi\u011fini yava\u015f yava\u015f IPv6\u2019ya ta\u015f\u0131yabilirsiniz.<\/p>\n<h3><span id=\"4_Hosting_ve_Veri_Merkezi_Stratejinizi_Gozden_Gecirin\">4) Hosting ve Veri Merkezi Stratejinizi G\u00f6zden Ge\u00e7irin<\/span><\/h3>\n<p>IP tahsis kurallar\u0131ndaki de\u011fi\u015fiklikler sadece adres seviyesinde de\u011fil, veri merkezi ve hosting stratejinizde de etkili olmal\u0131. Burada \u00fc\u00e7 temel senaryo \u00f6ne \u00e7\u0131k\u0131yor:<\/p>\n<ul>\n<li><strong>VPS ve bulut altyap\u0131s\u0131:<\/strong> Yeni a\u00e7aca\u011f\u0131n\u0131z VPS\u2019lerin IPv6 deste\u011fi olup olmad\u0131\u011f\u0131n\u0131 ve size ayr\u0131lan IPv4 say\u0131s\u0131n\u0131 dikkatle inceleyin.<\/li>\n<li><strong>Dedicated sunucu:<\/strong> Y\u00fcksek trafikli projelerde, tek bir g\u00fc\u00e7l\u00fc sunucuya atanm\u0131\u015f s\u0131n\u0131rl\u0131 IPv4 yerine; \u00e7oklu sunucu + IPv6 + load balancer mimarisi genelde daha esnek olur.<\/li>\n<li><strong>Colocation:<\/strong> Kendi router ve IP bloklar\u0131n\u0131zla veri merkezine indi\u011finizde, RIPE politikalar\u0131 ve y\u00f6nlendirme g\u00fcvenli\u011fi sizin sorumlulu\u011funuzda olur; bu da ayr\u0131 bir uzmanl\u0131k gerektirir.<\/li>\n<\/ul>\n<p>Bu konularda daha genel bir \u00e7er\u00e7eve \u00e7izmek isterseniz, <a href=\"https:\/\/www.dchost.com\/blog\/ripe-ncc-veri-merkezi-genislemeleri-ip-altyapiniz-icin-ne-anlama-geliyor\/\">RIPE NCC veri merkezi geni\u015flemelerinin IP altyap\u0131n\u0131za etkisini anlatt\u0131\u011f\u0131m\u0131z makale<\/a> ve <a href=\"https:\/\/www.dchost.com\/blog\/dedicated-sunucu-mu-vps-mi-hangisi-isinize-daha-uygun\/\">\u201cDedicated sunucu mu VPS mi?\u201d karar rehberimiz<\/a> birlikte okunmaya de\u011ferdir.<\/p>\n<h2><span id=\"LIRler_Kurumsal_Aglar_ve_Hosting_Musterileri_Icin_Uygulanabilir_Kontrol_Listesi\">LIR\u2019ler, Kurumsal A\u011flar ve Hosting M\u00fc\u015fterileri \u0130\u00e7in Uygulanabilir Kontrol Listesi<\/span><\/h2>\n<p>Teoriyi prati\u011fe d\u00f6kelim. RIPE NCC IP tahsislerindeki yeni kurallara uyum sa\u011flamak ve IPv4\/IPv6 dengesini do\u011fru kurmak i\u00e7in kullanabilece\u011finiz bir kontrol listesi haz\u0131rlad\u0131k.<\/p>\n<h3><span id=\"Adim_1_Politika_ve_Sozlesmelerinizi_Guncelleyin\">Ad\u0131m 1: Politika ve S\u00f6zle\u015fmelerinizi G\u00fcncelleyin<\/span><\/h3>\n<ul>\n<li>IP adreslerinin m\u00fc\u015fterilere tahsis \u015fartlar\u0131n\u0131 (s\u00fcre, ama\u00e7, alt kiralama yasa\u011f\u0131 vb.) s\u00f6zle\u015fmelerinize yaz\u0131n.<\/li>\n<li>IP kullan\u0131m politikas\u0131 (AUP) olu\u015fturun ve k\u00f6t\u00fcye kullan\u0131m \u015fikayetlerine yan\u0131t s\u00fcrecini tan\u0131mlay\u0131n.<\/li>\n<li>IP transferi yap\u0131yorsan\u0131z, RIPE politikalar\u0131na uyumlu i\u00e7 prosed\u00fcr haz\u0131rlay\u0131n.<\/li>\n<\/ul>\n<h3><span id=\"Adim_2_Ag_Tasariminizi_IP_Kitligina_Gore_Revize_Edin\">Ad\u0131m 2: A\u011f Tasar\u0131m\u0131n\u0131z\u0131 IP K\u0131tl\u0131\u011f\u0131na G\u00f6re Revize Edin<\/span><\/h3>\n<ul>\n<li>IP ba\u015f\u0131na servisi de\u011fil, servis ba\u015f\u0131na IP\u2019yi hedefleyin: Reverse proxy ve SNI ile \u00e7oklu domain yay\u0131mlay\u0131n.<\/li>\n<li>CGNAT veya outbound proxy ile ofis\/bayi a\u011flar\u0131n\u0131 daha az public IPv4 ile d\u0131\u015far\u0131 \u00e7\u0131kar\u0131n.<\/li>\n<li>\u0130\u00e7 a\u011fda m\u00fcmk\u00fcn oldu\u011funca IPv6 + \u00f6zel IPv4 (RFC1918) kombinasyonu kullan\u0131n.<\/li>\n<\/ul>\n<h3><span id=\"Adim_3_IPv6_Yayginlastirma_Plani_Hazirlayin\">Ad\u0131m 3: IPv6 Yayg\u0131nla\u015ft\u0131rma Plan\u0131 Haz\u0131rlay\u0131n<\/span><\/h3>\n<ul>\n<li>IPv6 adres plan\u0131n\u0131z\u0131 (prefix, site\/subnet da\u011f\u0131l\u0131m\u0131, VLAN e\u015flemesi) yaz\u0131l\u0131 hale getirin.<\/li>\n<li>Router, firewall, load balancer ve WAF konfig\u00fcrasyonlar\u0131n\u0131z\u0131 IPv6 uyumlu hale getirin.<\/li>\n<li>DNS\u2019te AAAA kay\u0131tlar\u0131n\u0131 ve PTR (reverse DNS) yap\u0131land\u0131rmas\u0131n\u0131 unutmay\u0131n.<\/li>\n<\/ul>\n<h3><span id=\"Adim_4_RIPE_Database_ve_RPKI_Temizligini_Yapin\">Ad\u0131m 4: RIPE Database ve RPKI Temizli\u011fini Yap\u0131n<\/span><\/h3>\n<ul>\n<li>Elinizdeki t\u00fcm IP bloklar\u0131 i\u00e7in RIPE Database kay\u0131tlar\u0131n\u0131 g\u00f6zden ge\u00e7irin, ileti\u015fim bilgilerini g\u00fcncelleyin.<\/li>\n<li>Her blok i\u00e7in route object olu\u015fturun veya mevcut olanlar\u0131 g\u00fcncelleyin.<\/li>\n<li>RPKI\u2019de ROA kay\u0131tlar\u0131n\u0131 tan\u0131mlay\u0131n; hangi AS\u2019lerin hangi prefix\u2019i anons edebilece\u011fini a\u00e7\u0131k\u00e7a belirleyin.<\/li>\n<\/ul>\n<h3><span id=\"Adim_5_Izleme_Loglama_ve_Guvenlik\">Ad\u0131m 5: \u0130zleme, Loglama ve G\u00fcvenlik<\/span><\/h3>\n<ul>\n<li>IPv4 ve IPv6 trafiklerini ayr\u0131 ayr\u0131 izleyin; b\u00fcy\u00fcme trendini g\u00f6r\u00fcn.<\/li>\n<li>Firewall log\u2019lar\u0131nda ve WAF kurallar\u0131nda IPv6\u2019y\u0131 g\u00f6r\u00fcn\u00fcr k\u0131l\u0131n.<\/li>\n<li>DDoS ve k\u00f6t\u00fcye kullan\u0131m (abuse) durumlar\u0131nda IP bazl\u0131 analiz yapabilecek ara\u00e7lar kullan\u0131n.<\/li>\n<\/ul>\n<h2><span id=\"DCHost_ile_Yeni_RIPE_NCC_Kurallarina_Uyum_Nasil_Yardimci_Oluyoruz\">DCHost ile Yeni RIPE NCC Kurallar\u0131na Uyum: Nas\u0131l Yard\u0131mc\u0131 Oluyoruz?<\/span><\/h2>\n<p>Biz DCHost ekibi olarak, RIPE NCC IP tahsislerindeki bu d\u00f6n\u00fc\u015f\u00fcm\u00fc \u201cd\u0131\u015fsal bir k\u0131s\u0131t\u201d de\u011fil, altyap\u0131y\u0131 modernle\u015ftirmek i\u00e7in bir f\u0131rsat olarak g\u00f6r\u00fcyoruz. Kendi LIR s\u00fcrecimiz, IP envanter y\u00f6netimimiz ve IPv6\u2019ya agresif ge\u00e7i\u015f planlar\u0131m\u0131z\u0131 tam da bu yeni kurallara g\u00f6re \u015fekillendirdik.<\/p>\n<p>Pratikte size nas\u0131l yard\u0131mc\u0131 olabiliriz?<\/p>\n<ul>\n<li><strong>IPv6 haz\u0131r VPS ve dedicated sunucular:<\/strong> Yeni projelerinizi ba\u015ftan \u00e7ift y\u0131\u011f\u0131n (dual-stack) olarak devreye alman\u0131za yard\u0131mc\u0131 oluyoruz.<\/li>\n<li><strong>Colocation ve kendi IP bloklar\u0131n\u0131z:<\/strong> Kendi ASN ve IP bloklar\u0131n\u0131zla DCHost veri merkezlerine inmek istiyorsan\u0131z, BGP, RPKI ve route-policy taraf\u0131nda tecr\u00fcbemizi payla\u015f\u0131yoruz.<\/li>\n<li><strong>Adres planlama dan\u0131\u015fmanl\u0131\u011f\u0131:<\/strong> IPv4 envanter temizli\u011fi, IPv6 adres \u015femas\u0131 ve NAT\/proxy mimarisi konular\u0131nda birlikte tasar\u0131m yapabiliyoruz.<\/li>\n<li><strong>G\u00fcvenlik ve uyum:<\/strong> Abuse y\u00f6netimi, DDoS senaryolar\u0131 ve loglama stratejilerinizin RIPE beklentileriyle uyumlu hale gelmesini sa\u011fl\u0131yoruz.<\/li>\n<\/ul>\n<p>\u00d6zetle; RIPE NCC IP tahsislerindeki yeni kurallar, IPv4\u2019\u00fcn art\u0131k \u201cucuz ve bol\u201d bir kaynak olmad\u0131\u011f\u0131n\u0131 a\u00e7\u0131k\u00e7a g\u00f6steriyor. IPv6 ise hem teknik hem de ekonomik a\u00e7\u0131dan b\u00fcy\u00fcmenin tek ger\u00e7ek\u00e7i adresi. E\u011fer siz de a\u011f\u0131n\u0131z\u0131, uygulamalar\u0131n\u0131z\u0131 ve b\u00fct\u00e7enizi bu yeni ger\u00e7ekli\u011fe g\u00f6re yeniden \u015fekillendirmek istiyorsan\u0131z, DCHost olarak IP planlamas\u0131ndan sunucu mimarisine kadar t\u00fcm katmanlarda yan\u0131n\u0131zda olmaktan memnuniyet duyar\u0131z.<\/p>\n<p>Bir sonraki ad\u0131m i\u00e7in; ister k\u00fc\u00e7\u00fck bir web projesi ister b\u00fcy\u00fck bir SaaS platformu planl\u0131yor olun, altyap\u0131 ve IP stratejinizi birlikte g\u00f6zden ge\u00e7irmek \u00fczere bizimle ileti\u015fime ge\u00e7ebilirsiniz. B\u00f6ylece RIPE NCC\u2019nin yeni IP tahsis kurallar\u0131n\u0131 sadece \u201czorunlu bir k\u0131s\u0131t\u201d de\u011fil, daha dayan\u0131kl\u0131, \u00f6l\u00e7eklenebilir ve s\u00fcrd\u00fcr\u00fclebilir bir altyap\u0131ya ge\u00e7i\u015f i\u00e7in kald\u0131ra\u00e7 olarak kullanm\u0131\u015f olursunuz.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>\u0130&ccedil;indekiler1 RIPE NCC IP Tahsislerinde Yeni D\u00f6nem: Neden Bu Kadar \u00d6nemli?2 RIPE NCC ve IP Tahsis S\u00fcrecinin Yeni Ger\u00e7e\u011fi3 Yeni RIPE NCC IP Tahsis Kurallar\u0131n\u0131n Ana Hatlar\u01313.1 1) Yeni IPv4 Tahsisleri: \u201cSon \/24\u201d Mant\u0131\u011f\u01313.2 2) Bekleme Listesi ve K\u0131tl\u0131k Y\u00f6netimi3.3 3) Transfer Kurallar\u0131n\u0131n S\u0131k\u0131la\u015fmas\u0131 ve Spek\u00fclasyon Engeli3.4 4) IPv6 Tahsisleri ve \u201cArt\u0131k Ka\u00e7\u0131\u015f Yok\u201d Noktas\u01313.5 [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":3377,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[32,24,33,30],"tags":[],"class_list":["post-3376","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-alan-adi","category-hosting","category-nasil-yapilir","category-nedir"],"_links":{"self":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/3376","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=3376"}],"version-history":[{"count":0,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/3376\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/3377"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=3376"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=3376"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=3376"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}