{"id":133,"date":"2026-10-10T09:01:08","date_gmt":"2026-10-10T06:01:08","guid":{"rendered":"https:\/\/mx1mail.com\/blog\/ptr-reverse-dns-nedir-rdns-kurulumu-teslim-edilebilirlik\/"},"modified":"2026-10-10T09:01:08","modified_gmt":"2026-10-10T06:01:08","slug":"ptr-reverse-dns-nedir-rdns-kurulumu-teslim-edilebilirlik","status":"publish","type":"post","link":"https:\/\/mx1mail.com\/blog\/tr\/ptr-reverse-dns-nedir-rdns-kurulumu-teslim-edilebilirlik\/","title":{"rendered":"PTR (Reverse DNS) Nedir? Mail Sunucusu \u0130\u00e7in rDNS Kurulumu ve Teslim Edilebilirli\u011fe Etkisi"},"content":{"rendered":"<h2>PTR (Reverse DNS) nedir ve e-postada ne i\u015fe yarar?<\/h2>\n<p>PTR kayd\u0131, bir IP adresinin hangi alan ad\u0131na (hostname) kar\u015f\u0131l\u0131k geldi\u011fini ters y\u00f6nde g\u00f6steren DNS kayd\u0131d\u0131r. Normalde DNS\u2019i \u201calan ad\u0131 \u2192 IP\u201d e\u015flemesi (A\/AAAA kayd\u0131) i\u00e7in d\u00fc\u015f\u00fcn\u00fcr\u00fcz. Reverse DNS (rDNS) ise \u201cIP \u2192 alan ad\u0131\u201d do\u011frulamas\u0131n\u0131 m\u00fcmk\u00fcn k\u0131lar. \u0130nternet \u00fczerinde bir\u00e7ok servis, \u00f6zellikle de e-posta kabul eden mail sunucular\u0131, gelen SMTP ba\u011flant\u0131s\u0131n\u0131n geldi\u011fi IP i\u00e7in bir PTR kayd\u0131 olmas\u0131n\u0131 bekler.<\/p>\n<p>Bu beklentinin nedeni g\u00fcvenlikten \u00e7ok pratik bir sinyal mekanizmas\u0131d\u0131r: Dinamik, rastgele veya k\u00f6t\u00fc niyetli sistemlerden \u00e7\u0131kan e-posta trafi\u011finde PTR \u00e7o\u011fu zaman ya yoktur ya da anlams\u0131zd\u0131r. Kurumsal e-posta g\u00f6nderen sistemlerde ise IP\u2019nin bir isimle tutarl\u0131 \u015fekilde ili\u015fkilendirilmesi, altyap\u0131n\u0131n daha \u201cy\u00f6netilen\u201d oldu\u011funu g\u00f6sterir. PTR tek ba\u015f\u0131na teslim edilebilirli\u011fi garanti etmez; ancak yoklu\u011fu veya tutars\u0131zl\u0131\u011f\u0131, baz\u0131 al\u0131c\u0131larda spam puan\u0131n\u0131 art\u0131rabilir veya kabul politikalar\u0131n\u0131 tetikleyebilir.<\/p>\n<h2>Forward DNS ve reverse DNS: \u201cFCrDNS\u201d neden konu\u015fulur?<\/h2>\n<p>Mail d\u00fcnyas\u0131nda s\u0131k ge\u00e7en bir kavram da \u201cForward-Confirmed reverse DNS (FCrDNS)\u201d kontrol\u00fcd\u00fcr. Basit\u00e7e \u015fu tutarl\u0131l\u0131k aran\u0131r:<\/p>\n<ul>\n<li>G\u00f6nderici IP i\u00e7in PTR kayd\u0131 vard\u0131r ve bir hostname d\u00f6ner.<\/li>\n<li>Bu hostname i\u00e7in A (veya AAAA) kayd\u0131 sorguland\u0131\u011f\u0131nda ayn\u0131 IP\u2019ye geri d\u00f6ner.<\/li>\n<\/ul>\n<p>Bu iki y\u00f6nl\u00fc tutarl\u0131l\u0131k, baz\u0131 sistemlerde art\u0131 puan say\u0131l\u0131r. \u00d6nemli ayr\u0131m \u015fudur: PTR kayd\u0131, alan ad\u0131n\u0131z\u0131n DNS panelinden her zaman y\u00f6netilemeyebilir; \u00e7o\u011fu zaman IP\u2019yi tahsis eden sa\u011flay\u0131c\u0131 (bar\u0131nd\u0131rma\/VPS\/dedicated\/ISP) taraf\u0131ndan y\u00f6netilir. Buna kar\u015f\u0131n A\/AAAA kayd\u0131 sizin alan ad\u0131 DNS\u2019inizde y\u00f6netilir. Dolay\u0131s\u0131yla FCrDNS sa\u011flamak, iki farkl\u0131 yerde do\u011fru yap\u0131land\u0131rma gerektirir.<\/p>\n<h2>PTR kayd\u0131 teslim edilebilirli\u011fi nas\u0131l etkiler?<\/h2>\n<p>Bir\u00e7ok al\u0131c\u0131 sistem, gelen SMTP ba\u011flant\u0131s\u0131 i\u00e7in en az\u0131ndan \u015fu sinyallere bakar: IP itibar\u0131, SPF\/DKIM\/DMARC uyumu, TLS kullan\u0131m\u0131, g\u00f6nderim davran\u0131\u015f\u0131, i\u00e7erik kalitesi ve altyap\u0131 tutarl\u0131l\u0131\u011f\u0131. PTR\/rDNS bu \u201caltyap\u0131 tutarl\u0131l\u0131\u011f\u0131\u201d taraf\u0131nda de\u011ferlendirilir.<\/p>\n<h3>PTR yoksa ne olur?<\/h3>\n<p>PTR kayd\u0131 olmayan bir IP\u2019den e-posta g\u00f6nderdi\u011finizde baz\u0131 al\u0131c\u0131lar mesaj\u0131 do\u011frudan reddedebilir; baz\u0131lar\u0131 kabul edip spam klas\u00f6r\u00fcne y\u00f6nlendirebilir; baz\u0131lar\u0131 ise sadece puanlama etkisi uygular. \u00d6zellikle kurumsal al\u0131c\u0131larda, \u201cPTR yok\u201d durumu gereksiz risk olarak g\u00f6r\u00fclebilir.<\/p>\n<h3>PTR var ama anlams\u0131zsa?<\/h3>\n<p>PTR\u2019nin \u201c123-45-67-89.isp.example\u201d gibi jenerik bir isim olmas\u0131 her zaman felaket de\u011fildir; ancak \u201cmail1.sirketiniz.com\u201d gibi g\u00f6nderim ama\u00e7l\u0131 bir isim daha temiz ve y\u00f6netilebilir bir g\u00f6r\u00fcnt\u00fc verir. En kritik nokta, PTR\u2019nin tutarl\u0131 olmas\u0131 ve m\u00fcmk\u00fcnse forward e\u015flemesinin sa\u011flanmas\u0131d\u0131r.<\/p>\n<h3>PTR ile SPF\/DKIM ili\u015fkisi<\/h3>\n<p>PTR, SPF\/DKIM\u2019in yerine ge\u00e7mez. SPF, g\u00f6nderen IP\u2019lerin yetkisini; DKIM, i\u00e7eri\u011fin imzas\u0131n\u0131; DMARC ise politika ve uyumu y\u00f6netir. PTR ise IP\u2019nin isimlendirilmesi ve altyap\u0131 hijyeni sinyalidir. Hepsinin birlikte do\u011fru olmas\u0131, toplam teslim edilebilirlik performans\u0131n\u0131 iyile\u015ftirir.<\/p>\n<h2>Mail sunucusu i\u00e7in do\u011fru rDNS tasar\u0131m\u0131<\/h2>\n<p>PTR kayd\u0131 tasarlarken ama\u00e7 \u201cinsan g\u00f6z\u00fcyle okunabilir, tek ama\u00e7l\u0131, stabil bir hostname\u201d se\u00e7mektir. A\u015fa\u011f\u0131daki yakla\u015f\u0131m pratikte i\u015fe yarar:<\/p>\n<ul>\n<li>Tek bir g\u00f6nderici IP\u2019niz varsa: mail.sirketiniz.com veya smtp.sirketiniz.com gibi bir isim se\u00e7in.<\/li>\n<li>Birden fazla IP\u2019niz varsa: mail1, mail2 gibi numaraland\u0131rma yap\u0131n.<\/li>\n<li>Hostname\u2019iniz, ger\u00e7ek bir A\/AAAA kayd\u0131yla ayn\u0131 IP\u2019ye d\u00f6ns\u00fcn.<\/li>\n<li>PTR ad\u0131nda marka d\u0131\u015f\u0131, alakas\u0131z veya \u015f\u00fcpheli kelimeler kullanmay\u0131n.<\/li>\n<\/ul>\n<p>Ek olarak, SMTP sunucunuzun kendini tan\u0131tt\u0131\u011f\u0131 HELO\/EHLO ad\u0131 (sunucu hostname\u2019i) da genellikle bu yap\u0131 ile tutarl\u0131 se\u00e7ilir. Her sistem ayn\u0131 kat\u0131l\u0131\u011f\u0131 uygulamasa da, \u201cHELO ad\u0131 \u2194 PTR ad\u0131 \u2194 A kayd\u0131\u201d tutarl\u0131l\u0131\u011f\u0131 temiz bir kurulumdur.<\/p>\n<h2>PTR (rDNS) kurulumu: ad\u0131m ad\u0131m kontrol listesi<\/h2>\n<p>A\u015fa\u011f\u0131daki ad\u0131mlar, bir mail sunucusu veya SMTP \u00e7\u0131k\u0131\u015f\u0131 olan bir sistem i\u00e7in genel bir yol haritas\u0131d\u0131r:<\/p>\n<h3>1) G\u00f6nderim IP\u2019nizi netle\u015ftirin<\/h3>\n<p>\u00d6nce hangi IP\u2019den d\u0131\u015f d\u00fcnyaya SMTP ba\u011flant\u0131s\u0131 kurdu\u011funuzu bilin. NAT arkas\u0131nda olabilirsiniz; uygulama sunucunuz farkl\u0131 IP\u2019den \u00e7\u0131k\u0131yor olabilir; bir e-posta servisinin \u00e7\u0131k\u0131\u015f IP\u2019leri bamba\u015fka olabilir. Yanl\u0131\u015f IP\u2019ye PTR tan\u0131mlamak en s\u0131k yap\u0131lan hatalardand\u0131r.<\/p>\n<h3>2) PTR kayd\u0131n\u0131n nereden y\u00f6netildi\u011fini belirleyin<\/h3>\n<p>PTR kayd\u0131, IP blo\u011funun reverse zone\u2019unda tutulur ve \u00e7o\u011funlukla IP\u2019yi sa\u011flayan kurum taraf\u0131ndan y\u00f6netilir. Bu genellikle:<\/p>\n<ul>\n<li>Sunucu sa\u011flay\u0131c\u0131s\u0131n\u0131n m\u00fc\u015fteri paneli<\/li>\n<li>ISP\/operat\u00f6r destek talebi<\/li>\n<li>Kurumsal IP tahsisi yapan network ekibi<\/li>\n<\/ul>\n<p>Alan ad\u0131n\u0131z\u0131n DNS panelinde \u201cPTR ekle\u201d g\u00f6rseniz bile, bu her zaman etkili olmayabilir. Yetkili olan taraf, IP blo\u011funu y\u00f6neten otoritedir.<\/p>\n<h3>3) Se\u00e7ti\u011finiz hostname i\u00e7in A\/AAAA kayd\u0131 ekleyin<\/h3>\n<p>Alan ad\u0131n\u0131z\u0131n DNS\u2019inde, PTR\u2019nin i\u015faret edece\u011fi hostname i\u00e7in A kayd\u0131n\u0131 (IPv4) ve gerekiyorsa AAAA kayd\u0131n\u0131 (IPv6) olu\u015fturun. A\/AAAA kayd\u0131, ayn\u0131 g\u00f6nderim IP\u2019sini g\u00f6stermelidir.<\/p>\n<h3>4) Reverse ve forward tutarl\u0131l\u0131\u011f\u0131n\u0131 do\u011frulay\u0131n<\/h3>\n<p>Do\u011frulama s\u0131ras\u0131nda \u015fu mant\u0131\u011f\u0131 izleyin: IP\u2019ye reverse sorgu yap\u0131nca hostname geliyor mu, hostname\u2019e forward sorgu yap\u0131nca ayn\u0131 IP\u2019ye d\u00f6n\u00fcyor mu. DNS de\u011fi\u015fiklikleri TTL nedeniyle hemen yans\u0131mayabilir; planlama yap\u0131n.<\/p>\n<h3>5) SMTP\/HELO ad\u0131n\u0131 tutarl\u0131 hale getirin<\/h3>\n<p>Mail sunucunuzun HELO\/EHLO ad\u0131, m\u00fcmk\u00fcnse PTR hostname\u2019i ile ayn\u0131 veya ayn\u0131 alan ad\u0131 alt\u0131nda ili\u015fkili olmal\u0131d\u0131r. Ama\u00e7, al\u0131c\u0131 tarafta \u201cbu makine kendini farkl\u0131 bir isimle tan\u0131t\u0131yor\u201d gibi bir tutars\u0131zl\u0131k izlenimi olu\u015fturmamakt\u0131r.<\/p>\n<h2>Yayg\u0131n PTR\/rDNS hatalar\u0131 ve nas\u0131l \u00f6nlenir?<\/h2>\n<h3>Ayn\u0131 IP\u2019ye birden fazla PTR beklemek<\/h3>\n<p>DNS standartlar\u0131nda bir IP i\u00e7in birden fazla PTR teknik olarak m\u00fcmk\u00fcn olsa da, pratikte e-posta i\u00e7in \u00f6nerilmez. Tutars\u0131zl\u0131k ve puanlama sorunlar\u0131na yol a\u00e7abilir. Tek, stabil PTR kullan\u0131n.<\/p>\n<h3>PTR\u2019nin ba\u015fka bir domain\u2019e i\u015faret etmesi<\/h3>\n<p>G\u00f6nderim domain\u2019iniz sirketiniz.com iken PTR\u2019nin alakas\u0131z bir domaine gitmesi (\u00f6r. eski bir marka, farkl\u0131 m\u00fc\u015fteri, sa\u011flay\u0131c\u0131 markas\u0131) risk sinyali olabilir. M\u00fcmk\u00fcnse kendi alan ad\u0131n\u0131z alt\u0131nda bir hostname se\u00e7in.<\/p>\n<h3>IPv6\u2019y\u0131 unutmak<\/h3>\n<p>Sunucunuz IPv6 \u00fczerinden de \u00e7\u0131k\u0131\u015f yap\u0131yorsa, IPv6 adresi i\u00e7in de PTR gerekir. IPv6 reverse (ip6.arpa) y\u00f6netimi ayr\u0131 olabilir. Sadece IPv4 PTR yapmak bazen yeterli g\u00f6r\u00fcnse de, \u00e7ift y\u0131\u011f\u0131nl\u0131 ortamlarda eksik kal\u0131r.<\/p>\n<h3>Yanl\u0131\u015f IP\u2019den g\u00f6nderim<\/h3>\n<p>\u00d6zellikle bulut ortamlar\u0131nda uygulama sunucusunun de\u011fil, \u00e7\u0131k\u0131\u015f gateway\u2019inin IP\u2019si g\u00f6r\u00fcnebilir. PTR\u2019yi do\u011fru IP i\u00e7in ayarlad\u0131\u011f\u0131n\u0131zdan emin olun; aksi halde \u201cPTR yapt\u0131m ama etkisi yok\u201d \u015fikayetleri ortaya \u00e7\u0131kar.<\/p>\n<h2>PTR tek ba\u015f\u0131na yeterli mi? Ne zaman sorun aramal\u0131s\u0131n\u0131z?<\/h2>\n<p>PTR do\u011fru olsa bile teslim edilebilirlik problemleri ya\u015fanabilir. E\u011fer e-postalar\u0131n\u0131z spam\u2019e d\u00fc\u015f\u00fcyorsa veya reddediliyorsa, PTR\u2019yi bir \u201ctemel hijyen\u201d ad\u0131m\u0131 olarak g\u00f6r\u00fcn ve di\u011fer alanlara bak\u0131n:<\/p>\n<ul>\n<li>SPF kayd\u0131 do\u011fru mu ve yetkili g\u00f6nderim kaynaklar\u0131n\u0131 kaps\u0131yor mu?<\/li>\n<li>DKIM imzas\u0131 var m\u0131 ve do\u011frulan\u0131yor mu?<\/li>\n<li>DMARC politikas\u0131 ve alignment do\u011fru mu?<\/li>\n<li>IP ve domain itibar\u0131 nas\u0131l? G\u00f6nderim hacmi\/artan trafik do\u011fal m\u0131?<\/li>\n<li>\u0130leti i\u00e7erikleri (ba\u011flant\u0131, ek, format) tetikleyici mi?<\/li>\n<\/ul>\n<p>PTR \u00e7o\u011fu zaman \u201csorunu tek ba\u015f\u0131na \u00e7\u00f6zmez\u201d ama \u201csorun \u00e7\u0131karabilecek gereksiz bir a\u00e7\u0131\u011f\u0131 kapat\u0131r\u201d. Bu y\u00fczden kurulumun ilk a\u015famalar\u0131nda tamamlanmas\u0131 \u00f6nerilir.<\/p>\n<h2>Son kontrol listesi ve pratik \u00f6neriler<\/h2>\n<ul>\n<li>G\u00f6nderim IP\u2019niz i\u00e7in PTR kayd\u0131 tan\u0131ml\u0131 m\u0131?<\/li>\n<li>PTR\u2019nin d\u00f6nd\u00fcrd\u00fc\u011f\u00fc hostname i\u00e7in A\/AAAA kayd\u0131 ayn\u0131 IP\u2019yi g\u00f6steriyor mu?<\/li>\n<li>SMTP sunucunuzun HELO\/EHLO ad\u0131 bu hostname ile tutarl\u0131 m\u0131?<\/li>\n<li>IPv6 kullan\u0131yorsan\u0131z IPv6 PTR de tan\u0131ml\u0131 m\u0131?<\/li>\n<li>DNS TTL ve de\u011fi\u015fiklik yay\u0131l\u0131m\u0131 i\u00e7in yeterli s\u00fcre tan\u0131nd\u0131 m\u0131?<\/li>\n<\/ul>\n<p>E-posta altyap\u0131n\u0131z\u0131 y\u00f6netirken PTR\/rDNS, SPF\/DKIM\/DMARC ve TLS gibi temel ta\u015flar birlikte ele al\u0131nd\u0131\u011f\u0131nda daha \u00f6ng\u00f6r\u00fclebilir bir teslim edilebilirlik elde edersiniz. MX1Mail\u2019e ge\u00e7i\u015f veya mevcut kurulumunuzu g\u00f6zden ge\u00e7irme s\u00fcre\u00e7lerinde, g\u00f6nderim alan ad\u0131n\u0131z ve DNS kay\u0131tlar\u0131n\u0131z planlan\u0131rken PTR tutarl\u0131l\u0131\u011f\u0131n\u0131 da kontrol listesine eklemek, sonradan ortaya \u00e7\u0131kabilecek teslimat sorunlar\u0131n\u0131 azaltmaya yard\u0131mc\u0131 olur.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>PTR (rDNS) kayd\u0131n\u0131n ne oldu\u011funu, mail sunucular\u0131nda neden beklendi\u011fini, do\u011fru kurulum ad\u0131mlar\u0131n\u0131 ve yayg\u0131n hatalar\u0131 teslim edilebilirlik oda\u011f\u0131nda \u00f6\u011frenin.<\/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":[320,318,277],"class_list":["post-133","post","type-post","status-publish","format-standard","hentry","category-dns-ve-e-posta-altyapisi","tag-ptr-kaydi","tag-reverse-dns-rdns","tag-teslim-edilebilirlik"],"_links":{"self":[{"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/posts\/133","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=133"}],"version-history":[{"count":0,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/posts\/133\/revisions"}],"wp:attachment":[{"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/media?parent=133"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/categories?post=133"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/tags?post=133"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}