{"id":4398,"date":"2026-02-03T21:24:30","date_gmt":"2026-02-03T18:24:30","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/en-sik-yapilan-dns-hatalari-web-sitesi-ve-e-postayi-ucurmadan-once-kontrol-etmeniz-gereken-10-kayit\/"},"modified":"2026-02-03T21:24:30","modified_gmt":"2026-02-03T18:24:30","slug":"en-sik-yapilan-dns-hatalari-web-sitesi-ve-e-postayi-ucurmadan-once-kontrol-etmeniz-gereken-10-kayit","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/en-sik-yapilan-dns-hatalari-web-sitesi-ve-e-postayi-ucurmadan-once-kontrol-etmeniz-gereken-10-kayit\/","title":{"rendered":"En S\u0131k Yap\u0131lan DNS Hatalar\u0131: Web Sitesi ve E\u2011Postay\u0131 U\u00e7urmadan \u00d6nce Kontrol Etmeniz Gereken 10 Kay\u0131t"},"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=\"#DNS_Ayarlarinda_Kucuk_Hata_Buyuk_Kesinti_Nerede_Takiliyoruz\"><span class=\"toc_number toc_depth_1\">1<\/span> DNS Ayarlar\u0131nda K\u00fc\u00e7\u00fck Hata, B\u00fcy\u00fck Kesinti: Nerede Tak\u0131l\u0131yoruz?<\/a><\/li><li><a href=\"#Kontrol_Listesi_Web_Sitesi_ve_EPostayi_Ucurmadan_Once_Bakmaniz_Gereken_10_DNS_Kaydi\"><span class=\"toc_number toc_depth_1\">2<\/span> Kontrol Listesi: Web Sitesi ve E\u2011Postay\u0131 U\u00e7urmadan \u00d6nce Bakman\u0131z Gereken 10 DNS Kayd\u0131<\/a><ul><li><a href=\"#1_NS_Kayitlari_Yanlis_Yetkili_DNS_Sunuculari\"><span class=\"toc_number toc_depth_2\">2.1<\/span> 1. NS Kay\u0131tlar\u0131: Yanl\u0131\u015f Yetkili DNS Sunucular\u0131<\/a><\/li><li><a href=\"#2_A_AAAA_Kayitlari_Yanlis_IP_Adresi_veya_Eski_Sunucuya_Bakan_Site\"><span class=\"toc_number toc_depth_2\">2.2<\/span> 2. A \/ AAAA Kay\u0131tlar\u0131: Yanl\u0131\u015f IP Adresi veya Eski Sunucuya Bakan Site<\/a><\/li><li><a href=\"#3_Kok_Alan_Adi_examplecom_ve_www_Tutarsizliklari\"><span class=\"toc_number toc_depth_2\">2.3<\/span> 3. K\u00f6k Alan Ad\u0131 (example.com) ve www Tutars\u0131zl\u0131klar\u0131<\/a><\/li><li><a href=\"#4_MX_Kayitlari_EPostanin_Gittigi_Yeri_Karistirmak\"><span class=\"toc_number toc_depth_2\">2.4<\/span> 4. MX Kay\u0131tlar\u0131: E\u2011Postan\u0131n Gitti\u011fi Yeri Kar\u0131\u015ft\u0131rmak<\/a><\/li><li><a href=\"#5_SPF_TXT_Kayitlari_10_DNS_Lookup_Limitine_Carpmak_ve_Yanlis_Izinler\"><span class=\"toc_number toc_depth_2\">2.5<\/span> 5. SPF (TXT) Kay\u0131tlar\u0131: 10 DNS Lookup Limitine \u00c7arpmak ve Yanl\u0131\u015f \u0130zinler<\/a><\/li><li><a href=\"#6_DKIM_Kayitlari_Eksik_Anahtar_Yanlis_Selector_Yanlis_TXT_Formati\"><span class=\"toc_number toc_depth_2\">2.6<\/span> 6. DKIM Kay\u0131tlar\u0131: Eksik Anahtar, Yanl\u0131\u015f Selector, Yanl\u0131\u015f TXT Format\u0131<\/a><\/li><li><a href=\"#7_DMARC_Kayitlari_Yanlis_Politika_Yanlis_Rapor_Adresi_Eksik_Kurulum\"><span class=\"toc_number toc_depth_2\">2.7<\/span> 7. DMARC Kay\u0131tlar\u0131: Yanl\u0131\u015f Politika, Yanl\u0131\u015f Rapor Adresi, Eksik Kurulum<\/a><\/li><li><a href=\"#8_PTR_Reverse_DNS_Kayitlari_Imzasiz_Gonderen_IP\"><span class=\"toc_number toc_depth_2\">2.8<\/span> 8. PTR (Reverse DNS) Kay\u0131tlar\u0131: \u0130mzas\u0131z G\u00f6nderen IP<\/a><\/li><li><a href=\"#9_CNAMEi_Yanlis_Yerde_Kullanmak_Kokte_CNAME_MXe_CNAME_Zincirli_Yonlendirmeler\"><span class=\"toc_number toc_depth_2\">2.9<\/span> 9. CNAME\u2019i Yanl\u0131\u015f Yerde Kullanmak: K\u00f6kte CNAME, MX\u2019e CNAME, Zincirli Y\u00f6nlendirmeler<\/a><\/li><li><a href=\"#10_TTL_ve_SOA_Degerleri_Yanlis_On_Bellek_Sureleri_Bitmeyen_Yayilim_Problemleri\"><span class=\"toc_number toc_depth_2\">2.10<\/span> 10. TTL ve SOA De\u011ferleri: Yanl\u0131\u015f \u00d6n Bellek S\u00fcreleri, Bitmeyen Yay\u0131l\u0131m Problemleri<\/a><\/li><\/ul><\/li><li><a href=\"#Gercek_Sorunlari_Teshis_Etmek_Sorun_DNS_mi_Sunucu_mu\"><span class=\"toc_number toc_depth_1\">3<\/span> Ger\u00e7ek Sorunlar\u0131 Te\u015fhis Etmek: Sorun DNS mi, Sunucu mu?<\/a><\/li><li><a href=\"#Ozet_ve_Yol_Haritasi_DNSi_Bir_Defa_Duzeltin_Uzun_Sure_Rahat_Edin\"><span class=\"toc_number toc_depth_1\">4<\/span> \u00d6zet ve Yol Haritas\u0131: DNS\u2019i Bir Defa D\u00fczeltin, Uzun S\u00fcre Rahat Edin<\/a><\/li><\/ul><\/div>\n<h2><span id=\"DNS_Ayarlarinda_Kucuk_Hata_Buyuk_Kesinti_Nerede_Takiliyoruz\">DNS Ayarlar\u0131nda K\u00fc\u00e7\u00fck Hata, B\u00fcy\u00fck Kesinti: Nerede Tak\u0131l\u0131yoruz?<\/span><\/h2>\n<p>Web siteniz ve kurumsal e\u2011postan\u0131z \u00e7al\u0131\u015f\u0131yorsa, \u00e7o\u011fu zaman DNS\u2019i hi\u00e7 d\u00fc\u015f\u00fcnmeyiz. Ama alan ad\u0131n\u0131z\u0131 yeni hostinge ta\u015f\u0131y\u0131nca, e\u2011posta servisini de\u011fi\u015ftirince veya Cloudflare gibi bir CDN ekleyince, en ufak bir DNS hatas\u0131 bile saatlerce s\u00fcren eri\u015fim sorunlar\u0131na, \u201cmail gelmiyor\u201d \u015fikayetlerine ve SEO taraf\u0131nda istenmeyen sonu\u00e7lara yol a\u00e7abiliyor. DCHost ekibi olarak yeni gelen projelerde en \u00e7ok vakit harcad\u0131\u011f\u0131m\u0131z yerlerden biri, bozuk veya da\u011f\u0131n\u0131k DNS kay\u0131tlar\u0131n\u0131 toparlamak.<\/p>\n<p>Bu yaz\u0131da \u201cDNS nedir?\u201d d\u00fczeyinde temel anlat\u0131mdan \u00e7ok, <strong>ger\u00e7ek d\u00fcnyada en s\u0131k patlayan 10 DNS kayd\u0131<\/strong> \u00fczerine odaklanaca\u011f\u0131z. Hedefimiz basit: Alan ad\u0131n\u0131z\u0131n DNS paneline girdi\u011finizde, web sitesi ve e\u2011postay\u0131 u\u00e7urmadan \u00f6nce bakman\u0131z gereken kritik noktalar\u0131 net bir kontrol listesi haline getirmek. Teknik terimleri m\u00fcmk\u00fcn oldu\u011funca sadele\u015ftirerek ve sahadan \u00f6rneklerle anlataca\u011f\u0131m; b\u00f6ylece ister ajans olun, ister KOB\u0130, ister tek geli\u015ftirici, kendi alan ad\u0131n\u0131z\u0131n DNS sa\u011fl\u0131\u011f\u0131n\u0131 g\u00fcvenle kontrol edebileceksiniz.<\/p>\n<h2><span id=\"Kontrol_Listesi_Web_Sitesi_ve_EPostayi_Ucurmadan_Once_Bakmaniz_Gereken_10_DNS_Kaydi\">Kontrol Listesi: Web Sitesi ve E\u2011Postay\u0131 U\u00e7urmadan \u00d6nce Bakman\u0131z Gereken 10 DNS Kayd\u0131<\/span><\/h2>\n<p>Ba\u015flamadan \u00f6nce, DNS kay\u0131t t\u00fcrleriyle ilgili kapsaml\u0131 bir \u00f6zet istiyorsan\u0131z, <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\u0131 A\u2019dan Z\u2019ye rehberimize<\/a> mutlaka g\u00f6z at\u0131n. Burada ise do\u011frudan \u201cen s\u0131k yap\u0131lan hatalar\u201d perspektifinden ilerleyece\u011fiz.<\/p>\n<h3><span id=\"1_NS_Kayitlari_Yanlis_Yetkili_DNS_Sunuculari\">1. NS Kay\u0131tlar\u0131: Yanl\u0131\u015f Yetkili DNS Sunucular\u0131<\/span><\/h3>\n<p>NS (Name Server) kay\u0131tlar\u0131, alan ad\u0131n\u0131z\u0131n \u201cDNS\u2019ine kim bak\u0131yor?\u201d sorusunun cevab\u0131d\u0131r. Yani taray\u0131c\u0131lar ve di\u011fer DNS \u00e7\u00f6z\u00fcc\u00fcler, hangi DNS sunucular\u0131ndan A, MX, TXT gibi kay\u0131tlar\u0131 alaca\u011f\u0131n\u0131 NS kay\u0131tlar\u0131 sayesinde bilir. En s\u0131k g\u00f6rd\u00fc\u011f\u00fcm\u00fcz sorun, alan ad\u0131n\u0131n <strong>NS kay\u0131tlar\u0131n\u0131n bir yere<\/strong>, ger\u00e7ek kay\u0131tlar\u0131n ise <strong>ba\u015fka bir DNS paneline<\/strong> yaz\u0131l\u0131 olmas\u0131.<\/p>\n<p>DCHost\u2019a proje ta\u015f\u0131yan bir ajans m\u00fc\u015fterisinde \u015fu senaryoyu s\u0131k g\u00f6r\u00fcyoruz:<\/p>\n<ul>\n<li>Alan ad\u0131 kay\u0131t firmas\u0131nda NS kay\u0131tlar\u0131 h\u00e2l\u00e2 eski hosting firmas\u0131n\u0131 g\u00f6steriyor.<\/li>\n<li>Ajans yeni A, MX, SPF kay\u0131tlar\u0131n\u0131 DCHost DNS paneline giriyor.<\/li>\n<li>Sonu\u00e7: Ziyaret\u00e7iler ve e\u2011posta trafi\u011fi eski DNS\u2019e bakt\u0131\u011f\u0131 i\u00e7in, yap\u0131lan hi\u00e7bir de\u011fi\u015fiklik etkisini g\u00f6stermiyor.<\/li>\n<\/ul>\n<p><strong>Kontrol etmeniz gerekenler:<\/strong><\/p>\n<ul>\n<li>Alan ad\u0131n\u0131n <strong>registry taraf\u0131ndaki NS kay\u0131tlar\u0131<\/strong> ile fiilen kulland\u0131\u011f\u0131n\u0131z DNS panelinin NS adresleri birebir ayn\u0131 m\u0131?<\/li>\n<li>Ayn\u0131 alan ad\u0131 i\u00e7in <strong>iki farkl\u0131 DNS sa\u011flay\u0131c\u0131da paralel kay\u0131t<\/strong> tutmuyor musunuz?<\/li>\n<li>Her nameserver \u00e7ifti i\u00e7in NS kay\u0131tlar\u0131 <strong>en az iki sunucu<\/strong> g\u00f6steriyor mu (ns1 \/ ns2 gibi)?<\/li>\n<\/ul>\n<p>\u00d6zellikle hosting veya DNS sa\u011flay\u0131c\u0131s\u0131 de\u011fi\u015ftirirken NS kay\u0131tlar\u0131n\u0131 do\u011fru ta\u015f\u0131mak i\u00e7in, <a href=\"https:\/\/www.dchost.com\/blog\/hosting-firmasi-degistirirken-dns-ve-domain-tasima-kontrol-listesi\/\">DNS ve domain ta\u015f\u0131ma kontrol listemizi<\/a> s\u00fcrecin ba\u015f\u0131nda elinizin alt\u0131nda tutman\u0131z \u00e7ok faydal\u0131 olur.<\/p>\n<h3><span id=\"2_A_AAAA_Kayitlari_Yanlis_IP_Adresi_veya_Eski_Sunucuya_Bakan_Site\">2. A \/ AAAA Kay\u0131tlar\u0131: Yanl\u0131\u015f IP Adresi veya Eski Sunucuya Bakan Site<\/span><\/h3>\n<p>A kayd\u0131 (IPv4) ve AAAA kayd\u0131 (IPv6), alan ad\u0131n\u0131z\u0131 hangi IP adresine y\u00f6nlendirece\u011finizi belirler. En kritik hatalardan biri, <strong>yanl\u0131\u015f veya eski IP\u2019ye bakan A\/AAAA kay\u0131tlar\u0131<\/strong>d\u0131r. Bu genellikle \u015fu durumlarda ortaya \u00e7\u0131kar:<\/p>\n<ul>\n<li>Yeni hosting veya <a href=\"https:\/\/www.dchost.com\/tr\/vps\">VPS<\/a>\u2019e ge\u00e7ilmi\u015f, fakat DNS\u2019te A kayd\u0131 h\u00e2l\u00e2 eski IP\u2019yi g\u00f6steriyor.<\/li>\n<li>Ge\u00e7ici test sunucusu i\u00e7in a\u00e7\u0131lan IP, yay\u0131na ta\u015f\u0131nd\u0131ktan sonra temizlenmiyor ve yanl\u0131\u015fl\u0131kla live site o IP\u2019ye \u00e7ekiliyor.<\/li>\n<li>IPv6 (AAAA) ekleniyor ancak sunucu taraf\u0131nda IPv6 konfig\u00fcrasyonu haz\u0131r de\u011fil, site baz\u0131 kullan\u0131c\u0131lar i\u00e7in a\u00e7\u0131lmaz hale geliyor.<\/li>\n<\/ul>\n<p><strong>\u00d6neriler:<\/strong><\/p>\n<ul>\n<li>Alan ad\u0131n\u0131z (\u00f6r. <code>example.com<\/code>) i\u00e7in A kayd\u0131n\u0131n <strong>sadece tek bir IP\u2019ye<\/strong> bakmas\u0131na \u00f6zen g\u00f6sterin (\u00f6zel bir geo-DNS mimariniz yoksa).<\/li>\n<li>AAAA kayd\u0131 eklemeden \u00f6nce, VPS veya sunucunuzda IPv6\u2019n\u0131n ger\u00e7ekten <strong>do\u011fru yap\u0131land\u0131r\u0131ld\u0131\u011f\u0131ndan<\/strong> emin olun.<\/li>\n<li>Ta\u015f\u0131ma sonras\u0131, eski IP\u2019yi mutlaka not al\u0131n ama aktif DNS kay\u0131tlar\u0131ndan temizleyin; kar\u0131\u015f\u0131kl\u0131\u011f\u0131 azalt\u0131r.<\/li>\n<\/ul>\n<p>IP de\u011fi\u015fimlerinde DNS yay\u0131l\u0131m s\u00fcresinin neden bazen 24 saate kadar uzayabildi\u011fini daha iyi anlamak i\u00e7in, <a href=\"https:\/\/www.dchost.com\/blog\/dns-yayilim-suresi-nedir-neden-24-saat-surer-ve-nasil-hizlandirilir\/\">DNS yay\u0131l\u0131m\u0131 ve h\u0131zland\u0131rma rehberimizi<\/a> inceleyebilirsiniz.<\/p>\n<h3><span id=\"3_Kok_Alan_Adi_examplecom_ve_www_Tutarsizliklari\">3. K\u00f6k Alan Ad\u0131 (example.com) ve www Tutars\u0131zl\u0131klar\u0131<\/span><\/h3>\n<p>Bir\u00e7ok projede k\u00f6k alan ad\u0131 (<code>example.com<\/code>) ve <code>www.example.com<\/code> i\u00e7in farkl\u0131 DNS stratejileri izleniyor. En s\u0131k g\u00f6rd\u00fc\u011f\u00fcm\u00fcz sorunlar:<\/p>\n<ul>\n<li><code>example.com<\/code> i\u00e7in A kayd\u0131 var, ama <code>www.example.com<\/code> hi\u00e7 tan\u0131ml\u0131 de\u011fil (www\u2019li URL\u2019ler a\u00e7\u0131lm\u0131yor).<\/li>\n<li>Hem k\u00f6k alan ad\u0131 hem de www alt alan\u0131 <strong>farkl\u0131 IP\u2019lere<\/strong> bak\u0131yor; bazen staging, bazen prod, bazen farkl\u0131 \u00fclkedeki sunucu.<\/li>\n<li>CDN kullan\u0131rken k\u00f6ke A, www\u2019ye CNAME veriliyor ama hedefler yanl\u0131\u015f ayarlanm\u0131\u015f; birinde CDN, di\u011ferinde direkt origin \u00e7al\u0131\u015f\u0131yor.<\/li>\n<\/ul>\n<p><strong>\u0130yi pratik yakla\u015f\u0131m:<\/strong><\/p>\n<ul>\n<li>Genellikle <code>www.example.com<\/code> i\u00e7in bir <strong>CNAME<\/strong> kullan\u0131p k\u00f6k alan ad\u0131na y\u00f6nlendirmek daha d\u00fczenli bir mimari sa\u011flar.<\/li>\n<li>K\u00f6k alan ad\u0131 i\u00e7in A kayd\u0131 (ve gerekiyorsa AAAA) tan\u0131mlay\u0131n; www\u2019nin CNAME ile bu kayd\u0131 i\u015faret etmesi i\u015fleri sadele\u015ftirir.<\/li>\n<li>T\u00fcm SEO ve HTTPS stratejinizi (www mi, \u00e7\u0131plak domain mi?) belirleyip, bu karar\u0131 DNS + 301 y\u00f6nlendirme ile tutarl\u0131 hale getirin. Bu konuda ayr\u0131nt\u0131l\u0131 \u00f6rnekler i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/www-mi-ciplak-alan-adi-mi-canonical-domain-301-ve-hsts-icin-dogru-ayarlar\/\">www mi \u00e7\u0131plak alan ad\u0131 m\u0131 rehberimize<\/a> g\u00f6z atabilirsiniz.<\/li>\n<\/ul>\n<h3><span id=\"4_MX_Kayitlari_EPostanin_Gittigi_Yeri_Karistirmak\">4. MX Kay\u0131tlar\u0131: E\u2011Postan\u0131n Gitti\u011fi Yeri Kar\u0131\u015ft\u0131rmak<\/span><\/h3>\n<p>MX kay\u0131tlar\u0131, alan ad\u0131n\u0131z i\u00e7in hangi sunucunun e\u2011posta kabul etti\u011fini belirler. E\u2011posta kesintilerinin \u00f6nemli bir k\u0131sm\u0131, yanl\u0131\u015f veya eksik MX kay\u0131tlar\u0131ndan kaynaklan\u0131yor. Tipik hatalar:<\/p>\n<ul>\n<li>Yeni hosting\u2019e ge\u00e7erken <strong>web sitesi ta\u015f\u0131n\u0131yor ama MX kay\u0131tlar\u0131 unutuluyor<\/strong>; e\u2011postalar h\u00e2l\u00e2 eski sunucuya gitmeye \u00e7al\u0131\u015f\u0131yor.<\/li>\n<li>MX kayd\u0131 bir alan ad\u0131n\u0131 g\u00f6steriyor ama bu alan ad\u0131 i\u00e7in A kayd\u0131 yok (veya yanl\u0131\u015f IP\u2019ye bak\u0131yor); e\u2011posta geri d\u00f6n\u00fcyor.<\/li>\n<li>Birden fazla MX tan\u0131mlanm\u0131\u015f ama \u00f6ncelik (<code>priority<\/code>) de\u011ferleri geli\u015fig\u00fczel verilmi\u015f; backup MX as\u0131l MX\u2019ten daha y\u00fcksek \u00f6ncelikte.<\/li>\n<\/ul>\n<p><strong>Nelere dikkat etmelisiniz?<\/strong><\/p>\n<ul>\n<li>MX kay\u0131tlar\u0131 <strong>mutlaka bir alan ad\u0131na<\/strong> i\u015faret etmeli, do\u011frudan IP\u2019ye de\u011fil.<\/li>\n<li>MX\u2019in i\u015faret etti\u011fi alan adlar\u0131 i\u00e7in mutlaka <strong>A (ve gerekiyorsa AAAA) kay\u0131tlar\u0131<\/strong> tan\u0131ml\u0131 olmal\u0131.<\/li>\n<li>Tek bir ana mail sunucusu kullan\u0131yorsan\u0131z, <code>priority<\/code> de\u011feri \u00f6rne\u011fin 10 olabilir; varsa yedek MX\u2019ler daha y\u00fcksek de\u011fer (20, 30) almal\u0131.<\/li>\n<\/ul>\n<p>Yeni bir e\u2011posta altyap\u0131s\u0131na ge\u00e7erken s\u0131f\u0131r kesinti hedefliyorsan\u0131z, MX ve di\u011fer kay\u0131tlar\u0131n nas\u0131l planlanmas\u0131 gerekti\u011fini <a href=\"https:\/\/www.dchost.com\/blog\/e-posta-altyapisini-tasirken-kesinti-yasamamak\/\">e\u2011posta altyap\u0131s\u0131 ta\u015f\u0131rken kesinti ya\u015famama rehberimizde<\/a> ayr\u0131nt\u0131l\u0131 anlatt\u0131k.<\/p>\n<h3><span id=\"5_SPF_TXT_Kayitlari_10_DNS_Lookup_Limitine_Carpmak_ve_Yanlis_Izinler\">5. SPF (TXT) Kay\u0131tlar\u0131: 10 DNS Lookup Limitine \u00c7arpmak ve Yanl\u0131\u015f \u0130zinler<\/span><\/h3>\n<p>SPF kayd\u0131, alan ad\u0131n\u0131z ad\u0131na hangi sunucular\u0131n e\u2011posta g\u00f6ndermeye yetkili oldu\u011funu tan\u0131mlar. Hata t\u00fcr\u00fc \u00e7ok, ama en s\u0131k g\u00f6rd\u00fcklerimiz \u015funlar:<\/p>\n<ul>\n<li>Birden fazla SPF kayd\u0131: \u00d6rne\u011fin hem hosting paneli hem de \u00fc\u00e7\u00fcnc\u00fc parti bir servis SPF ekliyor; sonu\u00e7ta <strong>iki SPF TXT kayd\u0131<\/strong> olu\u015fuyor ve bu ge\u00e7ersiz.<\/li>\n<li>Gere\u011finden fazla <code>include:<\/code> ile 10 DNS lookup limitine \u00e7arp\u0131p, SPF\u2019in fiilen bo\u015fa d\u00fc\u015fmesi.<\/li>\n<li>\u201cTest i\u00e7in\u201d eklenen <code>+all<\/code> gibi a\u015f\u0131r\u0131 geni\u015f izinlerin unutulmas\u0131; spam g\u00f6nderen herkes bu alan ad\u0131 ad\u0131na mail atabiliyor.<\/li>\n<\/ul>\n<p><strong>\u0130yi pratikler:<\/strong><\/p>\n<ul>\n<li>Her alan ad\u0131 i\u00e7in <strong>sadece 1 adet<\/strong> SPF TXT kayd\u0131 olmal\u0131.<\/li>\n<li>SPF kayd\u0131n\u0131 d\u00fczenlerken hangi sistemlerin ger\u00e7ekten e\u2011posta g\u00f6nderdi\u011fini netle\u015ftirin: Hosting sunucusu, transactional servis, pazarlama arac\u0131 vb.<\/li>\n<li>\u201c10 lookup\u201d limitine yakla\u015ft\u0131ysan\u0131z, <a href=\"https:\/\/www.dchost.com\/blog\/gelismis-spf-yonetimi-10-dns-lookup-limitine-takilmadan-coklu-e-posta-servisi-kullanmak\/\">geli\u015fmi\u015f SPF y\u00f6netimi ve lookup limitini a\u015fmadan \u00e7oklu servis kullanma<\/a> rehberimize mutlaka bak\u0131n.<\/li>\n<\/ul>\n<h3><span id=\"6_DKIM_Kayitlari_Eksik_Anahtar_Yanlis_Selector_Yanlis_TXT_Formati\">6. DKIM Kay\u0131tlar\u0131: Eksik Anahtar, Yanl\u0131\u015f Selector, Yanl\u0131\u015f TXT Format\u0131<\/span><\/h3>\n<p>DKIM, e\u2011postan\u0131n g\u00f6vdesine kriptografik bir imza ekleyerek, mesaj\u0131n iletim s\u0131ras\u0131nda de\u011fi\u015ftirilmedi\u011fini ve ger\u00e7ekten sizin altyap\u0131n\u0131zdan \u00e7\u0131kt\u0131\u011f\u0131n\u0131 ispatlar. DNS taraf\u0131nda ise DKIM, genellikle <code>selector._domainkey.example.com<\/code> \u015feklinde bir <strong>TXT kayd\u0131<\/strong> olarak tutulur.<\/p>\n<p>Sahada g\u00f6rd\u00fc\u011f\u00fcm\u00fcz yayg\u0131n hatalar:<\/p>\n<ul>\n<li>DKIM public key\u2019i uzun oldu\u011fu i\u00e7in TXT kayd\u0131 yanl\u0131\u015f b\u00f6l\u00fcnm\u00fc\u015f; baz\u0131 DNS panelleri sat\u0131r k\u0131rma ister, baz\u0131lar\u0131 istemez.<\/li>\n<li>Yanl\u0131\u015f selector: Mail sunucusu <code>mail2024<\/code> selector\u2019\u00fcyle imza at\u0131yor, DNS\u2019te ise <code>default._domainkey<\/code> tan\u0131ml\u0131.<\/li>\n<li>E\u2011posta servisi de\u011fi\u015ftirilirken eski DKIM kay\u0131tlar\u0131 silinmiyor, yenisi eklenmiyor; DMARC raporlar\u0131nda s\u00fcrekli \u201cdkim=fail\u201d g\u00f6r\u00fcn\u00fcyor.<\/li>\n<\/ul>\n<p><strong>Kontrol listesi:<\/strong><\/p>\n<ul>\n<li>Kulland\u0131\u011f\u0131n\u0131z her e\u2011posta kayna\u011f\u0131 (hosting, transactional servis vb.) i\u00e7in ilgili DKIM TXT kayd\u0131 ger\u00e7ekten DNS\u2019te tan\u0131ml\u0131 m\u0131?<\/li>\n<li>Selector adlar\u0131 e\u2011posta servisi panelindekiyle birebir ayn\u0131 m\u0131?<\/li>\n<li>TXT de\u011feri panelin destekledi\u011fi bi\u00e7imde (tek sat\u0131r veya do\u011fru b\u00f6l\u00fcnm\u00fc\u015f \u00e7ok sat\u0131r) kaydedildi mi?<\/li>\n<\/ul>\n<h3><span id=\"7_DMARC_Kayitlari_Yanlis_Politika_Yanlis_Rapor_Adresi_Eksik_Kurulum\">7. DMARC Kay\u0131tlar\u0131: Yanl\u0131\u015f Politika, Yanl\u0131\u015f Rapor Adresi, Eksik Kurulum<\/span><\/h3>\n<p>DMARC, SPF ve DKIM sonu\u00e7lar\u0131na bakarak, ge\u00e7ersiz e\u2011postalar i\u00e7in al\u0131c\u0131 sunucular\u0131n ne yapaca\u011f\u0131n\u0131 (kabul, karantina, reddet) belirlemenizi sa\u011flar. Ayr\u0131ca DMARC raporlar\u0131, alan ad\u0131n\u0131z ad\u0131na kimlerin mail g\u00f6ndermeye \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 g\u00f6rmeniz i\u00e7in \u00e7ok k\u0131ymetlidir.<\/p>\n<p>En s\u0131k yap\u0131lan hatalar:<\/p>\n<ul>\n<li>Hi\u00e7 DMARC kayd\u0131 olmamas\u0131: \u00d6zellikle marka de\u011feri olan alan adlar\u0131nda ciddi bir a\u00e7\u0131k kap\u0131.<\/li>\n<li>Bir anda <code>p=reject<\/code> ile ba\u015flamak ve yanl\u0131\u015f yap\u0131land\u0131r\u0131lm\u0131\u015f SPF\/DKIM y\u00fcz\u00fcnden kendi maillerinizi bile reddettirmek.<\/li>\n<li>Rapor e\u2011posta adreslerini (rua, ruf) yanl\u0131\u015f yazmak ya da ge\u00e7ersiz mailbox\u2019lara y\u00f6nlendirmek; de\u011ferli raporlar bo\u015fa gidiyor.<\/li>\n<\/ul>\n<p><strong>Nas\u0131l ilerlemelisiniz?<\/strong><\/p>\n<ul>\n<li>\u00d6nce <code>p=none<\/code> ile ba\u015flay\u0131p, DMARC raporlar\u0131n\u0131 bir s\u00fcre izleyin.<\/li>\n<li>SPF ve DKIM ba\u015far\u0131s\u0131zl\u0131klar\u0131n\u0131 d\u00fczelttik\u00e7e, politikay\u0131 yava\u015f yava\u015f <code>quarantine<\/code> ve <code>reject<\/code> taraf\u0131na \u00e7ekin.<\/li>\n<li>Bu kademeli ge\u00e7i\u015fi nas\u0131l yorumlayaca\u011f\u0131n\u0131z\u0131 ve raporlar\u0131 nas\u0131l okuyaca\u011f\u0131n\u0131z\u0131 <a href=\"https:\/\/www.dchost.com\/blog\/dmarc-raporlari-aggregate-ve-forensic-analiz-ile-pnonedan-prejecte-gecis\/\">p=none\u2019dan p=reject\u2019e ge\u00e7i\u015f rehberimizde<\/a> ad\u0131m ad\u0131m anlatt\u0131k.<\/li>\n<\/ul>\n<h3><span id=\"8_PTR_Reverse_DNS_Kayitlari_Imzasiz_Gonderen_IP\">8. PTR (Reverse DNS) Kay\u0131tlar\u0131: \u0130mzas\u0131z G\u00f6nderen IP<\/span><\/h3>\n<p>\u00d6zellikle kendi VPS\u2019inizden veya <a href=\"https:\/\/www.dchost.com\/tr\/fiziksel-sunucu\">dedicated sunucu<\/a>nuzdan e\u2011posta g\u00f6nderiyorsan\u0131z, PTR (reverse DNS) kritik bir DNS kayd\u0131d\u0131r. Al\u0131c\u0131 mail sunucular\u0131 genellikle g\u00f6nderen IP\u2019nin ters DNS kayd\u0131na bakar ve bu kayd\u0131n, mail ba\u015fl\u0131\u011f\u0131ndaki alan ad\u0131yla tutarl\u0131 olmas\u0131n\u0131 bekler.<\/p>\n<p>En s\u0131k kar\u015f\u0131la\u015ft\u0131\u011f\u0131m\u0131z problemler:<\/p>\n<ul>\n<li>PTR hi\u00e7 tan\u0131ml\u0131 de\u011fil: IP, generic bir ISP host ad\u0131yla g\u00f6r\u00fcn\u00fcyor; spam skorunu y\u00fckseltiyor.<\/li>\n<li>PTR, alan ad\u0131n\u0131zla ilgisiz bir hostname\u2019e i\u015faret ediyor; SPF\/DKIM d\u00fczg\u00fcn olsa bile teslim edilebilirli\u011fi d\u00fc\u015f\u00fcr\u00fcyor.<\/li>\n<li>IP de\u011fi\u015ftirildi\u011finde reverse DNS g\u00fcncellenmiyor; yeni IP\u2019den giden mailler bir anda spam klas\u00f6rlerine d\u00fc\u015fmeye ba\u015fl\u0131yor.<\/li>\n<\/ul>\n<p><strong>\u00d6neriler:<\/strong><\/p>\n<ul>\n<li>PTR, m\u00fcmk\u00fcnse <code>mail.example.com<\/code> gibi e\u2011posta i\u00e7in kulland\u0131\u011f\u0131n\u0131z host ad\u0131na i\u015faret etsin.<\/li>\n<li>Bu host i\u00e7in A kayd\u0131n\u0131n da ayn\u0131 IP\u2019yi g\u00f6stermesi gerekir; b\u00f6ylece forward-reverse DNS tutarl\u0131 olur.<\/li>\n<li>PTR ayar\u0131 genellikle IP sa\u011flay\u0131c\u0131n\u0131z taraf\u0131nda yap\u0131l\u0131r; DCHost VPS veya dedicated sunucu kullan\u0131yorsan\u0131z, destek talebiyle PTR\u2019\u0131 sizin ad\u0131n\u0131za do\u011fru \u015fekilde tan\u0131mlayabiliriz. Ayr\u0131nt\u0131lar i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/ptr-reverse-dns-kaydi-vps-ipniz-icin-dogru-ayar-ve-e-posta-teslimine-etkisi\/\">PTR ve e\u2011posta teslimi rehberimize<\/a> bakabilirsiniz.<\/li>\n<\/ul>\n<h3><span id=\"9_CNAMEi_Yanlis_Yerde_Kullanmak_Kokte_CNAME_MXe_CNAME_Zincirli_Yonlendirmeler\">9. CNAME\u2019i Yanl\u0131\u015f Yerde Kullanmak: K\u00f6kte CNAME, MX\u2019e CNAME, Zincirli Y\u00f6nlendirmeler<\/span><\/h3>\n<p>CNAME, bir alan ad\u0131n\u0131 ba\u015fka bir alan ad\u0131na y\u00f6nlendirmek i\u00e7in harika bir kay\u0131tt\u0131r; ancak yanl\u0131\u015f kullan\u0131ld\u0131\u011f\u0131nda ciddi sorunlara yol a\u00e7ar. \u00d6zellikle \u015fu hatalar\u0131 s\u0131k g\u00f6r\u00fcyoruz:<\/p>\n<ul>\n<li><strong>K\u00f6k alan ad\u0131nda CNAME<\/strong>: Bir\u00e7ok DNS standard\u0131na ve kay\u0131t firmas\u0131na g\u00f6re k\u00f6k alan ad\u0131nda CNAME kullanmak sorunludur; SOA, NS gibi kay\u0131tlarla \u00e7ak\u0131\u015f\u0131r.<\/li>\n<li>MX\u2019in CNAME\u2019i i\u015faret etmesi: MX kay\u0131tlar\u0131 do\u011frudan A (ve gerekirse AAAA) kayd\u0131 bulunan bir hostname\u2019e i\u015faret etmelidir, CNAME zincirleri kabul edilmez.<\/li>\n<li>\u00c7ok katmanl\u0131 CNAME zincirleri: \u00d6rne\u011fin <code>www<\/code> ba\u015fka bir alan ad\u0131na, o alan ad\u0131 bir \u00fc\u00e7\u00fcnc\u00fcs\u00fcne CNAME; her ek halka, hem gecikme hem de hata ihtimalini art\u0131r\u0131r.<\/li>\n<\/ul>\n<p><strong>Do\u011fru yakla\u015f\u0131m:<\/strong><\/p>\n<ul>\n<li>K\u00f6k alan ad\u0131 i\u00e7in A\/AAAA kullan\u0131n; gerekiyorsa alt alanlarda (www, cdn, statik vb.) CNAME\u2019den faydalan\u0131n.<\/li>\n<li>MX daima bir hostname\u2019e gitmeli; o hostname\u2019in A\/AAAA kayd\u0131 do\u011frudan IP\u2019yi g\u00f6stermeli.<\/li>\n<li>CNAME zincirlerini m\u00fcmk\u00fcn oldu\u011funca <strong>tek halkaya<\/strong> indirgeyin; hata ay\u0131klamay\u0131 da ciddi bi\u00e7imde kolayla\u015ft\u0131r\u0131r.<\/li>\n<\/ul>\n<h3><span id=\"10_TTL_ve_SOA_Degerleri_Yanlis_On_Bellek_Sureleri_Bitmeyen_Yayilim_Problemleri\">10. TTL ve SOA De\u011ferleri: Yanl\u0131\u015f \u00d6n Bellek S\u00fcreleri, Bitmeyen Yay\u0131l\u0131m Problemleri<\/span><\/h3>\n<p>TTL (Time To Live), bir DNS kayd\u0131n\u0131n DNS \u00f6nbelleklerinde ne kadar s\u00fcre saklanaca\u011f\u0131n\u0131 belirler. Yanl\u0131\u015f TTL de\u011ferleri y\u00fcz\u00fcnden, asl\u0131nda d\u00fczeltti\u011finiz bir hata ziyaret\u00e7iler i\u00e7in saatlerce devam ediyormu\u015f gibi g\u00f6r\u00fcnebilir. SOA kayd\u0131ndaki varsay\u0131lan TTL ve di\u011fer zaman parametreleri de bu davran\u0131\u015f\u0131 etkiler.<\/p>\n<p>En s\u0131k ya\u015fanan TTL kaynakl\u0131 problemler:<\/p>\n<ul>\n<li>Ta\u015f\u0131ma \u00f6ncesinde TTL de\u011ferleri \u00e7ok y\u00fcksek (\u00f6r. 86400 sn \/ 24 saat) b\u0131rak\u0131l\u0131yor; IP de\u011fi\u015fince yay\u0131l\u0131m \u00e7ok yava\u015f g\u00f6r\u00fcn\u00fcyor.<\/li>\n<li>S\u00fcrekli de\u011fi\u015fmeyecek kay\u0131tlar (\u00f6r. MX, SPF) i\u00e7in gereksiz d\u00fc\u015f\u00fck TTL veriliyor; t\u00fcm d\u00fcnyada gereksiz DNS trafi\u011fi olu\u015fuyor.<\/li>\n<li>Cloudflare gibi CDN\u2019ler kullan\u0131l\u0131rken, DNS TTL ve CDN cache TTL kavramlar\u0131 birbirine kar\u0131\u015ft\u0131r\u0131l\u0131yor.<\/li>\n<\/ul>\n<p><strong>Stratejik ayar \u00f6nerileri:<\/strong><\/p>\n<ul>\n<li>Ta\u015f\u0131ma veya b\u00fcy\u00fck de\u011fi\u015fikliklerin <strong>24\u201348 saat \u00f6ncesinde<\/strong> kritik kay\u0131tlar\u0131n TTL\u2019ini d\u00fc\u015f\u00fcr\u00fcn (\u00f6r. 300 sn).<\/li>\n<li>Stabil kay\u0131tlar i\u00e7in orta seviye TTL (\u00f6r. 3600\u201314400 sn) genellikle yeterlidir.<\/li>\n<li>TTL planlamas\u0131n\u0131 detayl\u0131 ele ald\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/dns-ttl-degerlerini-dogru-ayarlamak-a-mx-cname-ve-txt-kayitlari-icin-stratejik-rehber\/\">DNS TTL stratejisi rehberimizi<\/a> ve ta\u015f\u0131ma s\u0131ras\u0131nda yay\u0131l\u0131m\u0131 h\u0131zland\u0131rmak i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/zero-downtime-tasima-icin-ttl-stratejileri-dns-yayilimini-gercekten-nasil-hizlandirirsin\/\">zero\u2011downtime TTL oyun plan\u0131n\u0131<\/a> mutlaka inceleyin.<\/li>\n<\/ul>\n<p>\u00d6zellikle Cloudflare gibi bir proxy\/CDN araya girdi\u011finde, DNS ve SSL taraf\u0131nda ek katmanlar devreye giriyor. Bu noktada, <a href=\"https:\/\/www.dchost.com\/blog\/cloudflare-dns-ve-ssl-ayarlarini-dogru-yapmak\/\">Cloudflare DNS ve SSL ayarlar\u0131n\u0131 do\u011fru yapmak<\/a> yaz\u0131m\u0131z, pratik senaryolarla s\u0131k yap\u0131lan hatalar\u0131 d\u00fczeltmenize yard\u0131mc\u0131 olacakt\u0131r.<\/p>\n<h2><span id=\"Gercek_Sorunlari_Teshis_Etmek_Sorun_DNS_mi_Sunucu_mu\">Ger\u00e7ek Sorunlar\u0131 Te\u015fhis Etmek: Sorun DNS mi, Sunucu mu?<\/span><\/h2>\n<p>DCHost\u2019ta en s\u0131k ald\u0131\u011f\u0131m\u0131z destek taleplerinden biri \u201cSite a\u00e7\u0131lm\u0131yor, sorun sunucuda olmal\u0131.\u201d c\u00fcmlesiyle ba\u015fl\u0131yor; ancak te\u015fhise ge\u00e7ti\u011fimizde problemin b\u00fcy\u00fck k\u0131sm\u0131n\u0131n <strong>DNS katman\u0131nda<\/strong> oldu\u011funu g\u00f6r\u00fcyoruz. Yanl\u0131\u015f NS, bo\u015fta kalm\u0131\u015f alt alanlar, eksik A kayd\u0131, hatal\u0131 CNAME\u2026 Liste uzay\u0131p gidiyor.<\/p>\n<p>\u00d6zellikle <code>DNS_PROBE_FINISHED_NXDOMAIN<\/code> gibi hatalar al\u0131yorsan\u0131z, <a href=\"https:\/\/www.dchost.com\/blog\/dns-hatalari-yuzunden-site-acilmiyor-dns_probe_finished_nxdomain-teshis-rehberi\/\">NXDOMAIN te\u015fhis rehberimizde<\/a> ad\u0131m ad\u0131m anlatt\u0131\u011f\u0131m\u0131z te\u015fhis s\u00fcrecini takip ederek, sorunun ger\u00e7ekten DNS\u2019ten mi, sunucudan m\u0131 kaynakland\u0131\u011f\u0131n\u0131 \u00e7ok h\u0131zl\u0131 \u015fekilde netle\u015ftirebilirsiniz.<\/p>\n<p>DNS taraf\u0131 temizlendikten sonra h\u00e2l\u00e2 performans veya kaynak s\u0131k\u0131nt\u0131s\u0131 ya\u015f\u0131yorsan\u0131z, o noktada i\u015f CPU, RAM, disk I\/O ve network analizine; yani hosting mimarisine kay\u0131yor. Bu taraf\u0131 da DCHost\u2019ta <a href=\"https:\/\/www.dchost.com\/tr\/web-hosting\">payla\u015f\u0131ml\u0131 hosting<\/a>, VPS, dedicated sunucu veya colocation se\u00e7enekleriyle birlikte planl\u0131yoruz; ama her \u015feyden \u00f6nce <strong>DNS temelinin sa\u011flam<\/strong> olmas\u0131 \u015fart.<\/p>\n<h2><span id=\"Ozet_ve_Yol_Haritasi_DNSi_Bir_Defa_Duzeltin_Uzun_Sure_Rahat_Edin\">\u00d6zet ve Yol Haritas\u0131: DNS\u2019i Bir Defa D\u00fczeltin, Uzun S\u00fcre Rahat Edin<\/span><\/h2>\n<p>DNS \u00e7o\u011fu zaman \u201cbir kere kur, unut\u201d g\u00f6z\u00fcyle bak\u0131lan ama yanl\u0131\u015f kurguland\u0131\u011f\u0131nda aylarca g\u00f6r\u00fcnmez sorunlar \u00e7\u0131karan bir katman. Bu yaz\u0131da \u00f6zetledi\u011fimiz 10 kay\u0131t, DCHost ekibi olarak g\u00fcnl\u00fck i\u015fimizde en s\u0131k kar\u015f\u0131m\u0131za \u00e7\u0131kan, ger\u00e7ek projeleri etkileyen hatalar\u0131n neredeyse tamam\u0131n\u0131 kaps\u0131yor:<\/p>\n<ul>\n<li>Yanl\u0131\u015f NS ve kar\u0131\u015f\u0131k DNS panelleri<\/li>\n<li>Eski IP\u2019lere bakan A\/AAAA kay\u0131tlar\u0131<\/li>\n<li>K\u00f6k domain ve www tutars\u0131zl\u0131klar\u0131<\/li>\n<li>Eksik veya hatal\u0131 MX<\/li>\n<li>\u00c7ak\u0131\u015fan SPF ve lookup limit problemleri<\/li>\n<li>Eksik\/yanl\u0131\u015f DKIM ve agresif DMARC politikalar\u0131<\/li>\n<li>Tan\u0131ms\u0131z veya alakas\u0131z PTR<\/li>\n<li>Yanl\u0131\u015f yerde kullan\u0131lan CNAME\u2019ler<\/li>\n<li>K\u00f6t\u00fc planlanm\u0131\u015f TTL ve uzayan yay\u0131l\u0131m sorunlar\u0131<\/li>\n<\/ul>\n<p>Pratik yol haritas\u0131 \u015f\u00f6yle olabilir: \u00d6nce alan ad\u0131n\u0131z\u0131n DNS panelini a\u00e7\u0131n, bu 10 maddeyi <strong>tek tek kontrol edin<\/strong> ve not al\u0131n. Gerekiyorsa staging bir alan ad\u0131 veya alt alan \u00fczerinde test de\u011fi\u015fiklikleri yap\u0131p, <code>dig<\/code>, <code>nslookup<\/code> gibi ara\u00e7larla \u00e7\u0131kt\u0131lar\u0131 do\u011frulay\u0131n. \u00d6zellikle e\u2011posta taraf\u0131nda SPF, DKIM, DMARC ve PTR kombinasyonunu do\u011fru kurdu\u011funuzda, spam klas\u00f6r\u00fc \u015fikayetlerinin ne kadar h\u0131zl\u0131 azald\u0131\u011f\u0131n\u0131 bizzat g\u00f6receksiniz.<\/p>\n<p>E\u011fer DNS taraf\u0131nda nereden ba\u015flayaca\u011f\u0131n\u0131z\u0131 kestiremiyorsan\u0131z veya \u00e7ok alan adl\u0131, \u00e7ok b\u00f6lgeli bir mimari y\u00f6netiyorsan\u0131z, DCHost taraf\u0131nda alan ad\u0131, DNS ve hosting mimarinizi birlikte ele alarak, hem web sitesi hem e\u2011posta altyap\u0131n\u0131z i\u00e7in <strong>uzun vadeli, s\u00fcrd\u00fcr\u00fclebilir bir tasar\u0131m<\/strong> olu\u015fturman\u0131za yard\u0131mc\u0131 olabiliriz. Yeni projeye ba\u015flamadan veya b\u00fcy\u00fck bir ta\u015f\u0131ma planlamadan \u00f6nce, bu 10 DNS kayd\u0131n\u0131 check\u2011list\u2019inizin ba\u015f\u0131na yaz\u0131n; sonradan \u00e7\u0131kacak s\u00fcrprizleri ciddi oranda azalt\u0131rs\u0131n\u0131z.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>\u0130&ccedil;indekiler1 DNS Ayarlar\u0131nda K\u00fc\u00e7\u00fck Hata, B\u00fcy\u00fck Kesinti: Nerede Tak\u0131l\u0131yoruz?2 Kontrol Listesi: Web Sitesi ve E\u2011Postay\u0131 U\u00e7urmadan \u00d6nce Bakman\u0131z Gereken 10 DNS Kayd\u01312.1 1. NS Kay\u0131tlar\u0131: Yanl\u0131\u015f Yetkili DNS Sunucular\u01312.2 2. A \/ AAAA Kay\u0131tlar\u0131: Yanl\u0131\u015f IP Adresi veya Eski Sunucuya Bakan Site2.3 3. K\u00f6k Alan Ad\u0131 (example.com) ve www Tutars\u0131zl\u0131klar\u01312.4 4. MX Kay\u0131tlar\u0131: E\u2011Postan\u0131n Gitti\u011fi [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":4399,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-4398","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\/4398","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=4398"}],"version-history":[{"count":0,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/4398\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/4399"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=4398"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=4398"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=4398"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}