{"id":1420,"date":"2025-11-06T16:39:36","date_gmt":"2025-11-06T13:39:36","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/ozel-ad-sunucusu-ve-glue-record-nasil-kurulur-kendi-dnsine-adim-adim-yolculuk\/"},"modified":"2025-11-06T16:39:36","modified_gmt":"2025-11-06T13:39:36","slug":"ozel-ad-sunucusu-ve-glue-record-nasil-kurulur-kendi-dnsine-adim-adim-yolculuk","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/ozel-ad-sunucusu-ve-glue-record-nasil-kurulur-kendi-dnsine-adim-adim-yolculuk\/","title":{"rendered":"\u00d6zel Ad Sunucusu ve Glue Record Nas\u0131l Kurulur? Kendi DNS\u2019ine Ad\u0131m Ad\u0131m Yolculuk"},"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=\"#Kisa_Bir_Hikayeyle_Baslayalim_O_Alan_Adi_Neden_Acilmadi\"><span class=\"toc_number toc_depth_1\">1<\/span> K\u0131sa Bir Hik\u00e2yeyle Ba\u015flayal\u0131m: O Alan Ad\u0131 Neden A\u00e7\u0131lmad\u0131?<\/a><\/li><li><a href=\"#Ozel_Ad_Sunucusu_Nedir_Ne_Zaman_Ise_Yarar\"><span class=\"toc_number toc_depth_1\">2<\/span> \u00d6zel Ad Sunucusu Nedir, Ne Zaman \u0130\u015fe Yarar?<\/a><\/li><li><a href=\"#Glue_Record_Nedir_Neden_Bazen_En_Basa_Donuyoruz\"><span class=\"toc_number toc_depth_1\">3<\/span> Glue Record Nedir? Neden Bazen En Ba\u015fa D\u00f6n\u00fcyoruz?<\/a><\/li><li><a href=\"#Hazirliklar_IPler_DNS_Yazilimi_Guvenlik_ve_Kucuk_Ama_Kritik_Detaylar\"><span class=\"toc_number toc_depth_1\">4<\/span> Haz\u0131rl\u0131klar: IP\u2019ler, DNS Yaz\u0131l\u0131m\u0131, G\u00fcvenlik ve K\u00fc\u00e7\u00fck Ama Kritik Detaylar<\/a><\/li><li><a href=\"#Adim_Adim_Registrar_Uzerinde_Glue_Record_Olusturma\"><span class=\"toc_number toc_depth_1\">5<\/span> Ad\u0131m Ad\u0131m: Registrar \u00dczerinde Glue Record Olu\u015fturma<\/a><\/li><li><a href=\"#Sunucuda_NS_ve_Zonelari_Hazirlama_cPanel_Plesk_ve_BINDPowerDNS\"><span class=\"toc_number toc_depth_1\">6<\/span> Sunucuda NS ve Zone\u2019lar\u0131 Haz\u0131rlama: cPanel, Plesk ve BIND\/PowerDNS<\/a><ul><li><a href=\"#cPanelWHM_ile_hizli_kurulum\"><span class=\"toc_number toc_depth_2\">6.1<\/span> cPanel\/WHM ile h\u0131zl\u0131 kurulum<\/a><\/li><li><a href=\"#Plesk_ile_akici_yapilandirma\"><span class=\"toc_number toc_depth_2\">6.2<\/span> Plesk ile ak\u0131c\u0131 yap\u0131land\u0131rma<\/a><\/li><li><a href=\"#BINDPowerDNS_ile_yalin_kurulum\"><span class=\"toc_number toc_depth_2\">6.3<\/span> BIND\/PowerDNS ile yal\u0131n kurulum<\/a><\/li><\/ul><\/li><li><a href=\"#Domaini_Ozel_NSlere_Tasima_Test_ve_Yayilim\"><span class=\"toc_number toc_depth_1\">7<\/span> Domain\u2019i \u00d6zel NS\u2019lere Ta\u015f\u0131ma, Test ve Yay\u0131l\u0131m<\/a><\/li><li><a href=\"#Yaygin_Hatalar_ve_Hizli_Kurtarma_Senaryolari\"><span class=\"toc_number toc_depth_1\">8<\/span> Yayg\u0131n Hatalar ve H\u0131zl\u0131 Kurtarma Senaryolar\u0131<\/a><\/li><li><a href=\"#Ileri_Seviye_Dokunuslar_IPv6_Anycast_DNSSEC_ve_Otomasyon\"><span class=\"toc_number toc_depth_1\">9<\/span> \u0130leri Seviye Dokunu\u015flar: IPv6, Anycast, DNSSEC ve Otomasyon<\/a><\/li><li><a href=\"#Sahada_Kucuk_Ama_Hayat_Kurtaran_Ipuclari\"><span class=\"toc_number toc_depth_1\">10<\/span> Sahada K\u00fc\u00e7\u00fck Ama Hayat Kurtaran \u0130pu\u00e7lar\u0131<\/a><\/li><li><a href=\"#Kapanis_Kendi_DNSinin_Direksiyonunda\"><span class=\"toc_number toc_depth_1\">11<\/span> Kapan\u0131\u015f: Kendi DNS\u2019inin Direksiyonunda<\/a><\/li><\/ul><\/div>\n<h2 id='section-1'><span id=\"Kisa_Bir_Hikayeyle_Baslayalim_O_Alan_Adi_Neden_Acilmadi\">K\u0131sa Bir Hik\u00e2yeyle Ba\u015flayal\u0131m: O Alan Ad\u0131 Neden A\u00e7\u0131lmad\u0131?<\/span><\/h2>\n<p>Hi\u00e7 ba\u015f\u0131n\u0131za geldi mi? Bir sabah kahvenizi koyup sitenizi a\u00e7maya niyetleniyorsunuz, ama sayfa d\u00f6n\u00fcp duruyor. Bir m\u00fc\u015fterimle ya\u015fad\u0131\u011f\u0131m\u0131z ilk \u00f6zel ad sunucusu maceras\u0131nda b\u00f6yle olmu\u015ftu. Her \u015fey haz\u0131r san\u0131yorduk: sunucu kurulu, web dosyalar\u0131 yerinde, sertifika tamam. Ama alan ad\u0131 bir t\u00fcrl\u00fc bizim sunucunun IP&#8217;sine oturmuyor. Derken konu d\u00f6n\u00fcp dola\u015f\u0131p o me\u015fhur iki kelimeye geldi: <strong>\u00f6zel ad sunucusu<\/strong> ve <strong>glue record<\/strong>. \u0130tiraf edeyim, ilk kez yakla\u015fan biri i\u00e7in isimleri bile hafif \u00fcrk\u00fct\u00fcc\u00fc duruyor.<\/p>\n<p>\u0130\u015fte bu yaz\u0131da, kafadaki bu sis perdesini aralayaca\u011f\u0131z. \u00d6zel ad sunucusu nedir, neden i\u015fimize yarar, glue record ne i\u015fe yarar ve en \u00f6nemlisi ikisini <strong>ad\u0131m ad\u0131m<\/strong> nas\u0131l kurar\u0131z, birlikte ilerleyece\u011fiz. Kendi deneyimlerimden ak\u0131lda kalan p\u00fcfleri de serpi\u015ftirece\u011fim; mesela TTL\u2019yi ne zaman d\u00fc\u015f\u00fcrmek iyi fikirdir, firewall neden \u015faka kald\u0131rmaz, ya da tek bir rakam hatas\u0131 nas\u0131l g\u00fcn\u00fcn\u00fcz\u00fc karart\u0131r. Rahat olun, konu teknik gibi g\u00f6r\u00fcnse de, birka\u00e7 do\u011fru dokunu\u015fla gayet keyifli bir yolculu\u011fa d\u00f6n\u00fc\u015f\u00fcyor.<\/p>\n<p>Yaz\u0131n\u0131n sonunda, siz de alan ad\u0131n\u0131z\u0131 kendi ns1 ve ns2 adreslerinizle y\u00f6netebilecek, glue record\u2019lar\u0131 do\u011fru yere yerle\u015ftirip olas\u0131 hatalar\u0131 h\u0131zl\u0131ca te\u015fhis edebileceksiniz. Hadi ba\u015flayal\u0131m; \u00f6nce \u015fu \u00f6zel ad sunucusu i\u015fi nedir, onu netle\u015ftirelim.<\/p>\n<h2 id='section-2'><span id=\"Ozel_Ad_Sunucusu_Nedir_Ne_Zaman_Ise_Yarar\">\u00d6zel Ad Sunucusu Nedir, Ne Zaman \u0130\u015fe Yarar?<\/span><\/h2>\n<p>\u00d6zel ad sunucusu dedi\u011fimiz \u015fey, alan ad\u0131n\u0131z\u0131n kendi ad\u0131n\u0131 ta\u015f\u0131yan ad sunucular\u0131d\u0131r. Yani ns1.sizinalanadiniz.com ve ns2.sizinalanadiniz.com gibi. D\u0131\u015far\u0131dan bir DNS sa\u011flay\u0131c\u0131s\u0131n\u0131n ns\u2019lerini kullanmak yerine, kendi markan\u0131zla g\u00f6r\u00fcn\u00fcr olursunuz. Bir nevi d\u00fckkan\u0131n tabelas\u0131n\u0131 kendi ad\u0131n\u0131zla asmak gibi d\u00fc\u015f\u00fcnebilirsiniz. Mesela bir ajanssan\u0131z, m\u00fc\u015fterilerinize kendi ns\u2019lerinizle hizmet verirsiniz; kurumsal tarafta ise i\u00e7 sistemlerle d\u0131\u015f d\u00fcnyay\u0131 ayn\u0131 elde toplamak daha d\u00fczenli ilerler.<\/p>\n<p>Peki ne zaman mant\u0131kl\u0131? Birincisi, tam kontrol istedi\u011finizde. Kay\u0131tlar, TTL\u2019ler, zone \u015fablonlar\u0131; hepsi sizin elinizde. \u0130kincisi, m\u00fc\u015fteri deneyimi. Tek bir \u00e7at\u0131 ve tek bir isim alt\u0131nda y\u00f6netmek g\u00fcven verir. \u00dc\u00e7\u00fcnc\u00fcs\u00fc, otomasyon. CI\/CD s\u00fcre\u00e7lerine DNS\u2019i katmak gerekti\u011finde, d\u0131\u015f servise ba\u011f\u0131ml\u0131 kalmadan ilerlemek ho\u015f olur. Dezavantaj olarak, sorumluluk sizdedir. Yani eri\u015filebilirlik, g\u00fcvenlik, g\u00fcncellemeler ve yedek planlar\u0131. Ama iyi bir planla bu y\u00fck hafifler ve sistem y\u0131llarca sorunsuz \u00e7al\u0131\u015f\u0131r.<\/p>\n<p>Burada bir parantez a\u00e7ay\u0131m: DNS taraf\u0131ndaki de\u011fi\u015fikliklerin d\u00fcnyaya yay\u0131lmas\u0131 anl\u0131k olmaz. Yay\u0131l\u0131m ve kesintisiz ge\u00e7i\u015fler i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/zero-downtime-tasima-icin-ttl-stratejileri-dns-yayilimini-gercekten-nasil-hizlandirirsin\/\">DNS yay\u0131l\u0131m\u0131n\u0131 h\u0131zland\u0131ran TTL stratejileri \u00fczerine yaz\u0131m\u0131z<\/a> ho\u015f bir rehber olur. D\u00f6n\u00fc\u015f\u00fcmlerde paniklemek yerine \u00f6nceden haz\u0131rl\u0131k yapmak, g\u00fcn\u00fcn sonunda en b\u00fcy\u00fck kazan\u00e7.<\/p>\n<h2 id='section-3'><span id=\"Glue_Record_Nedir_Neden_Bazen_En_Basa_Donuyoruz\">Glue Record Nedir? Neden Bazen En Ba\u015fa D\u00f6n\u00fcyoruz?<\/span><\/h2>\n<p>Glue record, \u00f6zel ad sunucular\u0131n\u0131n kalp at\u0131\u015f\u0131 gibi. K\u0131sa bir \u00f6zetle, registrar taraf\u0131nda ns1 ve ns2 gibi ad sunucular\u0131n\u0131za ait <strong>IP adreslerini<\/strong> tescil etti\u011finiz k\u00fc\u00e7\u00fck ama kritik bir kay\u0131tt\u0131r. Neden kritik? \u00c7\u00fcnk\u00fc alan ad\u0131n\u0131z\u0131n ad sunucular\u0131 yine alan ad\u0131n\u0131z\u0131n alt\u0131ndad\u0131r. Yani ns\u2019lerin IP\u2019sini bilmiyorsak, ns\u2019lere gidip alan ad\u0131n\u0131n IP\u2019sini nas\u0131l soraca\u011f\u0131z? Burada sonsuz bir d\u00f6ng\u00fcye gireriz. \u0130\u015fte glue record bu d\u00fc\u011f\u00fcm\u00fc keser; \u201cns1.sizinalanadiniz.com \u015fu IP\u2019de\u201d diye tesciller ve \u00e7\u00f6z\u00fcm zinciri akmaya ba\u015flar.<\/p>\n<p>Glue record kavram\u0131n\u0131 sade bir dille anlatan bir referans isterseniz, <a href=\"https:\/\/www.cloudflare.com\/learning\/dns\/glue-record\/\" rel=\"nofollow noopener\" target=\"_blank\">glue record kavram\u0131n\u0131 sade bir dille anlatan bu kaynak<\/a> gayet anla\u015f\u0131l\u0131r. Bir de registrar bak\u0131\u015f a\u00e7\u0131s\u0131ndan g\u00f6rmek isterseniz, <a href=\"https:\/\/support.dnsimple.com\/articles\/glue-record\/\" rel=\"nofollow noopener\" target=\"_blank\">glue record\u2019lar\u0131n registrar taraf\u0131ndaki mant\u0131\u011f\u0131<\/a> i\u015fin mutfa\u011f\u0131na pencere a\u00e7ar. Ama siz bu yaz\u0131y\u0131 bitirdi\u011finizde, b\u00fcy\u00fck ihtimalle tekrar d\u00f6n\u00fcp bakman\u0131z gerekmeyecek.<\/p>\n<h2 id='section-4'><span id=\"Hazirliklar_IPler_DNS_Yazilimi_Guvenlik_ve_Kucuk_Ama_Kritik_Detaylar\">Haz\u0131rl\u0131klar: IP\u2019ler, DNS Yaz\u0131l\u0131m\u0131, G\u00fcvenlik ve K\u00fc\u00e7\u00fck Ama Kritik Detaylar<\/span><\/h2>\n<p>Kurulumdan \u00f6nce birka\u00e7 ta\u015f yerine oturmal\u0131. \u0130lk olarak, en az iki ayr\u0131 IP adresine ihtiyac\u0131n\u0131z var. Ayn\u0131 sunucuda iki farkl\u0131 IP de olur; farkl\u0131 sunucular da olur. \u0130kincisi, DNS hizmeti sunan yaz\u0131l\u0131m\u0131n\u0131z netle\u015fmeli: cPanel\/WHM kullan\u0131yorsan\u0131z aray\u00fczden dakikalar i\u00e7inde halledersiniz; Plesk de benzer \u015fekilde kolayd\u0131r. BIND, PowerDNS gibi \u00e7\u00f6z\u00fcmlerde ise birka\u00e7 dosyay\u0131 do\u011fru yerle\u015ftirmeniz yeterli.<\/p>\n<p>G\u00fcvenlik taraf\u0131nda, port 53\u2019\u00fcn UDP ve TCP i\u00e7in a\u00e7\u0131k olmas\u0131 gerekir. Firewall ve g\u00fcvenlik duvar\u0131 servisleriniz, DNS trafi\u011fini bloklamamal\u0131. Bu, g\u00f6zden ka\u00e7t\u0131\u011f\u0131nda \u201cHer \u015fey do\u011fru ama \u00e7al\u0131\u015fm\u0131yor\u201d hissine sebep olur. Bir de g\u00fcn\u00fcn birinde IPv6\u2019ya dokunman\u0131z neredeyse kesinle\u015fecek; \u015fimdiden <a href=\"https:\/\/www.dchost.com\/blog\/ipv6-benimseme-oranlari-artiyor-peki-bu-dalga-ne-zaman-sizin-aga-carpar\/\">IPv6 dalgas\u0131<\/a> sizi ne zaman yakalar diye bir g\u00f6z atmak k\u00f6t\u00fc fikir de\u011fildir. Glue kay\u0131tlar\u0131n\u0131n AAAA kay\u0131tlar\u0131yla uyumu, gelece\u011fi bug\u00fcn d\u00fczenler.<\/p>\n<p>Son olarak, planlama. Bir alan ad\u0131n\u0131 aktif trafikte kullan\u0131yorsan\u0131z, ta\u015f\u0131ma g\u00fcn\u00fc \u00f6ncesinde TTL\u2019leri d\u00fc\u015f\u00fcrmek, test alan\u0131 a\u00e7mak ve geri d\u00f6n\u00fc\u015f plan\u0131 yapmak huzur verir. DNS de\u011fi\u015fiklikleri bir ko\u015fu band\u0131ndan \u00e7ok, ritmi olan bir dans gibidir; ad\u0131mlar\u0131 do\u011fru atarsan\u0131z, performans bir anda akmaya ba\u015flar.<\/p>\n<h2 id='section-5'><span id=\"Adim_Adim_Registrar_Uzerinde_Glue_Record_Olusturma\">Ad\u0131m Ad\u0131m: Registrar \u00dczerinde Glue Record Olu\u015fturma<\/span><\/h2>\n<p>\u0130\u015fe en tepedeki kilitten, yani alan ad\u0131n\u0131z\u0131n kay\u0131t \u015firketinden ba\u015fl\u0131yoruz. Panelden \u2018host\u2019 ya da \u2018child nameserver\u2019 gibi bir men\u00fc g\u00f6receksiniz. Baz\u0131 panellerde \u2018private nameserver\u2019 olarak ge\u00e7er. Burada ns1 ve ns2 i\u00e7in IP adreslerinizi tek tek tan\u0131mlars\u0131n\u0131z. \u00d6nce ns1.sizinalanadiniz.com i\u00e7in IP\u2019yi yaz\u0131n, kaydedin. Sonra ns2\u2019yi ekleyin. E\u011fer IPv6 kullanacaksan\u0131z, ayn\u0131 ekranlarda AAAA adreslerini de girme \u015fans\u0131n\u0131z olur; yoksa sonra DNS b\u00f6lgenize ekleyebilirsiniz.<\/p>\n<p>Bu ad\u0131mda yap\u0131lan en yayg\u0131n hata, IP\u2019lerin kar\u0131\u015fmas\u0131 ya da rakam atlamalar\u0131d\u0131r. Bir kez daha kontrol edin. Bir noktada \u201cKay\u0131t ba\u015far\u0131yla al\u0131nd\u0131\u201d gibi bir mesaj g\u00f6r\u00fcrs\u00fcn\u00fcz. Ard\u0131ndan k\u0131sa bir bekleme olur; baz\u0131 registrarlarda anl\u0131k, baz\u0131lar\u0131nda birka\u00e7 dakika. G\u00f6revimiz burada bitmedi. S\u0131rada sunucu taraf\u0131 var ve o da en az buras\u0131 kadar keyifli.<\/p>\n<p>Yeri gelmi\u015fken, wildcard sertifikalarla u\u011fra\u015f\u0131yorsan\u0131z DNS taraf\u0131 hayat\u0131n\u0131z\u0131 kolayla\u015ft\u0131r\u0131r. Bunun i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/lets-encrypt-wildcard-ssl-otomasyonu-dns-01-ile-cpanel-plesk-ve-nginxte-zahmetsiz-kurulum-ve-yenileme-nasil-yapilir\/\">DNS-01 ile wildcard SSL otomasyonu<\/a> yaz\u0131s\u0131nda anlatt\u0131\u011f\u0131m\u0131z pratikler, \u00f6zel ad sunucusu kurduktan sonra resmen do\u011fru zemine oturur.<\/p>\n<h2 id='section-6'><span id=\"Sunucuda_NS_ve_Zonelari_Hazirlama_cPanel_Plesk_ve_BINDPowerDNS\">Sunucuda NS ve Zone\u2019lar\u0131 Haz\u0131rlama: cPanel, Plesk ve BIND\/PowerDNS<\/span><\/h2>\n<h3><span id=\"cPanelWHM_ile_hizli_kurulum\">cPanel\/WHM ile h\u0131zl\u0131 kurulum<\/span><\/h3>\n<p>WHM\u2019ye giri\u015f yapt\u0131ktan sonra, \u2018Basic WebHost Manager Setup\u2019 k\u0131sm\u0131nda ad sunucusu isimlerinizi belirlersiniz. ns1 ve ns2 yaz\u0131p, yanlar\u0131na IP\u2019leri atay\u0131n. WHM genelde gerekli A kay\u0131tlar\u0131n\u0131 alan ad\u0131n\u0131z\u0131n DNS b\u00f6lgesine otomatik ekler. Ard\u0131ndan \u2018DNS Functions\u2019 b\u00f6l\u00fcm\u00fcnde domain\u2019inize ait zone dosyas\u0131nda NS kay\u0131tlar\u0131n\u0131n ns1 ve ns2\u2019yi g\u00f6sterdi\u011fini ve A kay\u0131tlar\u0131n\u0131n yerli yerinde durdu\u011funu kontrol edin. Kapan\u0131\u015f\u0131 \u2018Resolver Configuration\u2019 ile yap\u0131p, sunucunun d\u0131\u015f d\u00fcnyay\u0131 sa\u011fl\u0131kl\u0131 \u00e7\u00f6zd\u00fc\u011f\u00fcnden emin olabilirsiniz.<\/p>\n<h3><span id=\"Plesk_ile_akici_yapilandirma\">Plesk ile ak\u0131c\u0131 yap\u0131land\u0131rma<\/span><\/h3>\n<p>Plesk\u2019te \u2018Tools &amp; Settings\u2019 i\u00e7indeki DNS Template ve domain bazl\u0131 DNS ayarlar\u0131 i\u015fimizi g\u00f6r\u00fcr. Domain\u2019in zone\u2019u i\u00e7inde ns1.sizinalanadiniz.com ve ns2.sizinalanadiniz.com i\u00e7in A kay\u0131tlar\u0131n\u0131 yaz\u0131n; NS kay\u0131tlar\u0131n\u0131n domain\u2019i bu iki ad sunucusuna delegelerine izin verdi\u011fini do\u011frulay\u0131n. Plesk\u2019in aray\u00fcz\u00fc bu ad\u0131mlar\u0131 \u00e7ok g\u00f6r\u00fcn\u00fcr k\u0131ld\u0131\u011f\u0131ndan, genellikle birka\u00e7 dakikada her \u015fey yerine oturur. K\u00fc\u00e7\u00fck bir ipucu: Plesk\u2019te \u015fablonlar\u0131 d\u00fczenleyip yeni domain\u2019ler i\u00e7in ayn\u0131 \u00f6zel ns\u2019leri otomatik tan\u0131tabilirsiniz.<\/p>\n<h3><span id=\"BINDPowerDNS_ile_yalin_kurulum\">BIND\/PowerDNS ile yal\u0131n kurulum<\/span><\/h3>\n<p>BIND ya da PowerDNS kullan\u0131yorsan\u0131z, i\u015fin kalbi zone dosyas\u0131nda atar. Domain\u2019inizin zone\u2019unda iki \u015feyi netle\u015ftireceksiniz: NS kay\u0131tlar\u0131 domain\u2019inizi ns1 ve ns2\u2019ye delegeler; A kay\u0131tlar\u0131 da ns1 ve ns2\u2019nin IP\u2019lerini tutar. Mesela \u2018ns1 IN A 203.0.113.10\u2019 ve \u2018ns2 IN A 203.0.113.11\u2019 gibi. Ard\u0131ndan servisleri yeniden y\u00fckleyip g\u00fcnl\u00fckleri bir g\u00f6zden ge\u00e7irin. K\u00fc\u00e7\u00fck bir virg\u00fcl, beklenmedik bir nokta veya TTL sat\u0131r\u0131ndaki yaz\u0131m hatas\u0131, saniyeler i\u00e7inde g\u00f6ze batmasa da g\u00fcn\u00fcn sonunda \u00e7\u00f6z\u00fcm\u00fc etkiler. Dikkatli bir son okuma her zaman kazand\u0131r\u0131r.<\/p>\n<h2 id='section-7'><span id=\"Domaini_Ozel_NSlere_Tasima_Test_ve_Yayilim\">Domain\u2019i \u00d6zel NS\u2019lere Ta\u015f\u0131ma, Test ve Yay\u0131l\u0131m<\/span><\/h2>\n<p>Registrar\u2019da glue kay\u0131tlar\u0131n\u0131 tan\u0131mlad\u0131k, sunucuda zone\u2019u haz\u0131rlad\u0131k. \u015eimdi domain\u2019in ad sunucular\u0131n\u0131 yeni \u00f6zel ns\u2019lere ta\u015f\u0131ma zaman\u0131. Registrar panelinde domain\u2019in DNS sunucular\u0131n\u0131 ns1.sizinalanadiniz.com ve ns2.sizinalanadiniz.com olarak de\u011fi\u015ftirin. Bu de\u011fi\u015fiklik d\u00fcnyan\u0131n d\u00f6rt bir yan\u0131ndaki cache\u2019lere yay\u0131l\u0131rken, bekleme anlar\u0131 olur. Burada sab\u0131r kadar, \u00f6ncesinde yap\u0131lan TTL haz\u0131rl\u0131\u011f\u0131 \u00f6nemlidir. Ta\u015f\u0131ma \u00f6ncesi TTL\u2019leri d\u00fc\u015f\u00fcrmek, dikkatli bir planla ge\u00e7i\u015fi neredeyse g\u00f6r\u00fcnmez hale getirir. Bu konuda tekrar not d\u00fc\u015feyim: <a href=\"https:\/\/www.dchost.com\/blog\/zero-downtime-tasima-icin-ttl-stratejileri-dns-yayilimini-gercekten-nasil-hizlandirirsin\/\">planl\u0131 TTL de\u011fi\u015fimiyle kesintisiz ge\u00e7i\u015f<\/a> yaz\u0131s\u0131 e\u015flik etsin.<\/p>\n<p>Test i\u00e7in yerel bilgisayar\u0131n\u0131zdan veya bir uzak sunucudan \u00e7\u00f6z\u00fcmleme deneyebilirsiniz. \u2018dig alanadiniz.com @8.8.8.8\u2019 gibi basit bir sorgu size A kayd\u0131n\u0131, \u2018dig NS alanadiniz.com\u2019 ise kimin yetkili oldu\u011funu g\u00f6sterir. \u2018dig ns1.sizinalanadiniz.com\u2019 ile ns1\u2019in IP\u2019si do\u011fru d\u00f6n\u00fcyor mu bakars\u0131n\u0131z; \u2018+trace\u2019 parametresiyle k\u00f6kten itibaren ad\u0131m ad\u0131m \u00e7\u00f6z\u00fcmlenmesini izlemek de ufuk a\u00e7ar. Komut detaylar\u0131 i\u00e7in <a href=\"https:\/\/bind9.readthedocs.io\/en\/latest\/manpages\/dig.html\" rel=\"nofollow noopener\" target=\"_blank\">dig komutunun kullan\u0131m\u0131na g\u00f6z atmak<\/a> faydal\u0131 olacakt\u0131r.<\/p>\n<p>Bu a\u015famada bir \u015feyler yolunda de\u011filse, genellikle \u00fc\u00e7 ihtimal var: glue\u2019da yanl\u0131\u015f IP, zone\u2019da eksik\/yanl\u0131\u015f A kayd\u0131 ya da firewall\u2019\u0131n 53 numaral\u0131 kap\u0131y\u0131 kapatmas\u0131. Bir de nadir g\u00f6r\u00fclen ama sinir bozan ters yaz\u0131m hatalar\u0131. Benim al\u0131\u015fkanl\u0131\u011f\u0131m, \u00f6nce ns1 ve ns2 i\u00e7in A kay\u0131tlar\u0131n\u0131 do\u011frudan sorgulamak, ard\u0131ndan domain NS kay\u0131tlar\u0131n\u0131 kontrol etmek. Zincir do\u011fruysa, sonu\u00e7 er ya da ge\u00e7 yerine oturuyor.<\/p>\n<h2 id='section-8'><span id=\"Yaygin_Hatalar_ve_Hizli_Kurtarma_Senaryolari\">Yayg\u0131n Hatalar ve H\u0131zl\u0131 Kurtarma Senaryolar\u0131<\/span><\/h2>\n<p>\u00d6zel ad sunucusu kurarken en \u00e7ok denk geldi\u011fim hata, sadece bir ad sunucusuyla yetinmek. \u0130ki ayr\u0131 IP kullanmak dayan\u0131kl\u0131l\u0131\u011f\u0131 art\u0131r\u0131r; tek bir p\u00fcr\u00fcz\u00fcn b\u00fct\u00fcn alan ad\u0131n\u0131 sarsmas\u0131n\u0131 engeller. \u0130kinci s\u0131rada, glue\u2019\u0131n unutulmas\u0131 geliyor. Registrar taraf\u0131nda tan\u0131t\u0131lmam\u0131\u015f ns\u2019ler, domain\u2019in kendi kendine adres sormaya \u00e7al\u0131\u015ft\u0131\u011f\u0131 o me\u015fhur d\u00f6ng\u00fcye girer. \u00dc\u00e7\u00fcnc\u00fcs\u00fc ise firewall. G\u00fcvenlik duvarlar\u0131 bazen erkek karde\u015f gibidir; sizi \u00e7ok sever ama bazen kap\u0131y\u0131 i\u00e7eriden kilitler. UDP 53 ve TCP 53\u2019e eri\u015fimi netle\u015ftirin.<\/p>\n<p>Hatalar\u0131 te\u015fhis ederken bir y\u00f6ntem \u00f6nerim var: par\u00e7ala ve yeniden kur. \u00d6nce ns1 ve ns2\u2019nin A kay\u0131tlar\u0131n\u0131 do\u011frudan sorgula; sonra domain\u2019in NS kay\u0131tlar\u0131n\u0131; ard\u0131ndan domain\u2019in A ve MX kay\u0131tlar\u0131n\u0131. Her halka do\u011fruysa, zincir \u00e7al\u0131\u015f\u0131r. Bir yerde kopukluk varsa, genelde bir sat\u0131rda sakl\u0131d\u0131r. TTL\u2019leri ge\u00e7ici olarak k\u0131saltmak ve sonra normale almak, h\u0131zl\u0131 denemeler yapman\u0131z\u0131 kolayla\u015ft\u0131r\u0131r.<\/p>\n<p>Bu arada, alan ad\u0131 d\u00fcnyas\u0131nda marka ve SEO taraf\u0131n\u0131 da d\u00fc\u015f\u00fcn\u00fcyorsan\u0131z, ad\u0131mlar\u0131n\u0131z\u0131 daha geni\u015f bir resmin i\u00e7ine koymak iyi gelir. Do\u011fru uzant\u0131 se\u00e7imi bazen teknik operasyondan daha uzun vadeli etki b\u0131rak\u0131r. Bu bak\u0131\u015f i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/seo-ve-marka-icin-alan-adi-ve-tld-secimi-com-io-ai-arasinda-dogru-isim-nasil-bulunur\/\">alan ad\u0131 ve TLD se\u00e7imi \u00fczerine notlar<\/a> faydal\u0131 bir okuma olur.<\/p>\n<h2 id='section-9'><span id=\"Ileri_Seviye_Dokunuslar_IPv6_Anycast_DNSSEC_ve_Otomasyon\">\u0130leri Seviye Dokunu\u015flar: IPv6, Anycast, DNSSEC ve Otomasyon<\/span><\/h2>\n<p>Temelleri sa\u011flam att\u0131ktan sonra, birka\u00e7 ileri seviye ba\u015fl\u0131k yolunuzu a\u00e7ar. IPv6 ile glue kay\u0131tlar\u0131n\u0131 AAAA d\u00fczeyinde tamamlamak, sizi bir sonraki dalgaya haz\u0131rlar. Anycast da\u011f\u0131t\u0131m\u0131, ns\u2019lerinizi co\u011frafyaya yayarak tek bir lokasyona ba\u011f\u0131ml\u0131l\u0131\u011f\u0131 azalt\u0131r; sunucular b\u00fcy\u00fcd\u00fck\u00e7e bu tatl\u0131 bir rahatl\u0131k getirir. DNSSEC ise imzal\u0131 kay\u0131tlarla g\u00fcven zincirine anlaml\u0131 bir halka ekler; kurarken dikkat ister ama kar\u015f\u0131l\u0131\u011f\u0131 b\u00fcy\u00fckt\u00fcr.<\/p>\n<p>Otomasyon taraf\u0131nda, yeni domain ekledi\u011finizde ns A kay\u0131tlar\u0131n\u0131n ve NS delegasyonlar\u0131n\u0131n \u015fablondan gelmesi size zaman kazand\u0131r\u0131r. CI\/CD boru hatt\u0131na \u201cdns deploy\u201d ad\u0131m\u0131 eklemek, staging\u2019den prod\u2019a ge\u00e7i\u015fte hatas\u0131z bir ritim sa\u011flar. Bir de TLS\/SSL konusuna de\u011finmi\u015ftik; wildcard sertifikalar ve DNS-01 do\u011frulamas\u0131, \u00f6zel ad sunucunuzun sa\u011flad\u0131\u011f\u0131 esneklikle \u00e7ok rahat ak\u0131yor. Bu noktada yine <a href=\"https:\/\/www.dchost.com\/blog\/lets-encrypt-wildcard-ssl-otomasyonu-dns-01-ile-cpanel-plesk-ve-nginxte-zahmetsiz-kurulum-ve-yenileme-nasil-yapilir\/\">DNS-01 ile wildcard otomasyonu<\/a> pratikleri elinizi g\u00fc\u00e7lendirir.<\/p>\n<p>\u00d6nbellek katmanlar\u0131n\u0131, CDN\u2019i ve uygulama taraf\u0131 optimizasyonlar\u0131n\u0131 da denklemden esirgemeyin. DNS sadece y\u00f6n g\u00f6sterir; arkas\u0131ndaki d\u00fcnya ne kadar haz\u0131rl\u0131kl\u0131ysa, ger\u00e7ek h\u0131z o kadar artar. Merak edenler i\u00e7in, uygulama ve altyap\u0131 taraf\u0131ndaki iyile\u015ftirmeleri daha geni\u015f bir resimde g\u00f6rmek her zaman ufuk a\u00e7ar.<\/p>\n<h2 id='section-10'><span id=\"Sahada_Kucuk_Ama_Hayat_Kurtaran_Ipuclari\">Sahada K\u00fc\u00e7\u00fck Ama Hayat Kurtaran \u0130pu\u00e7lar\u0131<\/span><\/h2>\n<p>\u00d6nce d\u00fc\u015f\u00fck riskli bir domain ile tatbikat yap\u0131n. Her \u015fey sorunsuz akt\u0131\u011f\u0131nda, \u00fcretimde kulland\u0131\u011f\u0131n\u0131z domain\u2019i ta\u015f\u0131y\u0131n. Bu, \u00f6zellikle e-posta kay\u0131tlar\u0131m\u0131z (MX, SPF, DKIM) ve alt alan adlar\u0131 \u00e7oksa, huzur verir. Ta\u015f\u0131ma g\u00fcn\u00fcnde, sunucu g\u00fcnl\u00fcklerini bir kenarda a\u00e7\u0131k tutmak faydal\u0131d\u0131r; ba\u015far\u0131s\u0131z sorgular ya da timeout\u2019lar ipucu verir. Bir de metin dosyas\u0131nda \u201ckontrol listesi\u201d bulundurun: glue IP\u2019leri, ns A kay\u0131tlar\u0131, firewall durumu, NS delegasyonlar\u0131, TTL\u2019ler\u2026<\/p>\n<p>Testlerde tek bir resolver\u2019a g\u00fcvenmeyin. Farkl\u0131 a\u011flardan, farkl\u0131 \u00e7\u00f6z\u00fcm sunucular\u0131ndan bakmak iyi fikir. Bazen ISS\u2019in \u00f6nbelle\u011fi beklenenden uzun s\u00fcre tutar ve sizi yan\u0131lt\u0131r. \u2018+trace\u2019 \u00e7\u0131kt\u0131s\u0131n\u0131 okumay\u0131 \u00f6\u011frenmek, trafik s\u0131k\u0131\u015f\u0131kl\u0131\u011f\u0131nda alternatif g\u00fczerg\u00e2h bilmek gibidir. Anlarsan\u0131z, rahat edersiniz.<\/p>\n<p>Son olarak, yaz\u0131ya e\u015flik eden d\u0131\u015f kaynaklar\u0131 elinizin alt\u0131nda tutun. Kimi zaman bir g\u00f6rsel ya da tan\u0131m, kavram\u0131 \u015f\u0131p diye yerine oturtur. Bu yaz\u0131da linkini verdi\u011fim <a href=\"https:\/\/www.cloudflare.com\/learning\/dns\/glue-record\/\" rel=\"nofollow noopener\" target=\"_blank\">glue record \u00f6zetleri<\/a>, <a href=\"https:\/\/support.dnsimple.com\/articles\/glue-record\/\" rel=\"nofollow noopener\" target=\"_blank\">registrar taraf\u0131 a\u00e7\u0131klamalar\u0131<\/a> ve <a href=\"https:\/\/bind9.readthedocs.io\/en\/latest\/manpages\/dig.html\" rel=\"nofollow noopener\" target=\"_blank\">dig komutu dok\u00fcmantasyonu<\/a> bu i\u015fin k\u00fc\u00e7\u00fck el kitaplar\u0131 gibi \u00e7al\u0131\u015f\u0131r.<\/p>\n<h2 id='section-11'><span id=\"Kapanis_Kendi_DNSinin_Direksiyonunda\">Kapan\u0131\u015f: Kendi DNS\u2019inin Direksiyonunda<\/span><\/h2>\n<p>\u00d6zel ad sunucusu kurmak, ilk bak\u0131\u015fta karma\u015f\u0131k g\u00f6r\u00fcnen ama bir kez ad\u0131mlar\u0131n\u0131 tan\u0131y\u0131nca gayet ak\u0131\u015fkan bir s\u00fcre\u00e7. Registrar taraf\u0131nda glue kay\u0131tlar\u0131n\u0131 tan\u0131mlad\u0131\u011f\u0131n\u0131zda, sunucu \u00fczerinde ns A kay\u0131tlar\u0131n\u0131 ve NS delegasyonlar\u0131n\u0131 do\u011fru yerle\u015ftirdi\u011finizde, gerisi tatl\u0131 kontroller ve birka\u00e7 sab\u0131rl\u0131 testten ibaret. En sevdi\u011fim an, \u2018dig NS alanadiniz.com\u2019 \u00e7\u0131kt\u0131s\u0131nda ns1 ve ns2\u2019yi g\u00f6rmek; i\u015fte o zaman yol a\u00e7\u0131lm\u0131\u015f demektir. Ufak tefek p\u00fcr\u00fczler \u00e7\u0131ksa da, hepsinin bir kar\u015f\u0131l\u0131\u011f\u0131 var ve \u00e7\u00f6z\u00fcm yolu k\u0131sa.<\/p>\n<p>Pratik bir \u00f6zet b\u0131rakay\u0131m: IP\u2019leri \u00f6nceden planlay\u0131n, firewall\u2019\u0131 unutmay\u0131n, TTL\u2019leri ta\u015f\u0131ma \u00f6ncesinde d\u00fc\u015f\u00fcr\u00fcn, glue\u2019\u0131 registrar\u2019da kaydedin, zone\u2019da ns A ve NS kay\u0131tlar\u0131n\u0131 do\u011frulay\u0131n, farkl\u0131 resolver\u2019larla test edin. Hepsi bu. E\u011fer bu yaz\u0131yla birlikte bir iki domaini \u00f6zel ad sunucusuna ta\u015f\u0131may\u0131 ba\u015fard\u0131ysan\u0131z, \u015fimdiden tebrikler. Bir g\u00fcn \u00f6nce kafa kar\u0131\u015ft\u0131ran terimler, \u015fimdi elinizin alt\u0131nda \u00e7al\u0131\u015fan k\u00fc\u00e7\u00fck birer yard\u0131mc\u0131ya d\u00f6n\u00fc\u015ft\u00fc.<\/p>\n<p>Umar\u0131m bu rehber size yol g\u00f6sterici olmu\u015ftur. Sorular\u0131n\u0131z olursa, not edin; bazen tek bir sat\u0131r, b\u00fct\u00fcn geceyi kurtar\u0131r. Yeni yaz\u0131larda yine DNS\u2019in farkl\u0131 k\u00f6\u015felerine, bazen de uygulama taraf\u0131n\u0131n h\u0131z ve g\u00fcvenli\u011fine u\u011frar\u0131z. \u015eimdilik ho\u015f\u00e7a kal\u0131n; kendi DNS\u2019inizin direksiyonunda keyifli s\u00fcr\u00fc\u015fler.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>\u0130&ccedil;indekiler1 K\u0131sa Bir Hik\u00e2yeyle Ba\u015flayal\u0131m: O Alan Ad\u0131 Neden A\u00e7\u0131lmad\u0131?2 \u00d6zel Ad Sunucusu Nedir, Ne Zaman \u0130\u015fe Yarar?3 Glue Record Nedir? Neden Bazen En Ba\u015fa D\u00f6n\u00fcyoruz?4 Haz\u0131rl\u0131klar: IP\u2019ler, DNS Yaz\u0131l\u0131m\u0131, G\u00fcvenlik ve K\u00fc\u00e7\u00fck Ama Kritik Detaylar5 Ad\u0131m Ad\u0131m: Registrar \u00dczerinde Glue Record Olu\u015fturma6 Sunucuda NS ve Zone\u2019lar\u0131 Haz\u0131rlama: cPanel, Plesk ve BIND\/PowerDNS6.1 cPanel\/WHM ile h\u0131zl\u0131 [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":1421,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-1420","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\/1420","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=1420"}],"version-history":[{"count":0,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/1420\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/1421"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=1420"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=1420"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=1420"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}