{"id":2839,"date":"2025-12-04T15:37:20","date_gmt":"2025-12-04T12:37:20","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/ajanslar-icin-dns-ve-alan-adi-erisimi-yonetimi\/"},"modified":"2025-12-04T15:37:20","modified_gmt":"2025-12-04T12:37:20","slug":"ajanslar-icin-dns-ve-alan-adi-erisimi-yonetimi","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/ajanslar-icin-dns-ve-alan-adi-erisimi-yonetimi\/","title":{"rendered":"Ajanslar \u0130\u00e7in DNS ve Alan Ad\u0131 Eri\u015fimi Y\u00f6netimi"},"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=\"#Ajanslar_Icin_DNS_ve_Alan_Adi_Erisimi_Neden_Kritik_Bir_Konu\"><span class=\"toc_number toc_depth_1\">1<\/span> Ajanslar \u0130\u00e7in DNS ve Alan Ad\u0131 Eri\u015fimi Neden Kritik Bir Konu?<\/a><\/li><li><a href=\"#Alan_Adi_ve_DNS_Erisim_Modelleri_Temel_Stratejiyi_Dogru_Kurmak\"><span class=\"toc_number toc_depth_1\">2<\/span> Alan Ad\u0131 ve DNS Eri\u015fim Modelleri: Temel Stratejiyi Do\u011fru Kurmak<\/a><ul><li><a href=\"#1_Musterinin_Alan_Adi_Hesabina_Dogrudan_Giris_Klasik_Riskli_Yol\"><span class=\"toc_number toc_depth_2\">2.1<\/span> 1) M\u00fc\u015fterinin Alan Ad\u0131 Hesab\u0131na Do\u011frudan Giri\u015f (Klasik, Riskli Yol)<\/a><\/li><li><a href=\"#2_Ajans_Hesabinda_Alan_Adi_Barindirma_Merkezi_Ama_Sahiplik_Riskli\"><span class=\"toc_number toc_depth_2\">2.2<\/span> 2) Ajans Hesab\u0131nda Alan Ad\u0131 Bar\u0131nd\u0131rma (Merkezi Ama Sahiplik Riskli)<\/a><\/li><li><a href=\"#3_Karma_Model_Musteri_Hesabinda_Sahiplik_Ajans_Tarafinda_DNS_Yonetimi\"><span class=\"toc_number toc_depth_2\">2.3<\/span> 3) Karma Model: M\u00fc\u015fteri Hesab\u0131nda Sahiplik, Ajans Taraf\u0131nda DNS Y\u00f6netimi<\/a><\/li><\/ul><\/li><li><a href=\"#Guvenli_Erisim_Tasarimi_Kim_Neye_Ne_Kadar_Sureyle_Ulasabilmeli\"><span class=\"toc_number toc_depth_1\">3<\/span> G\u00fcvenli Eri\u015fim Tasar\u0131m\u0131: Kim, Neye, Ne Kadar S\u00fcreyle Ula\u015fabilmeli?<\/a><ul><li><a href=\"#Ajans_Icindeki_Roller_ve_Yetki_Seviyeleri\"><span class=\"toc_number toc_depth_2\">3.1<\/span> Ajans \u0130\u00e7indeki Roller ve Yetki Seviyeleri<\/a><\/li><li><a href=\"#Musteri_Hesabina_Erisim_Sifre_Degil_Yetki_Istemek\"><span class=\"toc_number toc_depth_2\">3.2<\/span> M\u00fc\u015fteri Hesab\u0131na Eri\u015fim: \u015eifre De\u011fil, Yetki \u0130stemek<\/a><\/li><li><a href=\"#DNS_Panelini_Ajans_Tarafina_Tasimak_Nameserver_Degisimi\"><span class=\"toc_number toc_depth_2\">3.3<\/span> DNS Panelini Ajans Taraf\u0131na Ta\u015f\u0131mak: Nameserver De\u011fi\u015fimi<\/a><\/li><\/ul><\/li><li><a href=\"#Dokumantasyon_Ajansin_Hayatini_Kurtaran_Gorunmez_Katman\"><span class=\"toc_number toc_depth_1\">4<\/span> Dok\u00fcmantasyon: Ajans\u0131n Hayat\u0131n\u0131 Kurtaran G\u00f6r\u00fcnmez Katman<\/a><ul><li><a href=\"#Asgari_Duzeyde_Olmasi_Gereken_Dokuman_Seti\"><span class=\"toc_number toc_depth_2\">4.1<\/span> Asgari D\u00fczeyde Olmas\u0131 Gereken Dok\u00fcman Seti<\/a><\/li><li><a href=\"#Dokumantasyonu_Nerede_Tutmali_Not_Sadece_Excel_Yetmez\"><span class=\"toc_number toc_depth_2\">4.2<\/span> Dok\u00fcmantasyonu Nerede Tutmal\u0131? (Not: Sadece Excel Yetmez)<\/a><\/li><\/ul><\/li><li><a href=\"#Operasyonel_Surecler_Onboarding_Degisiklik_Yonetimi_ve_Offboarding\"><span class=\"toc_number toc_depth_1\">5<\/span> Operasyonel S\u00fcre\u00e7ler: Onboarding, De\u011fi\u015fiklik Y\u00f6netimi ve Offboarding<\/a><ul><li><a href=\"#Yeni_Musteri_Onboarding_Ilk_Gun_Yapilmasi_Gerekenler\"><span class=\"toc_number toc_depth_2\">5.1<\/span> Yeni M\u00fc\u015fteri Onboarding: \u0130lk G\u00fcn Yap\u0131lmas\u0131 Gerekenler<\/a><\/li><li><a href=\"#DNS_Degisiklik_Yonetimi_Her_Degisiklik_Kucuk_Bir_Projedir\"><span class=\"toc_number toc_depth_2\">5.2<\/span> DNS De\u011fi\u015fiklik Y\u00f6netimi: Her De\u011fi\u015fiklik K\u00fc\u00e7\u00fck Bir Projedir<\/a><\/li><li><a href=\"#Offboarding_Musteri_Ayrilirken_Kopruleri_Yakmamak\"><span class=\"toc_number toc_depth_2\">5.3<\/span> Offboarding: M\u00fc\u015fteri Ayr\u0131l\u0131rken K\u00f6pr\u00fcleri Yakmamak<\/a><\/li><\/ul><\/li><li><a href=\"#DCHost_ile_DNS_ve_Alan_Adi_Altyapisini_Merkezi_ve_Guvenli_Yonetmek\"><span class=\"toc_number toc_depth_1\">6<\/span> DCHost ile DNS ve Alan Ad\u0131 Altyap\u0131s\u0131n\u0131 Merkezi ve G\u00fcvenli Y\u00f6netmek<\/a><\/li><li><a href=\"#Sonuc_ve_Yol_Haritasi_Ajansiniz_Icin_Uygulanabilir_Bir_Model_Kurun\"><span class=\"toc_number toc_depth_1\">7<\/span> Sonu\u00e7 ve Yol Haritas\u0131: Ajans\u0131n\u0131z \u0130\u00e7in Uygulanabilir Bir Model Kurun<\/a><\/li><\/ul><\/div>\n<h2><span id=\"Ajanslar_Icin_DNS_ve_Alan_Adi_Erisimi_Neden_Kritik_Bir_Konu\">Ajanslar \u0130\u00e7in DNS ve Alan Ad\u0131 Eri\u015fimi Neden Kritik Bir Konu?<\/span><\/h2>\n<p>Bir ajans olarak onlarca hatta y\u00fczlerce m\u00fc\u015fterinin web sitesi, e-posta altyap\u0131s\u0131 ve kampanya landing sayfalar\u0131ndan sorumlu oldu\u011funuzda, teknik olarak en k\u0131r\u0131lgan noktalardan biri <strong>DNS ve alan ad\u0131 eri\u015fimi<\/strong> oluyor. Kreatif s\u00fcre\u00e7ler, i\u00e7erik \u00fcretimi ve performans raporlar\u0131 \u00f6n planda oldu\u011fu i\u00e7in, DNS genellikle \u201cson dakikada dokunulan\u201d bir alan olarak kal\u0131yor. Ancak yanl\u0131\u015f yap\u0131land\u0131r\u0131lm\u0131\u015f bir DNS kayd\u0131, s\u00fcresi ge\u00e7en bir alan ad\u0131 ya da kaybolmu\u015f bir giri\u015f bilgisi; b\u00fcy\u00fck kampanyalar\u0131n yay\u0131na girememesine, e-posta trafi\u011finin durmas\u0131na ve markan\u0131n g\u00f6z\u00fcnde ajans\u0131n g\u00fcvenilirli\u011finin ciddi \u015fekilde zedelenmesine yol a\u00e7abiliyor.<\/p>\n<p>Biz DCHost olarak ajanslardan en \u00e7ok \u015fu t\u00fcr hik\u00e2yeleri duyuyoruz: \u201cEski m\u00fc\u015fteri temsilcisi ayr\u0131ld\u0131, alan ad\u0131 \u015fifresi onda kalm\u0131\u015ft\u0131\u201d, \u201cM\u00fc\u015fteri kendi alan ad\u0131n\u0131 bir yerde alm\u0131\u015f ama nerede oldu\u011funu kimse bilmiyor\u201d, \u201cEski ajans DNS kay\u0131tlar\u0131n\u0131 kar\u0131\u015f\u0131k b\u0131rakm\u0131\u015f, dokunmaya korkuyoruz.\u201d T\u00fcm bu sorunlar\u0131n ortak noktas\u0131, <strong>standartla\u015ft\u0131r\u0131lmam\u0131\u015f eri\u015fim modeli ve yetersiz dok\u00fcmantasyon<\/strong>. Bu yaz\u0131da, \u00f6zellikle ajanslar i\u00e7in DNS ve alan ad\u0131 eri\u015fimini nas\u0131l g\u00fcvenli, tekrar edilebilir ve denetlenebilir hale getirebilece\u011finizi; m\u00fc\u015fteri hesaplar\u0131na nas\u0131l g\u00fcvenli yetki verece\u011finizi ve t\u00fcm s\u00fcreci nas\u0131l belgelendirmeniz gerekti\u011fini ad\u0131m ad\u0131m anlataca\u011f\u0131z.<\/p>\n<p>Amac\u0131m\u0131z, bir kere kurduktan sonra yeni her m\u00fc\u015fteri i\u00e7in kopyalayabilece\u011finiz, ajans \u00f6l\u00e7e\u011finiz b\u00fcy\u00fcd\u00fck\u00e7e de bozulmadan \u00e7al\u0131\u015fmaya devam eden pratik bir model ortaya koymak. B\u00f6ylece hem teknik ekipleriniz rahat eder hem de m\u00fc\u015fteri g\u00f6z\u00fcnde \u201caltyap\u0131s\u0131n\u0131 bilen, dokunmaya cesaret eden ajans\u201d konumuna yerle\u015firsiniz.<\/p>\n<h2><span id=\"Alan_Adi_ve_DNS_Erisim_Modelleri_Temel_Stratejiyi_Dogru_Kurmak\">Alan Ad\u0131 ve DNS Eri\u015fim Modelleri: Temel Stratejiyi Do\u011fru Kurmak<\/span><\/h2>\n<p>\u00d6ncelikle ajanslar\u0131n tipik olarak kar\u015f\u0131s\u0131na \u00e7\u0131kan \u00fc\u00e7 ana eri\u015fim modelini netle\u015ftirelim. Her bir modelin avantajlar\u0131 ve riskleri farkl\u0131; do\u011fru strateji genellikle bu modellerin kontroll\u00fc bir kombinasyonu oluyor.<\/p>\n<h3><span id=\"1_Musterinin_Alan_Adi_Hesabina_Dogrudan_Giris_Klasik_Riskli_Yol\">1) M\u00fc\u015fterinin Alan Ad\u0131 Hesab\u0131na Do\u011frudan Giri\u015f (Klasik, Riskli Yol)<\/span><\/h3>\n<p>En yayg\u0131n senaryo \u015fu: M\u00fc\u015fteri, alan ad\u0131n\u0131 y\u0131llar \u00f6nce bir yerden alm\u0131\u015ft\u0131r; kullan\u0131c\u0131 ad\u0131 ve \u015fifreyi ajansa g\u00f6nderir; ajans DNS kay\u0131tlar\u0131n\u0131 d\u00fczenler ve sonra o bilgiler e-posta ar\u015fivlerinin bir yerinde kaybolur. Bu modelin baz\u0131 avantajlar\u0131 olsa da (hemen i\u015f yapabilme, ek hesap a\u00e7ma derdi olmamas\u0131), ajans \u00f6l\u00e7e\u011fi b\u00fcy\u00fcd\u00fck\u00e7e ciddi riskler olu\u015fur:<\/p>\n<ul>\n<li><strong>\u015eifre payla\u015f\u0131m\u0131:<\/strong> Ajans i\u00e7inde birden fazla ki\u015fi ayn\u0131 kullan\u0131c\u0131 ad\u0131\/\u015fifre ile giri\u015f yapar. Kimin ne zaman ne yapt\u0131\u011f\u0131 takip edilemez.<\/li>\n<li><strong>\u00c7\u0131k\u0131\u015f s\u00fcre\u00e7leri:<\/strong> Ekipten ayr\u0131lan bir \u00e7al\u0131\u015fan, m\u00fc\u015fterinin alan ad\u0131 hesab\u0131na eri\u015fmeye devam edebilir.<\/li>\n<li><strong>Denetlenebilirlik yok:<\/strong> Hangi g\u00fcn hangi DNS kayd\u0131 kim taraf\u0131ndan de\u011fi\u015ftirildi, izlemek zordur.<\/li>\n<li><strong>G\u00fcven k\u0131r\u0131lmas\u0131 riski:<\/strong> M\u00fc\u015fteri, alan ad\u0131n\u0131n \u201ctamamen ajans\u0131n elinde\u201d oldu\u011funu d\u00fc\u015f\u00fcn\u00fcr ve bu, g\u00fcven ili\u015fkisini zedeleyebilir.<\/li>\n<\/ul>\n<p>Bu model, k\u00fc\u00e7\u00fck \u00f6l\u00e7ekli ve k\u0131sa s\u00fcreli projelerde i\u015fleri h\u0131zl\u0131 ba\u015flatmak i\u00e7in i\u015fe yarayabilir; ancak orta ve b\u00fcy\u00fck ajanslarda s\u00fcrd\u00fcr\u00fclebilir de\u011fildir.<\/p>\n<h3><span id=\"2_Ajans_Hesabinda_Alan_Adi_Barindirma_Merkezi_Ama_Sahiplik_Riskli\">2) Ajans Hesab\u0131nda Alan Ad\u0131 Bar\u0131nd\u0131rma (Merkezi Ama Sahiplik Riskli)<\/span><\/h3>\n<p>\u0130kinci modelde ajans, alan ad\u0131n\u0131 kendi hesab\u0131ndan sat\u0131n al\u0131r veya transfer eder; t\u00fcm y\u00f6netim ajans\u0131n hesab\u0131ndad\u0131r. M\u00fc\u015fteri ad\u0131na yeni domain a\u00e7mak, DNS\u2019i yap\u0131land\u0131rmak, sertifika almak gibi i\u015flemler ajans i\u00e7in olduk\u00e7a rahatt\u0131r. Ancak burada da kritik iki soru ortaya \u00e7\u0131kar:<\/p>\n<ul>\n<li><strong>Fatura ve m\u00fclkiyet:<\/strong> Alan ad\u0131 kimin ad\u0131na kay\u0131tl\u0131? M\u00fc\u015fteri mi, ajans m\u0131? Mukavelelerde bu net mi?<\/li>\n<li><strong>Ajans\u2013m\u00fc\u015fteri ili\u015fkisi sona erdi\u011finde:<\/strong> <a href=\"https:\/\/www.dchost.com\/tr\/alan-adi\/transfer-et\">alan ad\u0131 transfer<\/a> s\u00fcreci nas\u0131l i\u015fleyecek, \u00fccretleri kim \u00f6deyecek, ne kadar s\u00fcrede devredilecek?<\/li>\n<\/ul>\n<p>Bu model, \u00f6zellikle uzun soluklu m\u00fc\u015fterilerde ve ajans\u0131n \u201caltyap\u0131 partneri\u201d olarak konumland\u0131\u011f\u0131 ili\u015fkilerde mant\u0131kl\u0131 olabilir. Ancak mutlaka s\u00f6zle\u015fme ve s\u00fcre\u00e7 taraf\u0131 sa\u011flamla\u015ft\u0131r\u0131lmal\u0131d\u0131r. \u00d6rne\u011fin, alan ad\u0131n\u0131n m\u00fclkiyetinin her zaman m\u00fc\u015fteriye ait oldu\u011funu, ajans\u0131n sadece teknik y\u00f6netim hakk\u0131na sahip oldu\u011funu a\u00e7\u0131k\u00e7a belirten maddeler kullan\u0131labilir.<\/p>\n<h3><span id=\"3_Karma_Model_Musteri_Hesabinda_Sahiplik_Ajans_Tarafinda_DNS_Yonetimi\">3) Karma Model: M\u00fc\u015fteri Hesab\u0131nda Sahiplik, Ajans Taraf\u0131nda DNS Y\u00f6netimi<\/span><\/h3>\n<p>Bizim ajanslar i\u00e7in en sa\u011fl\u0131kl\u0131 buldu\u011fumuz model genellikle \u015fu:<\/p>\n<ul>\n<li>Alan ad\u0131, <strong>m\u00fc\u015fterinin kendi hesab\u0131nda<\/strong> ve kendi fatura bilgileriyle kay\u0131tl\u0131 olur.<\/li>\n<li>Nameserver\u2019lar, ajans\u0131n y\u00f6netti\u011fi DNS altyap\u0131s\u0131na (<strong>DCHost DNS veya ajans\u0131n tercih etti\u011fi profesyonel DNS \u00e7\u00f6z\u00fcm\u00fc<\/strong>) y\u00f6nlendirilir.<\/li>\n<li>Ajans, sadece DNS y\u00f6netim katman\u0131na eri\u015fir; alan ad\u0131n\u0131n m\u00fclkiyetine de\u011fil.<\/li>\n<\/ul>\n<p>B\u00f6ylece:<\/p>\n<ul>\n<li>M\u00fc\u015fteri, alan ad\u0131n\u0131n sahibi olmaya devam eder.<\/li>\n<li>Ajans, DNS kay\u0131tlar\u0131 \u00fczerinde h\u0131zl\u0131 ve esnek \u00e7al\u0131\u015f\u0131r (yeni sunucuya ge\u00e7i\u015f, e-posta servis de\u011fi\u015fimi, kampanya alt alan adlar\u0131 vb.).<\/li>\n<li>Eri\u015fim seviyesi net ayr\u0131lm\u0131\u015f olur: \u201cM\u00fclkiyet\u201d m\u00fc\u015fteride, \u201coperasyonel y\u00f6netim\u201d ajans taraf\u0131ndad\u0131r.<\/li>\n<\/ul>\n<p>Bu modelin <a href=\"https:\/\/www.dchost.com\/blog\/cloudflare-dns-mi-hosting-dnsi-mi-en-dogru-nameserver-stratejisi\/\">nameserver stratejisi<\/a>, TTL ayarlar\u0131 ve yedeklilik taraf\u0131n\u0131 daha derinlemesine anlamak i\u00e7in, ad sunucusu se\u00e7imi ve stratejilerini anlatt\u0131\u011f\u0131m\u0131z rehbere mutlaka g\u00f6z atman\u0131z\u0131 \u00f6neririz.<\/p>\n<h2><span id=\"Guvenli_Erisim_Tasarimi_Kim_Neye_Ne_Kadar_Sureyle_Ulasabilmeli\">G\u00fcvenli Eri\u015fim Tasar\u0131m\u0131: Kim, Neye, Ne Kadar S\u00fcreyle Ula\u015fabilmeli?<\/span><\/h2>\n<p>Modeli se\u00e7tikten sonra, ikinci kritik ad\u0131m <strong>eri\u015fim rollerini<\/strong> ve <strong>minimum yetki prensibini<\/strong> (least privilege) do\u011fru kurmakt\u0131r. Temel hedef: Kim ne yap\u0131yorsa, sadece ona yetecek kadar yetki sahibi olsun.<\/p>\n<h3><span id=\"Ajans_Icindeki_Roller_ve_Yetki_Seviyeleri\">Ajans \u0130\u00e7indeki Roller ve Yetki Seviyeleri<\/span><\/h3>\n<p>Tipik bir dijital ajans yap\u0131s\u0131n\u0131 d\u00fc\u015f\u00fcnelim: Hesap y\u00f6neticileri, proje y\u00f6neticileri, geli\u015ftiriciler, sistem y\u00f6neticileri, i\u00e7erik edit\u00f6rleri, kampanya uzmanlar\u0131\u2026 T\u00fcm bu ki\u015filer ayn\u0131 DNS veya alan ad\u0131 hesab\u0131na tam yetkili eri\u015firse, uzun vadede <strong>insan hatas\u0131 ka\u00e7\u0131n\u0131lmaz hale gelir<\/strong>. Sa\u011fl\u0131kl\u0131 bir model \u015f\u00f6yle olabilir:<\/p>\n<ul>\n<li><strong>DNS Y\u00f6neticisi \/ DevOps:<\/strong> T\u00fcm DNS kay\u0131tlar\u0131n\u0131 okuma\/yazma; nameserver de\u011fi\u015fikli\u011fi, zone olu\u015fturma, yedek alma gibi kritik yetkiler.<\/li>\n<li><strong>Geli\u015ftirici \/ Teknik Ekip:<\/strong> Belirli alan adlar\u0131nda A, AAAA, CNAME, TXT gibi kay\u0131tlar\u0131 g\u00fcncelleme; ancak domain transferi veya nameserver de\u011fi\u015ftirme yetkisi olmamas\u0131.<\/li>\n<li><strong>Hesap Y\u00f6neticisi \/ Proje Y\u00f6neticisi:<\/strong> Sadece okuma ve durum g\u00f6r\u00fcnt\u00fcleme; m\u00fc\u015fteriye raporlama i\u00e7in.<\/li>\n<li><strong>Stajyer \/ Junior Personel:<\/strong> Sadece test ortamlar\u0131 i\u00e7in s\u0131n\u0131rl\u0131 yetkiler; canl\u0131 alan adlar\u0131na eri\u015fim yok.<\/li>\n<\/ul>\n<p>Bu ayr\u0131m\u0131 desteklemek i\u00e7in kulland\u0131\u011f\u0131n\u0131z DNS ve hosting altyap\u0131s\u0131nda <strong>alt kullan\u0131c\u0131, rol bazl\u0131 yetki ve loglama<\/strong> \u00f6zellikleri olup olmad\u0131\u011f\u0131n\u0131 mutlaka de\u011ferlendirin. DCHost taraf\u0131nda, ajans m\u00fc\u015fterilerimizle birlikte bu yetki modelini planlayarak; hangi ekip \u00fcyesinin hangi panellere hangi seviyede eri\u015fmesi gerekti\u011fini birlikte kurguluyoruz.<\/p>\n<h3><span id=\"Musteri_Hesabina_Erisim_Sifre_Degil_Yetki_Istemek\">M\u00fc\u015fteri Hesab\u0131na Eri\u015fim: \u015eifre De\u011fil, Yetki \u0130stemek<\/span><\/h3>\n<p>Modern g\u00fcvenlik yakla\u015f\u0131m\u0131, \u201cm\u00fc\u015fteriden kullan\u0131c\u0131 ad\u0131\/\u015fifre istemek\u201d yerine; alt kullan\u0131c\u0131 veya yetkilendirme mekanizmalar\u0131 \u00fczerinden eri\u015fim almay\u0131 \u00f6nerir. \u00d6rne\u011fin:<\/p>\n<ul>\n<li>M\u00fc\u015fteriden, panelinde <strong>\u201cteknik kullan\u0131c\u0131\u201d<\/strong> veya <strong>\u201cajans kullan\u0131c\u0131s\u0131\u201d<\/strong> olu\u015fturarak size ayr\u0131 bir kullan\u0131c\u0131 tan\u0131mlamas\u0131n\u0131 istemek.<\/li>\n<li>Bu kullan\u0131c\u0131ya, sadece gerekli olan mod\u00fcllere (DNS y\u00f6netimi, nameserver de\u011fi\u015fimi vb.) yetki verilmesini sa\u011flamak.<\/li>\n<li>\u0130ki fakt\u00f6rl\u00fc do\u011frulamay\u0131 (2FA) m\u00fc\u015fterinin kendi ana hesab\u0131nda b\u0131rakmak; ajans hesab\u0131nda ise gerekirse ajans i\u00e7i SSO veya \u015fifre kasas\u0131 (password manager) kullanmak.<\/li>\n<\/ul>\n<p>Bu sayede \u015fifreler e-posta veya WhatsApp \u00fczerinden dola\u015fmaz, m\u00fc\u015fteri hesab\u0131 \u00fczerindeki tam kontrol m\u00fc\u015fteride kal\u0131r, ajans sadece ger\u00e7ekten ihtiya\u00e7 duydu\u011fu alanlara eri\u015fir.<\/p>\n<h3><span id=\"DNS_Panelini_Ajans_Tarafina_Tasimak_Nameserver_Degisimi\">DNS Panelini Ajans Taraf\u0131na Ta\u015f\u0131mak: Nameserver De\u011fi\u015fimi<\/span><\/h3>\n<p>Karma modelde s\u0131k yapt\u0131\u011f\u0131m\u0131z \u015feylerden biri de \u015fu: M\u00fc\u015fteriye ait alan ad\u0131, m\u00fc\u015fterinin registrar hesab\u0131nda kal\u0131r; ancak nameserver kay\u0131tlar\u0131, ajans\u0131n y\u00f6netebildi\u011fi DNS altyap\u0131s\u0131na y\u00f6nlendirilir. \u00d6rne\u011fin:<\/p>\n<ul>\n<li>Alan ad\u0131n\u0131n NS kay\u0131tlar\u0131, DCHost \u00fczerindeki DNS sunucular\u0131na y\u00f6nlendirilir.<\/li>\n<li>DNS kay\u0131tlar\u0131n\u0131n (A, AAAA, MX, TXT, CNAME, SRV, CAA vb.) tamam\u0131, ajans\u0131n eri\u015febildi\u011fi tek bir merkezden y\u00f6netilir.<\/li>\n<li>Yeni sunucuya ge\u00e7i\u015f veya e-posta altyap\u0131s\u0131 de\u011fi\u015fikli\u011fi gerekti\u011finde, her seferinde m\u00fc\u015fteriden panel bilgisi istemek zorunda kal\u0131nmaz.<\/li>\n<\/ul>\n<p>DNS kay\u0131t t\u00fcrleri ve hangi kayd\u0131n ne i\u015fe yarad\u0131\u011f\u0131n\u0131 anlamak i\u00e7in; ajans ekiplerinizi mutlaka <a href=\"https:\/\/www.dchost.com\/blog\/dns-kayitlari-adan-zye-a-aaaa-cname-mx-txt-srv-caa-ve-sizi-yakan-o-kucuk-hatalar\/\">DNS kay\u0131tlar\u0131n\u0131 A\u2019dan Z\u2019ye anlatt\u0131\u011f\u0131m\u0131z rehber<\/a> ile e\u011fitmeyi d\u00fc\u015f\u00fcnebilirsiniz. DNS temelleri sa\u011flam olan ekipler, de\u011fi\u015fiklikleri hem daha h\u0131zl\u0131 hem de daha g\u00fcvenli uygular.<\/p>\n<h2><span id=\"Dokumantasyon_Ajansin_Hayatini_Kurtaran_Gorunmez_Katman\">Dok\u00fcmantasyon: Ajans\u0131n Hayat\u0131n\u0131 Kurtaran G\u00f6r\u00fcnmez Katman<\/span><\/h2>\n<p>G\u00fcvenli eri\u015fim sadece do\u011fru yetki vermekle bitmiyor; en az onun kadar \u00f6nemli olan \u015fey, <strong>t\u00fcm alan adlar\u0131 ve DNS de\u011fi\u015fiklikleri i\u00e7in sistematik bir dok\u00fcmantasyon<\/strong> tutmak. \u0130yi dok\u00fcmantasyonun pratikte sa\u011flad\u0131\u011f\u0131 faydalar:<\/p>\n<ul>\n<li>Yeni bir ekip \u00fcyesi geldi\u011finde, m\u00fc\u015fterinin alan ad\u0131 altyap\u0131s\u0131n\u0131 anlamak i\u00e7in g\u00fcnlerce e-posta ar\u015fivini taramak zorunda kalmaz.<\/li>\n<li>Gece bir kesinti ya\u015fand\u0131\u011f\u0131nda, \u201ckim neyi bozdu\u201d tart\u0131\u015fmas\u0131 yerine, de\u011fi\u015fiklik loguna bak\u0131p do\u011frudan geri d\u00f6n\u00fc\u015f yap\u0131labilir.<\/li>\n<li>M\u00fc\u015fteri taraf\u0131ndaki IT ekibi de\u011fi\u015fti\u011finde bile, ajans\u0131n elinde teknik ger\u00e7ekli\u011fi g\u00f6steren g\u00fcncel bir kay\u0131t bulunur.<\/li>\n<\/ul>\n<h3><span id=\"Asgari_Duzeyde_Olmasi_Gereken_Dokuman_Seti\">Asgari D\u00fczeyde Olmas\u0131 Gereken Dok\u00fcman Seti<\/span><\/h3>\n<p>Ajans\u0131n\u0131z i\u00e7in pratik, ama g\u00fc\u00e7l\u00fc bir dok\u00fcmantasyon seti \u015f\u00f6yle olabilir:<\/p>\n<ul>\n<li><strong>Alan Ad\u0131 Envanteri:<\/strong> Her m\u00fc\u015fteri i\u00e7in a\u015fa\u011f\u0131daki bilgileri i\u00e7eren bir tablo:\n<ul>\n<li>Alan ad\u0131<\/li>\n<li>Registrar (kay\u0131t kurulu\u015fu) ad\u0131<\/li>\n<li>Domain kimin ad\u0131na kay\u0131tl\u0131 (\u015firket unvan\u0131)<\/li>\n<li>Nameserver\u2019lar<\/li>\n<li>DNS\u2019in nerede y\u00f6netildi\u011fi (DCHost paneli, ba\u015fka bir DNS servisi vb.)<\/li>\n<li>SSL sertifika durumu ve yenileme tarihleri<\/li>\n<li>Alan ad\u0131 biti\u015f tarihi ve yenileme sorumlusu<\/li>\n<\/ul>\n<\/li>\n<li><strong>Eri\u015fim Matrisi:<\/strong> Hangi m\u00fc\u015fteri i\u00e7in hangi panellere kimlerin eri\u015fimi oldu\u011funu g\u00f6steren bir \u00e7izelge (ki\u015fiye \u00f6zel hesaplar, rol ve yetki seviyesi).<\/li>\n<li><strong>De\u011fi\u015fiklik Logu:<\/strong> Her DNS de\u011fi\u015fikli\u011fi i\u00e7in tarih, yapan ki\u015fi, yap\u0131lan i\u015flem, \u00f6nceki ve yeni de\u011fer, gerek\u00e7e ve varsa ilgili ticket numaras\u0131n\u0131 i\u00e7eren kay\u0131t.<\/li>\n<li><strong>Runbook\u2019lar:<\/strong> \u201cYeni site yay\u0131na alma\u201d, \u201cSunucu ta\u015f\u0131ma\u201d, \u201cE-posta altyap\u0131s\u0131n\u0131 de\u011fi\u015ftirme\u201d gibi s\u0131k yapt\u0131\u011f\u0131n\u0131z i\u015fler i\u00e7in ad\u0131m ad\u0131m prosed\u00fcrler.<\/li>\n<\/ul>\n<p>Alan ad\u0131 envanteri ve portf\u00f6y\u00fc b\u00fcy\u00fcyen ajanslar i\u00e7in, bu s\u00fcreci nas\u0131l \u00f6l\u00e7ekleyebilece\u011finizi <a href=\"https:\/\/www.dchost.com\/blog\/alan-adi-portfoy-yonetimi-onlarca-domaini-kontrol-altina-alma-rehberi\/\">alan ad\u0131 portf\u00f6y y\u00f6netimi rehberimizde<\/a> detayl\u0131 anlatt\u0131k. Oradaki prensipleri ajans \u00f6l\u00e7e\u011fine uyarlayarak, 20\u201330 m\u00fc\u015fteriden sonra bile kontrol\u00fc kaybetmeyen bir yap\u0131 kurabilirsiniz.<\/p>\n<h3><span id=\"Dokumantasyonu_Nerede_Tutmali_Not_Sadece_Excel_Yetmez\">Dok\u00fcmantasyonu Nerede Tutmal\u0131? (Not: Sadece Excel Yetmez)<\/span><\/h3>\n<p>\u0130lk ad\u0131mda bir tablo (Google Sheets, Excel, Notion vb.) ile ba\u015flamak do\u011fal; ancak bir noktadan sonra merkezi ve denetlenebilir bir sisteme ihtiya\u00e7 duyars\u0131n\u0131z. \u00d6nerdi\u011fimiz yakla\u015f\u0131m:<\/p>\n<ul>\n<li>Alan ad\u0131 envanteri ve eri\u015fim matrisi gibi \u201cstatik\u201d bilgileri, herkesin g\u00fcncelleyebildi\u011fi ama de\u011fi\u015fiklik ge\u00e7mi\u015finin tutuldu\u011fu bir ortamda saklamak.<\/li>\n<li>DNS de\u011fi\u015fiklik loglar\u0131n\u0131, ajans i\u00e7i ticket sistemi veya proje y\u00f6netim arac\u0131 \u00fczerinden takip etmek (her DNS de\u011fi\u015fikli\u011finin kar\u015f\u0131l\u0131\u011f\u0131nda bir g\u00f6rev\/ticket olsun).<\/li>\n<li>Kritik zone dosyalar\u0131n\u0131n (DNS yap\u0131land\u0131rmalar\u0131n\u0131n) d\u00fczenli ar\u015fivlerini al\u0131p, m\u00fcmk\u00fcnse versiyon kontroll\u00fc bir depoda (Git repo vb.) saklamak.<\/li>\n<\/ul>\n<p>B\u00f6ylece hem de\u011fi\u015fikliklerin izini s\u00fcrebilir hem de gerekti\u011finde \u201crollback\u201d (geri alma) yapabilirsiniz. DNSSEC, Registrar Lock, Whois gizlili\u011fi ve 2FA gibi g\u00fcvenlik ayarlar\u0131n\u0131n da d\u00fczenli aral\u0131klarla g\u00f6zden ge\u00e7irilmesi i\u00e7in, bir kontrol listesi haz\u0131rlamakta fayda var. Bunun i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/alan-adi-guvenligi-rehberi-registrar-lock-dnssec-whois-gizliligi-ve-2fa\/\">alan ad\u0131 g\u00fcvenli\u011fi rehberimizdeki checklist<\/a>i ajans s\u00fcre\u00e7lerinize entegre edebilirsiniz.<\/p>\n<h2><span id=\"Operasyonel_Surecler_Onboarding_Degisiklik_Yonetimi_ve_Offboarding\">Operasyonel S\u00fcre\u00e7ler: Onboarding, De\u011fi\u015fiklik Y\u00f6netimi ve Offboarding<\/span><\/h2>\n<p>Teknik modeli ve dok\u00fcmantasyonu belirledikten sonra, hepsini bir araya getiren \u015fey <strong>operasyonel s\u00fcre\u00e7ler<\/strong> oluyor. \u00d6zellikle ajanslar i\u00e7in \u00fc\u00e7 kritik s\u00fcre\u00e7 var: Yeni m\u00fc\u015fteri kazan\u0131m\u0131 (onboarding), devam eden de\u011fi\u015fiklikler ve ili\u015fki sonland\u0131\u011f\u0131nda ayr\u0131lma (offboarding).<\/p>\n<h3><span id=\"Yeni_Musteri_Onboarding_Ilk_Gun_Yapilmasi_Gerekenler\">Yeni M\u00fc\u015fteri Onboarding: \u0130lk G\u00fcn Yap\u0131lmas\u0131 Gerekenler<\/span><\/h3>\n<p>Yeni bir m\u00fc\u015fteriyle \u00e7al\u0131\u015fmaya ba\u015flad\u0131\u011f\u0131n\u0131zda, daha ilk haftada \u015fu ad\u0131mlar\u0131 atman\u0131z i\u015fleri y\u0131llarca kolayla\u015ft\u0131r\u0131r:<\/p>\n<ol>\n<li><strong>Alan Ad\u0131 Durum Analizi:<\/strong> M\u00fc\u015fterinin hangi alan adlar\u0131na sahip oldu\u011funu, hangi TLD\u2019lerde (\u00f6rne\u011fin .com, .com.tr, .io vb.) yay\u0131n yapt\u0131\u011f\u0131n\u0131 netle\u015ftirin. Gerekirse, marka korumas\u0131 i\u00e7in ek domain \u00f6nerilerini de i\u00e7eren k\u00fc\u00e7\u00fck bir rapor haz\u0131rlay\u0131n.<\/li>\n<li><strong>Registrar ve DNS Haritas\u0131:<\/strong> Her domain\u2019in nerede kay\u0131tl\u0131 oldu\u011funu, DNS\u2019ini kimin y\u00f6netti\u011fini, nameserver\u2019lar\u0131n ne oldu\u011funu \u00e7\u0131kar\u0131n.<\/li>\n<li><strong>Eri\u015fim Modelini Kararla\u015ft\u0131r\u0131n:<\/strong> M\u00fc\u015fteriyle birlikte, yukar\u0131da anlatt\u0131\u011f\u0131m\u0131z \u00fc\u00e7 modelden hangisinin se\u00e7ilece\u011fine karar verin (m\u00fc\u015fteri hesab\u0131na yetki, ajans hesab\u0131nda domain, karma model).<\/li>\n<li><strong>Yetki Talebi:<\/strong> \u015eifre istemek yerine, m\u00fc\u015fteriden ajans i\u00e7in ayr\u0131 kullan\u0131c\u0131 olu\u015fturmas\u0131n\u0131 ve gerekli yetkileri tan\u0131mlamas\u0131n\u0131 isteyin.<\/li>\n<li><strong>Envanter ve Dok\u00fcmantasyon Kayd\u0131:<\/strong> T\u00fcm bu bilgileri ajans\u0131n\u0131z\u0131n alan ad\u0131 envanterine i\u015fleyin; eri\u015fim matrisi ve g\u00fcvenlik checklist\u2019lerini doldurun.<\/li>\n<\/ol>\n<p>Bu s\u00fcreci standart bir \u201conboarding formu\u201d ile desteklemek, hem teknik ekiplerin y\u00fck\u00fcn\u00fc hafifletir hem de m\u00fc\u015fteri g\u00f6z\u00fcnde ajans\u0131n\u0131z\u0131n kurumsall\u0131\u011f\u0131n\u0131 g\u00fc\u00e7lendirir.<\/p>\n<h3><span id=\"DNS_Degisiklik_Yonetimi_Her_Degisiklik_Kucuk_Bir_Projedir\">DNS De\u011fi\u015fiklik Y\u00f6netimi: Her De\u011fi\u015fiklik K\u00fc\u00e7\u00fck Bir Projedir<\/span><\/h3>\n<p>DNS taraf\u0131nda yap\u0131lan her de\u011fi\u015fiklik, ne kadar k\u00fc\u00e7\u00fck g\u00f6r\u00fcn\u00fcrse g\u00f6r\u00fcns\u00fcn, canl\u0131 trafi\u011fi etkileyebilir. Bu y\u00fczden ajans i\u00e7inde k\u00fc\u00e7\u00fck ama etkili bir de\u011fi\u015fiklik y\u00f6netimi s\u00fcreci kurgulamak gerekir:<\/p>\n<ul>\n<li>Her de\u011fi\u015fiklik i\u00e7in <strong>ticket\/g\u00f6rev<\/strong> a\u00e7\u0131lmas\u0131 (kim istedi, neden istedi, hedef tarih nedir?).<\/li>\n<li>De\u011fi\u015fiklikten \u00f6nce ilgili kay\u0131tlar\u0131n <strong>eski de\u011ferlerinin not edilmesi<\/strong> (gerekirse ekran g\u00f6r\u00fcnt\u00fcs\u00fc veya zone export).<\/li>\n<li>\u00d6zellikle IP veya MX de\u011fi\u015fikliklerinde, <strong>TTL stratejisi<\/strong> belirlenmesi (\u00f6nce TTL d\u00fc\u015f\u00fcr, sonra de\u011fi\u015fiklik yap, sonra tekrar y\u00fckselt gibi). Bu konuda <a href=\"https:\/\/www.dchost.com\/blog\/zero-downtime-tasima-icin-ttl-stratejileri-dns-yayilimini-gercekten-nasil-hizlandirirsin\/\">s\u0131f\u0131r kesintiyle DNS ta\u015f\u0131ma i\u00e7in TTL rehberimiz<\/a> size pratik bir oyun plan\u0131 sunuyor.<\/li>\n<li>De\u011fi\u015fiklik sonras\u0131 <strong>temel kontrollerin<\/strong> yap\u0131lmas\u0131: DNS lookup, HTTP\/HTTPS eri\u015fimi, e-posta testleri vb.<\/li>\n<li>T\u00fcm ad\u0131mlar\u0131n de\u011fi\u015fiklik loguna i\u015flenmesi.<\/li>\n<\/ul>\n<p>Bu yakla\u015f\u0131m, \u00f6zellikle yo\u011fun kampanya d\u00f6nemlerinde (Black Friday, lansman haftalar\u0131, TV reklam\u0131 \u00f6ncesi) hayat kurtar\u0131r. Planl\u0131 DNS de\u011fi\u015fiklikleri sayesinde, yay\u0131nda \u201cs\u00fcrpriz\u201d ya\u015fama ihtimaliniz ciddi oranda azal\u0131r.<\/p>\n<h3><span id=\"Offboarding_Musteri_Ayrilirken_Kopruleri_Yakmamak\">Offboarding: M\u00fc\u015fteri Ayr\u0131l\u0131rken K\u00f6pr\u00fcleri Yakmamak<\/span><\/h3>\n<p>Ajans\u2013m\u00fc\u015fteri ili\u015fkisi sonsuza kadar s\u00fcrmeyebilir; \u00f6nemli olan ili\u015fkiden nas\u0131l \u00e7\u0131kt\u0131\u011f\u0131n\u0131z. DNS ve alan ad\u0131 taraf\u0131nda temiz bir offboarding s\u00fcreci, markan\u0131z\u0131n itibar\u0131n\u0131 korur:<\/p>\n<ul>\n<li>M\u00fc\u015fteriyle, alan adlar\u0131n\u0131n durumunu (m\u00fclkiyet, yenileme tarihleri, nameserver\u2019lar) netle\u015ftiren k\u0131sa bir rapor payla\u015f\u0131n.<\/li>\n<li>E\u011fer alan adlar\u0131 ajans hesab\u0131n\u0131zda ise, <strong>transfer s\u00fcrecini<\/strong> (EPP kodu, transfer kilidi kald\u0131rma vb.) planl\u0131 ve dok\u00fcmante \u015fekilde y\u00fcr\u00fct\u00fcn. Bu konuda <a href=\"https:\/\/www.dchost.com\/blog\/alan-adi-transferi-nasil-yapilir-epp-kodu-transfer-kilidi-ve-kesintisiz-gecise-sakin-bir-rehber\/\">alan ad\u0131 transfer rehberimizdeki ad\u0131mlar\u0131<\/a> takip edebilirsiniz.<\/li>\n<li>M\u00fc\u015fterinin DNS y\u00f6netimi ba\u015fka bir ajansa veya kendi IT ekibine devredilecekse, mevcut zone dosyalar\u0131n\u0131n export\u2019unu ve k\u0131sa bir teknik notu (hangi kay\u0131t ne i\u015fe yar\u0131yor) teslim edin.<\/li>\n<li>Ajans i\u00e7i eri\u015fimleri kapat\u0131n: \u0130lgili t\u00fcm alt kullan\u0131c\u0131lar\u0131, API anahtarlar\u0131n\u0131 ve SSH anahtarlar\u0131n\u0131 iptal etti\u011finizden emin olun.<\/li>\n<\/ul>\n<p>Bu yakla\u015f\u0131m, m\u00fc\u015fteriden ayr\u0131l\u0131rken bile \u201cbu ajans i\u015fini d\u00fczg\u00fcn yap\u0131yor\u201d alg\u0131s\u0131n\u0131 g\u00fc\u00e7lendirir ve gelecekte farkl\u0131 bir projede yollar\u0131n yeniden kesi\u015fmesinin \u00f6n\u00fcn\u00fc a\u00e7ar.<\/p>\n<h2><span id=\"DCHost_ile_DNS_ve_Alan_Adi_Altyapisini_Merkezi_ve_Guvenli_Yonetmek\">DCHost ile DNS ve Alan Ad\u0131 Altyap\u0131s\u0131n\u0131 Merkezi ve G\u00fcvenli Y\u00f6netmek<\/span><\/h2>\n<p>Ajanslar i\u00e7in en b\u00fcy\u00fck zorluklardan biri, altyap\u0131n\u0131n \u00e7ok par\u00e7al\u0131 hale gelmesidir: Baz\u0131 siteler <a href=\"https:\/\/www.dchost.com\/tr\/web-hosting\">payla\u015f\u0131ml\u0131 hosting<\/a>\u2019te, baz\u0131lar\u0131 VPS\u2019te, baz\u0131lar\u0131 \u00f6zel sunucuda; DNS kimi zaman registrar\u2019da, kimi zaman farkl\u0131 bir servis sa\u011flay\u0131c\u0131da. Biz DCHost olarak ajanslarla \u00e7al\u0131\u015f\u0131rken m\u00fcmk\u00fcn oldu\u011funca <strong>merkez\u00ee, ama esnek<\/strong> bir mimari kurmaya odaklan\u0131yoruz.<\/p>\n<p>\u00d6rne\u011fin:<\/p>\n<ul>\n<li>Kritik m\u00fc\u015fteriler i\u00e7in performans ve izolasyon ihtiyac\u0131na g\u00f6re <strong>VPS veya <a href=\"https:\/\/www.dchost.com\/tr\/fiziksel-sunucu\">dedicated sunucu<\/a><\/strong> \u00e7\u00f6z\u00fcmleriyle birlikte, t\u00fcm DNS kay\u0131tlar\u0131n\u0131 tek bir noktadan y\u00f6netece\u011finiz bir yap\u0131 tasarl\u0131yoruz.<\/li>\n<li>Daha k\u00fc\u00e7\u00fck hacimli projeler i\u00e7in, <strong>payla\u015f\u0131ml\u0131 hosting ve reseller hosting<\/strong> altyap\u0131s\u0131n\u0131 kullanarak, ajans\u0131n t\u00fcm sitelerini tek panelden izlemesini sa\u011fl\u0131yoruz.<\/li>\n<li>Y\u00fcksek trafik veya \u00f6zel g\u00fcvenlik gereksinimi olan projelerde, <strong>colocation<\/strong> ve \u00f6zel a\u011f tasar\u0131mlar\u0131yla DNS\u2013sunucu\u2013CDN zincirini ba\u015ftan sona planl\u0131yoruz.<\/li>\n<\/ul>\n<p>Bu mimarinin en \u00f6nemli par\u00e7as\u0131, <strong>DNS eri\u015fim ve dok\u00fcmantasyon modelinin<\/strong> ba\u015ftan beraber kurgulanmas\u0131. Ajans ekiplerinizle yapt\u0131\u011f\u0131m\u0131z teknik planlama toplant\u0131lar\u0131nda, hangi sitenin hangi sunucuda, hangi alan ad\u0131n\u0131n hangi nameserver\u2019da, hangi kay\u0131tlar\u0131n hangi ortama i\u015faret etti\u011fini netle\u015ftiriyoruz. \u00d6zellikle \u00e7ok b\u00f6lgeli, \u00e7ok dilli ve \u00e7ok alan adl\u0131 yap\u0131larda; <a href=\"https:\/\/www.dchost.com\/blog\/cok-dilli-kurumsal-siteler-icin-domain-ve-hosting-mimarisi\/\">\u00e7ok dilli kurumsal siteler i\u00e7in domain ve hosting mimarisi rehberimizde<\/a> payla\u015ft\u0131\u011f\u0131m\u0131z prensipleri uygulayarak kar\u0131\u015f\u0131kl\u0131\u011f\u0131 en ba\u015ftan engelliyoruz.<\/p>\n<p>Ajanslar\u0131n i\u00e7 s\u00fcre\u00e7leri iyi oldu\u011funda, \u00fcst\u00fcne kurulan altyap\u0131 da \u00e7ok daha s\u00fcrd\u00fcr\u00fclebilir hale geliyor. Teknik tarafta biz DCHost olarak, siz de i\u00e7 s\u00fcre\u00e7 ve dok\u00fcmantasyon taraf\u0131nda \u00fczerine d\u00fc\u015feni yapt\u0131\u011f\u0131n\u0131zda; DNS ve alan ad\u0131 eri\u015fimi, \u201ckriz an\u0131nda panik olunan\u201d bir konu olmaktan \u00e7\u0131k\u0131p, <strong>kontrol\u00fcn\u00fcz alt\u0131nda, tahmin edilebilir<\/strong> bir alana d\u00f6n\u00fc\u015f\u00fcyor.<\/p>\n<h2><span id=\"Sonuc_ve_Yol_Haritasi_Ajansiniz_Icin_Uygulanabilir_Bir_Model_Kurun\">Sonu\u00e7 ve Yol Haritas\u0131: Ajans\u0131n\u0131z \u0130\u00e7in Uygulanabilir Bir Model Kurun<\/span><\/h2>\n<p>DNS ve alan ad\u0131 y\u00f6netimi, ajanslar\u0131n \u00e7o\u011funda \u201cen s\u0131k\u0131nt\u0131 \u00e7\u0131kan ama en az konu\u015fulan\u201d ba\u015fl\u0131klardan biri. M\u00fc\u015fteri taraf\u0131ndaki da\u011f\u0131n\u0131k hesaplar, ekip i\u00e7i \u015fifre payla\u015f\u0131mlar\u0131, dok\u00fcmante edilmemi\u015f de\u011fi\u015fiklikler ve plans\u0131z offboarding s\u00fcre\u00e7leri bir araya geldi\u011finde; k\u00fc\u00e7\u00fck bir DNS kayd\u0131 de\u011fi\u015fikli\u011fi bile gecenizi g\u00fcnd\u00fcz\u00fcn\u00fcze katabiliyor.<\/p>\n<p>Bu yaz\u0131da anlatt\u0131\u011f\u0131m\u0131z \u00e7er\u00e7eveyi \u00f6zetlersek:<\/p>\n<ul>\n<li>\u00d6nce eri\u015fim modelinizi se\u00e7in: M\u00fc\u015fteri hesab\u0131na do\u011frudan girmek yerine, m\u00fcmk\u00fcn oldu\u011funca <strong>yetki bazl\u0131, rol ayr\u0131ml\u0131<\/strong> bir yap\u0131 kurun.<\/li>\n<li>Alan adlar\u0131n\u0131n m\u00fclkiyetini m\u00fc\u015fteride b\u0131rak\u0131p, DNS y\u00f6netimini ajans taraf\u0131nda toplad\u0131\u011f\u0131n\u0131z <strong>karma modeli<\/strong> g\u00f6zden ge\u00e7irin.<\/li>\n<li>T\u00fcm alan adlar\u0131 ve DNS kay\u0131tlar\u0131 i\u00e7in <strong>envanter, eri\u015fim matrisi ve de\u011fi\u015fiklik logu<\/strong> tutmay\u0131 ajans k\u00fclt\u00fcr\u00fcn\u00fcz\u00fcn par\u00e7as\u0131 haline getirin.<\/li>\n<li>Onboarding, de\u011fi\u015fiklik y\u00f6netimi ve offboarding s\u00fcre\u00e7lerini yaz\u0131l\u0131 hale getirip, her yeni m\u00fc\u015fteri ve her yeni ekip \u00fcyesi i\u00e7in tekrar tekrar kullan\u0131n.<\/li>\n<li>G\u00fcvenlik taraf\u0131nda DNSSEC, registrar lock, 2FA ve TTL stratejisi gibi konular\u0131 checklist\u2019lerinize ekleyin.<\/li>\n<\/ul>\n<p>E\u011fer ajans\u0131n\u0131z i\u00e7in \u201cDNS ve alan ad\u0131 taraf\u0131n\u0131 ba\u015ftan a\u015fa\u011f\u0131 toparlayal\u0131m, merkezi ve \u00f6l\u00e7eklenebilir bir altyap\u0131 kural\u0131m\u201d diyorsan\u0131z; DCHost ekibi olarak sizinle teknik bir ke\u015fif toplant\u0131s\u0131 yapmaktan memnuniyet duyar\u0131z. Birlikte hem hosting (payla\u015f\u0131ml\u0131, VPS, dedicated, colocation) altyap\u0131n\u0131z\u0131 hem de DNS eri\u015fim ve dok\u00fcmantasyon modelinizi g\u00f6zden ge\u00e7irip; ajans\u0131n\u0131za y\u0131llarca rahat ettirecek bir yol haritas\u0131 \u00e7\u0131karabiliriz. B\u00f6ylece bir sonraki b\u00fcy\u00fck kampanyada, akl\u0131n\u0131z kreatifte ve sonu\u00e7larda olur; altyap\u0131 taraf\u0131 sessizce, sorunsuzca \u00e7al\u0131\u015fmaya devam eder.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>\u0130&ccedil;indekiler1 Ajanslar \u0130\u00e7in DNS ve Alan Ad\u0131 Eri\u015fimi Neden Kritik Bir Konu?2 Alan Ad\u0131 ve DNS Eri\u015fim Modelleri: Temel Stratejiyi Do\u011fru Kurmak2.1 1) M\u00fc\u015fterinin Alan Ad\u0131 Hesab\u0131na Do\u011frudan Giri\u015f (Klasik, Riskli Yol)2.2 2) Ajans Hesab\u0131nda Alan Ad\u0131 Bar\u0131nd\u0131rma (Merkezi Ama Sahiplik Riskli)2.3 3) Karma Model: M\u00fc\u015fteri Hesab\u0131nda Sahiplik, Ajans Taraf\u0131nda DNS Y\u00f6netimi3 G\u00fcvenli Eri\u015fim Tasar\u0131m\u0131: [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":2840,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-2839","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\/2839","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=2839"}],"version-history":[{"count":0,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/2839\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/2840"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=2839"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=2839"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=2839"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}