{"id":151,"date":"2026-10-14T17:01:29","date_gmt":"2026-10-14T14:01:29","guid":{"rendered":"https:\/\/mx1mail.com\/blog\/mx-priority-failover-tasarimi-birden-fazla-mx-kaydi\/"},"modified":"2026-10-14T17:01:29","modified_gmt":"2026-10-14T14:01:29","slug":"mx-priority-failover-tasarimi-birden-fazla-mx-kaydi","status":"publish","type":"post","link":"https:\/\/mx1mail.com\/blog\/tr\/mx-priority-failover-tasarimi-birden-fazla-mx-kaydi\/","title":{"rendered":"MX Priority ve Failover Tasar\u0131m\u0131: Birden Fazla MX Kayd\u0131yla Kesintisiz E-Posta Al\u0131m\u0131 Nas\u0131l Planlan\u0131r?"},"content":{"rendered":"<h2>MX priority nedir ve ger\u00e7ekte neyi belirler?<\/h2>\n<p>MX (Mail Exchanger) kayd\u0131, bir alan ad\u0131n\u0131n (domain) e-posta kabul eden sunucular\u0131n\u0131 DNS \u00fczerinden ilan eder. MX kayd\u0131ndaki say\u0131 \u201cpriority\u201d (\u00f6ncelik) de\u011feridir ve temel olarak \u015funu s\u00f6yler: G\u00f6nderen taraf, \u00f6nce en d\u00fc\u015f\u00fck say\u0131l\u0131 MX\u2019e teslim etmeyi dener. \u00d6rne\u011fin 10 de\u011ferli MX, 20 de\u011ferli MX\u2019ten daha \u00f6nceliklidir.<\/p>\n<p>Buradaki kritik nokta, MX priority\u2019nin bir y\u00fck dengeleme ya da an\u0131nda devralma (failover) garantisi olmad\u0131\u011f\u0131d\u0131r. MX kay\u0131tlar\u0131, \u201changi sunucuya \u00f6nce denensin\u201d sorusunu yan\u0131tlar; \u201ckesinti an\u0131nda otomatik olarak her zaman en h\u0131zl\u0131 \u015fekilde di\u011ferine ge\u00e7ilir\u201d s\u00f6z\u00fcn\u00fc vermez. G\u00f6nderen MTA\u2019n\u0131n (mail transfer agent) davran\u0131\u015f\u0131, DNS \u00f6nbelle\u011fi, yeniden deneme aral\u0131klar\u0131 ve mesaj kuyru\u011fu y\u00f6netimi gibi etkenler, failover deneyimini belirgin \u015fekilde de\u011fi\u015ftirir.<\/p>\n<h2>Birden fazla MX kayd\u0131 neden kullan\u0131l\u0131r?<\/h2>\n<p>Birden fazla MX kayd\u0131 tan\u0131mlaman\u0131n ana motivasyonu, e-posta al\u0131m\u0131nda dayan\u0131kl\u0131l\u0131k sa\u011flamakt\u0131r. Birincil sunucu ge\u00e7ici olarak ula\u015f\u0131lamazsa, g\u00f6nderen taraf mesaj\u0131 alternatif MX\u2019e denemeyi s\u00fcrd\u00fcrebilir. Ayr\u0131ca bak\u0131m pencerelerinde, a\u011f kesintilerinde veya tek bir IP\/rota sorununda e-posta ak\u0131\u015f\u0131n\u0131n tamamen durmas\u0131n\u0131 azaltmaya yard\u0131mc\u0131 olabilir.<\/p>\n<p>Ancak tasar\u0131m hedefini do\u011fru koymak gerekir: \u00c7oklu MX \u00e7o\u011fu zaman \u201ckesintisiz al\u0131m\u201ddan \u00e7ok \u201cgecikmeli ama kay\u0131ps\u0131z al\u0131m\u201d sa\u011flar. \u00c7\u00fcnk\u00fc standart davran\u0131\u015fta g\u00f6nderen sunucular mesaj\u0131 bir s\u00fcre kuyrukta tutar ve belirli aral\u0131klarla tekrar dener.<\/p>\n<h2>En yayg\u0131n yanl\u0131\u015f varsay\u0131mlar<\/h2>\n<h3>Yanl\u0131\u015f varsay\u0131m 1: \u0130ki MX kayd\u0131, aktif-aktif y\u00fck payla\u015f\u0131m\u0131 yapar<\/h3>\n<p>\u0130ki MX\u2019i ayn\u0131 priority ile tan\u0131mlamak, baz\u0131 g\u00f6nderenlerde trafi\u011fin da\u011f\u0131lmas\u0131na yol a\u00e7abilir; fakat bu bir garanti de\u011fildir. Bir\u00e7ok g\u00f6nderen, en uygun g\u00f6rd\u00fc\u011f\u00fc MX\u2019i se\u00e7ebilir veya birini \u201csticky\u201d \u015fekilde tercih edebilir. Ayr\u0131ca spam\/itibar kontrolleri, TLS politikalar\u0131 ve ba\u011flant\u0131 ba\u015far\u0131s\u0131 gibi fakt\u00f6rler se\u00e7imde rol oynar.<\/p>\n<h3>Yanl\u0131\u015f varsay\u0131m 2: \u0130kincil MX, birincil devre d\u0131\u015f\u0131 kal\u0131r kalmaz an\u0131nda devreye girer<\/h3>\n<p>G\u00f6nderen MTA \u00e7o\u011fu durumda \u00f6nce birincile ba\u011flanmay\u0131 dener. Ba\u011flant\u0131 reddi, timeout veya ge\u00e7ici hata al\u0131rsa alternatif MX\u2019i dener; fakat tekrar denemelerin zamanlamas\u0131 g\u00f6nderene ba\u011fl\u0131d\u0131r. Baz\u0131 sistemler dakikalar i\u00e7inde denerken baz\u0131lar\u0131 daha yava\u015f davranabilir.<\/p>\n<h3>Yanl\u0131\u015f varsay\u0131m 3: \u0130kincil MX benim yerime posta kutular\u0131na teslim eder<\/h3>\n<p>\u0130kincil MX \u00e7o\u011fu zaman \u201cstore-and-forward\u201d mant\u0131\u011f\u0131yla \u00e7al\u0131\u015f\u0131r: Mesaj\u0131 kabul eder, sonra as\u0131l teslim noktas\u0131na iletmeye \u00e7al\u0131\u015f\u0131r. Bu, ikincil sistemin do\u011fru yap\u0131land\u0131r\u0131lmas\u0131n\u0131 gerektirir. Aksi halde ikincil MX sadece kuyruk biriktiren bir ara durak olur veya daha k\u00f6t\u00fcs\u00fc yanl\u0131\u015f teslim\/sorunlu y\u00f6nlendirme yaratabilir.<\/p>\n<h2>Do\u011fru failover tasar\u0131m\u0131 i\u00e7in kavramlar<\/h2>\n<h3>Primary ve secondary MX rolleri<\/h3>\n<p>Birincil MX, normal \u015fartlarda e-postay\u0131 kabul eden ve al\u0131c\u0131 posta kutular\u0131na teslim eden ana sistemdir. \u0130kincil MX ise genellikle birincil ge\u00e7ici olarak ula\u015f\u0131lamad\u0131\u011f\u0131nda mesaj\u0131 kabul edip kuyruklayan, ard\u0131ndan birincile ileten bir ara katman olarak d\u00fc\u015f\u00fcn\u00fcl\u00fcr.<\/p>\n<h3>Kuyruk (queue) davran\u0131\u015f\u0131 ve yeniden denemeler<\/h3>\n<p>SMTP teslimat\u0131n\u0131n do\u011fas\u0131 gere\u011fi \u201canl\u0131k garanti\u201d yoktur. G\u00f6nderen sistemler ge\u00e7ici hatalarda (4xx) mesaj\u0131 kuyrukta tutar ve tekrar dener. Bu nedenle, failover s\u0131ras\u0131nda ya\u015fanan gecikme \u00e7o\u011fu zaman normaldir. Tasar\u0131m\u0131n amac\u0131, gecikme ya\u015fansa bile mesaj\u0131n kaybolmamas\u0131n\u0131 ve nihayetinde teslim edilmesini sa\u011flamakt\u0131r.<\/p>\n<h3>DNS TTL ve \u00f6nbellekleme<\/h3>\n<p>MX kay\u0131tlar\u0131n\u0131n TTL de\u011feri, kay\u0131tlar\u0131n ne kadar s\u00fcreyle \u00f6nbellekte kalaca\u011f\u0131n\u0131 etkiler. TTL, \u201cfailover h\u0131z\u0131n\u0131\u201d do\u011frudan belirlemez; \u00e7\u00fcnk\u00fc \u00e7oklu MX senaryosunda kay\u0131t de\u011fi\u015fikli\u011fi yapmadan da failover hedeflenir. Yine de bak\u0131m d\u00f6nemlerinde MX de\u011fi\u015fikli\u011fi planl\u0131yorsan\u0131z TTL\u2019i \u00f6nceden d\u00fc\u015f\u00fcrmek, ge\u00e7i\u015fin daha \u00f6ng\u00f6r\u00fclebilir olmas\u0131na yard\u0131mc\u0131 olabilir.<\/p>\n<h2>Pratik MX priority desenleri<\/h2>\n<h3>Desen 1: Tek birincil, tek ikincil (10 ve 20)<\/h3>\n<p>En yayg\u0131n modeldir. \u00d6rnek: mx1 alan ad\u0131n\u0131z i\u00e7in 10, mx2 i\u00e7in 20. Normalde t\u00fcm trafik mx1\u2019e gider; mx1 ge\u00e7ici sorun ya\u015farsa mx2 devreye girer. Bu d\u00fczen basittir; ancak ikincil MX\u2019in ger\u00e7ek anlamda \u201cyedek\u201d olabilmesi i\u00e7in, mx2\u2019nin mesaj kabul etmesi, kuyruklamas\u0131 ve daha sonra birincile g\u00fcvenli \u015fekilde iletmesi gerekir.<\/p>\n<h3>Desen 2: Ayn\u0131 \u00f6ncelikli birden \u00e7ok MX (10 ve 10)<\/h3>\n<p>Baz\u0131 kurulu\u015flar iki sunucuyu ayn\u0131 priority ile tan\u0131mlay\u0131p trafi\u011fi da\u011f\u0131tmay\u0131 hedefler. Bu yakla\u015f\u0131m, altta yatan altyap\u0131 ayn\u0131 kapasitede ve ayn\u0131 g\u00fcvenlik\/teslim kurallar\u0131nda tasarlanmad\u0131ysa karma\u015f\u0131kl\u0131k yarat\u0131r. Ayr\u0131ca g\u00f6nderenlerin davran\u0131\u015f\u0131 farkl\u0131 olabildi\u011fi i\u00e7in, beklenen y\u00fck payla\u015f\u0131m\u0131 ger\u00e7ekle\u015fmeyebilir.<\/p>\n<h3>Desen 3: Birden \u00e7ok ikincil MX (10, 20, 30)<\/h3>\n<p>Genellikle gereksiz karma\u015f\u0131kl\u0131k getirir. Her ek MX, y\u00f6netilecek ekstra g\u00fcvenlik y\u00fczeyi demektir. E\u011fer ger\u00e7ekten \u00e7oklu b\u00f6lge\/\u00e7oklu a\u011f yedeklili\u011fi hedefleniyorsa, bu ek MX\u2019lerin rol\u00fc, bak\u0131m s\u00fcre\u00e7leri ve izleme kapsam\u0131 net tan\u0131mlanmal\u0131d\u0131r.<\/p>\n<h2>\u0130kincil MX kullanman\u0131n operasyonel riskleri<\/h2>\n<h3>Spam ve k\u00f6t\u00fcye kullan\u0131m riski<\/h3>\n<p>\u0130kincil MX, e-posta kabul etti\u011fi i\u00e7in sald\u0131rganlar\u0131n hedefi olabilir. Birincil sistemdeki filtreler ikincilde ayn\u0131 \u015fekilde yoksa, ikincil \u201ckolay giri\u015f kap\u0131s\u0131\u201dna d\u00f6n\u00fc\u015febilir. Bu nedenle ikincil MX\u2019in de temel anti-spam, ba\u011flant\u0131 limitleri ve g\u00fcvenlik kontrollerine sahip olmas\u0131 gerekir.<\/p>\n<h3>Geri sa\u00e7\u0131lma (backscatter) ve yanl\u0131\u015f NDR \u00fcretimi<\/h3>\n<p>\u0130kincil MX\u2019in yanl\u0131\u015f konfig\u00fcrasyonuyla, var olmayan al\u0131c\u0131lara gelen postalar kabul edilip daha sonra reddedilebilir. Bu durum, sahte g\u00f6nderen adreslerine gereksiz hata mesajlar\u0131 \u00fcretilmesine (backscatter) yol a\u00e7abilir. Do\u011fru yakla\u015f\u0131m genellikle al\u0131c\u0131 do\u011frulamas\u0131n\u0131 m\u00fcmk\u00fcn oldu\u011funca erken a\u015famada yapmakt\u0131r.<\/p>\n<h3>TLS ve sertifika uyumu<\/h3>\n<p>Birincil MX TLS desteklerken ikincil desteklemezse, baz\u0131 g\u00f6nderenler teslimat\u0131 geciktirebilir veya farkl\u0131 risk de\u011ferlendirmeleri yapabilir. \u0130kincil MX\u2019in TLS yap\u0131land\u0131rmas\u0131 ve sertifika ge\u00e7erlili\u011fi operasyonel olarak takip edilmelidir.<\/p>\n<h2>Do\u011fru kurulum i\u00e7in kontrol listesi<\/h2>\n<ul>\n<li><strong>MX hedefleri tutarl\u0131 m\u0131?<\/strong> MX kay\u0131tlar\u0131 A\/AAAA kayd\u0131na de\u011fil, hostname\u2019e i\u015faret etmeli; hedef hostlar\u0131n do\u011fru IP\u2019lere \u00e7\u00f6z\u00fcmlendi\u011fi do\u011frulanmal\u0131.<\/li>\n<li><strong>\u00d6ncelikler anlaml\u0131 m\u0131?<\/strong> 10\/20 gibi basit bir hiyerar\u015fi \u00e7o\u011fu \u015firket i\u00e7in yeterlidir.<\/li>\n<li><strong>\u0130kincil MX rol\u00fc net mi?<\/strong> Mesaj\u0131 sadece kabul edip kuyruklayacak m\u0131, yoksa posta kutusuna teslim edecek mi? Buna g\u00f6re mimari belirlenmeli.<\/li>\n<li><strong>Al\u0131c\u0131 do\u011frulama stratejisi belirlendi mi?<\/strong> Var olmayan kullan\u0131c\u0131lar i\u00e7in nas\u0131l davran\u0131laca\u011f\u0131 planlanmal\u0131.<\/li>\n<li><strong>\u0130zleme var m\u0131?<\/strong> Kuyruk b\u00fcy\u00fcmesi, teslim gecikmeleri, ba\u011flant\u0131 hatalar\u0131 ve disk kapasitesi gibi metrikler izlenmeli.<\/li>\n<li><strong>Bak\u0131m senaryosu test edildi mi?<\/strong> Birincili ge\u00e7ici olarak devre d\u0131\u015f\u0131 b\u0131rak\u0131p (kontroll\u00fc \u015fekilde) alternatif MX\u2019in mesaj kabul etti\u011fini ve daha sonra iletti\u011fini g\u00f6zlemleyin.<\/li>\n<\/ul>\n<h2>Failover\u2019\u0131 test etmenin pratik yolu<\/h2>\n<p>Ger\u00e7ek\u00e7i test, yaln\u0131zca DNS\u2019e bakmakla olmaz. Ama\u00e7, farkl\u0131 a\u011flardan gelen SMTP sunucular\u0131n\u0131n nas\u0131l davrand\u0131\u011f\u0131n\u0131 g\u00f6rmektir. Planl\u0131 bir test penceresinde birincil MX\u2019i ge\u00e7ici olarak eri\u015filemez hale getirip (\u00f6rne\u011fin belirli kaynaklardan 25\/TCP engelleme) d\u0131\u015f d\u00fcnyadan gelen teslimat denemelerini incelemek faydal\u0131d\u0131r. Test s\u0131ras\u0131nda g\u00fcnl\u00fckleri (logs), kuyruk davran\u0131\u015f\u0131n\u0131 ve gecikmeleri not edin.<\/p>\n<p>Testten sonra birincili geri a\u00e7t\u0131\u011f\u0131n\u0131zda, kuyrukta biriken mesajlar\u0131n ne h\u0131zla bo\u015fald\u0131\u011f\u0131 da kapasite planlamas\u0131 a\u00e7\u0131s\u0131ndan \u00f6nemlidir. Failover tasar\u0131m\u0131n\u0131n ger\u00e7ek d\u00fcnyadaki ba\u015far\u0131s\u0131, \u201calternatif MX var\u201d demekten \u00e7ok, bu geri d\u00f6n\u00fc\u015f davran\u0131\u015f\u0131n\u0131n sorunsuz olmas\u0131na ba\u011fl\u0131d\u0131r.<\/p>\n<h2>Sonu\u00e7: Basit, \u00f6l\u00e7\u00fclebilir ve y\u00f6netilebilir tasar\u0131m<\/h2>\n<p>Birden fazla MX kayd\u0131, do\u011fru beklentiyle tasarlan\u0131rsa e-posta al\u0131m\u0131nda dayan\u0131kl\u0131l\u0131k sa\u011flar. En iyi yakla\u015f\u0131m genellikle sade bir \u00f6ncelik hiyerar\u015fisi, net bir ikincil rol tan\u0131m\u0131 ve d\u00fczenli test\/izleme disiplinidir. \u201cAn\u0131nda devralma\u201d yerine \u201cgecikmeli ama kay\u0131ps\u0131z teslimat\u201d hedefiyle plan yapmak \u00e7o\u011fu i\u015fletme i\u00e7in daha ger\u00e7ek\u00e7idir.<\/p>\n<p>Kurumsal e-posta altyap\u0131n\u0131z\u0131 planlarken, MX kay\u0131tlar\u0131, DNS y\u00f6netimi ve teslim alma taraf\u0131ndaki operasyonel s\u00fcre\u00e7ler birlikte ele al\u0131nmal\u0131d\u0131r. MX1Mail gibi y\u00f6netilen bir i\u015f e-posta hizmetine ge\u00e7i\u015f veya mevcut yap\u0131y\u0131 iyile\u015ftirme s\u00fcrecinde, MX tasar\u0131m\u0131n\u0131 bak\u0131m pencereleri ve i\u015f s\u00fcreklili\u011fi gereksinimleriyle uyumlu kurgulamak uzun vadede sorunlar\u0131 azalt\u0131r.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Birden fazla MX kayd\u0131yla do\u011fru \u00f6ncelik, yedeklilik ve teslim alma tasar\u0131m\u0131 nas\u0131l yap\u0131l\u0131r? Yanl\u0131\u015f failover beklentileri, kuyruk davran\u0131\u015f\u0131 ve test ad\u0131mlar\u0131.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[316],"tags":[381,379,213],"class_list":["post-151","post","type-post","status-publish","format-standard","hentry","category-dns-ve-e-posta-altyapisi","tag-eposta-altyapisi","tag-failover","tag-mx-kaydi"],"_links":{"self":[{"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/posts\/151","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/comments?post=151"}],"version-history":[{"count":0,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/posts\/151\/revisions"}],"wp:attachment":[{"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/media?parent=151"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/categories?post=151"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/tags?post=151"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}