{"id":3779,"date":"2025-12-30T22:51:39","date_gmt":"2025-12-30T19:51:39","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/ajanslar-icin-multi-tenant-e-posta-ve-dns-mimarisi-tek-sunucuda-onlarca-musteri-yonetmek\/"},"modified":"2025-12-30T22:51:39","modified_gmt":"2025-12-30T19:51:39","slug":"ajanslar-icin-multi-tenant-e-posta-ve-dns-mimarisi-tek-sunucuda-onlarca-musteri-yonetmek","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/ajanslar-icin-multi-tenant-e-posta-ve-dns-mimarisi-tek-sunucuda-onlarca-musteri-yonetmek\/","title":{"rendered":"Ajanslar \u0130\u00e7in Multi-Tenant E\u2011Posta ve DNS Mimarisi: Tek Sunucuda Onlarca M\u00fc\u015fteri Y\u00f6netmek"},"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_Multi-Tenant_EPosta_ve_DNS_Neden_Kritik_Hale_Geldi\"><span class=\"toc_number toc_depth_1\">1<\/span> Ajanslar \u0130\u00e7in Multi-Tenant E\u2011Posta ve DNS Neden Kritik Hale Geldi?<\/a><\/li><li><a href=\"#Temel_Kavramlar_Multi-Tenant_Tek_VPS_ve_Reseller_Yapisi\"><span class=\"toc_number toc_depth_1\">2<\/span> Temel Kavramlar: Multi-Tenant, Tek VPS ve Reseller Yap\u0131s\u0131<\/a><\/li><li><a href=\"#Mimari_Secenekler_Tek_VPS_mi_Reseller_mi\"><span class=\"toc_number toc_depth_1\">3<\/span> Mimari Se\u00e7enekler: Tek VPS mi Reseller m\u0131?<\/a><ul><li><a href=\"#Reseller_Hosting_Tercih_Etmeniz_Mantikli_Oldugu_Durumlar\"><span class=\"toc_number toc_depth_2\">3.1<\/span> Reseller Hosting Tercih Etmeniz Mant\u0131kl\u0131 Oldu\u011fu Durumlar<\/a><\/li><li><a href=\"#Tek_VPS_veya_Dedicated_Tercih_Etmeniz_Mantikli_Oldugu_Durumlar\"><span class=\"toc_number toc_depth_2\">3.2<\/span> Tek VPS (veya Dedicated) Tercih Etmeniz Mant\u0131kl\u0131 Oldu\u011fu Durumlar<\/a><\/li><\/ul><\/li><li><a href=\"#DNS_Mimarisi_Onlarca_Musteri_Icin_Yonetilebilir_Yapi\"><span class=\"toc_number toc_depth_1\">4<\/span> DNS Mimarisi: Onlarca M\u00fc\u015fteri \u0130\u00e7in Y\u00f6netilebilir Yap\u0131<\/a><ul><li><a href=\"#Nameserver_ve_Zone_Stratejisi\"><span class=\"toc_number toc_depth_2\">4.1<\/span> Nameserver ve Zone Stratejisi<\/a><\/li><li><a href=\"#Ajanslarda_Sik_Gorulen_DNS_Anti-Patternleri\"><span class=\"toc_number toc_depth_2\">4.2<\/span> Ajanslarda S\u0131k G\u00f6r\u00fclen DNS Anti-Pattern\u2019leri<\/a><\/li><li><a href=\"#Gelismis_DNS_Guvenligi_ve_Otomasyon\"><span class=\"toc_number toc_depth_2\">4.3<\/span> Geli\u015fmi\u015f DNS G\u00fcvenli\u011fi ve Otomasyon<\/a><\/li><\/ul><\/li><li><a href=\"#EPosta_Mimarisi_Teslim_Edilebilirlik_ve_Itibar_Odakli_Tasarim\"><span class=\"toc_number toc_depth_1\">5<\/span> E\u2011Posta Mimarisi: Teslim Edilebilirlik ve \u0130tibar Odakl\u0131 Tasar\u0131m<\/a><ul><li><a href=\"#Temel_Kayit_Sablonu_MX_SPF_DKIM_DMARC\"><span class=\"toc_number toc_depth_2\">5.1<\/span> Temel Kay\u0131t \u015eablonu: MX, SPF, DKIM, DMARC<\/a><\/li><li><a href=\"#IP_Adresi_Reverse_DNS_ve_IP_Isitma\"><span class=\"toc_number toc_depth_2\">5.2<\/span> IP Adresi, Reverse DNS ve IP Is\u0131tma<\/a><\/li><li><a href=\"#Tenant_Basina_Izolasyon_Kota_ve_Rate_Limit\"><span class=\"toc_number toc_depth_2\">5.3<\/span> Tenant Ba\u015f\u0131na \u0130zolasyon, Kota ve Rate Limit<\/a><\/li><li><a href=\"#Ileri_Seviye_MTA-STS_TLS-RPT_BIMI_ve_MTA_Guvenligi\"><span class=\"toc_number toc_depth_2\">5.4<\/span> \u0130leri Seviye: MTA-STS, TLS-RPT, BIMI ve MTA G\u00fcvenli\u011fi<\/a><\/li><\/ul><\/li><li><a href=\"#Tek_Sunucuda_Guvenlik_Yedekleme_ve_Izleme\"><span class=\"toc_number toc_depth_1\">6<\/span> Tek Sunucuda G\u00fcvenlik, Yedekleme ve \u0130zleme<\/a><ul><li><a href=\"#Panel_ve_Sunucu_Erisimi\"><span class=\"toc_number toc_depth_2\">6.1<\/span> Panel ve Sunucu Eri\u015fimi<\/a><\/li><li><a href=\"#Yedekleme_ve_Felaket_Kurtarma\"><span class=\"toc_number toc_depth_2\">6.2<\/span> Yedekleme ve Felaket Kurtarma<\/a><\/li><li><a href=\"#Izleme_Loglama_ve_Alarm_Mekanizmalari\"><span class=\"toc_number toc_depth_2\">6.3<\/span> \u0130zleme, Loglama ve Alarm Mekanizmalar\u0131<\/a><\/li><\/ul><\/li><li><a href=\"#Operasyonel_Akis_Yeni_Musteri_Acilisindan_Tasima_Sureclerine\"><span class=\"toc_number toc_depth_1\">7<\/span> Operasyonel Ak\u0131\u015f: Yeni M\u00fc\u015fteri A\u00e7\u0131l\u0131\u015f\u0131ndan Ta\u015f\u0131ma S\u00fcre\u00e7lerine<\/a><ul><li><a href=\"#Yeni_Musteri_Icin_Onerilen_Adim_Adim_Akis\"><span class=\"toc_number toc_depth_2\">7.1<\/span> Yeni M\u00fc\u015fteri \u0130\u00e7in \u00d6nerilen Ad\u0131m Ad\u0131m Ak\u0131\u015f<\/a><\/li><li><a href=\"#Mevcut_EPosta_Altyapisini_Tasirken_Dikkat_Edilecekler\"><span class=\"toc_number toc_depth_2\">7.2<\/span> Mevcut E\u2011Posta Altyap\u0131s\u0131n\u0131 Ta\u015f\u0131rken Dikkat Edilecekler<\/a><\/li><\/ul><\/li><li><a href=\"#DCHost_Uzerinde_Uygulanabilir_Ornek_Senaryolar\"><span class=\"toc_number toc_depth_1\">8<\/span> DCHost \u00dczerinde Uygulanabilir \u00d6rnek Senaryolar<\/a><ul><li><a href=\"#1_Kucuk_Ajans_Reseller_Standart_DNSEPosta\"><span class=\"toc_number toc_depth_2\">8.1<\/span> 1) K\u00fc\u00e7\u00fck Ajans: Reseller + Standart DNS\/E\u2011Posta<\/a><\/li><li><a href=\"#2_Orta_Olcek_Ajans_Tek_Guclu_VPS_Uzerinde_Multi-Tenant_Panel\"><span class=\"toc_number toc_depth_2\">8.2<\/span> 2) Orta \u00d6l\u00e7ek Ajans: Tek G\u00fc\u00e7l\u00fc VPS \u00dczerinde Multi-Tenant Panel<\/a><\/li><li><a href=\"#3_Buyuk_Ajans_SaaS_Benzeri_Platform_Cok_VPS_Ayri_Mail_Nodlari\"><span class=\"toc_number toc_depth_2\">8.3<\/span> 3) B\u00fcy\u00fck Ajans \/ SaaS Benzeri Platform: \u00c7ok VPS + Ayr\u0131 Mail Nodlar\u0131<\/a><\/li><\/ul><\/li><li><a href=\"#Sonuc_Ajanslar_Icin_Yol_Haritasi_ve_Sonraki_Adimlar\"><span class=\"toc_number toc_depth_1\">9<\/span> Sonu\u00e7: Ajanslar \u0130\u00e7in Yol Haritas\u0131 ve Sonraki Ad\u0131mlar<\/a><\/li><\/ul><\/div>\n<h2><span id=\"Ajanslar_Icin_Multi-Tenant_EPosta_ve_DNS_Neden_Kritik_Hale_Geldi\">Ajanslar \u0130\u00e7in Multi-Tenant E\u2011Posta ve DNS Neden Kritik Hale Geldi?<\/span><\/h2>\n<p>Web ajanslar\u0131, dijital pazarlama ekipleri ve freelance geli\u015ftiriciler i\u00e7in en b\u00fcy\u00fck operasyonel y\u00fcklerden biri; onlarca hatta y\u00fczlerce m\u00fc\u015fterinin alan ad\u0131, DNS ve e\u2011posta altyap\u0131s\u0131n\u0131 da\u011f\u0131n\u0131k halde y\u00f6netmek. Bir m\u00fc\u015fterinizin alan ad\u0131 bir yerde, DNS kay\u0131tlar\u0131 ba\u015fka bir yerde, e\u2011posta bamba\u015fka bir sa\u011flay\u0131c\u0131da olunca; basit bir SPF g\u00fcncellemesi bile saatler s\u00fcren, riskli bir i\u015fe d\u00f6n\u00fc\u015febiliyor. Tek bir yanl\u0131\u015f MX kayd\u0131 ya da bozulan bir SPF kayd\u0131 y\u00fcz\u00fcnden m\u00fc\u015fterinin t\u00fcm kurumsal e\u2011postalar\u0131n\u0131n spam\u2019e d\u00fc\u015fmesi, maalesef pratikte \u00e7ok s\u0131k g\u00f6rd\u00fc\u011f\u00fcm\u00fcz bir tablo.<\/p>\n<p>Bu y\u00fczden giderek daha fazla ajans, <strong>multi-tenant (\u00e7ok kirac\u0131l\u0131) bir e\u2011posta ve DNS mimarisini<\/strong> tek bir <a href=\"https:\/\/www.dchost.com\/tr\/vps\">VPS<\/a> veya reseller hosting \u00fczerinde in\u015fa edip t\u00fcm m\u00fc\u015fterilerini merkezi ama izole bi\u00e7imde y\u00f6netme yoluna gidiyor. B\u00f6yle bir mimari sayesinde:<\/p>\n<ul>\n<li>T\u00fcm m\u00fc\u015fterilerin DNS ve e\u2011posta ayarlar\u0131n\u0131 tek panelden g\u00f6rebilir,<\/li>\n<li>Her m\u00fc\u015fteri i\u00e7in g\u00fcvenli izolasyon sa\u011flayabilir,<\/li>\n<li>\u015eablonlar ve otomasyonla yeni m\u00fc\u015fteri kurulum s\u00fcresini dakikalara indirebilir,<\/li>\n<li>\u0130tibar, g\u00fcvenlik ve yedekleme politikalar\u0131n\u0131 t\u00fcm portf\u00f6yde tutarl\u0131 uygulayabilirsiniz.<\/li>\n<\/ul>\n<p>Bu yaz\u0131da DCHost taraf\u0131nda ajanslarla birlikte ger\u00e7ek projelerde \u015fekillendirdi\u011fimiz tecr\u00fcbeleri kullanarak, <strong>tek VPS veya reseller hesap \u00fczerinde onlarca m\u00fc\u015fteriyi y\u00f6netebilece\u011finiz multi-tenant e\u2011posta ve DNS mimarisini<\/strong> ad\u0131m ad\u0131m ele alaca\u011f\u0131z. Hem teknik detaylara girece\u011fiz, hem de ajans bak\u0131\u015f a\u00e7\u0131s\u0131yla operasyonu nas\u0131l sadele\u015ftirebilece\u011finizi konu\u015faca\u011f\u0131z.<\/p>\n<h2><span id=\"Temel_Kavramlar_Multi-Tenant_Tek_VPS_ve_Reseller_Yapisi\">Temel Kavramlar: Multi-Tenant, Tek VPS ve Reseller Yap\u0131s\u0131<\/span><\/h2>\n<p>\u00d6nce \u00fczerinde konu\u015ftu\u011fumuz kavramlar\u0131 netle\u015ftirelim. Multi-tenant mimari, basit\u00e7e <strong>tek bir altyap\u0131 \u00fczerinde birden \u00e7ok ba\u011f\u0131ms\u0131z m\u00fc\u015fteriyi (tenant) izole \u015fekilde bar\u0131nd\u0131rma<\/strong> yakla\u015f\u0131m\u0131d\u0131r. Ajans senaryosunda her tenant genellikle \u201cbir marka \/ bir \u015firket\u201d anlam\u0131na gelir ve en az bir alan ad\u0131 + e\u2011posta alan ad\u0131ndan olu\u015fur.<\/p>\n<p>Ajans d\u00fcnyas\u0131nda multi-tenant e\u2011posta ve DNS i\u00e7in en s\u0131k g\u00f6rd\u00fc\u011f\u00fcm\u00fcz iki temel se\u00e7enek var:<\/p>\n<ul>\n<li><strong>Tek VPS \u00dczerinde Multi-Tenant Panel<\/strong><br \/>cPanel, DirectAdmin veya benzeri bir paneli DCHost VPS \u00fczerinde kurup her m\u00fc\u015fteriye ayr\u0131 kullan\u0131c\u0131 hesab\u0131 a\u00e7ars\u0131n\u0131z. DNS, e\u2011posta ve web bar\u0131nd\u0131rma ayn\u0131 panel \u00fczerinden y\u00f6netilir.<\/li>\n<li><strong>Reseller Hosting \u00dczerinde \u00c7oklu Hesap<\/strong><br \/>DCHost reseller paketiniz olur; her m\u00fc\u015fteriye ayr\u0131 cPanel\/DirectAdmin hesab\u0131 tan\u0131mlars\u0131n\u0131z. Sunucu y\u00f6netimiyle u\u011fra\u015fmaz, daha \u00e7ok paket ve kota tasar\u0131m\u0131na odaklan\u0131rs\u0131n\u0131z.<\/li>\n<\/ul>\n<p>Bu iki yakla\u015f\u0131m\u0131 detayl\u0131 kar\u015f\u0131la\u015ft\u0131rd\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/reseller-hosting-mi-vps-mi-ajans-ve-freelancerlar-icin-yol-haritasi\/\">&#8220;Reseller hosting mi VPS mi? Ajans ve freelancerlar i\u00e7in yol haritas\u0131&#8221;<\/a> yaz\u0131m\u0131za mutlaka g\u00f6z atman\u0131z\u0131 \u00f6neririm. Burada ise \u00f6zellikle <strong>e\u2011posta ve DNS mimarisi<\/strong> taraf\u0131n\u0131 derinle\u015ftirece\u011fiz.<\/p>\n<h2><span id=\"Mimari_Secenekler_Tek_VPS_mi_Reseller_mi\">Mimari Se\u00e7enekler: Tek VPS mi Reseller m\u0131?<\/span><\/h2>\n<p>Ajanslar\u0131n akl\u0131ndaki ilk soru genelde \u015fu oluyor: \u201cOnlarca m\u00fc\u015fterinin DNS ve e\u2011postas\u0131n\u0131 tek bir g\u00fc\u00e7l\u00fc VPS\u2019te mi toplamal\u0131y\u0131m, yoksa reseller hosting ile mi ba\u015flamal\u0131y\u0131m?\u201d Net ve pratik bir \u00e7er\u00e7eve kural\u0131m.<\/p>\n<h3><span id=\"Reseller_Hosting_Tercih_Etmeniz_Mantikli_Oldugu_Durumlar\">Reseller Hosting Tercih Etmeniz Mant\u0131kl\u0131 Oldu\u011fu Durumlar<\/span><\/h3>\n<ul>\n<li>Sunucu y\u00f6netimiyle (OS g\u00fcncelleme, g\u00fcvenlik duvar\u0131, SMTP tuning vb.) u\u011fra\u015fmak istemiyorsan\u0131z,<\/li>\n<li>\u00d6nceli\u011finiz <strong>h\u0131zl\u0131 devreye alma ve basit y\u00f6netim<\/strong> ise,<\/li>\n<li>Genelde <strong>standart kurumsal siteler + d\u00fc\u015f\u00fck hacimli kurumsal e\u2011posta<\/strong> bar\u0131nd\u0131r\u0131yorsan\u0131z,<\/li>\n<li>Tek teknik ki\u015fiyle 30\u201340 m\u00fc\u015fteriyi ta\u015f\u0131may\u0131 planl\u0131yorsan\u0131z<\/li>\n<\/ul>\n<p>Reseller yap\u0131da DCHost taraf\u0131nda mail ve DNS servisleri zaten optimize ve izlenir gelir; siz daha \u00e7ok <strong>paket limitleri, \u015fifre politikalar\u0131 ve DNS \u015fablonlar\u0131<\/strong> taraf\u0131na odaklan\u0131rs\u0131n\u0131z.<\/p>\n<h3><span id=\"Tek_VPS_veya_Dedicated_Tercih_Etmeniz_Mantikli_Oldugu_Durumlar\">Tek VPS (veya Dedicated) Tercih Etmeniz Mant\u0131kl\u0131 Oldu\u011fu Durumlar<\/span><\/h3>\n<ul>\n<li>SMTP, DNS, g\u00fcvenlik duvar\u0131 ve yedekleme \u00fczerinde daha <strong>ince ayar<\/strong> yapmak istiyorsan\u0131z,<\/li>\n<li>Y\u00fcksek hacimli pazarlama e\u2011postalar\u0131 veya transactional (sistem) e\u2011postalar\u0131 da ayn\u0131 altyap\u0131dan g\u00f6nderecekseniz,<\/li>\n<li>Her m\u00fc\u015fteriye <strong>\u00f6zelle\u015fmi\u015f politikalar<\/strong> (farkl\u0131 kota, farkl\u0131 rate limit, farkl\u0131 IP vb.) tan\u0131mlamak istiyorsan\u0131z,<\/li>\n<li>G\u00fcn\u00fcn sonunda 100+ domain seviyesinde bir portf\u00f6y\u00fc merkezile\u015ftirmeyi hedefliyorsan\u0131z<\/li>\n<\/ul>\n<p>Bu senaryoda DCHost \u00fczerinde NVMe diskli, yeterli RAM\/CPU\u2019ya sahip bir VPS veya ihtiya\u00e7 b\u00fcy\u00fcd\u00fc\u011f\u00fcnde dedicated \/ colocation altyap\u0131s\u0131 ile <strong>kendi \u00e7ok kirac\u0131l\u0131 mail+DNS platformunuzu<\/strong> kurars\u0131n\u0131z. Y\u00f6netim biraz daha teknik bilgi ister ama kar\u015f\u0131l\u0131\u011f\u0131nda esneklik ve kontrol artar.<\/p>\n<h2><span id=\"DNS_Mimarisi_Onlarca_Musteri_Icin_Yonetilebilir_Yapi\">DNS Mimarisi: Onlarca M\u00fc\u015fteri \u0130\u00e7in Y\u00f6netilebilir Yap\u0131<\/span><\/h2>\n<p>Ajanslarda en \u00e7ok hata \u00fcretilen yer genelde DNS taraf\u0131 oluyor. Farkl\u0131 registrar\u2019lar, kar\u0131\u015f\u0131k nameserver\u2019lar, TTL\u2019ler, unutulmu\u015f eski kay\u0131tlar\u2026 Multi-tenant DNS mimarisinde hedefimiz; <strong>t\u00fcm alan adlar\u0131n\u0131 tek bir mant\u0131kl\u0131 \u00e7at\u0131 alt\u0131nda toplamak ve tekrar eden i\u015flemleri otomatikle\u015ftirmek<\/strong>.<\/p>\n<h3><span id=\"Nameserver_ve_Zone_Stratejisi\">Nameserver ve Zone Stratejisi<\/span><\/h3>\n<p>Ajanslar\u0131n b\u00fcy\u00fck \u00e7o\u011funlu\u011fu i\u00e7in en pratik yol, DCHost \u00fczerindeki hosting veya VPS panelini <strong>merkezi DNS sa\u011flay\u0131c\u0131n\u0131z<\/strong> haline getirmek:<\/p>\n<ul>\n<li>T\u00fcm m\u00fc\u015fterilerin domain\u2019lerini ilgili registrar\u2019da tutup,<\/li>\n<li>Nameserver\u2019lar\u0131 ajans\u0131n DCHost DNS altyap\u0131s\u0131na y\u00f6nlendirip,<\/li>\n<li>Her m\u00fc\u015fteri i\u00e7in ayr\u0131 bir DNS zone a\u00e7mak.<\/li>\n<\/ul>\n<p>Tek VPS senaryosunda bu genelde ns1\/ns2 \u015feklinde <strong>\u00f6zel ad sunucusu (glue record) yap\u0131land\u0131r\u0131lm\u0131\u015f<\/strong> NS kay\u0131tlar\u0131yla yap\u0131l\u0131r. Bu yap\u0131y\u0131 ad\u0131m ad\u0131m anlatt\u0131\u011f\u0131m\u0131z <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 rehberi<\/a>, ajans taraf\u0131nda kendi nameserver markan\u0131z\u0131 olu\u015ftururken \u00e7ok i\u015finize yarar.<\/p>\n<p>Reseller taraf\u0131nda ise panelin verdi\u011fi varsay\u0131lan NS kay\u0131tlar\u0131n\u0131 (\u00f6rne\u011fin ns1.ajansdns.com \/ ns2.ajansdns.com gibi) kullanarak daha basit bir yap\u0131 kurabilirsiniz.<\/p>\n<h3><span id=\"Ajanslarda_Sik_Gorulen_DNS_Anti-Patternleri\">Ajanslarda S\u0131k G\u00f6r\u00fclen DNS Anti-Pattern\u2019leri<\/span><\/h3>\n<p>Ger\u00e7ek projelerde en s\u0131k g\u00f6rd\u00fc\u011f\u00fcm\u00fcz problemli desenler \u015funlar:<\/p>\n<ul>\n<li><strong>Farkl\u0131 m\u00fc\u015fterilerde farkl\u0131 NS stratejisi<\/strong>: Bir m\u00fc\u015fteri registrar DNS\u2019inde, di\u011feri Cloud tabanl\u0131 DNS\u2019te, di\u011feri hosting\u2019in NS\u2019inde. T\u00fcm portf\u00f6y\u00fcn durumunu tek bak\u0131\u015fta g\u00f6remiyorsunuz.<\/li>\n<li><strong>TTL\u2019lerin rastgele olmas\u0131<\/strong>: Bir kay\u0131tta 14400, di\u011ferinde 300, baz\u0131s\u0131nda 86400\u2026 Ta\u015f\u0131ma \u00f6ncesi TTL d\u00fc\u015f\u00fcrmeyi unutmak ciddi kesintilere yol a\u00e7\u0131yor.<\/li>\n<li><strong>Bo\u015fta kalm\u0131\u015f, eskiye y\u00f6nlenen kay\u0131tlar<\/strong>: Art\u0131k var olmayan sunuculara bakan A kay\u0131tlar\u0131, eski e\u2011posta servislerine bakan MX kay\u0131tlar\u0131.<\/li>\n<li><strong>Alan adlar\u0131 ve DNS eri\u015fimlerinin da\u011f\u0131n\u0131k olmas\u0131<\/strong>: Kimde hangi panel eri\u015fimi var belli de\u011fil, kay\u0131t de\u011fi\u015ftirme s\u00fcreci uzuyor.<\/li>\n<\/ul>\n<p>Bu konular\u0131 sistematik \u00e7\u00f6zmek i\u00e7in haz\u0131rlad\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/ajanslar-icin-dns-ve-alan-adi-erisimi-yonetimi\/\">&#8220;Ajanslar i\u00e7in DNS ve alan ad\u0131 eri\u015fimi y\u00f6netimi&#8221;<\/a> rehberini mutlaka yan\u0131n\u0131zda tutun; burada anlataca\u011f\u0131m\u0131z mimariyi o eri\u015fim modelinin \u00fczerine in\u015fa etti\u011finizde operasyon \u00e7ok daha temiz hale geliyor.<\/p>\n<h3><span id=\"Gelismis_DNS_Guvenligi_ve_Otomasyon\">Geli\u015fmi\u015f DNS G\u00fcvenli\u011fi ve Otomasyon<\/span><\/h3>\n<p>Ajans olarak onlarca domain y\u00f6netti\u011finizde, \u201cg\u00fcvenlik ayarlar\u0131n\u0131 sonra bakar\u0131z\u201d deme l\u00fcks\u00fcn\u00fcz kalm\u0131yor. \u00d6zellikle e\u2011posta g\u00fcvenli\u011fi ve marka korumas\u0131 i\u00e7in a\u015fa\u011f\u0131daki ad\u0131mlar ajans mimarisinin par\u00e7as\u0131 olmal\u0131:<\/p>\n<ul>\n<li><strong>DNSSEC<\/strong>: Alan adlar\u0131n\u0131z i\u00e7in DNS imzalama ile sahte kay\u0131t riskini azalt\u0131rs\u0131n\u0131z. Temeli i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/dnssec-nedir-ne-ise-yarar-alan-adiniz-ve-hostinginiz-icin-adim-adim-dnssec-kurulum-rehberi\/\">DNSSEC kurulum rehberimize<\/a> g\u00f6z atabilirsiniz.<\/li>\n<li><strong>CAA kay\u0131tlar\u0131<\/strong>: Hangi CA\u2019lar\u0131n sertifika \u00fcretebilece\u011fini s\u0131n\u0131rland\u0131rmak, \u00f6zellikle \u00e7ok domain\u2019li yap\u0131larda \u00f6nemli bir g\u00fcvenlik katman\u0131 ekler.<\/li>\n<li><strong>TXT ve SRV \u015fablonlar\u0131<\/strong>: SPF, DMARC, MTA-STS, BIMI, VoIP vb. kay\u0131tlar\u0131n\u0131 her yeni m\u00fc\u015fteri i\u00e7in manuel yazmak yerine panelde \u015fablonlar olu\u015fturun.<\/li>\n<\/ul>\n<p>Otomasyon taraf\u0131nda, Terraform veya benzeri ara\u00e7larla DNS\u2019i kodla y\u00f6netmek de m\u00fcmk\u00fcn. Bunun DCHost altyap\u0131s\u0131nda nas\u0131l kurgulanabilece\u011fine dair iyi bir bak\u0131\u015f i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/terraform-ile-vps-ve-dns-otomasyonu-cloudflare-proxmox-openstack-ve-sifir-kesinti-dagitim-nasil-bir-araya-gelir\/\">VPS ve DNS otomasyonu rehberimize<\/a> bakabilirsiniz.<\/p>\n<h2><span id=\"EPosta_Mimarisi_Teslim_Edilebilirlik_ve_Itibar_Odakli_Tasarim\">E\u2011Posta Mimarisi: Teslim Edilebilirlik ve \u0130tibar Odakl\u0131 Tasar\u0131m<\/span><\/h2>\n<p>DNS\u2019i oturttuktan sonra as\u0131l kritik konuya geliyoruz: <strong>e\u2011posta teslim edilebilirli\u011fi (deliverability)<\/strong> ve IP itibar y\u00f6netimi. Ajanslar\u0131n s\u0131kl\u0131kla ya\u015fad\u0131\u011f\u0131 problem \u015fudur: Bir m\u00fc\u015fterinin agresif kampanyalar\u0131 di\u011fer t\u00fcm m\u00fc\u015fterilerin de ayn\u0131 IP\u2019den mail att\u0131\u011f\u0131 i\u00e7in IP itibar\u0131n\u0131 d\u00fc\u015f\u00fcr\u00fcr ve portf\u00f6y\u00fcn\u00fczdeki herkes etkilenir.<\/p>\n<h3><span id=\"Temel_Kayit_Sablonu_MX_SPF_DKIM_DMARC\">Temel Kay\u0131t \u015eablonu: MX, SPF, DKIM, DMARC<\/span><\/h3>\n<p>Multi-tenant mimaride her m\u00fc\u015fteri i\u00e7in en az\u0131ndan a\u015fa\u011f\u0131daki temel \u015fablonu standartla\u015ft\u0131rman\u0131z gerekir:<\/p>\n<ul>\n<li><strong>MX<\/strong>: M\u00fc\u015fterinin alan ad\u0131n\u0131n e\u2011posta trafi\u011fi sizin DCHost sunucunuza aks\u0131n.<\/li>\n<li><strong>SPF<\/strong>: Hangi sunucular\u0131n o alan ad\u0131na ait e\u2011posta g\u00f6ndermeye yetkili oldu\u011funu beyan edin.<\/li>\n<li><strong>DKIM<\/strong>: \u00c7\u0131k\u0131\u015f yapan mailler kriptografik olarak imzalanarak sahtecili\u011fe kar\u015f\u0131 korunur.<\/li>\n<li><strong>DMARC<\/strong>: SPF ve DKIM sonu\u00e7lar\u0131na g\u00f6re al\u0131c\u0131 taraf\u0131n nas\u0131l davranmas\u0131 gerekti\u011fini tan\u0131mlars\u0131n\u0131z.<\/li>\n<\/ul>\n<p>Bu temeli s\u0131f\u0131rdan nas\u0131l kuraca\u011f\u0131n\u0131z\u0131 ad\u0131m ad\u0131m anlatt\u0131\u011f\u0131m\u0131z <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 ve DMARC rehberi<\/a>, ajanslar\u0131n multi-tenant mail mimarisi tasarlarken dayand\u0131\u011f\u0131 ana kaynaklardan biri haline geldi diyebiliriz.<\/p>\n<p>Panel taraf\u0131nda yap\u0131labilecek en iyi \u015fey, <strong>yeni a\u00e7\u0131lan her hesapta bu kay\u0131tlar\u0131n otomatik olu\u015fturulmas\u0131n\u0131<\/strong> sa\u011flamak ve sadece gerekti\u011finde \u00f6zelle\u015ftirmek.<\/p>\n<h3><span id=\"IP_Adresi_Reverse_DNS_ve_IP_Isitma\">IP Adresi, Reverse DNS ve IP Is\u0131tma<\/span><\/h3>\n<p>Tek VPS veya reseller \u00fczerinde multi-tenant mail tasarlarken kritik sorulardan biri \u015fu: \u201cT\u00fcm m\u00fc\u015fteriler ayn\u0131 payla\u015f\u0131ml\u0131 IP\u2019den mi mail atmal\u0131, yoksa baz\u0131lar\u0131na dedicated IP mi vermeliyim?\u201d<\/p>\n<p>Genellikle ajanslarda mant\u0131kl\u0131 yakla\u015f\u0131m \u015f\u00f6yle oluyor:<\/p>\n<ul>\n<li>K\u00fc\u00e7\u00fck hacimli kurumsal mail trafi\u011fi olan m\u00fc\u015fterileri <strong>payla\u015f\u0131ml\u0131 IP<\/strong> \u00fczerinde toplamak,<\/li>\n<li>B\u00fcy\u00fck hacimli pazarlama veya transactional g\u00f6nderim yapan kritik markalar i\u00e7in <strong>ayr\u0131 bir IP havuzu<\/strong> tan\u0131mlamak,<\/li>\n<li>Yeni IP\u2019leri bir anda binlerce maille bo\u011fmak yerine <strong>kademeli IP \u0131s\u0131tma<\/strong> stratejisi uygulamak.<\/li>\n<\/ul>\n<p>Bu konuda \u00e7ok detayl\u0131 bir rehberi zaten haz\u0131rlad\u0131k: <a href=\"https:\/\/www.dchost.com\/blog\/dedicated-ip-isitma-ve-e-posta-itibari-yonetimi\/\">&#8220;Dedicated IP \u0131s\u0131tma ve e\u2011posta itibar\u0131 y\u00f6netimi&#8221;<\/a>. Multi-tenant senaryoda fark, bu s\u00fcreci <strong>m\u00fc\u015fteriler aras\u0131nda \u00f6nceliklendirme ve kota y\u00f6netimiyle<\/strong> birle\u015ftirmeniz.<\/p>\n<p>Ayr\u0131ca her IP i\u00e7in do\u011fru bir <strong>PTR (Reverse DNS) kayd\u0131<\/strong> ve tutarl\u0131 HELO\/EHLO host ad\u0131 \u015fart. PTR yap\u0131land\u0131rmas\u0131n\u0131n e\u2011posta teslimine etkisini anlatt\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/ptr-reverse-dns-kaydi-vps-ipniz-icin-dogru-ayar-ve-e-posta-teslimine-etkisi\/\">PTR rehberi<\/a>, tek VPS \u00fczerinde kendi MTA\u2019n\u0131z\u0131 y\u00f6netirken i\u015finizi olduk\u00e7a kolayla\u015ft\u0131racakt\u0131r.<\/p>\n<h3><span id=\"Tenant_Basina_Izolasyon_Kota_ve_Rate_Limit\">Tenant Ba\u015f\u0131na \u0130zolasyon, Kota ve Rate Limit<\/span><\/h3>\n<p>Multi-tenant mimaride, herkesin ayn\u0131 SMTP kuyru\u011funu payla\u015ft\u0131\u011f\u0131n\u0131 unutmamak gerekiyor. Bu y\u00fczden:<\/p>\n<ul>\n<li>Her m\u00fc\u015fteri i\u00e7in <strong>g\u00fcnl\u00fck \/ saatlik g\u00f6nderim limiti<\/strong> belirleyin (panel veya MTA seviyesinde),<\/li>\n<li>\u015e\u00fcpheli bir m\u00fc\u015fteri (\u00e7ok bounce alan, \u00e7ok spam \u015fik\u00e2yeti gelen) tespit etti\u011finizde onu <strong>hemen ayr\u0131 bir IP veya hatta ayr\u0131 bir SMTP noduna<\/strong> ta\u015f\u0131yabilin,<\/li>\n<li>Loglarda tenant bazl\u0131 filtreleme yaparak \u201changi m\u00fc\u015fteri ne kadar hata \u00fcretiyor\u201du g\u00f6rebilin.<\/li>\n<\/ul>\n<p>Bu t\u00fcr politikalar, ileride ya\u015fayaca\u011f\u0131n\u0131z blacklist veya itibar sorunlar\u0131n\u0131 daha olu\u015fmadan y\u00f6netebilmenizi sa\u011flar. E\u011fer tek VPS \u00fczerinde kendi Postfix\/Dovecot+rspamd yap\u0131n\u0131z\u0131 kurmak istiyorsan\u0131z, <a href=\"https:\/\/www.dchost.com\/blog\/vpste-e-posta-sunucusu-kurulumu-postfix-dovecot-rspamd-ile-teslim-edilebilirlik-ve-ip-isitma-adim-adim\/\">VPS\u2019te e\u2011posta sunucusu kurulumu rehberimiz<\/a> size olduk\u00e7a yol g\u00f6sterecektir.<\/p>\n<h3><span id=\"Ileri_Seviye_MTA-STS_TLS-RPT_BIMI_ve_MTA_Guvenligi\">\u0130leri Seviye: MTA-STS, TLS-RPT, BIMI ve MTA G\u00fcvenli\u011fi<\/span><\/h3>\n<p>Ajanslar\u0131n \u00f6zellikle kurumsal m\u00fc\u015fterilerde tercih etti\u011fi ileri seviye g\u00fcvenlik ayarlar\u0131 da var:<\/p>\n<ul>\n<li><strong>MTA-STS ve TLS-RPT<\/strong> ile SMTP trafi\u011finin TLS ile \u015fifrelenmesini zorunlu k\u0131lmak ve rapor toplamak,<\/li>\n<li><strong>BIMI<\/strong> ile marka logolar\u0131n\u0131n destekleyen e\u2011posta istemcilerde g\u00f6r\u00fcnmesini sa\u011flamak,<\/li>\n<li><strong>DANE\/TLSA<\/strong> ile DNSSEC \u00fczerinden ek bir g\u00fcvenlik katman\u0131 eklemek.<\/li>\n<\/ul>\n<p>Bunlar\u0131n tamam\u0131n\u0131 DNS taraf\u0131nda nas\u0131l konumland\u0131rabilece\u011finizi anlatt\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/mta-sts-tls-rpt-ve-bimi-nedir-e-posta-guvenligi-ve-marka-gorunurlugu-icin-gelismis-dns-ayarlari\/\">MTA-STS, TLS-RPT ve BIMI rehberi<\/a>, multi-tenant DNS mimarinize bu katmanlar\u0131 sa\u011flam \u015fekilde oturtman\u0131z i\u00e7in ideal bir referans.<\/p>\n<h2><span id=\"Tek_Sunucuda_Guvenlik_Yedekleme_ve_Izleme\">Tek Sunucuda G\u00fcvenlik, Yedekleme ve \u0130zleme<\/span><\/h2>\n<p>Onlarca m\u00fc\u015fterinin mail kutular\u0131 ve DNS kay\u0131tlar\u0131 tek VPS veya reseller \u00fczerinde duruyorsa, art\u0131k o makine sizin i\u00e7in <strong>\u00e7ok kritik bir altyap\u0131<\/strong> haline gelir. G\u00fcvenlik, yedek ve izleme taraf\u0131nda minimum yap\u0131lmas\u0131 gerekenleri toparlayal\u0131m.<\/p>\n<h3><span id=\"Panel_ve_Sunucu_Erisimi\">Panel ve Sunucu Eri\u015fimi<\/span><\/h3>\n<ul>\n<li>cPanel\/DirectAdmin\/WHM gibi panellere <strong>iki fakt\u00f6rl\u00fc kimlik do\u011frulama (2FA)<\/strong> zorunlu olmal\u0131.<\/li>\n<li>Ajans ekibinde kim hangi hesaba eri\u015febilir; bunu netle\u015ftiren bir <strong>yetkilendirme matrisi<\/strong> kurun. Bunun i\u00e7in haz\u0131rlad\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/ajanslar-icin-hosting-paneli-erisim-yonetimi-uygulanabilir-rehber\/\">ajanslar i\u00e7in hosting paneli eri\u015fim y\u00f6netimi rehberi<\/a> somut bir ba\u015flang\u0131\u00e7 sa\u011flar.<\/li>\n<li>VPS kullan\u0131yorsan\u0131z, SSH eri\u015fimlerini anahtar tabanl\u0131 yap\u0131n, root giri\u015fini kapat\u0131n, ufw\/fail2ban gibi temel sertle\u015ftirme ad\u0131mlar\u0131n\u0131 eksiksiz uygulay\u0131n.<\/li>\n<\/ul>\n<h3><span id=\"Yedekleme_ve_Felaket_Kurtarma\">Yedekleme ve Felaket Kurtarma<\/span><\/h3>\n<p>Tek sunucuda t\u00fcm m\u00fc\u015fterilerin mail ve DNS verisinin durdu\u011funu d\u00fc\u015f\u00fcn\u00fcrseniz, yedekleme stratejisinin \u00f6nemi daha da netle\u015fiyor. Ajans taraf\u0131nda genelde \u015fu model iyi \u00e7al\u0131\u015f\u0131yor:<\/p>\n<ul>\n<li>G\u00fcnl\u00fck tam veya art\u0131ml\u0131 hesap yedekleri (web+mail+DNS),<\/li>\n<li>Yedeklerin en az bir kopyas\u0131n\u0131n <strong>farkl\u0131 bir fiziksel lokasyonda<\/strong> tutulmas\u0131,<\/li>\n<li>Haftal\u0131k veya ayl\u0131k bazda <strong>geri y\u00fckleme testi<\/strong> (restore drill) yap\u0131lmas\u0131.<\/li>\n<\/ul>\n<p>Bu yap\u0131y\u0131 3-2-1 kural\u0131yla birlikte ele ald\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/3-2-1-yedekleme-stratejisi-neden-ise-yariyor-cpanel-plesk-ve-vpste-otomatik-yedekleri-nasil-kurarsin\/\">3\u20112\u20111 yedekleme stratejisi rehberi<\/a>, \u00f6zellikle tek VPS \u00fczerinde ajans platformu kuranlar i\u00e7in olmazsa olmaz okumal\u0131k.<\/p>\n<h3><span id=\"Izleme_Loglama_ve_Alarm_Mekanizmalari\">\u0130zleme, Loglama ve Alarm Mekanizmalar\u0131<\/span><\/h3>\n<p>Multi-tenant yap\u0131da sorunlar\u0131n m\u00fc\u015fteriniz fark etmeden \u00f6nce sizin radar\u0131n\u0131za d\u00fc\u015fmesi gerekir. Bunun i\u00e7in:<\/p>\n<ul>\n<li>Sunucunun CPU, RAM, disk, I\/O ve network kullan\u0131m\u0131n\u0131 izleyen bir monitoring (Netdata, Prometheus+Grafana vb.) kurun.<\/li>\n<li>Mail kuyru\u011fu boyu, bounce oranlar\u0131 ve SMTP hata kodlar\u0131 i\u00e7in basit metrikler \u00e7\u0131kar\u0131n. <a href=\"https:\/\/www.dchost.com\/blog\/smtp-hata-kodlari-ve-bounce-mesajlari-rehberi\/\">SMTP hata kodlar\u0131 ve bounce mesajlar\u0131 rehberimizi<\/a> operasyon dok\u00fcman\u0131n\u0131za eklemeniz, destek ekibinin i\u015fini \u00e7ok kolayla\u015ft\u0131r\u0131r.<\/li>\n<li>DNS taraf\u0131nda yanl\u0131\u015fl\u0131kla silinen kritik kay\u0131tlar veya beklenmedik de\u011fi\u015fiklikleri tespit eden bir s\u00fcre\u00e7 (manuel veya otomatik rapor) olu\u015fturun.<\/li>\n<\/ul>\n<h2><span id=\"Operasyonel_Akis_Yeni_Musteri_Acilisindan_Tasima_Sureclerine\">Operasyonel Ak\u0131\u015f: Yeni M\u00fc\u015fteri A\u00e7\u0131l\u0131\u015f\u0131ndan Ta\u015f\u0131ma S\u00fcre\u00e7lerine<\/span><\/h2>\n<p>Teknik mimari kadar \u00f6nemli olan bir di\u011fer konu da <strong>ajans i\u00e7i s\u00fcre\u00e7ler<\/strong>. Multi-tenant e\u2011posta ve DNS yap\u0131n\u0131z varsa, her yeni m\u00fc\u015fteri i\u00e7in tekrar eden i\u015fleri otomatikle\u015ftirmek b\u00fcy\u00fck zaman kazand\u0131r\u0131r.<\/p>\n<h3><span id=\"Yeni_Musteri_Icin_Onerilen_Adim_Adim_Akis\">Yeni M\u00fc\u015fteri \u0130\u00e7in \u00d6nerilen Ad\u0131m Ad\u0131m Ak\u0131\u015f<\/span><\/h3>\n<ol>\n<li><strong>Alan ad\u0131 durumu<\/strong>: Domain sizde mi, m\u00fc\u015fteride mi, kimin registrar hesab\u0131nda?<\/li>\n<li><strong>Nameserver ge\u00e7i\u015fi<\/strong>: Domain\u2019in NS kay\u0131tlar\u0131n\u0131 DCHost \u00fczerindeki DNS altyap\u0131n\u0131za y\u00f6nlendirin.<\/li>\n<li><strong>Hesap a\u00e7\u0131l\u0131\u015f\u0131<\/strong>: VPS veya reseller \u00fczerinde m\u00fc\u015fteri i\u00e7in ayr\u0131 bir hosting hesab\u0131 olu\u015fturun.<\/li>\n<li><strong>DNS \u015fablonu<\/strong>: A\/AAAA, MX, SPF, DKIM, DMARC, MTA-STS, CAA vb. kay\u0131tlar\u0131n\u0131z\u0131 otomatik \u015fablonla olu\u015fturun.<\/li>\n<li><strong>E\u2011posta kutular\u0131<\/strong>: Kurumsal e\u2011posta adreslerini a\u00e7\u0131n, kota ve \u015fifre politikalar\u0131n\u0131 uygulay\u0131n.<\/li>\n<li><strong>Test ve devreye alma<\/strong>: Yeni DNS\/MX\u2019ler ile test mail g\u00f6nderip SPF\/DKIM\/DMARC ge\u00e7i\u015flerini kontrol edin.<\/li>\n<\/ol>\n<p>DNS ve nameserver ge\u00e7i\u015flerinde kesinti ya\u015famamak i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/zero-downtime-tasima-icin-ttl-stratejileri-dns-yayilimini-gercekten-nasil-hizlandirirsin\/\">TTL stratejileriyle s\u0131f\u0131r kesinti ta\u015f\u0131ma rehberi<\/a>nde anlatt\u0131\u011f\u0131m\u0131z teknikleri bu ak\u0131\u015f\u0131n \u201cNS ge\u00e7i\u015fi\u201d ad\u0131m\u0131na entegre etmeniz, ajans olarak sizi olduk\u00e7a rahatlat\u0131r.<\/p>\n<h3><span id=\"Mevcut_EPosta_Altyapisini_Tasirken_Dikkat_Edilecekler\">Mevcut E\u2011Posta Altyap\u0131s\u0131n\u0131 Ta\u015f\u0131rken Dikkat Edilecekler<\/span><\/h3>\n<p>Var olan bir m\u00fc\u015fterinin e\u2011posta altyap\u0131s\u0131n\u0131 kendi multi-tenant yap\u0131n\u0131za al\u0131rken en \u00e7ok hata yap\u0131lan yerler:<\/p>\n<ul>\n<li>Eski sunucudaki mailler tam ta\u015f\u0131nmadan MX kay\u0131tlar\u0131n\u0131 g\u00fcncellemek,<\/li>\n<li>SPF kay\u0131tlar\u0131n\u0131 g\u00fcncellemeden \u00f6nce eski servisleri SPF\u2019ten \u00e7\u0131karmak,<\/li>\n<li>DMARC politikas\u0131 s\u0131k\u0131 (reject\/quarantine) iken ani DNS de\u011fi\u015fiklikleri yapmak.<\/li>\n<\/ul>\n<p>Bu ge\u00e7i\u015flerde ad\u0131m ad\u0131m yol haritas\u0131 i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/e-posta-altyapisini-tasirken-kesinti-yasamamak\/\">e\u2011posta altyap\u0131s\u0131n\u0131 ta\u015f\u0131rken kesinti ya\u015famamak<\/a> yaz\u0131m\u0131z\u0131, ayr\u0131ca cPanel taraf\u0131nda IMAP senkronizasyonu ve DNS cutover detaylar\u0131 i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/cpanel-e%e2%80%91posta-hesaplarini-yeni-sunucuya-tasimak-imap-senkronizasyonu-ve-dns-cutover\/\">cPanel e\u2011posta hesaplar\u0131n\u0131 yeni sunucuya ta\u015f\u0131mak<\/a> rehberimizi s\u00fcrecinize eklemenizi \u00f6neririz.<\/p>\n<h2><span id=\"DCHost_Uzerinde_Uygulanabilir_Ornek_Senaryolar\">DCHost \u00dczerinde Uygulanabilir \u00d6rnek Senaryolar<\/span><\/h2>\n<p>Teoriyi biraz somutla\u015ft\u0131ral\u0131m. DCHost taraf\u0131nda ajanslarla en s\u0131k kurdu\u011fumuz \u00fc\u00e7 temel modeli \u00f6zetleyelim:<\/p>\n<h3><span id=\"1_Kucuk_Ajans_Reseller_Standart_DNSEPosta\">1) K\u00fc\u00e7\u00fck Ajans: Reseller + Standart DNS\/E\u2011Posta<\/span><\/h3>\n<ul>\n<li>20\u201340 aras\u0131 kurumsal site ve d\u00fc\u015f\u00fck hacimli e\u2011posta trafi\u011fi,<\/li>\n<li>DCHost reseller hosting paketi,<\/li>\n<li>Her m\u00fc\u015fteri i\u00e7in ayr\u0131 cPanel\/DirectAdmin hesab\u0131,<\/li>\n<li>Panelin sundu\u011fu varsay\u0131lan NS\u2019ler ve otomatik SPF\/DKIM,<\/li>\n<li>Basit DMARC (p=quarantine veya p=none) politikas\u0131.<\/li>\n<\/ul>\n<p>Bu modelde ajans neredeyse hi\u00e7 sunucu taraf\u0131na dokunmadan, sadece panel ve DNS y\u00f6neterek t\u00fcm portf\u00f6y\u00fcn\u00fc toparlayabiliyor.<\/p>\n<h3><span id=\"2_Orta_Olcek_Ajans_Tek_Guclu_VPS_Uzerinde_Multi-Tenant_Panel\">2) Orta \u00d6l\u00e7ek Ajans: Tek G\u00fc\u00e7l\u00fc VPS \u00dczerinde Multi-Tenant Panel<\/span><\/h3>\n<ul>\n<li>40\u2013100+ m\u00fc\u015fteri, karma trafik hacimleri,<\/li>\n<li>DCHost \u00fczerinde NVMe diskli, y\u00fcksek I\/O\u2019lu bir VPS,<\/li>\n<li>\u00dczerine kurulmu\u015f cPanel\/DirectAdmin veya benzeri panel,<\/li>\n<li>Kendi ns1\/ns2.ajansdns.com ad sunucular\u0131 (glue record ile),<\/li>\n<li>Payla\u015f\u0131ml\u0131 IP + 1\u20132 adet dedicated IP havuzu,<\/li>\n<li>\u0130leri seviye SPF, DKIM, DMARC; baz\u0131 m\u00fc\u015fterilerde MTA-STS ve BIMI.<\/li>\n<\/ul>\n<p>Bu noktada ajanslar, kimi m\u00fc\u015fterilerin transactional maillerini ayr\u0131 bir tenant grubuna b\u00f6lerek IP itibar\u0131n\u0131 daha kontroll\u00fc y\u00f6netmeye ba\u015fl\u0131yor.<\/p>\n<h3><span id=\"3_Buyuk_Ajans_SaaS_Benzeri_Platform_Cok_VPS_Ayri_Mail_Nodlari\">3) B\u00fcy\u00fck Ajans \/ SaaS Benzeri Platform: \u00c7ok VPS + Ayr\u0131 Mail Nodlar\u0131<\/span><\/h3>\n<ul>\n<li>100+ m\u00fc\u015fteri, y\u00fcksek hacimli transactional ve pazarlama mailleri,<\/li>\n<li>DCHost\u2019ta birden \u00e7ok VPS (web, mail, DNS rollerinin ayr\u0131lmas\u0131),<\/li>\n<li>Merkezi DNS + ayr\u0131 mail node\u2019lar\u0131 (Postfix\/Dovecot k\u00fcmesi),<\/li>\n<li>Farkl\u0131 m\u00fc\u015fteri segmentleri i\u00e7in farkl\u0131 IP havuzlar\u0131 ve rate-limit politikalar\u0131,<\/li>\n<li>Terrafrom\/Ansible ile otomatik m\u00fc\u015fteri kurulumu, DNS ve SSL provisioning.<\/li>\n<\/ul>\n<p>Bu model SaaS mant\u0131\u011f\u0131na yakla\u015fan ajanslarda veya kendi bar\u0131nd\u0131rma platformunu kurumsal bir hizmet gibi satan ajanslarda yayg\u0131nla\u015f\u0131yor. DCHost taraf\u0131nda VPS, dedicated ve gerekirse colocation ile bu mimarinin \u00f6l\u00e7eklenebilir omurgas\u0131n\u0131 kurmak m\u00fcmk\u00fcn.<\/p>\n<h2><span id=\"Sonuc_Ajanslar_Icin_Yol_Haritasi_ve_Sonraki_Adimlar\">Sonu\u00e7: Ajanslar \u0130\u00e7in Yol Haritas\u0131 ve Sonraki Ad\u0131mlar<\/span><\/h2>\n<p>Onlarca m\u00fc\u015fterinin alan ad\u0131, DNS ve e\u2011posta altyap\u0131s\u0131n\u0131 da\u011f\u0131n\u0131k halde y\u00f6netmek; ilk bak\u0131\u015fta \u201cal\u0131\u015ft\u0131k art\u0131k\u201d denip ge\u00e7ilecek bir durum gibi g\u00f6r\u00fcnebilir. Ama ne zaman bir m\u00fc\u015fterinin alan ad\u0131 s\u00fcresi doldu\u011funda, MX kayd\u0131 yanl\u0131\u015f g\u00fcncellendi\u011finde veya payla\u015f\u0131ml\u0131 IP\u2019niz blacklist\u2019e girdi\u011finde, o da\u011f\u0131n\u0131kl\u0131\u011f\u0131n ger\u00e7ek maliyeti bir anda ortaya \u00e7\u0131k\u0131yor. Multi-tenant e\u2011posta ve DNS mimarisi, ajanslar i\u00e7in bu kaosu sistematik \u015fekilde toparlaman\u0131n en g\u00fc\u00e7l\u00fc arac\u0131.<\/p>\n<p>DCHost taraf\u0131nda g\u00f6rd\u00fc\u011f\u00fcm\u00fcz ba\u015far\u0131l\u0131 ajanslarda ortak \u00f6zellikler \u015funlar:<\/p>\n<ul>\n<li>T\u00fcm alan adlar\u0131n\u0131 ve DNS\u2019i tek mant\u0131kl\u0131 NS stratejisinde toplamalar\u0131,<\/li>\n<li>E\u2011posta taraf\u0131nda SPF, DKIM, DMARC ve rDNS gibi temel ayarlar\u0131 <strong>\u015fablon haline getirmeleri<\/strong>,<\/li>\n<li>Riskli m\u00fc\u015fterileri IP ve rate-limit politikalar\u0131yla di\u011ferlerinden ay\u0131rmalar\u0131,<\/li>\n<li>Yedekleme, izleme ve eri\u015fim y\u00f6netimini ba\u015ftan tasarlamalar\u0131.<\/li>\n<\/ul>\n<p>E\u011fer siz de ajans olarak \u201cart\u0131k bu karma\u015fay\u0131 toparlayal\u0131m\u201d diyorsan\u0131z, ilk ad\u0131m\u0131n\u0131z mevcut portf\u00f6y\u00fcn\u00fcz\u00fc haritaland\u0131rmak ve ard\u0131ndan yukar\u0131da anlatt\u0131\u011f\u0131m\u0131z \u00fc\u00e7 mimari modelden hangisinin size daha uygun oldu\u011funa karar vermek olmal\u0131. DCHost \u00fczerindeki reseller, VPS, dedicated ve colocation \u00e7\u00f6z\u00fcmlerimizle; ister basit bir reseller mimarisi, ister \u00e7ok VPS\u2019li geli\u015fmi\u015f multi-tenant e\u2011posta ve DNS platformu kurmak isteyin, ekibimizle birlikte bu yolculu\u011fu tasarlayabiliriz.<\/p>\n<p>Sonraki ad\u0131m olarak \u00f6zellikle <a href=\"https:\/\/www.dchost.com\/blog\/spf-dkim-dmarc-ve-rdns-ile-e-posta-teslim-edilebilirligini-nasil-adim-adim-yukseltirsin\/\">e\u2011posta teslim edilebilirli\u011fini ad\u0131m ad\u0131m y\u00fckseltme rehberimizi<\/a> ve <a href=\"https:\/\/www.dchost.com\/blog\/ajanslar-icin-dns-ve-alan-adi-erisimi-yonetimi\/\">ajanslar i\u00e7in DNS eri\u015fim y\u00f6netimi yaz\u0131m\u0131z\u0131<\/a> okuman\u0131z\u0131 \u00f6neririm. Bu iki rehberi elinize al\u0131p kendi mimarinize uyarlad\u0131\u011f\u0131n\u0131zda, ajans olarak e\u2011posta ve DNS taraf\u0131nda \u00e7ok daha \u00f6ng\u00f6r\u00fclebilir, y\u00f6netilebilir ve \u00f6l\u00e7eklenebilir bir yap\u0131ya ge\u00e7mi\u015f olursunuz.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>\u0130&ccedil;indekiler1 Ajanslar \u0130\u00e7in Multi-Tenant E\u2011Posta ve DNS Neden Kritik Hale Geldi?2 Temel Kavramlar: Multi-Tenant, Tek VPS ve Reseller Yap\u0131s\u01313 Mimari Se\u00e7enekler: Tek VPS mi Reseller m\u0131?3.1 Reseller Hosting Tercih Etmeniz Mant\u0131kl\u0131 Oldu\u011fu Durumlar3.2 Tek VPS (veya Dedicated) Tercih Etmeniz Mant\u0131kl\u0131 Oldu\u011fu Durumlar4 DNS Mimarisi: Onlarca M\u00fc\u015fteri \u0130\u00e7in Y\u00f6netilebilir Yap\u01314.1 Nameserver ve Zone Stratejisi4.2 Ajanslarda S\u0131k [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":3780,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-3779","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\/3779","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=3779"}],"version-history":[{"count":0,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/3779\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/3780"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=3779"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=3779"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=3779"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}