{"id":5923,"date":"2026-10-29T23:11:21","date_gmt":"2026-10-29T20:11:21","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/?p=5923"},"modified":"2026-10-29T23:11:21","modified_gmt":"2026-10-29T20:11:21","slug":"alt-alan-adi-dns-delegasyonu","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/alt-alan-adi-dns-delegasyonu\/","title":{"rendered":"Alt Alan Ad\u0131n\u0131 NS Kayd\u0131yla Ayr\u0131 DNS&#8217;e Devretmek"},"content":{"rendered":"<div class=\"dchost-blog-content-wrapper\"><div class=\"aiw-summary\">\n<p class=\"aiw-box-title\">H\u0131zl\u0131 \u00f6zet<\/p>\n<p>Alt alan ad\u0131 DNS delegasyonu, ana alan\u0131n\u0131z\u0131n DNS y\u00f6netimini ta\u015f\u0131madan belirli bir alt alan\u0131n y\u00f6netimini ba\u015fka ekibe veya sa\u011flay\u0131c\u0131ya b\u0131rakman\u0131z\u0131 sa\u011flar. Bunun i\u00e7in ana alan\u0131n kay\u0131tlar\u0131n\u0131n tutuldu\u011fu \u00fcst DNS b\u00f6lgesine NS kay\u0131tlar\u0131 eklenir. Bu kay\u0131tlar, alt alan\u0131n DNS sorgular\u0131n\u0131 yan\u0131tlayacak yetkili sunucular\u0131 g\u00f6sterir.<\/p>\n<ul>\n<li>Ana alan ad\u0131n\u0131n nameserver, yani yetkili DNS sunucusu ayarlar\u0131 de\u011fi\u015fmez.<\/li>\n<li>Yeni sa\u011flay\u0131c\u0131da alt alana ait ayr\u0131 DNS b\u00f6lgesi olu\u015fturulur; o alt alan\u0131n kay\u0131tlar\u0131 burada y\u00f6netilir.<\/li>\n<li>NS kayd\u0131 y\u00f6netim yetkisini devreder; bir adresi IP&#8217;ye ba\u011flayan A veya ba\u015fka bir ada ba\u011flayan CNAME kayd\u0131 ayn\u0131 i\u015fi yapmaz.<\/li>\n<li>Devirden \u00f6nce yeni sunucular\u0131n yan\u0131tlar\u0131, ard\u0131ndan sorgular\u0131n bu sunuculara y\u00f6nlendirildi\u011fi kontrol edilir.<\/li>\n<\/ul>\n<\/div>\n<p>Geli\u015ftirme ekibinizin bir alt alan\u0131 y\u00f6netmesi gerekiyor ama ana sitenizin ve e-postan\u0131z\u0131n DNS ayarlar\u0131na eri\u015fim vermek istemiyorsunuz. Yaln\u0131zca ilgili alt alan\u0131 devretmek, ekibin kendi kay\u0131tlar\u0131n\u0131 y\u00f6netmesini sa\u011flarken ana alan\u0131n kontrol\u00fcn\u00fc sizde tutar. Bu i\u015flem uygulaman\u0131z\u0131 ba\u015fka sunucuya ta\u015f\u0131maz; kay\u0131tlar\u0131n nerede ve kim taraf\u0131ndan y\u00f6netilece\u011fini de\u011fi\u015ftirir.<\/p>\n<p><strong>\u00d6rnek senaryoda<\/strong> <code>example.com<\/code> mevcut DNS hizmetinde kalacak, <code>dev.example.com<\/code> ise ikinci bir hizmette y\u00f6netilecek. \u00d6nce yeni b\u00f6lgeyi haz\u0131rlayacak, ard\u0131ndan \u00fcst b\u00f6lgedeki NS kay\u0131tlar\u0131yla yetkiyi devredeceksiniz. Son ad\u0131mda <code>dig<\/code> adl\u0131 DNS sorgulama arac\u0131yla do\u011fru sunucular\u0131n yan\u0131t verdi\u011fini kontrol edeceksiniz. B\u00f6ylece paneldeki kay\u0131tlar\u0131n yan\u0131 s\u0131ra devrin DNS \u00fczerinden \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 da do\u011frulayabileceksiniz.<\/p>\n<div id=\"toc_container\" role=\"navigation\" aria-label=\"Table of Contents\" data-nosnippet class=\"toc_transparent no_bullets toc_numbered toc_title_center\"><p class=\"toc_title\">\u0130\u00e7indekiler<\/p><ul class=\"toc_list\"><li><a href=\"#Alt_alan_adi_DNS_delegasyonu_neyi_degistirir\"><span class=\"toc_number toc_depth_1\">1.<\/span> Alt alan ad\u0131 DNS delegasyonu neyi de\u011fi\u015ftirir?<\/a><ul><li><a href=\"#NS_kaydi_neden_A_veya_CNAME_yerine_kullanilir\"><span class=\"toc_number toc_depth_2\">1.1.<\/span> NS kayd\u0131 neden A veya CNAME yerine kullan\u0131l\u0131r?<\/a><\/li><li><a href=\"#Ust_bolge_nerede_biter_alt_bolge_nerede_baslar\"><span class=\"toc_number toc_depth_2\">1.2.<\/span> \u00dcst b\u00f6lge nerede biter, alt b\u00f6lge nerede ba\u015flar?<\/a><\/li><li><a href=\"#Yetki_devri_sizin_ihtiyaciniza_uygun_mu\"><span class=\"toc_number toc_depth_2\">1.3.<\/span> Yetki devri sizin ihtiyac\u0131n\u0131za uygun mu?<\/a><\/li><\/ul><\/li><li><a href=\"#Ornek_ortami_ve_yeni_DNS_bolgesini_hazirlayin\"><span class=\"toc_number toc_depth_1\">2.<\/span> \u00d6rnek ortam\u0131 ve yeni DNS b\u00f6lgesini haz\u0131rlay\u0131n<\/a><ul><li><a href=\"#Erisimleri_ve_mevcut_kayitlari_hazirlayin\"><span class=\"toc_number toc_depth_2\">2.1.<\/span> Eri\u015fimleri ve mevcut kay\u0131tlar\u0131 haz\u0131rlay\u0131n<\/a><\/li><li><a href=\"#Alt_bolgeyi_olusturup_kayitlari_ekleyin\"><span class=\"toc_number toc_depth_2\">2.2.<\/span> Alt b\u00f6lgeyi olu\u015fturup kay\u0131tlar\u0131 ekleyin<\/a><\/li><li><a href=\"#Devirden_once_iki_yetkili_sunucuyu_sorgulayin\"><span class=\"toc_number toc_depth_2\">2.3.<\/span> Devirden \u00f6nce iki yetkili sunucuyu sorgulay\u0131n<\/a><\/li><\/ul><\/li><li><a href=\"#Ust_bolgeye_NS_kayitlarini_ekleyerek_yetkiyi_devredin\"><span class=\"toc_number toc_depth_1\">3.<\/span> \u00dcst b\u00f6lgeye NS kay\u0131tlar\u0131n\u0131 ekleyerek yetkiyi devredin<\/a><ul><li><a href=\"#Cakisan_kayitlari_ayirin\"><span class=\"toc_number toc_depth_2\">3.1.<\/span> \u00c7ak\u0131\u015fan kay\u0131tlar\u0131 ay\u0131r\u0131n<\/a><\/li><li><a href=\"#Iki_NS_kaydini_kaydedin\"><span class=\"toc_number toc_depth_2\">3.2.<\/span> \u0130ki NS kayd\u0131n\u0131 kaydedin<\/a><\/li><li><a href=\"#Gerekirse_eski_yonetime_donun\"><span class=\"toc_number toc_depth_2\">3.3.<\/span> Gerekirse eski y\u00f6netime d\u00f6n\u00fcn<\/a><\/li><\/ul><\/li><li><a href=\"#Delegasyonu_dig_ile_dogrulayin_ve_hatalari_ayirin\"><span class=\"toc_number toc_depth_1\">4.<\/span> Delegasyonu dig ile do\u011frulay\u0131n ve hatalar\u0131 ay\u0131r\u0131n<\/a><ul><li><a href=\"#Ust_yonlendirmeyi_ve_alt_yetkilileri_karsilastirin\"><span class=\"toc_number toc_depth_2\">4.1.<\/span> \u00dcst y\u00f6nlendirmeyi ve alt yetkilileri kar\u015f\u0131la\u015ft\u0131r\u0131n<\/a><\/li><li><a href=\"#Onbellegi_gercek_yayin_hatasindan_ayirin\"><span class=\"toc_number toc_depth_2\">4.2.<\/span> \u00d6nbelle\u011fi ger\u00e7ek yay\u0131n hatas\u0131ndan ay\u0131r\u0131n<\/a><\/li><li><a href=\"#Glue_ve_DNSSEC_gereken_durumlar\"><span class=\"toc_number toc_depth_2\">4.3.<\/span> Glue ve DNSSEC gereken durumlar<\/a><\/li><\/ul><\/li><li><a href=\"#Sik_Sorulan_Sorular\"><span class=\"toc_number toc_depth_1\">5.<\/span> S\u0131k Sorulan Sorular<\/a><ul><li><a href=\"#Alt_alani_devretmek_icin_alan_adi_transferi_gerekir_mi\"><span class=\"toc_number toc_depth_2\">5.1.<\/span> Alt alan\u0131 devretmek i\u00e7in alan ad\u0131 transferi gerekir mi?<\/a><\/li><li><a href=\"#NS_kayitlarini_ekleyince_SSL_sertifikasi_otomatik_gelir_mi\"><span class=\"toc_number toc_depth_2\">5.2.<\/span> NS kay\u0131tlar\u0131n\u0131 ekleyince SSL sertifikas\u0131 otomatik gelir mi?<\/a><\/li><li><a href=\"#Ana_alan_adinin_e-postasi_etkilenir_mi\"><span class=\"toc_number toc_depth_2\">5.3.<\/span> Ana alan ad\u0131n\u0131n e-postas\u0131 etkilenir mi?<\/a><\/li><li><a href=\"#Alt_ekibin_yetkisini_yalnizca_bu_bolgeyle_nasil_sinirlarim\"><span class=\"toc_number toc_depth_2\">5.4.<\/span> Alt ekibin yetkisini yaln\u0131zca bu b\u00f6lgeyle nas\u0131l s\u0131n\u0131rlar\u0131m?<\/a><\/li><\/ul><\/li><li><a href=\"#Devir_sonrasi_kontrol_listesi\"><span class=\"toc_number toc_depth_1\">6.<\/span> Devir sonras\u0131 kontrol listesi<\/a><\/li><\/ul><\/div>\n<h2><span id=\"Alt_alan_adi_DNS_delegasyonu_neyi_degistirir\">Alt alan ad\u0131 DNS delegasyonu neyi de\u011fi\u015ftirir?<\/span><\/h2>\n<p><strong>Alt alan ad\u0131 DNS delegasyonu<\/strong>, yani alt alan\u0131n DNS y\u00f6netim yetkisinin devri, ana alan ad\u0131n\u0131z\u0131n y\u00f6netimini ta\u015f\u0131madan belirli bir alt alan\u0131n kay\u0131tlar\u0131n\u0131 ba\u015fka bir DNS hizmetine b\u0131rakman\u0131z\u0131 sa\u011flar. De\u011fi\u015fen, web sitesinin bulundu\u011fu sunucu de\u011fil, o alt alan\u0131n kay\u0131tlar\u0131 i\u00e7in hangi DNS sunucular\u0131n\u0131n yetkili oldu\u011fudur. B\u00f6ylece ilgili ekip, kendisine ayr\u0131lan kay\u0131tlar\u0131 sizin ana DNS panelinize girmeden y\u00f6netebilir.<\/p>\n<figure class=\"aiw-figure\" data-aiw-visual-id=\"5919\" data-aiw-visual-key=\"c9a458abab4fa65a374deef4710c9887fbf62e689b829ea2d00af36e44c8caef\"><img decoding=\"async\" src=\"https:\/\/www.dchost.com\/blog\/wp-content\/uploads\/2026\/10\/dchost-flow-tr-08400e92e22055602cb6.png\" alt=\"example.com \u00fcst b\u00f6lgesindeki NS kay\u0131tlar\u0131ndan ayr\u0131 y\u00f6netilen dev.example.com alt b\u00f6lgesine uzanan yetki devri.\" width=\"840\" height=\"948\" loading=\"lazy\" class=\"aiw-article-visual wp-image-5919\" srcset=\"https:\/\/www.dchost.com\/blog\/wp-content\/uploads\/2026\/10\/dchost-flow-tr-08400e92e22055602cb6.png 840w, https:\/\/www.dchost.com\/blog\/wp-content\/uploads\/2026\/10\/dchost-flow-tr-08400e92e22055602cb6-266x300.png 266w, https:\/\/www.dchost.com\/blog\/wp-content\/uploads\/2026\/10\/dchost-flow-tr-08400e92e22055602cb6-768x867.png 768w\" sizes=\"auto, (max-width: 840px) 100vw, 840px\" \/><figcaption>Ak\u0131\u015f \u015femas\u0131: \u015eema, ana alan\u0131n DNS y\u00f6netimi ta\u015f\u0131nmadan yaln\u0131zca dev.example.com ve alt\u0131ndaki adlar\u0131n yetkisinin nas\u0131l ayr\u0131ld\u0131\u011f\u0131n\u0131 g\u00f6sterir.<\/figcaption><\/figure>\n<h3><span id=\"NS_kaydi_neden_A_veya_CNAME_yerine_kullanilir\">NS kayd\u0131 neden A veya CNAME yerine kullan\u0131l\u0131r?<\/span><\/h3>\n<p>DNS, alan adlar\u0131n\u0131 IP adresleri gibi ba\u011flant\u0131 bilgileriyle e\u015fle\u015ftiren sistemdir. Her kay\u0131t t\u00fcr\u00fcn\u00fcn g\u00f6revi farkl\u0131d\u0131r: yaln\u0131zca uygulamay\u0131 ba\u015fka bir sunucuya ba\u011flamak istiyorsan\u0131z yetki devri gerekmeyebilir. Kay\u0131t y\u00f6netimini de ay\u0131rmak istiyorsan\u0131z yetkili ad sunucular\u0131n\u0131 belirten NS kayd\u0131 kullan\u0131l\u0131r.<\/p>\n<table>\n<thead>\n<tr>\n<th>Kay\u0131t<\/th>\n<th>Ne yapar?<\/th>\n<th>Hangi ihtiya\u00e7ta se\u00e7ilir?<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>A<\/td>\n<td>Bir ad\u0131 IPv4 adresiyle e\u015fle\u015ftirir.<\/td>\n<td>Alt alan\u0131 belirli bir sunucuya ba\u011flamak istedi\u011finizde.<\/td>\n<\/tr>\n<tr>\n<td>CNAME<\/td>\n<td>Bir ad\u0131 ba\u015fka bir DNS ad\u0131na takma ad olarak ba\u011flar.<\/td>\n<td>Hizmetin verdi\u011fi hedef ad\u0131 kullanman\u0131z gerekti\u011finde.<\/td>\n<\/tr>\n<tr>\n<td>NS<\/td>\n<td>Bir DNS b\u00f6lgesinin yetkili ad sunucular\u0131n\u0131 belirtir; \u00fcst b\u00f6lgede alt alan\u0131n yetkisini devretmek i\u00e7in kullan\u0131l\u0131r.<\/td>\n<td>Alt alan\u0131n kay\u0131t y\u00f6netimini ayr\u0131 ekibe veya sa\u011flay\u0131c\u0131ya b\u0131rakmak istedi\u011finizde.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>A veya CNAME kayd\u0131 eklemek, kar\u015f\u0131 tarafa DNS y\u00f6netim yetkisi vermez. NS ile yetki devrinde ise alt alan\u0131n kay\u0131tlar\u0131 yeni yetkili sunuculardan \u00f6\u011frenilir. Bu i\u015flem tek ba\u015f\u0131na dosyalar\u0131, veritaban\u0131n\u0131 veya uygulamay\u0131 ta\u015f\u0131maz; uygulaman\u0131z ayn\u0131 sunucuda \u00e7al\u0131\u015fmaya devam edebilir.<\/p>\n<h3><span id=\"Ust_bolge_nerede_biter_alt_bolge_nerede_baslar\">\u00dcst b\u00f6lge nerede biter, alt b\u00f6lge nerede ba\u015flar?<\/span><\/h3>\n<p><strong>DNS b\u00f6lgesi<\/strong>, DNS a\u011fac\u0131nda birlikte y\u00f6netilen bir kay\u0131t alan\u0131d\u0131r. \u00d6rnek senaryoda <code>example.com<\/code> mevcut DNS hizmetinde kal\u0131rken <code>dev.example.com<\/code> ikinci hizmette ayr\u0131 bir b\u00f6lge olur. Ana alan\u0131 i\u00e7eren b\u00f6lgeye \u00fcst b\u00f6lge, devredilen b\u00f6lgeye alt b\u00f6lge diyece\u011fiz.<\/p>\n<p>\u00dcst b\u00f6lgedeki <code>dev.example.com<\/code> NS kay\u0131tlar\u0131, sizin ad\u0131n\u0131za DNS sorgular\u0131n\u0131 yapan \u00e7\u00f6z\u00fcmleyiciye yan\u0131t\u0131 hangi alt b\u00f6lge sunucular\u0131ndan alaca\u011f\u0131n\u0131 g\u00f6sterir. <code>dev.example.com<\/code> ve <code>www.dev.example.com<\/code> gibi onun alt\u0131ndaki adlar\u0131n kay\u0131tlar\u0131 art\u0131k alt b\u00f6lgede y\u00f6netilir. <code>example.com<\/code>, <code>www.example.com<\/code> ve di\u011fer karde\u015f alt alanlar bu devrin d\u0131\u015f\u0131nda kal\u0131r.<\/p>\n<p>Bu s\u0131n\u0131r, kay\u0131tlar\u0131 hangi panelde d\u00fczenleyece\u011finizi de belirler. Devirden sonra \u00fcst b\u00f6lgeye <code>www.dev.example.com<\/code> i\u00e7in s\u0131radan bir kay\u0131t eklemek, alt b\u00f6lgedeki kayd\u0131 de\u011fi\u015ftirmez ve normal DNS \u00e7\u00f6z\u00fcmlemesinde o ad\u0131n yan\u0131t kayna\u011f\u0131 olmaz. Bu nedenle ekiplerin hangi kay\u0131tlar\u0131 hangi DNS hizmetinde y\u00f6netece\u011fini a\u00e7\u0131k\u00e7a belirleyin.<\/p>\n<h3><span id=\"Yetki_devri_sizin_ihtiyaciniza_uygun_mu\">Yetki devri sizin ihtiyac\u0131n\u0131za uygun mu?<\/span><\/h3>\n<p>Geli\u015ftirme ekibinin kendisine ayr\u0131lan dalda yeni alt alanlar a\u00e7mas\u0131, do\u011frulama kay\u0131tlar\u0131 eklemesi veya hizmet hedeflerini ba\u011f\u0131ms\u0131z de\u011fi\u015ftirmesi gerekiyorsa delegasyon uygundur. Yaln\u0131zca tek bir sitenin adresini ba\u015fka sunucuya ba\u011flayacaksan\u0131z mevcut b\u00f6lgede A ya da CNAME kayd\u0131 kullanmak daha sade olabilir. Karar \u00f6l\u00e7\u00fct\u00fc, uygulaman\u0131n nerede \u00e7al\u0131\u015ft\u0131\u011f\u0131ndan \u00e7ok <strong>DNS kay\u0131tlar\u0131n\u0131 kimin ba\u011f\u0131ms\u0131z y\u00f6netmesi gerekti\u011fidir<\/strong>.<\/p>\n<h2><span id=\"Ornek_ortami_ve_yeni_DNS_bolgesini_hazirlayin\">\u00d6rnek ortam\u0131 ve yeni DNS b\u00f6lgesini haz\u0131rlay\u0131n<\/span><\/h2>\n<h3><span id=\"Erisimleri_ve_mevcut_kayitlari_hazirlayin\">Eri\u015fimleri ve mevcut kay\u0131tlar\u0131 haz\u0131rlay\u0131n<\/span><\/h3>\n<p>\u00d6rnek senaryoda iki y\u00f6netilen DNS hizmetinin de alt b\u00f6lge bar\u0131nd\u0131rmay\u0131 destekledi\u011fini varsay\u0131yoruz. \u00dcst b\u00f6lgenin yetkili sunucular\u0131 <code>ns1.parent.example<\/code> ve <code>ns2.parent.example<\/code>, alt b\u00f6lgenin yeni yetkilileri <code>ns1.child.example<\/code> ve <code>ns2.child.example<\/code> olsun. Bunlar temsili adlard\u0131r; i\u015flemlerde sa\u011flay\u0131c\u0131lar\u0131n\u0131z\u0131n verdi\u011fi ger\u00e7ek sunucu adlar\u0131n\u0131 kullan\u0131n. Ana anlat\u0131m, DNS yan\u0131tlar\u0131n\u0131 imzalarla do\u011frulayan DNSSEC mekanizmas\u0131n\u0131n kullan\u0131lmad\u0131\u011f\u0131 ve ad sunucular\u0131 devredilen alt alan\u0131n d\u0131\u015f\u0131nda bulunan bir alt b\u00f6lge i\u00e7indir.<\/p>\n<p>Mevcut hizmette <code>example.com<\/code> kay\u0131tlar\u0131n\u0131 d\u00fczenleme, yeni hizmette ise b\u00f6lge olu\u015fturma yetkiniz olmal\u0131. \u00d6nce mevcut panelin b\u00f6lge y\u00f6netimi ekran\u0131ndan kay\u0131tlar\u0131 d\u0131\u015fa aktar\u0131n. D\u0131\u015fa aktarma se\u00e7ene\u011fi yoksa kay\u0131t adlar\u0131n\u0131, t\u00fcrlerini, de\u011ferlerini ve TTL de\u011ferlerini, yani \u00f6nbellekte tutulma s\u00fcrelerini kaydedin. Bu d\u00f6k\u00fcm, geri d\u00f6n\u00fc\u015f gerekirse eski kay\u0131tlar\u0131 yeniden kurman\u0131z\u0131 sa\u011flar. \u00d6zellikle <code>dev.example.com<\/code> ve alt\u0131ndaki A, AAAA, CNAME, MX, TXT ve di\u011fer kay\u0131tlar\u0131 ay\u0131r\u0131n; yaln\u0131zca web kayd\u0131n\u0131 ta\u015f\u0131mak, posta veya hizmet do\u011frulama kay\u0131tlar\u0131n\u0131n eksik kalmas\u0131na neden olabilir.<\/p>\n<p>Mevcut panelin kay\u0131t d\u00fczenleme ekran\u0131nda ta\u015f\u0131nacak kay\u0131tlar\u0131n <strong>TTL<\/strong> de\u011ferini, hizmet destekliyorsa <code>300<\/code> saniyeye indirin. Bu, de\u011fi\u015fiklikten sonra al\u0131nan yan\u0131tlar\u0131n \u00f6nbellekte daha k\u0131sa tutulmas\u0131n\u0131 sa\u011flar. Ancak daha \u00f6nce \u00f6nbelle\u011fe al\u0131nan yan\u0131tlar eski TTL boyunca kullan\u0131labilir; yetki devrine ge\u00e7meden \u00f6nce eski s\u00fcrenin dolmas\u0131n\u0131 bekleyin. Bu haz\u0131rl\u0131k a\u015famas\u0131nda hi\u00e7bir kayd\u0131 silmeyin.<\/p>\n<h3><span id=\"Alt_bolgeyi_olusturup_kayitlari_ekleyin\">Alt b\u00f6lgeyi olu\u015fturup kay\u0131tlar\u0131 ekleyin<\/span><\/h3>\n<p>Yeni hizmette temsili <strong>DNS &gt; Zones &gt; Add zone<\/strong> yolunu, yani b\u00f6lge ekleme ekran\u0131n\u0131 a\u00e7\u0131n. Aray\u00fcz adlar\u0131 sa\u011flay\u0131c\u0131ya g\u00f6re de\u011fi\u015febilir. B\u00f6lge ad\u0131 alan\u0131na <code>dev.example.com<\/code> yaz\u0131p yetkili DNS b\u00f6lgesi olarak olu\u015fturun. Sa\u011flay\u0131c\u0131n\u0131n bu b\u00f6lgeye atad\u0131\u011f\u0131 iki NS ad\u0131n\u0131 kaydedin; \u00fcst b\u00f6lgeye yetki devri kay\u0131tlar\u0131n\u0131 eklerken bu adlar\u0131 kullanacaks\u0131n\u0131z.<\/p>\n<p><strong>Records &gt; Add record<\/strong>, yani kay\u0131t ekleme ekran\u0131nda a\u015fa\u011f\u0131daki \u00f6rnek kay\u0131tlar\u0131 ekleyin. <strong>Name<\/strong> kay\u0131t ad\u0131n\u0131, <strong>Type<\/strong> kay\u0131t t\u00fcr\u00fcn\u00fc, <strong>Value\/Target<\/strong> ise de\u011feri veya hedefi belirtir. <code>@<\/code> burada b\u00f6lgenin k\u00f6k\u00fc olan <code>dev.example.com<\/code> anlam\u0131na gelir. \u0130lk kay\u0131t k\u00f6k ad\u0131 uygulaman\u0131n IP adresine ba\u011flar; ikinci kay\u0131t www ad\u0131n\u0131 ayn\u0131 hedefe y\u00f6neltir.<\/p>\n<table>\n<thead>\n<tr>\n<th>Name<\/th>\n<th>Type<\/th>\n<th>Value\/Target<\/th>\n<th>TTL<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>@<\/td>\n<td>A<\/td>\n<td>192.0.2.80<\/td>\n<td>300<\/td>\n<\/tr>\n<tr>\n<td>www<\/td>\n<td>CNAME<\/td>\n<td>dev.example.com.<\/td>\n<td>300<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><code>192.0.2.80<\/code> dok\u00fcmantasyon i\u00e7in ayr\u0131lm\u0131\u015f bir \u00f6rnek adrestir; bunun yerine ger\u00e7ek uygulama IP adresinizi kullan\u0131n. Hedefin sonundaki nokta tam DNS ad\u0131n\u0131 belirtir; baz\u0131 paneller bunu kendisi ekler. Kaydettikten sonra kay\u0131t listesinde b\u00f6lge ad\u0131n\u0131n yanl\u0131\u015fl\u0131kla hedefe ikinci kez eklenmedi\u011fini kontrol edin. D\u00f6k\u00fcm\u00fcn\u00fczdeki di\u011fer kay\u0131tlar\u0131 da yeni b\u00f6lgeye g\u00f6re adland\u0131r\u0131n: \u00fcst b\u00f6lgedeki <code>api.dev<\/code> kayd\u0131 burada <code>api<\/code> olur. B\u00f6ylece kayd\u0131n tam ad\u0131 de\u011fi\u015fmeden kal\u0131r.<\/p>\n<h3><span id=\"Devirden_once_iki_yetkili_sunucuyu_sorgulayin\">Devirden \u00f6nce iki yetkili sunucuyu sorgulay\u0131n<\/span><\/h3>\n<p>Sa\u011flay\u0131c\u0131n\u0131n olu\u015fturdu\u011fu <strong>SOA<\/strong> kayd\u0131, b\u00f6lgenin y\u00f6netim ve s\u00fcr\u00fcm bilgilerini ta\u015f\u0131r; NS kay\u0131tlar\u0131 ise atanan yetkilileri g\u00f6stermelidir. Bu kay\u0131tlar\u0131 tahmini de\u011ferlerle de\u011fi\u015ftirmek yerine do\u011frudan sunuculardan sorgulay\u0131n. Komutlar\u0131 Ubuntu terminalinde, paket kurmak i\u00e7in sudo yetkisi olan bir kullan\u0131c\u0131yla \u00e7al\u0131\u015ft\u0131r\u0131n. \u00d6nce DNS sorgulama arac\u0131 <code>dig<\/code> i\u00e7in paketi kurun; ard\u0131ndan sorgulardaki temsili sunucu ve alan adlar\u0131n\u0131 kendi de\u011ferlerinizle de\u011fi\u015ftirin. Sorgular ba\u015fka sunuculara ba\u015fvurulmadan yan\u0131tlanaca\u011f\u0131 i\u00e7in her yetkilinin yeni b\u00f6lgeyi yay\u0131mlay\u0131p yay\u0131mlamad\u0131\u011f\u0131n\u0131 g\u00f6rebilirsiniz:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">sudo apt update\nsudo apt install dnsutils\nfor ns in ns1.child.example ns2.child.example; do\n  dig @&quot;$ns&quot; dev.example.com SOA +norecurse\n  dig @&quot;$ns&quot; dev.example.com NS +norecurse\n  dig @&quot;$ns&quot; dev.example.com A +norecurse\n  dig @&quot;$ns&quot; www.dev.example.com CNAME +norecurse\ndone<\/code><\/pre>\n<p>Her iki sunucunun yan\u0131t\u0131nda <code>status: NOERROR<\/code>, bayraklarda yetkili yan\u0131t\u0131 belirten <code>aa<\/code> ve sorgulad\u0131\u011f\u0131n\u0131z kay\u0131tlar\u0131n beklenen de\u011ferlerini g\u00f6rmelisiniz. NS kay\u0131tlar\u0131 sa\u011flay\u0131c\u0131n\u0131n atad\u0131\u011f\u0131 sunucularla e\u015fle\u015fmeli; SOA bilgileri de sa\u011flay\u0131c\u0131n\u0131n b\u00f6lge ayarlar\u0131yla tutarl\u0131 olmal\u0131d\u0131r. Yan\u0131t gelmezse \u00f6nce panelde b\u00f6lgenin yay\u0131mland\u0131\u011f\u0131n\u0131 ve sorguda do\u011fru sunucu ad\u0131n\u0131 kulland\u0131\u011f\u0131n\u0131z\u0131 kontrol edin. Yanl\u0131\u015f hedefi veya yay\u0131mlama sorununu d\u00fczelttikten sonra ayn\u0131 sorgular\u0131 tekrarlay\u0131n. \u0130ki sunucudan da do\u011fru yan\u0131t almadan \u00fcst b\u00f6lgede devri ba\u015flatmay\u0131n; mevcut trafik bu a\u015famada eski DNS kay\u0131tlar\u0131n\u0131 kullanmaya devam eder.<\/p>\n<h2><span id=\"Ust_bolgeye_NS_kayitlarini_ekleyerek_yetkiyi_devredin\">\u00dcst b\u00f6lgeye NS kay\u0131tlar\u0131n\u0131 ekleyerek yetkiyi devredin<\/span><\/h2>\n<p>Yeni alt b\u00f6lge iki yetkili sunucudan da do\u011fru yan\u0131t veriyorsa mevcut DNS hizmetindeki <code>example.com<\/code> b\u00f6lgesine ge\u00e7ebilirsiniz. Buraya ekleyece\u011finiz iki NS kayd\u0131 yaln\u0131zca <code>dev.example.com<\/code> ve alt\u0131ndaki adlar\u0131n y\u00f6netimini devreder. <strong>Alan ad\u0131 kay\u0131t firmas\u0131ndaki Nameserver (yetkili ad sunucusu) ayar\u0131n\u0131 de\u011fi\u015ftirmeyin;<\/strong> ana alan\u0131n yetkilileri <code>ns1.parent.example<\/code> ve <code>ns2.parent.example<\/code> olarak kal\u0131r.<\/p>\n<h3><span id=\"Cakisan_kayitlari_ayirin\">\u00c7ak\u0131\u015fan kay\u0131tlar\u0131 ay\u0131r\u0131n<\/span><\/h3>\n<p>Mevcut panelde <strong>DNS &gt; Zones<\/strong> yolundan <code>example.com<\/code> b\u00f6lgesini a\u00e7\u0131n. <strong>Records<\/strong> (kay\u0131tlar) ekran\u0131nda <code>dev<\/code> ve alt\u0131nda kalan adlar\u0131 filtreleyin. Devir \u00f6ncesinde ald\u0131\u011f\u0131n\u0131z kay\u0131t d\u00f6k\u00fcm\u00fcyle yeni alt b\u00f6lgeyi kar\u015f\u0131la\u015ft\u0131r\u0131n. Ta\u015f\u0131nmam\u0131\u015f bir MX veya TXT kayd\u0131 varsa \u00f6nce yeni b\u00f6lgeye ekleyin; devirden sonra bu kay\u0131tlar da yeni yetkililerden sorgulanacakt\u0131r.<\/p>\n<p><code>dev<\/code> ad\u0131nda CNAME varsa ayn\u0131 adda NS kay\u0131tlar\u0131 bulunamaz. Eski hedefin yeni alt b\u00f6lgede uygun kay\u0131tlarla kar\u015f\u0131land\u0131\u011f\u0131n\u0131 kontrol ettikten sonra, NS eklemeden hemen \u00f6nce bu CNAME kayd\u0131n\u0131 kald\u0131r\u0131n. Alt b\u00f6lgenin k\u00f6k\u00fcnde SOA ve NS kay\u0131tlar\u0131 bulundu\u011fu i\u00e7in buraya CNAME koyamazs\u0131n\u0131z. Bu \u00f6rnekte k\u00f6k adresi A kayd\u0131 kar\u015f\u0131lar.<\/p>\n<p>\u00dcst b\u00f6lgedeki eski <code>dev<\/code> A\/AAAA kay\u0131tlar\u0131 ve <code>www.dev<\/code> gibi alt kay\u0131tlar devirden sonra yan\u0131t kayna\u011f\u0131 olmaz. Geri d\u00f6n\u00fc\u015fte kullanmak \u00fczere d\u00f6k\u00fcmlerini saklay\u0131n ve bunlar\u0131 NS ekleme i\u015flemiyle ayn\u0131 de\u011fi\u015fiklik aral\u0131\u011f\u0131nda kald\u0131r\u0131n. Panel toplu yay\u0131mlamay\u0131 destekliyorsa silme ve ekleme i\u015flemlerini birlikte yay\u0131mlayarak arada kay\u0131tlar\u0131n eksik kald\u0131\u011f\u0131 bir s\u00fcre olu\u015fmas\u0131n\u0131 \u00f6nleyin. Di\u011fer alt alanlar\u0131n kay\u0131tlar\u0131na dokunmay\u0131n.<\/p>\n<h3><span id=\"Iki_NS_kaydini_kaydedin\">\u0130ki NS kayd\u0131n\u0131 kaydedin<\/span><\/h3>\n<p>Ayn\u0131 \u00fcst b\u00f6lgede <strong>Records &gt; Add record<\/strong> (kay\u0131t ekleme) ekran\u0131n\u0131 a\u00e7\u0131n ve a\u015fa\u011f\u0131daki kay\u0131tlar\u0131 ayr\u0131 ayr\u0131 ekleyin. <strong>Name<\/strong> alan\u0131 kay\u0131t ad\u0131n\u0131, <strong>Type<\/strong> kay\u0131t t\u00fcr\u00fcn\u00fc, <strong>Value\/Target<\/strong> ise hedefi belirtir. Hedef alan\u0131na IP adresi de\u011fil, yeni sa\u011flay\u0131c\u0131n\u0131n atad\u0131\u011f\u0131 ad sunucusu ad\u0131n\u0131 yaz\u0131n. Ge\u00e7i\u015f s\u0131ras\u0131nda \u00f6nbellekte tutulma s\u00fcresini k\u0131sa tutmak i\u00e7in <strong>TTL<\/strong> alan\u0131nda, hizmet destekliyorsa, tabloda g\u00f6sterilen 300 saniyeyi kullan\u0131n.<\/p>\n<table>\n<thead>\n<tr>\n<th>Name<\/th>\n<th>Type<\/th>\n<th>Value\/Target<\/th>\n<th>TTL<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>dev<\/td>\n<td>NS<\/td>\n<td>ns1.child.example.<\/td>\n<td>300<\/td>\n<\/tr>\n<tr>\n<td>dev<\/td>\n<td>NS<\/td>\n<td>ns2.child.example.<\/td>\n<td>300<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Temsili hedefleri ger\u00e7ek sunucu adlar\u0131yla de\u011fi\u015ftirin. Panel tam kay\u0131t ad\u0131 istiyorsa <code>dev.example.com<\/code> yaz\u0131n; <code>@<\/code> kullanmay\u0131n, \u00e7\u00fcnk\u00fc bu ekranda ana alan\u0131 belirtir. Kaydettikten sonra kay\u0131t listesinde iki kayd\u0131n da <code>dev.example.com<\/code> ad\u0131na ait oldu\u011funu ve hedeflerin alt b\u00f6lgedeki NS k\u00fcmesiyle e\u015fle\u015fti\u011fini kontrol edin. Bu kontrol panelde do\u011fru kay\u0131tlar\u0131n bulundu\u011funu g\u00f6sterir; kay\u0131tlar\u0131n DNS \u00fczerinden yay\u0131mland\u0131\u011f\u0131n\u0131 sonraki b\u00f6l\u00fcmde sorgulayaca\u011f\u0131z.<\/p>\n<h3><span id=\"Gerekirse_eski_yonetime_donun\">Gerekirse eski y\u00f6netime d\u00f6n\u00fcn<\/span><\/h3>\n<p>Geri d\u00f6n\u00fc\u015f i\u00e7in \u00fcst b\u00f6lgedeki bu iki NS kayd\u0131n\u0131 kald\u0131r\u0131p d\u00f6k\u00fcmdeki eski kay\u0131tlar\u0131 geri y\u00fckleyin; m\u00fcmk\u00fcnse de\u011fi\u015fiklikleri birlikte yay\u0131mlay\u0131n. Ard\u0131ndan \u00fcst yetkili sunucular\u0131 do\u011frudan sorgulay\u0131n: alt sunuculara y\u00f6nlendirme yerine eski kay\u0131tlar\u0131n yan\u0131tland\u0131\u011f\u0131n\u0131 g\u00f6rmelisiniz.<\/p>\n<p>Delegasyonu \u00f6nbelle\u011finde tutan \u00e7\u00f6z\u00fcmleyiciler bir s\u00fcre yeni yetkililere gitmeye devam edebilir. Bu y\u00fczden geri d\u00f6n\u00fc\u015fte alt b\u00f6lgeyi hemen silmeyin; \u00f6nbellekteki NS kay\u0131tlar\u0131n\u0131n TTL s\u00fcresi dolana kadar gerekli kay\u0131tlar\u0131 yan\u0131tlar durumda tutun. Bu s\u00fcreyi de\u011ferlendirirken yaln\u0131zca \u00fcst b\u00f6lgeye ekledi\u011finiz NS kay\u0131tlar\u0131n\u0131n de\u011fil, alt b\u00f6lgenin yay\u0131mlad\u0131\u011f\u0131 NS kay\u0131tlar\u0131n\u0131n TTL de\u011ferini de dikkate al\u0131n.<\/p>\n<h2><span id=\"Delegasyonu_dig_ile_dogrulayin_ve_hatalari_ayirin\">Delegasyonu dig ile do\u011frulay\u0131n ve hatalar\u0131 ay\u0131r\u0131n<\/span><\/h2>\n<h3><span id=\"Ust_yonlendirmeyi_ve_alt_yetkilileri_karsilastirin\">\u00dcst y\u00f6nlendirmeyi ve alt yetkilileri kar\u015f\u0131la\u015ft\u0131r\u0131n<\/span><\/h3>\n<p>\u00d6nce \u00fcst b\u00f6lgenin sorgular\u0131 yeni yetkililere y\u00f6nlendirdi\u011fini kontrol edin. Ubuntu terminalinde a\u015fa\u011f\u0131daki sorgular\u0131 ger\u00e7ek sunucu ve alan adlar\u0131n\u0131zla \u00e7al\u0131\u015ft\u0131r\u0131n. <code>+norecurse<\/code>, sunucunun ba\u015fka sunuculara ba\u015fvurmadan yan\u0131t vermesini ister; b\u00f6ylece do\u011frudan o sunucunun yay\u0131mlad\u0131\u011f\u0131 bilgiyi g\u00f6r\u00fcrs\u00fcn\u00fcz.<\/p>\n<figure class=\"aiw-figure\" data-aiw-visual-id=\"5921\" data-aiw-visual-key=\"e469817ca84eb7c51f77961eba02f5592daa2c33b645e09d18cf50dcaeeeccec\"><img decoding=\"async\" src=\"https:\/\/www.dchost.com\/blog\/wp-content\/uploads\/2026\/10\/dchost-flow-tr-365a71a410f327aa5adb.png\" alt=\"\u00dcst b\u00f6lgenin NS y\u00f6nlendirmesinden alt yetkili yan\u0131tlara, ard\u0131ndan iz s\u00fcrme ve \u00f6nbellek kar\u015f\u0131la\u015ft\u0131rmas\u0131na ilerleyen kontrol ak\u0131\u015f\u0131.\" width=\"840\" height=\"1110\" loading=\"lazy\" class=\"aiw-article-visual wp-image-5921\" srcset=\"https:\/\/www.dchost.com\/blog\/wp-content\/uploads\/2026\/10\/dchost-flow-tr-365a71a410f327aa5adb.png 840w, https:\/\/www.dchost.com\/blog\/wp-content\/uploads\/2026\/10\/dchost-flow-tr-365a71a410f327aa5adb-227x300.png 227w, https:\/\/www.dchost.com\/blog\/wp-content\/uploads\/2026\/10\/dchost-flow-tr-365a71a410f327aa5adb-775x1024.png 775w, https:\/\/www.dchost.com\/blog\/wp-content\/uploads\/2026\/10\/dchost-flow-tr-365a71a410f327aa5adb-768x1015.png 768w\" sizes=\"auto, (max-width: 840px) 100vw, 840px\" \/><figcaption>Ak\u0131\u015f \u015femas\u0131: Bu kontrol s\u0131ras\u0131, \u00fcst b\u00f6lgedeki y\u00f6nlendirmeyi, alt b\u00f6lgenin yetkili yan\u0131tlar\u0131n\u0131 ve \u00e7\u00f6z\u00fcmleyici \u00f6nbelle\u011fini ayr\u0131 ayr\u0131 incelemenizi sa\u011flar.<\/figcaption><\/figure>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">for ns in ns1.parent.example ns2.parent.example; do\n  dig @&quot;$ns&quot; dev.example.com A +norecurse\ndone<\/code><\/pre>\n<p>Bu \u00f6rnekte iki \u00fcst yetkilide de beklenen yan\u0131t <strong>referral<\/strong>, yani alt yetkililere y\u00f6nlendirmedir: <code>status: NOERROR<\/code>, bo\u015f <code>ANSWER<\/code> b\u00f6l\u00fcm\u00fc ve <code>AUTHORITY<\/code> b\u00f6l\u00fcm\u00fcnde iki alt NS kayd\u0131 g\u00f6r\u00fcn\u00fcr. Bu y\u00f6nlendirmede yetkili yan\u0131t\u0131 belirten <code>aa<\/code> bayra\u011f\u0131 beklenmez. Sunuculardan biri h\u00e2l\u00e2 eski A kayd\u0131n\u0131 veriyorsa \u00fcst hizmetin yetkilileri ayn\u0131 de\u011fi\u015fikli\u011fi hen\u00fcz yay\u0131mlam\u0131yor demektir. Panelde de\u011fi\u015fikliklerin yay\u0131mland\u0131\u011f\u0131n\u0131 kontrol edip iki sunucuyu yeniden sorgulay\u0131n.<\/p>\n<p>\u00dcst y\u00f6nlendirme do\u011fruysa s\u0131radaki kontrol, alt yetkililerin b\u00f6lgeyi ve uygulama kay\u0131tlar\u0131n\u0131 ayn\u0131 \u015fekilde sunmas\u0131d\u0131r. A\u015fa\u011f\u0131daki sorgular\u0131 yine Ubuntu terminalinde, ger\u00e7ek adlar\u0131n\u0131zla \u00e7al\u0131\u015ft\u0131r\u0131n.<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">for ns in ns1.child.example ns2.child.example; do\n  dig @&quot;$ns&quot; dev.example.com SOA +norecurse\n  dig @&quot;$ns&quot; dev.example.com NS +norecurse\n  dig @&quot;$ns&quot; dev.example.com A +norecurse\n  dig @&quot;$ns&quot; www.dev.example.com CNAME +norecurse\ndone<\/code><\/pre>\n<p>Alt sunucular\u0131n ilgili yan\u0131tlar\u0131nda <code>NOERROR<\/code> ve <code>aa<\/code> ile birlikte SOA, ayn\u0131 NS k\u00fcmesi ve \u00f6rnekteki A\/CNAME de\u011ferlerini g\u00f6rmelisiniz. SOA i\u00e7indeki <code>serial<\/code> b\u00f6lge s\u00fcr\u00fcm\u00fcn\u00fc belirtir. Sunucular aras\u0131nda s\u00fcr\u00fcm veya kay\u0131t fark\u0131 kal\u0131yorsa yeni sa\u011flay\u0131c\u0131n\u0131n panelindeki yay\u0131mlama durumunu kontrol edin; yay\u0131mlama tamamlan\u0131nca sorgular\u0131 tekrarlay\u0131n. SOA kayd\u0131ndaki ana sunucu alan\u0131 tek bir ad i\u00e7erir; iki NS hedefinin listelendi\u011fi yer NS kay\u0131tlar\u0131d\u0131r.<\/p>\n<h3><span id=\"Onbellegi_gercek_yayin_hatasindan_ayirin\">\u00d6nbelle\u011fi ger\u00e7ek yay\u0131n hatas\u0131ndan ay\u0131r\u0131n<\/span><\/h3>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">dig +trace dev.example.com A\ndig dev.example.com A<\/code><\/pre>\n<p>Bu iki komutu ayn\u0131 terminalde ger\u00e7ek alan ad\u0131n\u0131zla \u00e7al\u0131\u015ft\u0131r\u0131n. \u0130lk komut k\u00f6kten ba\u015flayarak yetki zincirini izler; \u00fcst b\u00f6lgeden alt NS sunucular\u0131na ge\u00e7ip beklenen A kayd\u0131na ula\u015fmal\u0131d\u0131r. \u0130kinci komut bilgisayar\u0131n\u0131z\u0131n kulland\u0131\u011f\u0131 <strong>\u00e7\u00f6z\u00fcmleyiciyi<\/strong>, yani sizin ad\u0131n\u0131za sorgu yapan DNS hizmetini kullan\u0131r. \u0130ki yan\u0131t\u0131 kar\u015f\u0131la\u015ft\u0131rmak, yetkililerin yay\u0131mlad\u0131\u011f\u0131 bilgiyle \u00f6nbellekteki bilgiyi ay\u0131rman\u0131z\u0131 sa\u011flar.<\/p>\n<p>Temsili <code>.example<\/code> sunucular\u0131 internette \u00e7al\u0131\u015fmaz. Ayr\u0131ca a\u011f\u0131n\u0131z d\u0131\u015f DNS sorgular\u0131n\u0131 engelliyorsa <code>+trace<\/code> kesilebilir; bu tek ba\u015f\u0131na delegasyon hatas\u0131 de\u011fildir. B\u00f6yle bir durumda sorguyu d\u0131\u015f DNS eri\u015fimine izin verilen ba\u015fka bir a\u011fdan tekrarlay\u0131n.<\/p>\n<ul>\n<li><strong>Eski IP:<\/strong> Do\u011frudan yetkililer beklenen adresi veriyorsa \u00e7\u00f6z\u00fcmleyici yan\u0131t\u0131ndaki TTL&#8217;yi, yani kalan \u00f6nbellek s\u00fcresini inceleyin. \u00d6nceki TTL dolana kadar bekleyip ayn\u0131 sorguyu tekrarlay\u0131n. Yaln\u0131zca \u00f6nbellek fark\u0131 nedeniyle kay\u0131tlar\u0131 yeniden de\u011fi\u015ftirmek gerekmez.<\/li>\n<li><strong>SERVFAIL:<\/strong> \u00c7\u00f6z\u00fcmleyici sorguyu ba\u015far\u0131yla tamamlayamam\u0131\u015ft\u0131r. \u00d6nce iki alt sunucuyu do\u011frudan sorgulay\u0131n. Biri <code>REFUSED<\/code> veriyorsa atanan NS ad\u0131n\u0131 ve b\u00f6lgenin yay\u0131mland\u0131\u011f\u0131n\u0131 kontrol edin. Yanl\u0131\u015f NS hedefi veya yay\u0131mlama sorunu bulursan\u0131z yaln\u0131zca o sorunu d\u00fczeltin; ard\u0131ndan hem do\u011frudan sorguyu hem \u00e7\u00f6z\u00fcmleyici sorgusunu yineleyin. Zaman a\u015f\u0131m\u0131nda sunucunun eri\u015filebilirli\u011fini sa\u011flay\u0131c\u0131yla inceleyin.<\/li>\n<li><strong>NXDOMAIN:<\/strong> Sorgulanan ad\u0131n bulunmad\u0131\u011f\u0131n\u0131 belirtir. Alt yetkili de ayn\u0131 yan\u0131t\u0131 veriyorsa yeni b\u00f6lgenin Records (kay\u0131tlar) ekran\u0131nda eksik veya iki kez uzat\u0131lm\u0131\u015f kay\u0131t ad\u0131n\u0131 d\u00fczeltip do\u011frudan sorguyu tekrarlay\u0131n. Yetkili do\u011fru yan\u0131t veriyorsa \u00e7\u00f6z\u00fcmleyicide eski olumsuz yan\u0131t tutuluyor olabilir; bunun \u00f6nbellek s\u00fcresi SOA bilgilerine ba\u011fl\u0131d\u0131r. Yetkili alt sunucudan gelen <code>NOERROR<\/code> ile bo\u015f yan\u0131t ise ad\u0131n de\u011fil, istenen kay\u0131t t\u00fcr\u00fcn\u00fcn yoklu\u011fu olabilir.<\/li>\n<\/ul>\n<h3><span id=\"Glue_ve_DNSSEC_gereken_durumlar\">Glue ve DNSSEC gereken durumlar<\/span><\/h3>\n<p>\u00d6rnekte NS adlar\u0131 devredilen b\u00f6lgenin d\u0131\u015f\u0131ndad\u0131r; bu delegasyon i\u00e7in \u00fcst b\u00f6lgeye <strong>glue<\/strong>, yani ad sunucusuna ilk eri\u015fimi sa\u011flayan yard\u0131mc\u0131 IP kayd\u0131 eklemek gerekmez. Hedef <code>ns1.dev.example.com<\/code> olsayd\u0131 ad sunucusunun adresini \u00f6\u011frenmek i\u00e7in yine ayn\u0131 sunucuya ula\u015fmak gerekirdi. Bu d\u00f6ng\u00fcy\u00fc k\u0131rmak i\u00e7in \u00fcst hizmette bu ad\u0131n glue A\/AAAA kayd\u0131, alt b\u00f6lgede de kar\u015f\u0131l\u0131k gelen adres kayd\u0131 bulunmal\u0131d\u0131r. B\u00f6yle bir kurulumda \u00f6nce \u00fcst DNS sa\u011flay\u0131c\u0131n\u0131z\u0131n glue kayd\u0131n\u0131 hangi ekrandan kabul etti\u011fini \u00f6\u011frenin.<\/p>\n<p><strong>DNSSEC<\/strong>, DNS yan\u0131tlar\u0131n\u0131n kayna\u011f\u0131n\u0131 ve b\u00fct\u00fcnl\u00fc\u011f\u00fcn\u00fc dijital imzalarla do\u011frulamay\u0131 sa\u011flayan mekanizmad\u0131r. Ana \u00f6rnekte alt b\u00f6lge imzas\u0131zd\u0131r; \u00fcst b\u00f6lgede bu alt b\u00f6lgeye ait DS, yani imza g\u00fcven ba\u011flant\u0131s\u0131 kayd\u0131 bulunmamal\u0131d\u0131r. \u00dcst b\u00f6lgenin kendisinin imzal\u0131 olmas\u0131, alt b\u00f6lgenin de mutlaka imzal\u0131 olmas\u0131n\u0131 gerektirmez.<\/p>\n<p>\u0130ki alt yetkili do\u011fru yan\u0131t verdi\u011fi h\u00e2lde DNSSEC do\u011frulamas\u0131 yapan \u00e7\u00f6z\u00fcmleyici SERVFAIL \u00fcretiyorsa \u00fcst yetkilide <code>dig @ns1.parent.example dev.example.com DS +norecurse<\/code> ile DS varl\u0131\u011f\u0131n\u0131 kontrol edin; komutta ger\u00e7ek sunucu ve alan ad\u0131n\u0131z\u0131 kullan\u0131n. Eski DS veya ge\u00e7ersiz alt b\u00f6lge imzalar\u0131 bu hataya yol a\u00e7abilir. DS&#8217;yi geli\u015fig\u00fczel silmek yerine mevcut DS de\u011ferini ve imzalama durumunu kaydedin, sa\u011flay\u0131c\u0131n\u0131n anahtar ge\u00e7i\u015fi ya da imzay\u0131 kapatma s\u0131ras\u0131n\u0131 izleyin. Geri d\u00f6n\u00fc\u015f\u00fcn de DS ile alt b\u00f6lgedeki anahtarlar\u0131n uyumunu korumas\u0131 gerekir. \u0130\u015flemden sonra DNSSEC do\u011frulamas\u0131 yapan \u00e7\u00f6z\u00fcmleyicide yeniden sorgulay\u0131n; beklenen kayd\u0131n SERVFAIL olmadan d\u00f6nmesi gerekir.<\/p>\n<h2><span id=\"Sik_Sorulan_Sorular\">S\u0131k Sorulan Sorular<\/span><\/h2>\n<h3><span id=\"Alt_alani_devretmek_icin_alan_adi_transferi_gerekir_mi\">Alt alan\u0131 devretmek i\u00e7in alan ad\u0131 transferi gerekir mi?<\/span><\/h3>\n<p>Hay\u0131r. Alan ad\u0131 transferi, alan ad\u0131n\u0131n kay\u0131tl\u0131 oldu\u011fu firmay\u0131 de\u011fi\u015ftirmektir; alt alan ad\u0131 DNS delegasyonu ise yaln\u0131zca belirli bir alt alan\u0131n ve onun alt\u0131ndaki adlar\u0131n DNS y\u00f6netimini ay\u0131r\u0131r. <code>example.com<\/code> ayn\u0131 kay\u0131t firmas\u0131nda ve mevcut DNS hizmetinde kalabilir. Alt ekibe alan ad\u0131 kay\u0131t hesab\u0131n\u0131z\u0131 veya transfer i\u00e7in kullan\u0131lan EPP yetkilendirme kodunu vermeniz gerekmez.<\/p>\n<h3><span id=\"NS_kayitlarini_ekleyince_SSL_sertifikasi_otomatik_gelir_mi\">NS kay\u0131tlar\u0131n\u0131 ekleyince SSL sertifikas\u0131 otomatik gelir mi?<\/span><\/h3>\n<p>Hay\u0131r. DNS delegasyonu, HTTPS ba\u011flant\u0131s\u0131n\u0131 g\u00fcvenli h\u00e2le getirmek i\u00e7in kullan\u0131lan TLS sertifikas\u0131n\u0131, yayg\u0131n ad\u0131yla SSL sertifikas\u0131n\u0131 olu\u015fturmaz. <code>dev.example.com<\/code> i\u00e7in sertifikay\u0131 web sunucusunda veya uygulamay\u0131 yay\u0131mlayan hizmette ayr\u0131ca ayarlaman\u0131z gerekir. Hizmet otomatik sertifika sa\u011fl\u0131yorsa bu, delegasyonun de\u011fil o hizmetin \u00f6zelli\u011fidir.<\/p>\n<p>Sertifikan\u0131n hangi adlar\u0131 kapsad\u0131\u011f\u0131n\u0131 da kontrol edin: <code>*.example.com<\/code> sertifikas\u0131 <code>dev.example.com<\/code> ad\u0131n\u0131 kapsar, ancak <code>www.dev.example.com<\/code> ad\u0131n\u0131 kapsamaz. DNS kay\u0131tlar\u0131 \u00fczerinden alan ad\u0131 do\u011frulamas\u0131 kullan\u0131yorsan\u0131z sertifika arac\u0131na yaln\u0131zca gerekli alt b\u00f6lgeye eri\u015fen kimlik bilgileri verin.<\/p>\n<h3><span id=\"Ana_alan_adinin_e-postasi_etkilenir_mi\">Ana alan ad\u0131n\u0131n e-postas\u0131 etkilenir mi?<\/span><\/h3>\n<p><code>example.com<\/code> i\u00e7in posta sunucular\u0131n\u0131 belirleyen MX kay\u0131tlar\u0131 ve ilgili di\u011fer kay\u0131tlar de\u011fi\u015fmiyorsa normalde etkilenmez. Ancak ana alan\u0131n MX hedefi <code>mail.dev.example.com<\/code> gibi devredilen dal\u0131n i\u00e7indeyse bu hedefin adres kay\u0131tlar\u0131 art\u0131k alt b\u00f6lgeden yan\u0131tlan\u0131r. Ta\u015f\u0131ma s\u0131ras\u0131nda eksik b\u0131rak\u0131lan bir kay\u0131t, ana alan\u0131n posta teslimini de bozabilir.<\/p>\n<p>Bu nedenle yaln\u0131zca kay\u0131tlar\u0131n bulundu\u011fu yere de\u011fil, hedeflerine de bak\u0131n. Ana alan\u0131n posta ayarlar\u0131 devredilen dala ba\u015fvuruyorsa \u00f6nceki b\u00f6l\u00fcmdeki do\u011frudan sorgu y\u00f6ntemini kullanarak ilgili hedeflerin A ve varsa AAAA kay\u0131tlar\u0131n\u0131 iki yeni yetkiliden sorgulay\u0131n; beklenen posta sunucusu adreslerini g\u00f6rmelisiniz. <code>kullanici&#64;dev.example.com<\/code> adresleri kullan\u0131lacaksa bu alt alan\u0131n posta kay\u0131tlar\u0131 da yeni alt b\u00f6lgede y\u00f6netilir.<\/p>\n<h3><span id=\"Alt_ekibin_yetkisini_yalnizca_bu_bolgeyle_nasil_sinirlarim\">Alt ekibin yetkisini yaln\u0131zca bu b\u00f6lgeyle nas\u0131l s\u0131n\u0131rlar\u0131m?<\/span><\/h3>\n<p>Yeni DNS hizmetinin kullan\u0131c\u0131 ve rol ayarlar\u0131nda ekibe yaln\u0131zca <code>dev.example.com<\/code> b\u00f6lgesi i\u00e7in kay\u0131t d\u00fczenleme izni verin; ana hesap parolas\u0131n\u0131 payla\u015fmay\u0131n. Otomasyonun DNS hizmetine ba\u011flanmas\u0131n\u0131 sa\u011flayan API eri\u015fim anahtarlar\u0131n\u0131 da ayn\u0131 b\u00f6lgeyle s\u0131n\u0131rland\u0131r\u0131n. Sa\u011flay\u0131c\u0131 b\u00f6lge baz\u0131nda yetki sunmuyorsa alt b\u00f6lge i\u00e7in ayr\u0131 bir hesap kullan\u0131n. <a href=\"https:\/\/www.dchost.com\/blog\/ajanslar-icin-dns-ve-alan-adi-erisimi-yonetimi\/\">DNS eri\u015fim yetkilerini s\u0131n\u0131rland\u0131rma<\/a> yakla\u015f\u0131m\u0131n\u0131 hem kullan\u0131c\u0131 hesaplar\u0131na hem otomasyon anahtarlar\u0131na uygulay\u0131n.<\/p>\n<p>Bu ekip, devredilen dal\u0131n kay\u0131tlar\u0131n\u0131 de\u011fi\u015ftirebilir ve DNS do\u011frulamas\u0131yla o dal i\u00e7in sertifika al\u0131nmas\u0131n\u0131 sa\u011flayabilir. Bu y\u00fczden verdi\u011finiz yetki, yaln\u0131zca site adresini de\u011fi\u015ftirmekle s\u0131n\u0131rl\u0131 de\u011fildir. \u00dcst b\u00f6lgedeki NS kay\u0131tlar\u0131n\u0131n kontrol\u00fcn\u00fc sizde tutun. Ekip veya hizmet de\u011fi\u015fti\u011finde <a href=\"https:\/\/www.dchost.com\/blog\/subdomain-takeover-ve-bosta-kalan-dns-kayitlari-alan-adi-guvenligi\/\">bo\u015fta kalan DNS kay\u0131tlar\u0131<\/a> b\u0131rakmamak i\u00e7in delegasyonun kald\u0131r\u0131lmas\u0131n\u0131 veya yeni yetkililere ta\u015f\u0131nmas\u0131n\u0131 da eri\u015fim kapatma plan\u0131na ekleyin.<\/p>\n<h2><span id=\"Devir_sonrasi_kontrol_listesi\">Devir sonras\u0131 kontrol listesi<\/span><\/h2>\n<p>Alt alan ad\u0131 DNS delegasyonunu yaln\u0131zca site a\u00e7\u0131ld\u0131\u011f\u0131 i\u00e7in tamamlanm\u0131\u015f saymay\u0131n. A\u015fa\u011f\u0131daki listeyle DNS yan\u0131tlar\u0131n\u0131, uygulaman\u0131n \u00e7al\u0131\u015fmas\u0131n\u0131 ve y\u00f6netim sorumlulu\u011funu birlikte kontrol edin. Sorgularda temsili adlar yerine kendi alan\u0131n\u0131z\u0131 ve sa\u011flay\u0131c\u0131n\u0131z\u0131n verdi\u011fi sunucu adlar\u0131n\u0131 kullan\u0131n.<\/p>\n<ul>\n<li><strong>\u0130ki alt yetkili de do\u011fru yan\u0131t veriyor:<\/strong> Ubuntu terminalinde \u00f6nceki b\u00f6l\u00fcmdeki do\u011frudan SOA, NS ve adres sorgular\u0131n\u0131 her iki sunucu i\u00e7in \u00e7al\u0131\u015ft\u0131r\u0131n. Yan\u0131tlarda yetkili yan\u0131t\u0131 belirten <code>aa<\/code> bayra\u011f\u0131n\u0131, ayn\u0131 NS k\u00fcmesini ve beklenen uygulama adreslerini g\u00f6rmelisiniz. \u00dcst b\u00f6lgenin iki yetkili sunucusu da ayn\u0131 alt NS hedeflerine y\u00f6nlendirmelidir; yaln\u0131zca bir sunucudan do\u011fru yan\u0131t almak yeterli de\u011fildir.<\/li>\n<li><strong>Uygulamaya ger\u00e7ek adlar\u0131yla eri\u015filiyor:<\/strong> Taray\u0131c\u0131da \u00f6rnekteki <code>dev.example.com<\/code> ve kullan\u0131l\u0131yorsa <code>www.dev.example.com<\/code> yerine kendi adreslerinizi HTTPS \u00fczerinden a\u00e7\u0131n. Beklenen sitenin geldi\u011fini, sertifikan\u0131n ziyaret etti\u011finiz ad\u0131 kapsad\u0131\u011f\u0131n\u0131 ve giri\u015f gibi temel bir i\u015flemin \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 kontrol edin. DNS do\u011fru \u00e7\u00f6z\u00fcld\u00fc\u011f\u00fc h\u00e2lde yanl\u0131\u015f site a\u00e7\u0131l\u0131yorsa NS kay\u0131tlar\u0131n\u0131 de\u011fi\u015ftirmek yerine web sunucusunun bu alan ad\u0131n\u0131 hangi siteyle e\u015fle\u015ftirdi\u011fini inceleyin.<\/li>\n<li><strong>DNSSEC durumu planla uyumlu:<\/strong> Bu imzas\u0131z \u00f6rnekte \u00fcst b\u00f6lgede <code>dev.example.com<\/code> i\u00e7in DS kayd\u0131 bulunmamal\u0131d\u0131r. \u0130mzal\u0131 bir kurulum kullan\u0131yorsan\u0131z DS kayd\u0131n\u0131n alt b\u00f6lgenin imzalama anahtarlar\u0131yla e\u015fle\u015fti\u011fini ve DNSSEC do\u011frulamas\u0131 yapan \u00e7\u00f6z\u00fcmleyicide sorgunun ba\u015far\u0131l\u0131 oldu\u011funu kontrol edin. Do\u011frudan yetkili sunucudan do\u011fru kay\u0131tlar\u0131 almak, tek ba\u015f\u0131na imza zincirinin sa\u011flam oldu\u011funu g\u00f6stermez.<\/li>\n<li><strong>Kay\u0131tlar\u0131n sorumlusu ve d\u00fczenleme yeri belli:<\/strong> Y\u00f6netim notunuza \u00fcst b\u00f6lgedeki yetki devri kay\u0131tlar\u0131ndan kimin, alt b\u00f6lgedeki uygulama ve do\u011frulama kay\u0131tlar\u0131ndan kimin sorumlu oldu\u011funu yaz\u0131n. Her kay\u0131t grubunun hangi DNS panelinde d\u00fczenlenece\u011fini de belirtin. Yeni DNS hizmetinin kullan\u0131c\u0131 ve eri\u015fim anahtar\u0131 listesini g\u00f6zden ge\u00e7irin; alt ekibin izinlerinin yaln\u0131zca devredilen b\u00f6lgeyle s\u0131n\u0131rl\u0131 oldu\u011funu kontrol edin.<\/li>\n<li><strong>Geri d\u00f6n\u00fc\u015f i\u00e7in gereken bilgiler eri\u015filebilir:<\/strong> Devir \u00f6ncesi kay\u0131t d\u00f6k\u00fcm\u00fcn\u00fc, eski TTL de\u011ferlerini ve de\u011fi\u015fiklik listesini saklay\u0131n. Geri d\u00f6n\u00fc\u015fte \u00fcst b\u00f6lgedeki NS kay\u0131tlar\u0131 kald\u0131r\u0131l\u0131rken hangi eski kay\u0131tlar\u0131n geri eklenece\u011fi a\u00e7\u0131k olsun. \u00d6nbellekte tutulan yetki devri kay\u0131tlar\u0131n\u0131n s\u00fcresi dolmadan yeni alt b\u00f6lgeyi silmeyin; geri d\u00f6n\u00fc\u015f boyunca hem eski kay\u0131tlar hem de yeni alt b\u00f6lge gerekli yan\u0131tlar\u0131 vermeye devam etsin.<\/li>\n<\/ul>\n<p>Bir sonraki ad\u0131m, izleme ve m\u00fcdahale sorumlular\u0131n\u0131 belirlemektir. \u0130ki alt yetkili sunucunun DNS yan\u0131tlar\u0131n\u0131 ve uygulaman\u0131n HTTPS eri\u015fimini kimin izleyece\u011fini, uyar\u0131lar\u0131n kime gidece\u011fini ve acil durumda \u00fcst b\u00f6lgedeki yetki devri NS kay\u0131tlar\u0131n\u0131 kimin de\u011fi\u015ftirebilece\u011fini kaydedin. B\u00f6ylece sonraki ekip veya sa\u011flay\u0131c\u0131 de\u011fi\u015fiminde hangi ayar\u0131n nerede yap\u0131laca\u011f\u0131 ve gerekti\u011finde kimin m\u00fcdahale edece\u011fi belli olur.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>Ana alan ad\u0131n\u0131z\u0131n DNS y\u00f6netimini de\u011fi\u015ftirmeden bir alt alan\u0131 ba\u015fka ekibe veya sa\u011flay\u0131c\u0131ya devredebilirsiniz. \u00d6rnek kurulum \u00fczerinden alt b\u00f6lgeyi haz\u0131rlamay\u0131, \u00fcst b\u00f6lgeye NS kay\u0131tlar\u0131n\u0131 eklemeyi ve devri dig ile do\u011frulamay\u0131 \u00f6\u011frenin.<\/p>\n","protected":false},"author":4,"featured_media":5915,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[32],"tags":[630,661,664,385,663,662],"class_list":["post-5923","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-alan-adi","tag-alan-adi","tag-alt-alan-adi","tag-dig","tag-dns","tag-dns-delegasyonu","tag-ns-kaydi"],"_links":{"self":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/5923","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\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/comments?post=5923"}],"version-history":[{"count":1,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/5923\/revisions"}],"predecessor-version":[{"id":5930,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/5923\/revisions\/5930"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/5915"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=5923"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=5923"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=5923"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}