{"id":4584,"date":"2026-02-06T13:38:43","date_gmt":"2026-02-06T10:38:43","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/ajanslar-ve-bayiler-icin-ozel-nameserver-kurulumu-ve-markali-dns-mimarisi\/"},"modified":"2026-02-06T13:38:43","modified_gmt":"2026-02-06T10:38:43","slug":"ajanslar-ve-bayiler-icin-ozel-nameserver-kurulumu-ve-markali-dns-mimarisi","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/ajanslar-ve-bayiler-icin-ozel-nameserver-kurulumu-ve-markali-dns-mimarisi\/","title":{"rendered":"Ajanslar ve Bayiler \u0130\u00e7in \u00d6zel Nameserver Kurulumu ve Markal\u0131 DNS Mimarisi"},"content":{"rendered":"<div class=\"dchost-blog-content-wrapper\"><p>Bir ajans veya bayi olarak onlarca, hatta y\u00fczlerce m\u00fc\u015fterinin domain ve hosting altyap\u0131s\u0131n\u0131 y\u00f6netirken en \u00e7ok can s\u0131kan konulardan biri, DNS taraf\u0131nda da\u011f\u0131n\u0131kl\u0131k ve kontrol eksikli\u011fidir. Her m\u00fc\u015fterinin alan ad\u0131 farkl\u0131 kay\u0131t firmas\u0131ndad\u0131r, kimi registrar DNS\u2019i, kimi hosting DNS\u2019i, kimi de \u00fc\u00e7\u00fcnc\u00fc parti bir DNS hizmeti kullan\u0131r. Bu yap\u0131 hem operasyonel y\u00fck\u00fc art\u0131r\u0131r hem de markan\u0131n g\u00f6r\u00fcn\u00fcrl\u00fc\u011f\u00fcn\u00fc zay\u0131flat\u0131r. Tam bu noktada devreye <strong>\u00f6zel nameserver (ns1\/ns2)<\/strong> ve <strong>markal\u0131 DNS mimarisi<\/strong> giriyor.<\/p>\n<p>Kendi alan ad\u0131n\u0131z alt\u0131nda <strong>ns1.sizinmarkaniz.com<\/strong> ve <strong>ns2.sizinmarkaniz.com<\/strong> gibi isim sunucular\u0131 kullanmak, hem m\u00fc\u015fteriye daha kurumsal bir deneyim sunman\u0131z\u0131 hem de DNS taraf\u0131nda tam kontrol sahibi olman\u0131z\u0131 sa\u011flar. Ajans ya da bayi olarak DCHost altyap\u0131s\u0131 \u00fczerinde reseller, VPS ya da <a href=\"https:\/\/www.dchost.com\/tr\/fiziksel-sunucu\">dedicated sunucu<\/a> y\u00f6netiyorsan\u0131z; markal\u0131 DNS mimarisiyle, teknik yap\u0131y\u0131 merkezile\u015ftirebilir, SSL, e-posta ve y\u00f6nlendirme gibi i\u015flemleri \u00e7ok daha g\u00fcvenli ve \u00f6ng\u00f6r\u00fclebilir hale getirebilirsiniz.<\/p>\n<p>Bu yaz\u0131da, ajans ve bayilerin s\u0131k kulland\u0131\u011f\u0131 senaryolara odaklanarak <strong>\u00f6zel nameserver kurulumu<\/strong>nu u\u00e7tan uca anlataca\u011f\u0131z: Alan ad\u0131 taraf\u0131nda glue record tan\u0131mlamak, sunucu \u00fczerinde DNS servisini markal\u0131 \u015fekilde yap\u0131land\u0131rmak, m\u00fc\u015fteri domain\u2019lerini yeni nameserver\u2019lara ge\u00e7irmek ve bunu \u00f6l\u00e7eklenebilir, g\u00fcvenli bir DNS mimarisine d\u00f6n\u00fc\u015ft\u00fcrmek. Ayr\u0131ca DCHost altyap\u0131s\u0131 \u00fczerinde kullanabilece\u011finiz pratik mimari \u00f6rneklerini de payla\u015faca\u011f\u0131z.<\/p>\n<div id=\"toc_container\" class=\"toc_transparent no_bullets\"><p class=\"toc_title\">\u0130&ccedil;indekiler<\/p><ul class=\"toc_list\"><li><a href=\"#Neden_Ajanslar_ve_Bayiler_Icin_Ozel_Nameserver_Sart\"><span class=\"toc_number toc_depth_1\">1<\/span> Neden Ajanslar ve Bayiler \u0130\u00e7in \u00d6zel Nameserver \u015eart?<\/a><\/li><li><a href=\"#Markali_DNS_Mimarisi_Nedir\"><span class=\"toc_number toc_depth_1\">2<\/span> Markal\u0131 DNS Mimarisi Nedir?<\/a><ul><li><a href=\"#Temel_bilesenler\"><span class=\"toc_number toc_depth_2\">2.1<\/span> Temel bile\u015fenler<\/a><\/li><\/ul><\/li><li><a href=\"#Ajanslarin_Kullandigi_Yaygin_Senaryolar\"><span class=\"toc_number toc_depth_1\">3<\/span> Ajanslar\u0131n Kulland\u0131\u011f\u0131 Yayg\u0131n Senaryolar<\/a><\/li><li><a href=\"#Ozel_Nameserver_Kurulumu_Icin_On_Gereksinimler\"><span class=\"toc_number toc_depth_1\">4<\/span> \u00d6zel Nameserver Kurulumu \u0130\u00e7in \u00d6n Gereksinimler<\/a><\/li><li><a href=\"#Adim_Adim_Ozel_Nameserver_ns1ns2_Kurulumu\"><span class=\"toc_number toc_depth_1\">5<\/span> Ad\u0131m Ad\u0131m \u00d6zel Nameserver (ns1\/ns2) Kurulumu<\/a><ul><li><a href=\"#1_Alan_adi_tarafinda_ns1ns2_glue_record_tanimlama\"><span class=\"toc_number toc_depth_2\">5.1<\/span> 1. Alan ad\u0131 taraf\u0131nda ns1\/ns2 glue record tan\u0131mlama<\/a><\/li><li><a href=\"#2_DCHost_sunucunuzda_DNS_servisinin_ns1ns2_ile_eslestirilmesi\"><span class=\"toc_number toc_depth_2\">5.2<\/span> 2. DCHost sunucunuzda DNS servisinin ns1\/ns2 ile e\u015fle\u015ftirilmesi<\/a><ul><li><a href=\"#21_cPanelWHM_kullanan_ajanslar\"><span class=\"toc_number toc_depth_3\">5.2.1<\/span> 2.1. cPanel\/WHM kullanan ajanslar<\/a><\/li><li><a href=\"#22_DirectAdmin_kullanan_ajanslar\"><span class=\"toc_number toc_depth_3\">5.2.2<\/span> 2.2. DirectAdmin kullanan ajanslar<\/a><\/li><li><a href=\"#23_Elle_yonetilen_BINDPowerDNS_kullanan_ajanslar\"><span class=\"toc_number toc_depth_3\">5.2.3<\/span> 2.3. Elle y\u00f6netilen BIND\/PowerDNS kullanan ajanslar<\/a><\/li><\/ul><\/li><li><a href=\"#3_Musteri_domainlerini_yeni_nameserverlara_gecirmek\"><span class=\"toc_number toc_depth_2\">5.3<\/span> 3. M\u00fc\u015fteri domain\u2019lerini yeni nameserver\u2019lara ge\u00e7irmek<\/a><\/li><li><a href=\"#4_Test_yayilim_ve_izleme\"><span class=\"toc_number toc_depth_2\">5.4<\/span> 4. Test, yay\u0131l\u0131m ve izleme<\/a><\/li><\/ul><\/li><li><a href=\"#Markali_DNS_Icin_Ileri_Seviye_Tasarim_Secenekleri\"><span class=\"toc_number toc_depth_1\">6<\/span> Markal\u0131 DNS \u0130\u00e7in \u0130leri Seviye Tasar\u0131m Se\u00e7enekleri<\/a><ul><li><a href=\"#Ayri_DNS-only_VPSler_ile_yedekli_mimari\"><span class=\"toc_number toc_depth_2\">6.1<\/span> Ayr\u0131 DNS-only VPS\u2019ler ile yedekli mimari<\/a><\/li><li><a href=\"#TTL_stratejisi_ile_esnek_ama_kontrollu_DNS\"><span class=\"toc_number toc_depth_2\">6.2<\/span> TTL stratejisi ile esnek ama kontroll\u00fc DNS<\/a><\/li><li><a href=\"#Coklu_saglayici_DNS_ve_Anycast_secenekleri\"><span class=\"toc_number toc_depth_2\">6.3<\/span> \u00c7oklu sa\u011flay\u0131c\u0131 DNS ve Anycast se\u00e7enekleri<\/a><\/li><\/ul><\/li><li><a href=\"#Ajanslar_Icin_Operasyonel_En_Iyi_Uygulamalar\"><span class=\"toc_number toc_depth_1\">7<\/span> Ajanslar \u0130\u00e7in Operasyonel En \u0130yi Uygulamalar<\/a><ul><li><a href=\"#Mimariyi_dokumante_edin_ve_standartlastirin\"><span class=\"toc_number toc_depth_2\">7.1<\/span> Mimariyi dok\u00fcmante edin ve standartla\u015ft\u0131r\u0131n<\/a><\/li><li><a href=\"#Rollerinizi_ve_erisimlerinizi_ayirin\"><span class=\"toc_number toc_depth_2\">7.2<\/span> Rollerinizi ve eri\u015fimlerinizi ay\u0131r\u0131n<\/a><\/li><li><a href=\"#Sablon_template_kullanin\"><span class=\"toc_number toc_depth_2\">7.3<\/span> \u015eablon (template) kullan\u0131n<\/a><\/li><\/ul><\/li><li><a href=\"#DCHost_Uzerinde_Ornek_Markali_DNS_Mimarileri\"><span class=\"toc_number toc_depth_1\">8<\/span> DCHost \u00dczerinde \u00d6rnek Markal\u0131 DNS Mimarileri<\/a><ul><li><a href=\"#Senaryo_1_cPanel_reseller_ozel_nameserver\"><span class=\"toc_number toc_depth_2\">8.1<\/span> Senaryo 1: cPanel reseller + \u00f6zel nameserver<\/a><\/li><li><a href=\"#Senaryo_2_VPS_cPanelDirectAdmin_DNS-only_VPSler\"><span class=\"toc_number toc_depth_2\">8.2<\/span> Senaryo 2: VPS + cPanel\/DirectAdmin + DNS-only VPS\u2019ler<\/a><\/li><li><a href=\"#Senaryo_3_Multi-tenant_e-posta_ve_DNS_yonetimi\"><span class=\"toc_number toc_depth_2\">8.3<\/span> Senaryo 3: Multi-tenant e-posta ve DNS y\u00f6netimi<\/a><\/li><\/ul><\/li><li><a href=\"#Sonuc_Markali_DNS_Ajans_Operasyonunun_Gizli_Iskeleti\"><span class=\"toc_number toc_depth_1\">9<\/span> Sonu\u00e7: Markal\u0131 DNS, Ajans Operasyonunun Gizli \u0130skeleti<\/a><\/li><\/ul><\/div>\n<h2><span id=\"Neden_Ajanslar_ve_Bayiler_Icin_Ozel_Nameserver_Sart\">Neden Ajanslar ve Bayiler \u0130\u00e7in \u00d6zel Nameserver \u015eart?<\/span><\/h2>\n<p>Ajans ve bayi taraf\u0131nda konu\u015ftu\u011fumuz neredeyse t\u00fcm ekiplerde DNS ile ilgili ya\u015fanan sorunlar\u0131n b\u00fcy\u00fck b\u00f6l\u00fcm\u00fc, <strong>par\u00e7al\u0131 sorumluluk<\/strong>tan kaynaklan\u0131yor. Domain ba\u015fka yerde, hosting ba\u015fka yerde, DNS kayd\u0131yla ilgili k\u00fc\u00e7\u00fck bir de\u011fi\u015fiklik i\u00e7in bile \u00fc\u00e7 farkl\u0131 paneli dola\u015fman\u0131z gerekiyor. \u00d6zel nameserver kullanmak bu tabloyu \u00f6nemli \u00f6l\u00e7\u00fcde sadele\u015ftiriyor.<\/p>\n<p>\u00d6zel nameserver (ns1\/ns2) ile:<\/p>\n<ul>\n<li><strong>Markal\u0131 deneyim<\/strong> sunars\u0131n\u0131z: M\u00fc\u015fterinin domain\u2019i hangi firmadan al\u0131nm\u0131\u015f olursa olsun, DNS taraf\u0131nda hep sizin markan\u0131z g\u00f6r\u00fcn\u00fcr.<\/li>\n<li><strong>Merkezi y\u00f6netim<\/strong> sa\u011flars\u0131n\u0131z: T\u00fcm DNS kay\u0131tlar\u0131, sizin belirledi\u011finiz bir veya birka\u00e7 panelde toplan\u0131r.<\/li>\n<li><strong>Operasyonel maliyeti d\u00fc\u015f\u00fcr\u00fcrs\u00fcn\u00fcz<\/strong>: DNS taraf\u0131nda yap\u0131lacak de\u011fi\u015fiklikler i\u00e7in farkl\u0131 aray\u00fczlerle u\u011fra\u015fmak zorunda kalmazs\u0131n\u0131z.<\/li>\n<li><strong>Gizlilik ve kurumsall\u0131k<\/strong> elde edersiniz: Son m\u00fc\u015fteri, altyap\u0131n\u0131n hangi hosting firmas\u0131nda oldu\u011funu de\u011fil, sizin markan\u0131z\u0131 g\u00f6r\u00fcr.<\/li>\n<li><strong>G\u00fcvenlik politikalar\u0131n\u0131 tek noktadan<\/strong> uygulars\u0131n\u0131z: TTL, DNSSEC, SPF\/DKIM\/DMARC ve CAA gibi g\u00fcvenlik odakl\u0131 kay\u0131tlar\u0131 t\u00fcm portf\u00f6ye standartla\u015ft\u0131rabilirsiniz.<\/li>\n<\/ul>\n<p>DNS taraf\u0131ndaki hatalar\u0131n proje ve gelir \u00fczerindeki etkilerini detayl\u0131ca anlatt\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/en-sik-yapilan-dns-hatalari-web-sitesi-ve-e-postayi-ucurmadan-once-kontrol-etmeniz-gereken-10-kayit\/\">s\u0131k yap\u0131lan DNS hatalar\u0131 rehberi<\/a>nde de g\u00f6rd\u00fc\u011f\u00fcm\u00fcz gibi, k\u00fc\u00e7\u00fck bir TXT ya da MX hatas\u0131 bile t\u00fcm e-posta trafi\u011fini kilitleyebiliyor. \u00d6zel nameserver, bu hatalar\u0131 azaltmak i\u00e7in g\u00fc\u00e7l\u00fc bir temel sunuyor.<\/p>\n<h2><span id=\"Markali_DNS_Mimarisi_Nedir\">Markal\u0131 DNS Mimarisi Nedir?<\/span><\/h2>\n<p><strong>Markal\u0131 DNS mimarisi<\/strong>, basit\u00e7e s\u00f6ylemek gerekirse DNS\u2019e dair t\u00fcm u\u00e7lar\u0131n sizin alan ad\u0131n\u0131z alt\u0131nda topland\u0131\u011f\u0131 bir yap\u0131d\u0131r. Sadece ns1\/ns2 de\u011fil; SPF, DKIM, DMARC, MTA-STS, TLS-RPT, CAA gibi kay\u0131tlar\u0131n da tutarl\u0131 bir \u015fekilde y\u00f6netildi\u011fi, m\u00fcmk\u00fcnse birden fazla sunucuya yay\u0131lm\u0131\u015f bir DNS altyap\u0131s\u0131ndan bahsediyoruz.<\/p>\n<h3><span id=\"Temel_bilesenler\">Temel bile\u015fenler<\/span><\/h3>\n<ul>\n<li><strong>Nameserver hostname\u2019leri<\/strong>: ns1.sizinmarkaniz.com, ns2.sizinmarkaniz.com gibi FQDN\u2019ler.<\/li>\n<li><strong>Glue record\u2019lar<\/strong>: <a href=\"https:\/\/www.dchost.com\/tr\/alan-adi\/kaydet\">alan ad\u0131 kay\u0131t<\/a> operat\u00f6r\u00fc (registrar) taraf\u0131nda ns1\/ns2 i\u00e7in IP adreslerinin tan\u0131mlanmas\u0131.<\/li>\n<li><strong>DNS sunucusu<\/strong>: BIND, PowerDNS, cPanel\/DirectAdmin DNS servisi, DNS-only sunucular vb.<\/li>\n<li><strong>DNS y\u00f6netim paneli<\/strong>: cPanel, DirectAdmin, Plesk veya DCHost \u00fczerinde y\u00f6netti\u011finiz \u00f6zel DNS paneli.<\/li>\n<li><strong>TTL stratejisi<\/strong>: A, MX, CNAME, TXT gibi kay\u0131tlar\u0131n ya\u015fam s\u00fcrelerinin (TTL) ak\u0131ll\u0131ca belirlenmesi.<\/li>\n<li><strong>Yedeklilik<\/strong>: En az iki farkl\u0131 nameserver ve tercihen farkl\u0131 sunucu ya da a\u011f segmentleri.<\/li>\n<\/ul>\n<p>Glue record kavram\u0131na ve temel \u00f6zel ad sunucusu mant\u0131\u011f\u0131na daha derin girmek isterseniz, <a href=\"https:\/\/www.dchost.com\/blog\/ozel-ad-sunucusu-ve-glue-record-nasil-kurulur-kendi-dnsine-adim-adim-yolculuk\/\">\u00f6zel ad sunucusu ve glue record kurulumunu ad\u0131m ad\u0131m anlatt\u0131\u011f\u0131m\u0131z rehbere<\/a> mutlaka g\u00f6z at\u0131n. Bu yaz\u0131da ise perspektifi ajans ve bayi \u00f6l\u00e7e\u011fine, yani \u00e7oklu m\u00fc\u015fteri y\u00f6netimi ve markal\u0131 DNS mimarisine geni\u015fletiyoruz.<\/p>\n<h2><span id=\"Ajanslarin_Kullandigi_Yaygin_Senaryolar\">Ajanslar\u0131n Kulland\u0131\u011f\u0131 Yayg\u0131n Senaryolar<\/span><\/h2>\n<p>DCHost taraf\u0131nda birlikte \u00e7al\u0131\u015ft\u0131\u011f\u0131m\u0131z ajans ve bayilerin pratikte en s\u0131k kulland\u0131\u011f\u0131 \u00fc\u00e7 temel DNS senaryosu var:<\/p>\n<ol>\n<li><strong>Reseller hosting + \u00f6zel nameserver<\/strong>: Ajans, DCHost \u00fczerinde bir cPanel reseller paketi kullan\u0131r; ns1\/ns2 i\u00e7in IP\u2019ler bu reseller sunucusundan al\u0131n\u0131r ve t\u00fcm m\u00fc\u015fteriler ayn\u0131 DNS servisi \u00fczerinden y\u00f6netilir.<\/li>\n<li><strong>VPS\/dedicated + panel (cPanel\/DirectAdmin) + \u00f6zel nameserver<\/strong>: Ajans, DCHost\u2019ta kendi VPS veya dedicated sunucusunda panel \u00e7al\u0131\u015ft\u0131r\u0131r; DNS servisi de ayn\u0131 sunucu veya ek DNS-only sunucular \u00fczerinde ko\u015fturulur.<\/li>\n<li><strong>Ayr\u0131 DNS k\u00fcmesi + web sunucular\u0131<\/strong>: Ajans DNS i\u015fini tamamen ayr\u0131 bir DCHost VPS \u00e7ifti \u00fczerinde y\u00fcr\u00fct\u00fcr; web ve e-posta sunucular\u0131 farkl\u0131 makinelerde olabilir. Bu model, y\u00fcksek eri\u015filebilirlik ve karma\u015f\u0131k projeler i\u00e7in idealdir.<\/li>\n<\/ol>\n<p>Hangi senaryoyu se\u00e7erseniz se\u00e7in, temel s\u00fcre\u00e7 ayn\u0131d\u0131r: \u00d6nce alan ad\u0131 taraf\u0131nda ns1\/ns2 i\u00e7in glue record tan\u0131m\u0131, sonra DNS sunucusunda bu hostnamelerin IP\u2019lere ba\u011flanmas\u0131 ve son olarak da m\u00fc\u015fteri domain\u2019lerinin yeni nameserver\u2019lara ge\u00e7irilmesi.<\/p>\n<h2><span id=\"Ozel_Nameserver_Kurulumu_Icin_On_Gereksinimler\">\u00d6zel Nameserver Kurulumu \u0130\u00e7in \u00d6n Gereksinimler<\/span><\/h2>\n<p>Sa\u011flam bir ba\u015flang\u0131\u00e7 i\u00e7in a\u015fa\u011f\u0131daki \u00f6n gereksinimlere sahip olman\u0131z \u00f6nemli:<\/p>\n<ul>\n<li><strong>Marka alan ad\u0131n\u0131z<\/strong>: \u00d6rne\u011fin ajansiniz.com. T\u00fcm ns1\/ns2 vb. bu domain alt\u0131nda olacak.<\/li>\n<li><strong>En az bir, tercihen iki IP adresi<\/strong>: ns1 ve ns2 i\u00e7in ayr\u0131 IP\u2019ler kullanmak hem iyi bir pratik hem de baz\u0131 TLD\u2019ler i\u00e7in fiili gereklilik.<\/li>\n<li><strong>DNS sunucusu\/panel eri\u015fimi<\/strong>: DCHost reseller hesab\u0131n\u0131zda WHM\/cPanel, kendi VPS\u2019inizde cPanel\/DirectAdmin veya elle y\u00f6netilen BIND\/PowerDNS.<\/li>\n<li><strong>Alan ad\u0131n\u0131 y\u00f6netti\u011finiz registrar paneline eri\u015fim<\/strong>: Glue record\/child nameserver tan\u0131mlar\u0131 burada yap\u0131lacak.<\/li>\n<li><strong>Temel DNS kay\u0131t tipleri bilgisi<\/strong>: A, AAAA, CNAME, MX, TXT, NS; \u00f6zetini isterseniz <a href=\"https:\/\/www.dchost.com\/blog\/dns-kayitlari-nedir-a-aaaa-cname-mx-txt-ve-srv-rehberi\/\">DNS kay\u0131tlar\u0131 rehberi<\/a>ni inceleyebilirsiniz.<\/li>\n<\/ul>\n<h2><span id=\"Adim_Adim_Ozel_Nameserver_ns1ns2_Kurulumu\">Ad\u0131m Ad\u0131m \u00d6zel Nameserver (ns1\/ns2) Kurulumu<\/span><\/h2>\n<h3><span id=\"1_Alan_adi_tarafinda_ns1ns2_glue_record_tanimlama\">1. Alan ad\u0131 taraf\u0131nda ns1\/ns2 glue record tan\u0131mlama<\/span><\/h3>\n<p>\u0130lk katman, <strong>registrar<\/strong> taraf\u0131d\u0131r. Burada yapaca\u011f\u0131n\u0131z i\u015flem, alan ad\u0131n\u0131z i\u00e7in child nameserver (host) kay\u0131tlar\u0131 olu\u015fturmakt\u0131r. \u00d6rnek senaryo \u00fczerinden gidelim:<\/p>\n<ul>\n<li>Alan ad\u0131n\u0131z: <strong>ajansiniz.com<\/strong><\/li>\n<li>DNS i\u00e7in kullanaca\u011f\u0131n\u0131z IP\u2019ler: 203.0.113.10 (ns1), 203.0.113.11 (ns2)<\/li>\n<\/ul>\n<p>Registrar panelinizde genellikle \u015fu isimlerle g\u00f6r\u00fcnen bir men\u00fc olur:<\/p>\n<ul>\n<li>\u201cChild nameserver\u201d, \u201cHost kay\u0131tlar\u0131\u201d, \u201cGlue records\u201d, \u201c\u00d6zel ad sunucusu\u201d vb.<\/li>\n<\/ul>\n<p>Burada a\u015fa\u011f\u0131daki kay\u0131tlar\u0131 eklemeniz gerekir:<\/p>\n<ul>\n<li><strong>ns1.ajansiniz.com \u2192 203.0.113.10<\/strong><\/li>\n<li><strong>ns2.ajansiniz.com \u2192 203.0.113.11<\/strong><\/li>\n<\/ul>\n<p>Bu ad\u0131m, \u201cns1.ajansiniz.com diye bir hostname var ve \u015furadaki IP\u2019ye kar\u015f\u0131l\u0131k geliyor\u201d bilgisini <strong>k\u00f6k DNS zincirine<\/strong> tan\u0131t\u0131r. Bu olmazsa, alan ad\u0131 i\u00e7in ns1\/ns2\u2019yi se\u00e7seniz bile resolver\u2019lar bu isim sunucular\u0131n IP\u2019sini bulamaz.<\/p>\n<p>Farkl\u0131 TLD\u2019lerde (\u00f6zellikle .tr alan adlar\u0131nda) aray\u00fczler de\u011fi\u015febildi\u011fi i\u00e7in, glue record\u2019u nas\u0131l tan\u0131mlayaca\u011f\u0131n\u0131z\u0131 ad\u0131m ad\u0131m g\u00f6rmek isterseniz <a href=\"https:\/\/www.dchost.com\/blog\/ozel-ad-sunucusu-ve-glue-record-nasil-kurulur-kendi-dnsine-adim-adim-yolculuk\/\">\u00f6zel ad sunucusu ve glue record rehberimiz<\/a>den yararlanabilirsiniz.<\/p>\n<h3><span id=\"2_DCHost_sunucunuzda_DNS_servisinin_ns1ns2_ile_eslestirilmesi\">2. DCHost sunucunuzda DNS servisinin ns1\/ns2 ile e\u015fle\u015ftirilmesi<\/span><\/h3>\n<p>Glue record\u2019lar, \u201cbu hostname\u2019lerin IP\u2019si budur\u201d bilgisini d\u00fcnyaya duyurur. Ancak sunucu taraf\u0131nda da \u201cben bu hostname ile an\u0131lan DNS sunucusuyum\u201d demeniz gerekir. Bu a\u015fama kulland\u0131\u011f\u0131n\u0131z panele g\u00f6re k\u00fc\u00e7\u00fck farklarla ilerler.<\/p>\n<h4><span id=\"21_cPanelWHM_kullanan_ajanslar\">2.1. cPanel\/WHM kullanan ajanslar<\/span><\/h4>\n<ol>\n<li>WHM\u2019ye root ya da reseller yetkisiyle giri\u015f yap\u0131n.<\/li>\n<li><strong>Basic WebHost Manager Setup<\/strong> men\u00fcs\u00fcne girin.<\/li>\n<li>\u201cNameservers\u201d b\u00f6l\u00fcm\u00fcnde a\u015fa\u011f\u0131daki hostnameleri tan\u0131mlay\u0131n:<br \/>\n    ns1.ajansiniz.com<br \/>\n    ns2.ajansiniz.com\n  <\/li>\n<li>Her hostname\u2019in yan\u0131nda bir IP adresi alan\u0131 g\u00f6receksiniz. Glue record\u2019larda kulland\u0131\u011f\u0131n\u0131z IP\u2019leri buraya girip \u201cAssign IP Address\u201d deyin.<\/li>\n<li>\u0130\u015flem tamamland\u0131\u011f\u0131nda WHM, gerekirse ajansiniz.com\u2019un zone dosyas\u0131na da ilgili A kay\u0131tlar\u0131n\u0131 ekler.<\/li>\n<\/ol>\n<p>Bu noktadan sonra cPanel \u00fczerinden yeni olu\u015fturaca\u011f\u0131n\u0131z hosting hesaplar\u0131n\u0131n DNS zone\u2019lar\u0131, otomatik olarak ns1.ajansiniz.com ve ns2.ajansiniz.com\u2019u NS kayd\u0131 olarak i\u00e7erecektir.<\/p>\n<h4><span id=\"22_DirectAdmin_kullanan_ajanslar\">2.2. DirectAdmin kullanan ajanslar<\/span><\/h4>\n<ol>\n<li>DirectAdmin\u2019e admin hesab\u0131yla giri\u015f yap\u0131n.<\/li>\n<li><strong>Administrator Settings<\/strong> veya \u201cReseller Level \u2192 Nameservers\u201d men\u00fcs\u00fcne gidin (kurulumunuza g\u00f6re de\u011fi\u015febilir).<\/li>\n<li>Varsay\u0131lan nameserver alanlar\u0131na ns1.ajansiniz.com ve ns2.ajansiniz.com de\u011ferlerini girin.<\/li>\n<li>Gerekirse ajansiniz.com zone dosyas\u0131nda \u015fu A kay\u0131tlar\u0131n\u0131 manuel ekleyin:<br \/>\n    ns1  IN  A  203.0.113.10<br \/>\n    ns2  IN  A  203.0.113.11\n  <\/li>\n<\/ol>\n<p>DirectAdmin ile cPanel\u2019in DNS yakla\u015f\u0131mlar\u0131n\u0131 genel hosting ba\u011flam\u0131nda detayl\u0131 kar\u015f\u0131la\u015ft\u0131rd\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/cpanel-mi-directadmin-mi-plesk-mi-wordpress-ve-php-siteler-icin-dogru-paneli-secmek\/\">panel se\u00e7imi rehberine<\/a> de g\u00f6z atabilirsiniz.<\/p>\n<h4><span id=\"23_Elle_yonetilen_BINDPowerDNS_kullanan_ajanslar\">2.3. Elle y\u00f6netilen BIND\/PowerDNS kullanan ajanslar<\/span><\/h4>\n<p>E\u011fer DCHost \u00fczerinde panel kullanmak yerine do\u011frudan BIND veya PowerDNS y\u00f6netiyorsan\u0131z, yapman\u0131z gerekenler \u00f6zetle:<\/p>\n<ul>\n<li>ajansiniz.com zone dosyas\u0131na ns1 ve ns2 i\u00e7in A kay\u0131tlar\u0131n\u0131 eklemek,<\/li>\n<li>Her m\u00fc\u015fteri domain\u2019inin zone dosyas\u0131nda NS kay\u0131tlar\u0131n\u0131 ns1\/ns2\u2019ye g\u00fcncellemek,<\/li>\n<li>named.conf veya ilgili konfig\u00fcrasyonda bu zone\u2019lar\u0131 authoritative olarak tan\u0131mlamak.<\/li>\n<\/ul>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">; ajansiniz.com zone \u00f6rne\u011fi\n@   IN  SOA  ns1.ajansiniz.com. dns.ajansiniz.com. (\n        2026020601 ; serial\n        3600       ; refresh\n        900        ; retry\n        604800     ; expire\n        86400 )    ; minimum\n\n    IN  NS   ns1.ajansiniz.com.\n    IN  NS   ns2.ajansiniz.com.\n\nns1 IN  A    203.0.113.10\nns2 IN  A    203.0.113.11\n<\/code><\/pre>\n<h3><span id=\"3_Musteri_domainlerini_yeni_nameserverlara_gecirmek\">3. M\u00fc\u015fteri domain\u2019lerini yeni nameserver\u2019lara ge\u00e7irmek<\/span><\/h3>\n<p>Art\u0131k ns1\/ns2 altyap\u0131s\u0131 haz\u0131r. \u015eimdi s\u0131rada m\u00fc\u015fterilerin alan adlar\u0131n\u0131 bu nameserver\u2019lara ta\u015f\u0131mak var. Bu ad\u0131m\u0131 <strong>kademeli<\/strong> yapmak, olas\u0131 hatalarda riskinizi azalt\u0131r.<\/p>\n<ol>\n<li>\u00d6nce d\u00fc\u015f\u00fck kritiklikte 1\u20132 test domain\u2019i se\u00e7in.<\/li>\n<li>Se\u00e7ti\u011finiz domain\u2019lerin DNS kay\u0131tlar\u0131n\u0131 (\u00f6zellikle MX, SPF, WWW A kayd\u0131, kritik CNAME\u2019ler) yeni panelinizde birebir olu\u015fturun.<\/li>\n<li>Test domain\u2019in registrar panelinde nameserver\u2019lar\u0131 \u015fu \u015fekilde g\u00fcncelleyin:<br \/>\n    ns1.ajansiniz.com<br \/>\n    ns2.ajansiniz.com\n  <\/li>\n<li>DNS yay\u0131l\u0131m\u0131n\u0131 ve sitenin\/e-postan\u0131n sa\u011fl\u0131\u011f\u0131n\u0131 24 saat izleyin.<\/li>\n<li>Her \u015fey yolundaysa di\u011fer domain\u2019leri parti parti ta\u015f\u0131y\u0131n.<\/li>\n<\/ol>\n<p>DNS ge\u00e7i\u015flerinde kesintiyi minimize etmek i\u00e7in TTL ayarlar\u0131n\u0131 nas\u0131l optimize edebilece\u011finizi <a href=\"https:\/\/www.dchost.com\/blog\/zero-downtime-tasima-icin-ttl-stratejileri-dns-yayilimini-gercekten-nasil-hizlandirirsin\/\">zero-downtime DNS ta\u015f\u0131ma ve TTL stratejileri rehberimizde<\/a> detayl\u0131ca anlatt\u0131k. K\u0131saca: Ge\u00e7i\u015ften birka\u00e7 g\u00fcn \u00f6nce TTL\u2019leri d\u00fc\u015f\u00fcrmek, de\u011fi\u015fikliklerin daha h\u0131zl\u0131 yay\u0131lmas\u0131n\u0131 sa\u011flar.<\/p>\n<h3><span id=\"4_Test_yayilim_ve_izleme\">4. Test, yay\u0131l\u0131m ve izleme<\/span><\/h3>\n<p>Nameserver de\u011fi\u015fikli\u011finden sonra a\u015fa\u011f\u0131daki kontrolleri mutlaka yap\u0131n:<\/p>\n<ul>\n<li><strong>whois<\/strong> \u00e7\u0131kt\u0131s\u0131nda domain\u2019in yeni NS\u2019leri g\u00f6r\u00fcn\u00fcyor mu?<\/li>\n<li><strong>dig NS domain.com<\/strong> \u00e7\u0131kt\u0131s\u0131nda ns1\/ns2 authoritative olarak d\u00f6n\u00fcyor mu?<\/li>\n<li><strong>dig A www.domain.com @ns1.ajansiniz.com<\/strong> bekledi\u011finiz IP\u2019yi veriyor mu?<\/li>\n<li>Web sitesi a\u00e7\u0131l\u0131yor mu, <a href=\"https:\/\/www.dchost.com\/tr\/ssl\">SSL sertifikas\u0131<\/a> do\u011fru alan ad\u0131na m\u0131 ait?<\/li>\n<li>E-posta g\u00f6nderip-alma testleri (\u00f6zellikle SPF, DKIM, DMARC ge\u00e7i\u015fleri) sorunsuz mu?<\/li>\n<\/ul>\n<p>E-posta taraf\u0131nda SPF\/DKIM\/DMARC yap\u0131land\u0131rmas\u0131n\u0131 markal\u0131 DNS mimarinizle uyumlu \u015fekilde kurmak kritik \u00f6nem ta\u015f\u0131yor. Bunun i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/spf-dkim-ve-dmarc-nedir-ozel-alan-adi-ile-e-posta-dogrulamasini-cpanel-ve-vpste-sifirdan-kurmak\/\">SPF, DKIM, DMARC ve rDNS ile e-posta teslim edilebilirli\u011fini art\u0131rma rehberimizi<\/a> ajans mimarinize entegre etmenizi tavsiye ederiz.<\/p>\n<h2><span id=\"Markali_DNS_Icin_Ileri_Seviye_Tasarim_Secenekleri\">Markal\u0131 DNS \u0130\u00e7in \u0130leri Seviye Tasar\u0131m Se\u00e7enekleri<\/span><\/h2>\n<p>\u00d6zel nameserver\u2019\u0131 aya\u011fa kald\u0131rd\u0131ktan sonra, ajans olarak bir sonraki ad\u0131m <strong>\u00f6l\u00e7eklenebilirlik<\/strong> ve <strong>y\u00fcksek eri\u015filebilirlik<\/strong> olur. \u00d6zellikle onlarca\/ y\u00fczlerce domain y\u00f6netti\u011finizde a\u015fa\u011f\u0131daki tasar\u0131mlar ciddi fark yarat\u0131r.<\/p>\n<h3><span id=\"Ayri_DNS-only_VPSler_ile_yedekli_mimari\">Ayr\u0131 DNS-only VPS\u2019ler ile yedekli mimari<\/span><\/h3>\n<p>En \u00e7ok \u00f6nerdi\u011fimiz ajans modelinde, DNS g\u00f6revini web sunucular\u0131ndan ay\u0131r\u0131p iki k\u00fc\u00e7\u00fck DCHost VPS \u00fczerinde \u00e7al\u0131\u015ft\u0131r\u0131yoruz:<\/p>\n<ul>\n<li>VPS 1: ns1.ajansiniz.com (BIND\/cPanel DNSOnly\/PowerDNS)<\/li>\n<li>VPS 2: ns2.ajansiniz.com (ayn\u0131 yaz\u0131l\u0131m, ayr\u0131 node)<\/li>\n<li>Web sunucular\u0131: Ayr\u0131 VPS veya reseller hesaplar\u0131<\/li>\n<\/ul>\n<p>B\u00f6ylece web sunucusuna bak\u0131m yapt\u0131\u011f\u0131n\u0131zda DNS etkilenmez; tam tersi, DNS \u00fczerinde bak\u0131m yaparken de siteler \u00e7al\u0131\u015fmaya devam eder. Bu yakla\u015f\u0131m, <a href=\"https:\/\/www.dchost.com\/blog\/kucuk-isletme-siteleri-icin-multi-region-dns-ve-cdn-failover-mimarisi\/\">multi-region DNS ve failover mimarisi<\/a> tart\u0131\u015fmalar\u0131nda anlatt\u0131\u011f\u0131m\u0131z prensiplerin daha k\u00fc\u00e7\u00fck \u00f6l\u00e7ekteki bir yans\u0131mas\u0131d\u0131r.<\/p>\n<h3><span id=\"TTL_stratejisi_ile_esnek_ama_kontrollu_DNS\">TTL stratejisi ile esnek ama kontroll\u00fc DNS<\/span><\/h3>\n<p>Ajanslar\u0131n s\u0131k yapt\u0131\u011f\u0131 hatalardan biri, t\u00fcm kay\u0131tlar\u0131 300 saniye TTL ile b\u0131rakmak veya tam tersi, her \u015feyi 86400 saniye (24 saat) yapmak. Markal\u0131 DNS mimarinizde:<\/p>\n<ul>\n<li><strong>Statik kay\u0131tlar<\/strong> (\u00f6r. \u00e7\u0131plak domain A kayd\u0131, MX): 3600\u201314400 sn<\/li>\n<li><strong>S\u0131k de\u011fi\u015febilecek kay\u0131tlar<\/strong> (ge\u00e7ici y\u00f6nlendirmeler, test subdomain\u2019ler): 300\u2013900 sn<\/li>\n<li><strong>SPF\/DKIM\/DMARC gibi e-posta kay\u0131tlar\u0131<\/strong>: Genelde 3600\u201386400 sn aras\u0131<\/li>\n<\/ul>\n<p>Hangi kay\u0131t i\u00e7in hangi TTL aral\u0131\u011f\u0131n\u0131 se\u00e7menin mant\u0131kl\u0131 oldu\u011funu detayl\u0131 olarak <a href=\"https:\/\/www.dchost.com\/blog\/dns-ttl-degerlerini-dogru-ayarlamak-a-mx-cname-ve-txt-kayitlari-icin-stratejik-rehber\/\">TTL de\u011ferlerini do\u011fru ayarlama rehberimizde<\/a> anlatt\u0131k; markal\u0131 DNS yap\u0131n\u0131z\u0131 tasarlarken bu rehberi referans alman\u0131z\u0131 \u00f6neririz.<\/p>\n<h3><span id=\"Coklu_saglayici_DNS_ve_Anycast_secenekleri\">\u00c7oklu sa\u011flay\u0131c\u0131 DNS ve Anycast se\u00e7enekleri<\/span><\/h3>\n<p>Daha ileri senaryolarda, ajanslar DNS altyap\u0131s\u0131n\u0131 <strong>\u00e7oklu sa\u011flay\u0131c\u0131<\/strong> yakla\u015f\u0131m\u0131yla tasarlamay\u0131 tercih edebiliyor. \u00d6rne\u011fin ns1 i\u00e7in kendi DCHost VPS\u2019iniz, ns2 i\u00e7inse farkl\u0131 bir managed DNS servisi kullanmak gibi. Bu t\u00fcr hibrit yap\u0131larda tutarl\u0131l\u0131\u011f\u0131 korumak i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/coklu-saglayici-dns-nasil-kurulur-octodns-ile-zero%e2%80%91downtime-gecis-ve-dayaniklilik-rehberi\/\">\u00e7oklu sa\u011flay\u0131c\u0131 DNS ve octoDNS rehberimizde<\/a> anlatt\u0131\u011f\u0131m\u0131z otomasyon yakla\u015f\u0131mlar\u0131n\u0131 kullanabilirsiniz.<\/p>\n<p>Anycast DNS hizmetleri de, \u00f6zellikle global ziyaret\u00e7i kitlesi olan kurumsal m\u00fc\u015fterileriniz i\u00e7in anlaml\u0131 olabilir. Burada kritik nokta, t\u00fcm bu \u00e7\u00f6z\u00fcmleri <strong>markal\u0131 ns1\/ns2 hostname\u2019lerinizin arkas\u0131na gizlemek<\/strong>; yani son kullan\u0131c\u0131 hep ajansiniz.com alt\u0131nda bir deneyim g\u00f6r\u00fcr.<\/p>\n<h2><span id=\"Ajanslar_Icin_Operasyonel_En_Iyi_Uygulamalar\">Ajanslar \u0130\u00e7in Operasyonel En \u0130yi Uygulamalar<\/span><\/h2>\n<h3><span id=\"Mimariyi_dokumante_edin_ve_standartlastirin\">Mimariyi dok\u00fcmante edin ve standartla\u015ft\u0131r\u0131n<\/span><\/h3>\n<p>DNS mimarinizi oturttuktan sonra, ekip i\u00e7inde herkesin ayn\u0131 dili konu\u015fmas\u0131 i\u00e7in k\u0131sa ama net bir <strong>DNS runbook<\/strong> haz\u0131rlay\u0131n:<\/p>\n<ul>\n<li>\u201cYeni m\u00fc\u015fteri eklendi\u011finde yap\u0131lacaklar listesi\u201d<\/li>\n<li>\u201cAlan ad\u0131 ta\u015f\u0131n\u0131rken dikkat edilecek DNS maddeleri\u201d<\/li>\n<li>\u201cE-posta \u015fikayeti geldi\u011finde kontrol edilecek DNS kay\u0131tlar\u0131\u201d<\/li>\n<\/ul>\n<p>Bu runbook\u2019u, <a href=\"https:\/\/www.dchost.com\/blog\/ajanslar-icin-dns-ve-alan-adi-erisimi-yonetimi\/\">ajanslar i\u00e7in DNS ve alan ad\u0131 eri\u015fimi y\u00f6netimi rehberimizde<\/a> anlatt\u0131\u011f\u0131m\u0131z yetki ve eri\u015fim mimarisiyle birlikte d\u00fc\u015f\u00fcnmek, hem g\u00fcvenlik hem de operasyonel kalite a\u00e7\u0131s\u0131ndan b\u00fcy\u00fck fark yarat\u0131r.<\/p>\n<h3><span id=\"Rollerinizi_ve_erisimlerinizi_ayirin\">Rollerinizi ve eri\u015fimlerinizi ay\u0131r\u0131n<\/span><\/h3>\n<p>DNS\u2019e herkesin tam yetkiyle girmesi ajanslar i\u00e7in en riskli senaryolardan biridir. Pratik bir model:<\/p>\n<ul>\n<li><strong>Altyap\u0131 sorumlular\u0131<\/strong>: ns1\/ns2, glue record, zone templateleri, TTL stratejisi.<\/li>\n<li><strong>Uygulama ekipleri<\/strong>: Sadece belirli domain\u2019lerin belirli kay\u0131tlar\u0131n\u0131 de\u011fi\u015ftirme yetkisi.<\/li>\n<li><strong>M\u00fc\u015fteri temsilcileri<\/strong>: Sadece okuma yetkisi veya haz\u0131r \u015fablonlar\u0131 tetikleme hakk\u0131.<\/li>\n<\/ul>\n<p>DNS paneliniz bu seviyede rol bazl\u0131 yetkilendirme desteklemiyorsa, en az\u0131ndan kimlerin DNS\u2019e girebildi\u011fini s\u0131n\u0131rlamak ve t\u00fcm de\u011fi\u015fiklikleri loglamak iyi bir ba\u015flang\u0131\u00e7 olacakt\u0131r.<\/p>\n<h3><span id=\"Sablon_template_kullanin\">\u015eablon (template) kullan\u0131n<\/span><\/h3>\n<p>Ajans portf\u00f6y\u00fcn\u00fczdeki sitelerin b\u00fcy\u00fck b\u00f6l\u00fcm\u00fc benzer yap\u0131lardaysa (\u00f6rne\u011fin WordPress + cPanel, standart e-posta kurulumlar\u0131 vb.),<\/p>\n<ul>\n<li>Varsay\u0131lan A, AAAA, MX, SPF, DKIM, DMARC, CAA kay\u0131tlar\u0131n\u0131 i\u00e7eren bir <strong>zone \u015fablonu<\/strong> olu\u015fturun.<\/li>\n<li>Yeni m\u00fc\u015fteri a\u00e7arken bu \u015fablonu otomatik uygulay\u0131n.<\/li>\n<li>Ortaya \u00e7\u0131kan kay\u0131tlar\u0131, m\u00fc\u015fteriye \u00f6zel ihtiya\u00e7larla g\u00fcncelleyin (alt alan adlar\u0131, harici servis entegrasyonlar\u0131 vb.).<\/li>\n<\/ul>\n<p>Bu yakla\u015f\u0131m, \u201cbir domain\u2019de SPF d\u00fczg\u00fcn, di\u011ferinde eksik, \u00f6b\u00fcr\u00fcnde hi\u00e7 yok\u201d gibi durumlardan sizi kurtar\u0131r.<\/p>\n<h2><span id=\"DCHost_Uzerinde_Ornek_Markali_DNS_Mimarileri\">DCHost \u00dczerinde \u00d6rnek Markal\u0131 DNS Mimarileri<\/span><\/h2>\n<h3><span id=\"Senaryo_1_cPanel_reseller_ozel_nameserver\">Senaryo 1: cPanel reseller + \u00f6zel nameserver<\/span><\/h3>\n<p>En h\u0131zl\u0131 devreye al\u0131nan ajans modeli \u015fu \u015fekilde \u00e7al\u0131\u015f\u0131r:<\/p>\n<ul>\n<li>DCHost\u2019ta bir <strong>cPanel reseller paketi<\/strong> kullan\u0131rs\u0131n\u0131z.<\/li>\n<li>Reseller sunucunuzdan size tan\u0131mlanan iki IP\u2019yi ns1 ve ns2 i\u00e7in kullan\u0131rs\u0131n\u0131z.<\/li>\n<li>Glue record\u2019lar\u0131 ajansiniz.com alan ad\u0131n\u0131z i\u00e7in olu\u015fturursunuz.<\/li>\n<li>WHM\u2019den varsay\u0131lan nameserver\u2019lar\u0131 ns1\/ns2 yapars\u0131n\u0131z.<\/li>\n<\/ul>\n<p>B\u00f6ylece t\u00fcm yeni a\u00e7\u0131lan cPanel hesaplar\u0131, otomatik olarak sizin markal\u0131 nameserver\u2019lar\u0131n\u0131zla yay\u0131nlan\u0131r. Mevcut m\u00fc\u015fterileri ise yava\u015f yava\u015f bu ns1\/ns2\u2019ye ta\u015f\u0131yabilirsiniz. Bu yap\u0131 \u00f6l\u00e7eklendik\u00e7e, ileride ayr\u0131 DNS-only VPS\u2019lere ge\u00e7mek de olduk\u00e7a kolayd\u0131r.<\/p>\n<h3><span id=\"Senaryo_2_VPS_cPanelDirectAdmin_DNS-only_VPSler\">Senaryo 2: VPS + cPanel\/DirectAdmin + DNS-only VPS\u2019ler<\/span><\/h3>\n<p>Daha kontroll\u00fc ve y\u00fcksek eri\u015filebilir bir yap\u0131 i\u00e7in:<\/p>\n<ul>\n<li>VPS-A: Web + e-posta (cPanel\/DirectAdmin)<\/li>\n<li>VPS-B: ns1.ajansiniz.com (DNS-only)<\/li>\n<li>VPS-C: ns2.ajansiniz.com (DNS-only)<\/li>\n<\/ul>\n<p>Burada panelinizin DNS cluster\/DNS-only \u00f6zelliklerinden faydalanarak, zone\u2019lar\u0131n VPS-B ve VPS-C aras\u0131nda otomatik replikasyonunu sa\u011flayabilirsiniz. B\u00f6ylece web sunucusunu b\u00fcy\u00fctmek veya de\u011fi\u015ftirmek istedi\u011finizde, DNS taraf\u0131na dokunmadan yeni topolojiye ge\u00e7ebilirsiniz.<\/p>\n<h3><span id=\"Senaryo_3_Multi-tenant_e-posta_ve_DNS_yonetimi\">Senaryo 3: Multi-tenant e-posta ve DNS y\u00f6netimi<\/span><\/h3>\n<p>E\u011fer ajans olarak sadece web de\u011fil, e-posta altyap\u0131s\u0131n\u0131 da merkezi y\u00f6netiyorsan\u0131z, <a href=\"https:\/\/www.dchost.com\/blog\/ajanslar-icin-multi-tenant-e-posta-ve-dns-mimarisi-tek-sunucuda-onlarca-musteri-yonetmek\/\">ajanslar i\u00e7in multi-tenant e-posta ve DNS mimarisi rehberimizde<\/a> anlatt\u0131\u011f\u0131m\u0131z yakla\u015f\u0131m\u0131 markal\u0131 DNS yap\u0131n\u0131zla birle\u015ftirebilirsiniz. Bu sayede:<\/p>\n<ul>\n<li>M\u00fc\u015fterilerin g\u00f6nderen alan adlar\u0131 i\u00e7in SPF\/DKIM\/DMARC kay\u0131tlar\u0131n\u0131 tek merkezden y\u00f6netirsiniz.<\/li>\n<li>MX ve ilgili TXT kay\u0131tlar\u0131n\u0131 standardize edersiniz.<\/li>\n<li>Yeni m\u00fc\u015fteri eklemek, sadece bir \u015fablon uygulay\u0131p birka\u00e7 alan ad\u0131 girmek kadar basit hale gelir.<\/li>\n<\/ul>\n<h2><span id=\"Sonuc_Markali_DNS_Ajans_Operasyonunun_Gizli_Iskeleti\">Sonu\u00e7: Markal\u0131 DNS, Ajans Operasyonunun Gizli \u0130skeleti<\/span><\/h2>\n<p>Ajans ve bayi taraf\u0131nda g\u00fcnl\u00fck hayat genelde siteler, tasar\u0131m, SEO, kampanyalar ve raporlamalar etraf\u0131nda d\u00f6ner; DNS ise ancak bir \u015fey bozuldu\u011funda akla gelir. Oysa iyi tasarlanm\u0131\u015f bir <strong>markal\u0131 DNS mimarisi<\/strong>, b\u00fct\u00fcn bu i\u015flerin sorunsuz ve \u00f6ng\u00f6r\u00fclebilir \u00e7al\u0131\u015fmas\u0131n\u0131n g\u00f6r\u00fcnmeyen iskeletidir. Kendi ns1\/ns2 altyap\u0131n\u0131z\u0131 kurup t\u00fcm m\u00fc\u015fterilerinizi bu \u00e7at\u0131 alt\u0131nda toplad\u0131\u011f\u0131n\u0131zda, proje teslim s\u00fcre\u00e7leri h\u0131zlan\u0131r, hata oran\u0131 d\u00fc\u015fer ve marka alg\u0131n\u0131z g\u00fc\u00e7lenir.<\/p>\n<p>DCHost olarak, reseller paketlerinden y\u00f6netilen VPS \u00e7\u00f6z\u00fcmlerine, dedicated ve colocation altyap\u0131lar\u0131na kadar farkl\u0131 \u00f6l\u00e7ekte ajanslarla \u00e7al\u0131\u015f\u0131rken g\u00f6rd\u00fc\u011f\u00fcm\u00fcz ortak nokta \u015fu: <strong>\u00d6zel nameserver kurulumu bir kez d\u00fczg\u00fcn yap\u0131ld\u0131\u011f\u0131nda, y\u0131llarca meyvesini veriyor.<\/strong> E\u011fer siz de da\u011f\u0131n\u0131k DNS yap\u0131s\u0131n\u0131 toparlamak, markan\u0131z alt\u0131nda kurumsal bir ns1\/ns2 altyap\u0131s\u0131 kurmak ve bunu \u00f6l\u00e7eklenebilir hale getirmek istiyorsan\u0131z; mevcut DCHost hesab\u0131n\u0131z \u00fczerinden ya da yeni plan se\u00e7imi a\u015famas\u0131nda ekibimizle birlikte size uygun DNS mimarisini planlayabilirsiniz.<\/p>\n<p>\u0130lk ad\u0131m olarak, elinizdeki m\u00fc\u015fterileri ve kulland\u0131klar\u0131 DNS\u2019leri basit bir tabloya d\u00f6k\u00fcn; ard\u0131ndan bu rehberdeki ad\u0131mlarla kendi ns1\/ns2 yap\u0131n\u0131z\u0131 kurun ve \u00f6nceli\u011fi kritik olmayan domain\u2019lere vererek ge\u00e7i\u015fe ba\u015flay\u0131n. Birka\u00e7 proje sonra markal\u0131 DNS\u2019in getirdi\u011fi h\u0131z, g\u00fcven ve kontrol fark\u0131n\u0131 \u00e7ok net hissedeceksiniz.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>Bir ajans veya bayi olarak onlarca, hatta y\u00fczlerce m\u00fc\u015fterinin domain ve hosting altyap\u0131s\u0131n\u0131 y\u00f6netirken en \u00e7ok can s\u0131kan konulardan biri, DNS taraf\u0131nda da\u011f\u0131n\u0131kl\u0131k ve kontrol eksikli\u011fidir. Her m\u00fc\u015fterinin alan ad\u0131 farkl\u0131 kay\u0131t firmas\u0131ndad\u0131r, kimi registrar DNS\u2019i, kimi hosting DNS\u2019i, kimi de \u00fc\u00e7\u00fcnc\u00fc parti bir DNS hizmeti kullan\u0131r. Bu yap\u0131 hem operasyonel y\u00fck\u00fc art\u0131r\u0131r hem de [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":4585,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-4584","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\/4584","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=4584"}],"version-history":[{"count":0,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/4584\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/4585"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=4584"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=4584"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=4584"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}