{"id":40315,"date":"2026-02-26T05:40:59","date_gmt":"2026-02-26T02:40:59","guid":{"rendered":"https:\/\/fatihsoysal.com\/blog\/?p=40315"},"modified":"2026-02-26T05:40:59","modified_gmt":"2026-02-26T02:40:59","slug":"bind-dns-sunucusunu-centos-6-uzerine-kurulumu-ve-yapilandirmasi","status":"publish","type":"post","link":"https:\/\/fatihsoysal.com\/blog\/bind-dns-sunucusunu-centos-6-uzerine-kurulumu-ve-yapilandirmasi\/","title":{"rendered":"BIND DNS Sunucusunu CentOS 6 \u00dczerine Kurulumu ve Yap\u0131land\u0131rmas\u0131"},"content":{"rendered":"

<\/p>\n

BIND DNS Sunucusunu CentOS 6 \u00dczerine Kurulumu ve Yap\u0131land\u0131rmas\u0131<\/h2>\n

Alan Ad\u0131 Sistemi (DNS), internetin telefon rehberidir. \u0130nsanlar\u0131n hat\u0131rlamas\u0131 kolay alan adlar\u0131n\u0131 (\u00f6rne\u011fin, google.com) bilgisayarlar\u0131n birbirini tan\u0131mlamak i\u00e7in kulland\u0131\u011f\u0131 IP adreslerine (\u00f6rne\u011fin, 172.217.160.142) \u00e7evirir. Bu temel hizmet olmadan, internetin mevcut haliyle \u00e7al\u0131\u015fmas\u0131 m\u00fcmk\u00fcn de\u011fildir. DNS, web sitelerine eri\u015fimden e-posta g\u00f6nderimine kadar her \u015feyin sorunsuz \u00e7al\u0131\u015fmas\u0131n\u0131 sa\u011flar. Herhangi bir a\u011f altyap\u0131s\u0131n\u0131n temel bir bile\u015fenidir ve do\u011fru yap\u0131land\u0131r\u0131lmas\u0131, a\u011f\u0131n\u0131z\u0131n g\u00fcvenilirli\u011fi ve performans\u0131 i\u00e7in kritik \u00f6neme sahiptir.<\/p>\n

BIND (Berkeley Internet Name Domain), internet \u00fczerindeki en yayg\u0131n kullan\u0131lan DNS yaz\u0131l\u0131m\u0131d\u0131r. A\u00e7\u0131k kaynakl\u0131d\u0131r, g\u00fc\u00e7l\u00fcd\u00fcr, esnektir ve milyonlarca sunucuda DNS \u00e7\u00f6z\u00fcmlemesini sa\u011flamak i\u00e7in kullan\u0131l\u0131r. BIND, hem k\u00fc\u00e7\u00fck \u00f6l\u00e7ekli a\u011flarda hem de b\u00fcy\u00fck, karma\u015f\u0131k kurumsal ortamlarda veya internet servis sa\u011flay\u0131c\u0131lar\u0131nda birincil veya ikincil DNS sunucusu olarak g\u00f6rev yapabilir. Kapsaml\u0131 \u00f6zellik seti, zone transferleri, dinamik DNS g\u00fcncellemeleri, DNSSEC deste\u011fi gibi ileri d\u00fczey i\u015flevleri bar\u0131nd\u0131r\u0131r.<\/p>\n

CentOS 6, her ne kadar \u00f6mr\u00fcn\u00fcn sonuna gelmi\u015f bir i\u015fletim sistemi olsa da, bir\u00e7ok eski sistemde hala kullan\u0131lmaktad\u0131r ve BIND’\u0131 bu platformda kurma bilgisi hala de\u011ferli olabilir. Bu makale, CentOS 6 \u00fczerinde BIND DNS sunucusunu ad\u0131m ad\u0131m nas\u0131l kuraca\u011f\u0131n\u0131z\u0131 ve temel birincil (master) DNS sunucusu olarak nas\u0131l yap\u0131land\u0131raca\u011f\u0131n\u0131z\u0131 ayr\u0131nt\u0131l\u0131 olarak a\u00e7\u0131klayacakt\u0131r. Bu rehber, hem ileriye d\u00f6n\u00fck (forward lookup) hem de geriye d\u00f6n\u00fck (reverse lookup) DNS b\u00f6lgelerini yap\u0131land\u0131rmay\u0131, g\u00fcvenlik \u00f6nlemlerini ve sorun giderme ipu\u00e7lar\u0131n\u0131 kapsayacakt\u0131r.<\/p>\n

\u00d6n Gereksinimler<\/h3>\n

BIND kurulumuna ba\u015flamadan \u00f6nce a\u015fa\u011f\u0131daki \u00f6n gereksinimlerin kar\u015f\u0131land\u0131\u011f\u0131ndan emin olun:<\/p>\n

* CentOS 6 \u0130\u015fletim Sistemi:<\/strong> \u00c7al\u0131\u015f\u0131r durumda bir CentOS 6 sunucusu.
\n* Root Eri\u015fimi veya Sudo Yetkileri:<\/strong> Kurulum ve yap\u0131land\u0131rma i\u015flemleri i\u00e7in root kullan\u0131c\u0131s\u0131 olarak veya sudo yetkilerine sahip bir kullan\u0131c\u0131 ile oturum a\u00e7m\u0131\u015f olman\u0131z gerekmektedir.
\n* Statik IP Adresi:<\/strong> DNS sunucusunun kararl\u0131 ve g\u00fcvenilir \u00e7al\u0131\u015fmas\u0131 i\u00e7in sunucunuza statik bir IP adresi atanm\u0131\u015f olmal\u0131d\u0131r. Dinamik IP adresleri, DNS \u00e7\u00f6z\u00fcmlemesinde tutars\u0131zl\u0131klara yol a\u00e7abilir. \u00d6rne\u011fin, 192.168.1.10<\/code> gibi bir IP adresi kullanaca\u011f\u0131z.
\n* \u0130nternet Ba\u011flant\u0131s\u0131:<\/strong> BIND paketlerini indirmek ve sistemi g\u00fcncellemek i\u00e7in sunucunuzun internet eri\u015fimi olmal\u0131d\u0131r.
\n* Temel Linux Komut Bilgisi:<\/strong> yum<\/code>, service<\/code>, vi<\/code>\/nano<\/code> gibi temel Linux komutlar\u0131na a\u015fina olman\u0131z beklenir.<\/p>\n

Ad\u0131m 1: Sistemi G\u00fcncelleme ve Gerekli Paketleri Kurma<\/h3>\n

Herhangi bir yaz\u0131l\u0131m kurulumuna ba\u015flamadan \u00f6nce, sisteminizin g\u00fcncel oldu\u011fundan emin olmak iyi bir uygulamad\u0131r. Bu, potansiyel g\u00fcvenlik a\u00e7\u0131klar\u0131n\u0131 kapat\u0131r ve yaz\u0131l\u0131m uyumlulu\u011fu sorunlar\u0131n\u0131 \u00f6nler. Ayr\u0131ca, BIND ve ilgili yard\u0131mc\u0131 programlar\u0131 kurmak i\u00e7in gerekli paketleri indirece\u011fiz.<\/p>\n

Terminali a\u00e7\u0131n ve root kullan\u0131c\u0131s\u0131 olarak veya sudo<\/code> ile a\u015fa\u011f\u0131daki komutlar\u0131 \u00e7al\u0131\u015ft\u0131r\u0131n:<\/p>\n

sudo yum update -y<\/code><\/pre>\n
Bu komut, sisteminizdeki t\u00fcm y\u00fckl\u00fc paketleri en son s\u00fcr\u00fcmlerine g\u00fcncelleyecektir. \u0130\u015flem biraz zaman alabilir. G\u00fcncelleme tamamland\u0131ktan sonra, BIND DNS sunucusunu ve onunla birlikte gelen yard\u0131mc\u0131 programlar\u0131 kurmak i\u00e7in a\u015fa\u011f\u0131daki komutu kullan\u0131n:<\/p>\n
sudo yum install bind bind-utils -y<\/code><\/pre>\n
*   bind<\/code>:<\/strong> BIND DNS sunucusunun kendisini i\u00e7eren ana pakettir.
\n*   bind-utils<\/code>:<\/strong> dig<\/code>, nslookup<\/code>, host<\/code>, named-checkconf<\/code>, named-checkzone<\/code> gibi DNS sorun giderme ve sorgulama ara\u00e7lar\u0131n\u0131 i\u00e7erir. Bu ara\u00e7lar, DNS yap\u0131land\u0131rman\u0131z\u0131 test etmek i\u00e7in paha bi\u00e7ilmezdir.<\/p>\n
Kurulum tamamland\u0131\u011f\u0131nda, BIND’\u0131n ana yap\u0131land\u0131rma dosyalar\u0131 \/etc\/named.conf<\/code> alt\u0131nda ve b\u00f6lge dosyalar\u0131 \/var\/named<\/code> dizini alt\u0131nda bulunacakt\u0131r.<\/p>\n
Ad\u0131m 2: SELinux ve Firewall Ayarlar\u0131<\/h3>\n
CentOS, g\u00fcvenlik i\u00e7in SELinux ve iptables (g\u00fcvenlik duvar\u0131) kullan\u0131r. BIND’\u0131n d\u00fczg\u00fcn \u00e7al\u0131\u015fabilmesi i\u00e7in bu bile\u015fenlerin do\u011fru \u015fekilde yap\u0131land\u0131r\u0131lmas\u0131 gerekir. Aksi takdirde, DNS sorgular\u0131 engellenebilir veya BIND gerekli dosyalara eri\u015femeyebilir.<\/p>\n
SELinux Yap\u0131land\u0131rmas\u0131<\/h4>\n
SELinux, Linux \u00e7ekirde\u011fine entegre edilmi\u015f bir g\u00fcvenlik mekanizmas\u0131d\u0131r ve uygulamalar\u0131n sistem kaynaklar\u0131na eri\u015fimini k\u0131s\u0131tlar. BIND’\u0131n d\u00fczg\u00fcn \u00e7al\u0131\u015fmas\u0131 i\u00e7in SELinux kurallar\u0131n\u0131n ayarlanmas\u0131 veya ge\u00e7ici olarak devre d\u0131\u015f\u0131 b\u0131rak\u0131lmas\u0131 gerekebilir. Geli\u015ftirme veya test ortamlar\u0131nda ge\u00e7ici olarak devre d\u0131\u015f\u0131 b\u0131rakmak yayg\u0131n olsa da, \u00fcretim ortamlar\u0131nda SELinux politikalar\u0131n\u0131 do\u011fru \u015fekilde yap\u0131land\u0131rmak en iyi uygulamad\u0131r.<\/p>\n
SELinux’u ge\u00e7ici olarak devre d\u0131\u015f\u0131 b\u0131rakmak i\u00e7in:<\/p>\n
sudo setenforce 0<\/code><\/pre>\n
Bu komut, SELinux’u zorlama modundan izin verilen moda (Permissive) ge\u00e7irir. Bu, BIND’\u0131n \u00e7al\u0131\u015fmas\u0131na izin verirken, SELinux’un hala olas\u0131 g\u00fcvenlik ihlallerini kaydetmeye devam etmesini sa\u011flar.<\/p>\n
SELinux’u kal\u0131c\u0131 olarak devre d\u0131\u015f\u0131 b\u0131rakmak veya yap\u0131land\u0131rmak i\u00e7in \/etc\/selinux\/config<\/code> dosyas\u0131n\u0131 d\u00fczenlemeniz gerekir:<\/p>\n
sudo vi \/etc\/selinux\/config<\/code><\/pre>\n
Dosyada SELINUX=<\/code> ile ba\u015flayan sat\u0131r\u0131 bulun ve de\u011ferini enforcing<\/code> yerine disabled<\/code> olarak de\u011fi\u015ftirin:<\/p>\n
# This file controls the state of SELinux on the system.\n
SELINUX= can take one of these three values:<\/h2>\n
enforcing - SELinux security policy is enforced.<\/h2>\n
permissive - SELinux prints warnings instead of enforcing.<\/h2>\n
disabled - No SELinux policy is loaded.<\/h2>\nSELINUX=disabled\n
SELINUXTYPE= can take one of these two values:<\/h2>\n
targeted - Targeted processes are protected,<\/h2>\n
mls - Multi Level Security protection.<\/h2>\nSELINUXTYPE=targeted<\/code><\/pre>\n
De\u011fi\u015fikli\u011fi kaydettikten sonra, sisteminizi yeniden ba\u015flatman\u0131z gerekir ki de\u011fi\u015fiklikler etkili olsun:<\/p>\n
sudo reboot<\/code><\/pre>\n
E\u011fer SELinux’u tamamen devre d\u0131\u015f\u0131 b\u0131rakmak istemiyorsan\u0131z, BIND i\u00e7in \u00f6zel SELinux kurallar\u0131 eklemeniz gerekir. Ancak bu, daha ileri bir konudur ve bu rehberin kapsam\u0131 d\u0131\u015f\u0131ndad\u0131r. En basit yol, yukar\u0131daki gibi devre d\u0131\u015f\u0131 b\u0131rakmakt\u0131r.<\/p>\n
Firewall (iptables) Yap\u0131land\u0131rmas\u0131<\/h4>\n
DNS sunucusu, istemcilerden gelen DNS sorgular\u0131n\u0131 dinlemek i\u00e7in 53 numaral\u0131 portu (hem TCP hem de UDP) kullan\u0131r. G\u00fcvenlik duvar\u0131n\u0131z bu portlar\u0131 engelliyorsa, DNS sorgular\u0131 sunucuya ula\u015famaz. CentOS 6’da varsay\u0131lan g\u00fcvenlik duvar\u0131 iptables<\/code>‘t\u0131r.<\/p>\n
A\u015fa\u011f\u0131daki komutlarla 53 numaral\u0131 portu a\u00e7\u0131n:<\/p>\n
sudo iptables -A INPUT -p udp --dport 53 -j ACCEPT\nsudo iptables -A INPUT -p tcp --dport 53 -j ACCEPT<\/code><\/pre>\n
Bu komutlar, 53 numaral\u0131 UDP ve TCP portlar\u0131 \u00fczerinden gelen ba\u011flant\u0131lara izin veren kurallar ekler. De\u011fi\u015fikliklerin kal\u0131c\u0131 olmas\u0131 i\u00e7in iptables<\/code> yap\u0131land\u0131rmas\u0131n\u0131 kaydetmeniz gerekir:<\/p>\n
sudo service iptables save<\/code><\/pre>\n
Ard\u0131ndan, iptables hizmetini yeniden ba\u015flat\u0131n:<\/p>\n
sudo service iptables restart<\/code><\/pre>\n
Bu ad\u0131mlar\u0131 tamamlad\u0131ktan sonra, BIND’\u0131n a\u011f ve g\u00fcvenlik k\u0131s\u0131tlamalar\u0131 olmadan \u00e7al\u0131\u015fmaya ba\u015flayabilece\u011fi bir ortama sahip olmal\u0131s\u0131n\u0131z.<\/p>\n
Ad\u0131m 3: Ana Yap\u0131land\u0131rma Dosyas\u0131: named.conf<\/h3>\n
BIND’\u0131n ana yap\u0131land\u0131rma dosyas\u0131 \/etc\/named.conf<\/code>‘tur. Bu dosya, BIND’\u0131n nas\u0131l davranaca\u011f\u0131n\u0131, hangi b\u00f6lgeleri y\u00f6netece\u011fini, hangi IP adreslerinden sorgular\u0131 dinleyece\u011fini ve di\u011fer genel ayarlar\u0131 i\u00e7erir. \u0130lk kurulumda bu dosya genellikle baz\u0131 varsay\u0131lan ayarlar ve \u00f6rnek b\u00f6lge tan\u0131mlamalar\u0131yla gelir. Biz bu dosyay\u0131 kendi ihtiya\u00e7lar\u0131m\u0131za g\u00f6re d\u00fczenleyece\u011fiz.<\/p>\n
Dosyay\u0131 bir metin d\u00fczenleyici ile a\u00e7\u0131n:<\/p>\n
sudo vi \/etc\/named.conf<\/code><\/pre>\n
Varsay\u0131lan named.conf<\/code> dosyas\u0131 genellikle a\u015fa\u011f\u0131daki gibi bir yap\u0131ya sahiptir:<\/p>\n
options {\n    listen-on port 53 { 127.0.0.1; };\n    listen-on-v6 port 53 { ::1; };\n    directory       \"\/var\/named\";\n    dump-file       \"\/var\/named\/data\/cache_dump.db\";\n    statistics-file \"\/var\/named\/data\/named_stats.txt\";\n    memstatistics-file \"\/var\/named\/data\/named_mem_stats.txt\";\n    allow-query     { localhost; };\n    recursion yes;\n\n    dnssec-enable yes;\n    dnssec-validation yes;\n    dnssec-lookaside auto;\n\n    \/ Path to ISC DLV key <\/em>\/\n    bindkeys-file \"\/etc\/named.root.key\";\n\n    managed-keys-directory \"\/var\/named\/dynamic\";\n};\n\nlogging {\n        channel default_debug {\n                file \"data\/named.run\";\n                severity dynamic;\n        };\n};\n\nzone \".\" IN {\n    type hint;\n    file \"named.ca\";\n};\n\nzone \"localhost.localdomain\" IN {\n    type master;\n    file \"named.localhost\";\n    allow-update { none; };\n};\n\nzone \"localhost\" IN {\n    type master;\n    file \"named.localhost\";\n    allow-update { none; };\n};\n\nzone \"1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa\" IN {\n    type master;\n    file \"named.loopback\";\n    allow-update { none; };\n};\n\nzone \"1.0.0.127.in-addr.arpa\" IN {\n    type master;\n    file \"named.loopback\";\n    allow-update { none; };\n};\n\nzone \"0.in-addr.arpa\" IN {\n    type master;\n    file \"named.empty\";\n    allow-update { none; };\n};<\/code><\/pre>\n
Bu dosyay\u0131 kendi DNS sunucumuz i\u00e7in a\u015fa\u011f\u0131daki gibi d\u00fczenleyece\u011fiz. \u00d6zellikle options<\/code> blo\u011funda ve yeni zone<\/code> tan\u0131mlamalar\u0131nda de\u011fi\u015fiklikler yapaca\u011f\u0131z.<\/p>\n
\/\/\n\/\/ named.conf for BIND DNS Server on CentOS 6\n\/\/\n\noptions {\n    \/\/ DNS sunucunuzun dinleyece\u011fi IP adresleri ve port.\n    \/\/ Kendi sunucunuzun statik IP adresini (\u00f6rn. 192.168.1.10) veya 'any' olarak ayarlayabilirsiniz.\n    listen-on port 53 { 192.168.1.10; }; \/\/ Sunucunuzun IP adresini buraya yaz\u0131n\n    \/\/ IPv6 dinlemesini kapatmak i\u00e7in yorum sat\u0131r\u0131 yapabilir veya kendi IPv6 adresinizi belirtebilirsiniz.\n    \/\/ listen-on-v6 port 53 { ::1; };\n\n    \/\/ B\u00f6lge dosyalar\u0131n\u0131n bulundu\u011fu dizin. Varsay\u0131lan olarak \/var\/named'dir.\n    directory       \"\/var\/named\";\n\n    \/\/ \u00d6nbellek d\u00f6k\u00fcm dosyas\u0131, istatistik dosyalar\u0131.\n    dump-file       \"\/var\/named\/data\/cache_dump.db\";\n    statistics-file \"\/var\/named\/data\/named_stats.txt\";\n    memstatistics-file \"\/var\/named\/data\/named_mem_stats.txt\";\n\n    \/\/ Sorgulara izin verilecek IP adresleri.\n    \/\/ 'any' t\u00fcm IP'lerden sorgulara izin verir (g\u00fcvenlik riski ta\u015f\u0131yabilir).\n    \/\/ Belirli bir a\u011fdan (\u00f6rn. 192.168.1.0\/24) veya IP adreslerinden izin vermek daha g\u00fcvenlidir.\n    allow-query     { 192.168.1.0\/24; localhost; }; \/\/ Kendi a\u011f\u0131n\u0131z\u0131 buraya yaz\u0131n\n\n    \/\/ \u00d6zyinelemeli sorgulara izin verilip verilmeyece\u011fi.\n    \/\/ \u0130\u00e7 a\u011f DNS sunucular\u0131 i\u00e7in 'yes' olmal\u0131d\u0131r.\n    recursion yes;\n\n    \/\/ DNSSEC ayarlar\u0131. \u00dcretim ortamlar\u0131nda etkinle\u015ftirilmesi \u00f6nerilir.\n    dnssec-enable yes;\n    dnssec-validation yes;\n    dnssec-lookaside auto;\n\n    \/\/ Root hint dosyas\u0131. \u0130nternet DNS \u00e7\u00f6z\u00fcmlemesi i\u00e7in gereklidir.\n    \/\/ bindkeys-file \"\/etc\/named.root.key\"; \/\/ Bu sat\u0131r\u0131 genellikle dokunmadan b\u0131rakabilirsiniz.\n    \/\/ managed-keys-directory \"\/var\/named\/dynamic\";\n\n    \/\/ E\u011fer bir upstream DNS sunucusu kullanmak istiyorsan\u0131z (\u00f6rne\u011fin ISP'nizin DNS'i veya Google DNS),\n    \/\/ a\u015fa\u011f\u0131daki forwarders blo\u011funu etkinle\u015ftirebilirsiniz.\n    \/\/ forwarders {\n    \/\/     8.8.8.8;\n    \/\/     8.8.4.4;\n    \/\/ };\n    \/\/ forward only; \/\/ E\u011fer sadece forwarder'lara iletmek istiyorsan\u0131z.\n};\n\n\/\/ G\u00fcnl\u00fck kayd\u0131 ayarlar\u0131. Sorun giderme i\u00e7in \u00f6nemlidir.\nlogging {\n        channel default_debug {\n                file \"data\/named.run\";\n                severity dynamic;\n        };\n};\n\n\/\/ K\u00f6k ipu\u00e7lar\u0131 (root hints) b\u00f6lgesi. \u0130nternet DNS \u00e7\u00f6z\u00fcmlemesi i\u00e7in gereklidir.\nzone \".\" IN {\n    type hint;\n    file \"named.ca\";\n};\n\n\/\/ Yerel ana bilgisayar (localhost) i\u00e7in ileriye d\u00f6n\u00fck b\u00f6lge.\nzone \"localhost.localdomain\" IN {\n    type master;\n    file \"named.localhost\";\n    allow-update { none; };\n};\n\nzone \"localhost\" IN {\n    type master;\n    file \"named.localhost\";\n    allow-update { none; };\n};\n\n\/\/ Yerel ana bilgisayar (loopback) i\u00e7in geriye d\u00f6n\u00fck b\u00f6lge.\nzone \"1.0.0.127.in-addr.arpa\" IN {\n    type master;\n    file \"named.loopback\";\n    allow-update { none; };\n};\n\n\/\/ \u00d6rnek \u00f6zel alan ad\u0131n\u0131z i\u00e7in ileriye d\u00f6n\u00fck b\u00f6lge tan\u0131mlamas\u0131.\n\/\/ Kendi alan ad\u0131n\u0131z\u0131 (\u00f6rn. example.com) ve dosya ad\u0131n\u0131 buna g\u00f6re de\u011fi\u015ftirin.\nzone \"example.com\" IN {\n    type master;\n    file \"example.com.zone\"; \/\/ Bu dosyay\u0131 \/var\/named\/ dizininde olu\u015fturaca\u011f\u0131z.\n    allow-update { none; };\n};\n\n\/\/ \u00d6rnek \u00f6zel a\u011f\u0131n\u0131z i\u00e7in geriye d\u00f6n\u00fck b\u00f6lge tan\u0131mlamas\u0131.\n\/\/ Kendi a\u011f\u0131n\u0131z\u0131n tersini (\u00f6rn. 1.168.192.in-addr.arpa) ve dosya ad\u0131n\u0131 buna g\u00f6re de\u011fi\u015ftirin.\nzone \"1.168.192.in-addr.arpa\" IN {\n    type master;\n    file \"db.192.168.1\"; \/\/ Bu dosyay\u0131 \/var\/named\/ dizininde olu\u015fturaca\u011f\u0131z.\n    allow-update { none; };\n};<\/code><\/pre>\n
Yukar\u0131daki \u00f6rnekte \u015funlara dikkat edin:
\n*   listen-on port 53 { 192.168.1.10; };<\/code>: DNS sunucunuzun dinleyece\u011fi IP adresini buraya yaz\u0131n. Birden fazla IP adresiniz varsa virg\u00fclle ay\u0131rarak ekleyebilirsiniz. any<\/code> olarak b\u0131rakmak t\u00fcm aray\u00fczlerde dinlemeye izin verir ancak g\u00fcvenlik a\u00e7\u0131s\u0131ndan belirli bir IP’ye ba\u011flamak daha iyidir.
\n*   allow-query { 192.168.1.0\/24; localhost; };<\/code>: DNS sorgular\u0131na izin verilecek istemci IP’lerini veya a\u011flar\u0131n\u0131 belirtin. any<\/code> olarak b\u0131rakmak, herkesin sunucunuzdan sorgu yapmas\u0131na izin verir ve bu, a\u00e7\u0131k bir \u00e7\u00f6z\u00fcmleyici (open resolver) olu\u015fturarak DDoS sald\u0131r\u0131lar\u0131 i\u00e7in k\u00f6t\u00fcye kullan\u0131labilir. Kendi yerel a\u011f\u0131n\u0131z\u0131n IP aral\u0131\u011f\u0131n\u0131 kullan\u0131n.
\n*   zone \"example.com\" IN { ... };<\/code>: Kendi \u00f6zel alan ad\u0131n\u0131z i\u00e7in bir ileriye d\u00f6n\u00fck b\u00f6lge tan\u0131mlamas\u0131. example.com<\/code> yerine kendi alan ad\u0131n\u0131z\u0131 yaz\u0131n.
\n*   zone \"1.168.192.in-addr.arpa\" IN { ... };<\/code>: Kendi a\u011f\u0131n\u0131z i\u00e7in bir geriye d\u00f6n\u00fck b\u00f6lge tan\u0131mlamas\u0131. 192.168.1.0\/24<\/code> a\u011f\u0131n\u0131n tersi 1.168.192.in-addr.arpa<\/code> \u015feklindedir (IP adresinin oktetleri tersten yaz\u0131l\u0131r ve sonuna .in-addr.arpa<\/code> eklenir).<\/p>\n
De\u011fi\u015fiklikleri kaydedip dosyay\u0131 kapat\u0131n.<\/p>\n
Ad\u0131m 4: \u0130leri Y\u00f6nl\u00fc B\u00f6lge Dosyas\u0131 Olu\u015fturma<\/h3>\n
\u0130leriye d\u00f6n\u00fck b\u00f6lge dosyalar\u0131, alan adlar\u0131n\u0131 IP adreslerine \u00e7evirmek i\u00e7in kullan\u0131l\u0131r (\u00f6rne\u011fin, www.example.com<\/code> -> 192.168.1.100<\/code>). Bu dosyalar\u0131 \/var\/named\/<\/code> dizininde olu\u015fturaca\u011f\u0131z.<\/p>\n
\u00d6nce, BIND’\u0131n varsay\u0131lan b\u00f6lge dosyalar\u0131ndan birini kopyalayarak ba\u015flayabiliriz. Bu, dosya izinleri ve SELinux ba\u011flam\u0131 gibi \u015feyleri do\u011fru ayarlaman\u0131za yard\u0131mc\u0131 olur.<\/p>\n
sudo cp \/var\/named\/named.localhost \/var\/named\/example.com.zone<\/code><\/pre>\n
\u015eimdi example.com.zone<\/code> dosyas\u0131n\u0131 d\u00fczenleyin:<\/p>\n
sudo vi \/var\/named\/example.com.zone<\/code><\/pre>\n
Dosyan\u0131n i\u00e7eri\u011fini a\u015fa\u011f\u0131daki gibi de\u011fi\u015ftirin. example.com<\/code> ve IP adreslerini kendi de\u011ferlerinizle g\u00fcncellemeyi unutmay\u0131n.<\/p>\n
$TTL 86400\n@   IN  SOA ns1.example.com. admin.example.com. (\n                                2023112001  ; Serial (YYYYMMDDNN)\n                                3H          ; Refresh (3 hours)\n                                1H          ; Retry (1 hour)\n                                1W          ; Expire (1 week)\n                                1D )        ; Minimum TTL (1 day)\n\n; Name Servers\n@           IN  NS      ns1.example.com.\nns1         IN  A       192.168.1.10        ; BIND sunucunuzun IP adresi\n\n; Host Records\n@           IN  A       192.168.1.10\nwww         IN  A       192.168.1.100       ; Web sunucusu IP\nmail        IN  A       192.168.1.110       ; Mail sunucusu IP\nftp         IN  CNAME   www                 ; FTP sunucusu (www ile ayn\u0131)\n\n; MX Record (Mail Exchanger)\n@           IN  MX  10  mail.example.com.   ; Mail sunucusu<\/code><\/pre>\n
A\u00e7\u0131klamalar:<\/strong><\/p>\n
*   $TTL 86400<\/code><\/strong>: Bu b\u00f6lgedeki kay\u0131tlar\u0131n varsay\u0131lan ya\u015fam s\u00fcresini (Time To Live) saniye cinsinden belirtir. 86400 saniye = 1 g\u00fcn.
\n*   @ IN SOA ns1.example.com. admin.example.com. (...)<\/code><\/strong>: Start of Authority (SOA) kayd\u0131, bir b\u00f6lgenin yetkili ad sunucusunu ve b\u00f6lge hakk\u0131nda \u00f6nemli y\u00f6netim bilgilerini tan\u0131mlar.
\n    *   ns1.example.com.<\/code>: Birincil ad sunucusunun tam nitelikli alan ad\u0131 (FQDN). Sonundaki nokta \u00f6nemlidir.
\n    *   admin.example.com.<\/code>: B\u00f6lge y\u00f6neticisinin e-posta adresi (burada @<\/code> yerine .<\/code> kullan\u0131l\u0131r).
\n    *   Serial<\/code>: B\u00f6lge dosyas\u0131n\u0131n s\u00fcr\u00fcm numaras\u0131. Bu numara her de\u011fi\u015fiklik yap\u0131ld\u0131\u011f\u0131nda art\u0131r\u0131lmal\u0131d\u0131r. Genellikle YYYYMMDDNN<\/code> (Y\u0131lAyG\u00fcnS\u0131raNo) format\u0131 kullan\u0131l\u0131r.
\n    *   Refresh<\/code>: \u0130kincil DNS sunucular\u0131n\u0131n birincil sunucuyu ne s\u0131kl\u0131kla g\u00fcncellemeler i\u00e7in kontrol etmesi gerekti\u011fi.
\n    *   Retry<\/code>: Birincil sunucuya ula\u015f\u0131lamazsa, ikincil sunucular\u0131n tekrar denemek i\u00e7in ne kadar beklemesi gerekti\u011fi.
\n    *   Expire<\/code>: \u0130kincil sunucular\u0131n birincil sunucuya ula\u015famazsa b\u00f6lge verilerini ne kadar s\u00fcreyle ge\u00e7erli kabul edece\u011fi.
\n    *   Minimum TTL<\/code>: Negatif \u00f6nbellekleme i\u00e7in minimum TTL.
\n*   @ IN NS ns1.example.com.<\/code><\/strong>: Name Server (NS) kayd\u0131, bu b\u00f6lge i\u00e7in yetkili ad sunucular\u0131n\u0131 belirtir.
\n*   ns1 IN A 192.168.1.10<\/code><\/strong>: A (Address) kayd\u0131, bir ana bilgisayar ad\u0131n\u0131 (ns1) bir IPv4 adresine e\u015fler.
\n*   @ IN A 192.168.1.10<\/code><\/strong>: @<\/code> sembol\u00fc, alan ad\u0131n\u0131n kendisini (example.com<\/code>) ifade eder. Bu, alan ad\u0131n\u0131n kendi IP adresidir.
\n*   www IN A 192.168.1.100<\/code><\/strong>: www.example.com<\/code>‘u 192.168.1.100<\/code> IP adresine e\u015fler.
\n*   ftp IN CNAME www<\/code><\/strong>: CNAME (Canonical Name) kayd\u0131, bir takma ad\u0131 (ftp) ba\u015fka bir ana bilgisayar ad\u0131na (www) e\u015fler. Bu, ftp.example.com<\/code>‘un www.example.com<\/code> ile ayn\u0131 IP adresine sahip olaca\u011f\u0131 anlam\u0131na gelir.
\n*   @ IN MX 10 mail.example.com.<\/code><\/strong>: MX (Mail Exchanger) kayd\u0131, bu alan ad\u0131 i\u00e7in e-posta sunucusunu belirtir. 10<\/code> \u00f6ncelik de\u011feridir; daha d\u00fc\u015f\u00fck say\u0131lar daha y\u00fcksek \u00f6nceli\u011fe sahiptir.<\/p>\n
Dosyay\u0131 kaydettikten sonra, BIND’\u0131n bu dosyaya do\u011fru izinlerle eri\u015febildi\u011finden emin olun. named<\/code> kullan\u0131c\u0131s\u0131 ve grubu genellikle dosya ve dizinlere sahip olmal\u0131d\u0131r.<\/p>\n
sudo chown root:named \/var\/named\/example.com.zone\nsudo chmod 640 \/var\/named\/example.com.zone<\/code><\/pre>\n
Ad\u0131m 5: Geri Y\u00f6nl\u00fc B\u00f6lge Dosyas\u0131 Olu\u015fturma<\/h3>\n
Geriye d\u00f6n\u00fck b\u00f6lge dosyalar\u0131, IP adreslerini alan adlar\u0131na \u00e7evirmek i\u00e7in kullan\u0131l\u0131r (\u00f6rne\u011fin, 192.168.1.100<\/code> -> www.example.com<\/code>). Bu, \u00f6zellikle e-posta sunucular\u0131 i\u00e7in \u00f6nemlidir, \u00e7\u00fcnk\u00fc bir\u00e7ok e-posta sunucusu, spam’i \u00f6nlemek i\u00e7in g\u00f6nderen sunucunun IP adresinin alan ad\u0131na do\u011fru \u015fekilde \u00e7\u00f6z\u00fcmlenebildi\u011fini kontrol eder (PTR kayd\u0131).<\/p>\n
Ayn\u0131 \u015fekilde, varsay\u0131lan bir b\u00f6lge dosyas\u0131n\u0131 kopyalayarak ba\u015flay\u0131n:<\/p>\n
sudo cp \/var\/named\/named.loopback \/var\/named\/db.192.168.1<\/code><\/pre>\n
\u015eimdi db.192.168.1<\/code> dosyas\u0131n\u0131 d\u00fczenleyin:<\/p>\n
sudo vi \/var\/named\/db.192.168.1<\/code><\/pre>\n
Dosyan\u0131n i\u00e7eri\u011fini a\u015fa\u011f\u0131daki gibi de\u011fi\u015ftirin. A\u011f\u0131n\u0131z\u0131n ve ana bilgisayarlar\u0131n\u0131z\u0131n IP adreslerini ve alan adlar\u0131n\u0131 kendi de\u011ferlerinizle g\u00fcncellemeyi unutmay\u0131n. Unutmay\u0131n, geriye d\u00f6n\u00fck b\u00f6lge dosyalar\u0131nda IP adreslerinin son okteti kullan\u0131l\u0131r.<\/p>\n
$TTL 86400\n@   IN  SOA ns1.example.com. admin.example.com. (\n                                2023112001  ; Serial\n                                3H          ; Refresh\n                                1H          ; Retry\n                                1W          ; Expire\n                                1D )        ; Minimum TTL\n\n; Name Servers\n@           IN  NS      ns1.example.com.\n\n; PTR Records (IP to Hostname)\n10          IN  PTR     ns1.example.com.    ; 192.168.1.10 -> ns1.example.com\n100         IN  PTR     www.example.com.    ; 192.168.1.100 -> www.example.com\n110         IN  PTR     mail.example.com.   ; 192.168.1.110 -> mail.example.com<\/code><\/pre>\n
A\u00e7\u0131klamalar:<\/strong><\/p>\n
*   @ IN SOA ns1.example.com. admin.example.com. (...)<\/code><\/strong>: SOA kayd\u0131, ileriye d\u00f6n\u00fck b\u00f6lge dosyas\u0131ndaki ile ayn\u0131 mant\u0131kla \u00e7al\u0131\u015f\u0131r.
\n*   @ IN NS ns1.example.com.<\/code><\/strong>: NS kayd\u0131 da ayn\u0131d\u0131r.
\n*   10 IN PTR ns1.example.com.<\/code><\/strong>: PTR (Pointer) kayd\u0131, bir IP adresinin son oktetini (\u00f6rne\u011fin, 192.168.1.10<\/strong> i\u00e7in 10<\/code>) bir alan ad\u0131na (FQDN) e\u015fler. Sonundaki nokta \u00f6nemlidir.<\/p>\n
Dosyay\u0131 kaydettikten sonra, izinleri ayarlay\u0131n:<\/p>\n
sudo chown root:named \/var\/named\/db.192.168.1\nsudo chmod 640 \/var\/named\/db.192.168.1<\/code><\/pre>\n
Ad\u0131m 6: Yap\u0131land\u0131rma Dosyalar\u0131n\u0131 Kontrol Etme<\/h3>\n
BIND servisini ba\u015flatmadan \u00f6nce, yap\u0131land\u0131rma dosyalar\u0131n\u0131zda herhangi bir s\u00f6zdizimi hatas\u0131 olup olmad\u0131\u011f\u0131n\u0131 kontrol etmek \u00e7ok \u00f6nemlidir. Yanl\u0131\u015f yap\u0131land\u0131r\u0131lm\u0131\u015f bir dosya, BIND’\u0131n ba\u015flamamas\u0131na veya beklendi\u011fi gibi \u00e7al\u0131\u015fmamas\u0131na neden olabilir.<\/p>\n
named-checkconf<\/h4>\n
Bu ara\u00e7, \/etc\/named.conf<\/code> dosyas\u0131n\u0131n s\u00f6zdizimini kontrol eder.<\/p>\n
sudo named-checkconf<\/code><\/pre>\n
E\u011fer herhangi bir \u00e7\u0131kt\u0131 g\u00f6rm\u00fcyorsan\u0131z, bu, ana yap\u0131land\u0131rma dosyas\u0131nda s\u00f6zdizimi hatas\u0131 olmad\u0131\u011f\u0131 anlam\u0131na gelir. E\u011fer hatalar varsa, hata mesajlar\u0131 ile birlikte sat\u0131r numaralar\u0131n\u0131 g\u00f6sterecektir.<\/p>\n
named-checkzone<\/h4>\n
Bu ara\u00e7, her bir b\u00f6lge dosyas\u0131n\u0131n s\u00f6zdizimini ve i\u00e7eri\u011fini kontrol eder.<\/p>\n
\u0130leriye d\u00f6n\u00fck b\u00f6lge dosyas\u0131n\u0131 kontrol edin:<\/p>\n
sudo named-checkzone example.com \/var\/named\/example.com.zone<\/code><\/pre>\n
\u00c7\u0131kt\u0131 a\u015fa\u011f\u0131dakine benzer olmal\u0131d\u0131r:<\/p>\n
zone example.com\/IN: loaded serial 2023112001\nOK<\/code><\/pre>\n
Geriye d\u00f6n\u00fck b\u00f6lge dosyas\u0131n\u0131 kontrol edin:<\/p>\n
sudo named-checkzone 1.168.192.in-addr.arpa \/var\/named\/db.192.168.1<\/code><\/pre>\n
\u00c7\u0131kt\u0131 a\u015fa\u011f\u0131dakine benzer olmal\u0131d\u0131r:<\/p>\n
zone 1.168.192.in-addr.arpa\/IN: loaded serial 2023112001\nOK<\/code><\/pre>\n
E\u011fer OK<\/code> mesaj\u0131n\u0131 al\u0131rsan\u0131z, b\u00f6lge dosyalar\u0131n\u0131z\u0131n do\u011fru \u015fekilde yap\u0131land\u0131r\u0131ld\u0131\u011f\u0131 anlam\u0131na gelir. Herhangi bir hata durumunda, hata mesajlar\u0131n\u0131 dikkatlice okuyarak ilgili dosyay\u0131 d\u00fczeltmeniz gerekir.<\/p>\n
Ad\u0131m 7: BIND Servisini Ba\u015flatma ve Etkinle\u015ftirme<\/h3>\n
T\u00fcm yap\u0131land\u0131rma dosyalar\u0131 kontrol edildikten ve hatalar giderildikten sonra, BIND DNS servisini ba\u015flatabiliriz. Ayr\u0131ca, sunucu yeniden ba\u015flat\u0131ld\u0131\u011f\u0131nda otomatik olarak ba\u015flamas\u0131 i\u00e7in servisi etkinle\u015ftirece\u011fiz.<\/p>\n
BIND servisini ba\u015flat\u0131n:<\/p>\n
sudo service named start<\/code><\/pre>\n
Servisin durumunu kontrol edin:<\/p>\n
sudo service named status<\/code><\/pre>\n
\u00c7\u0131kt\u0131 named (pid xxxx) is running...<\/code> gibi bir \u015fey g\u00f6stermelidir. E\u011fer servis ba\u015flamad\u0131ysa veya hata veriyorsa, \/var\/log\/messages<\/code> dosyas\u0131n\u0131 kontrol etmeniz gerekir (bkz. Sorun Giderme b\u00f6l\u00fcm\u00fc).<\/p>\n
Servisi sistem ba\u015flang\u0131c\u0131nda otomatik olarak ba\u015flamas\u0131 i\u00e7in etkinle\u015ftirin:<\/p>\n
sudo chkconfig named on<\/code><\/pre>\n
Bu komut, sistem yeniden ba\u015flat\u0131ld\u0131\u011f\u0131nda BIND servisini otomatik olarak ba\u015flatacak gerekli ba\u011flant\u0131lar\u0131 olu\u015fturur.<\/p>\n
Ad\u0131m 8: DNS \u00c7\u00f6z\u00fcmlemesini Test Etme<\/h3>\n
BIND sunucunuzu kurup yap\u0131land\u0131rd\u0131ktan ve ba\u015flatt\u0131ktan sonra, d\u00fczg\u00fcn \u00e7al\u0131\u015f\u0131p \u00e7al\u0131\u015fmad\u0131\u011f\u0131n\u0131 test etmeniz gerekir.<\/p>\n
Sunucunun Kendi \u00c7\u00f6z\u00fcmleyicisini Yap\u0131land\u0131rma<\/h4>\n
\u0130lk olarak, DNS sunucunuzun kendisinin kendi DNS sunucusunu kullanmas\u0131n\u0131 sa\u011flamak i\u00e7in \/etc\/resolv.conf<\/code> dosyas\u0131n\u0131 d\u00fczenleyin. Bu, sunucunun kendi DNS hizmetini test etmenin ilk ad\u0131m\u0131d\u0131r.<\/p>\n
sudo vi \/etc\/resolv.conf<\/code><\/pre>\n
Dosyan\u0131n i\u00e7eri\u011fini a\u015fa\u011f\u0131daki gibi de\u011fi\u015ftirin (veya ekleyin):<\/p>\n
search example.com\nnameserver 192.168.1.10<\/code><\/pre>\n
*   search example.com<\/code>: DNS sorgular\u0131n\u0131 yaparken varsay\u0131lan olarak aranacak alan ad\u0131n\u0131 belirtir.
\n*   nameserver 192.168.1.10<\/code>: DNS sorgular\u0131n\u0131n g\u00f6nderilece\u011fi DNS sunucusunun IP adresini belirtir. Kendi sunucunuzun IP adresini kullan\u0131n.<\/p>\n
Not:<\/strong> CentOS 6’da NetworkManager<\/code> veya di\u011fer a\u011f yap\u0131land\u0131rma ara\u00e7lar\u0131 \/etc\/resolv.conf<\/code> dosyas\u0131n\u0131 otomatik olarak g\u00fcncelleyebilir. E\u011fer de\u011fi\u015fiklikleriniz kal\u0131c\u0131 olmuyorsa, a\u011f aray\u00fcz yap\u0131land\u0131rma dosyan\u0131z\u0131 (\/etc\/sysconfig\/network-scripts\/ifcfg-eth0<\/code>) d\u00fczenleyerek DNS sunucusunu orada belirtmeniz gerekebilir (\u00f6rn. DNS1=192.168.1.10<\/code>).<\/p>\n
dig<\/code> Komutu ile Test Etme<\/h4>\n
dig<\/code> (domain information groper), DNS sunucular\u0131n\u0131 sorgulamak i\u00e7in g\u00fc\u00e7l\u00fc bir ara\u00e7t\u0131r.<\/p>\n
1.  Kendi alan ad\u0131n\u0131z\u0131 sorgulay\u0131n (\u0130leriye D\u00f6n\u00fck \u00c7\u00f6z\u00fcmleme):<\/strong><\/p>\n
dig www.example.com @192.168.1.10<\/code><\/pre>\n
    Veya e\u011fer \/etc\/resolv.conf<\/code> do\u011fru yap\u0131land\u0131r\u0131ld\u0131ysa:<\/p>\n
dig www.example.com<\/code><\/pre>\n
    \u00c7\u0131kt\u0131da ANSWER SECTION<\/code> alt\u0131nda www.example.com. IN A 192.168.1.100<\/code> gibi bir kay\u0131t g\u00f6rmelisiniz.<\/p>\n
2.  Kendi alan ad\u0131n\u0131z\u0131n ana IP’sini sorgulay\u0131n:<\/strong><\/p>\n
dig example.com @192.168.1.10<\/code><\/pre>\n
    ANSWER SECTION<\/code> alt\u0131nda example.com. IN A 192.168.1.10<\/code> gibi bir kay\u0131t g\u00f6rmelisiniz.<\/p>\n
3.  Geriye D\u00f6n\u00fck \u00c7\u00f6z\u00fcmlemeyi Test Edin (PTR Kayd\u0131):<\/strong><\/p>\n
dig -x 192.168.1.100 @192.168.1.10<\/code><\/pre>\n
    \u00c7\u0131kt\u0131da ANSWER SECTION<\/code> alt\u0131nda 100.1.168.192.in-addr.arpa. IN PTR www.example.com.<\/code> gibi bir kay\u0131t g\u00f6rmelisiniz.<\/p>\n
4.  Harici bir alan ad\u0131n\u0131 sorgulay\u0131n (\u00d6zyineleme testi):<\/strong><\/p>\n
dig google.com @192.168.1.10<\/code><\/pre>\n
    Bu, BIND sunucunuzun harici DNS sunucular\u0131ndan bilgi al\u0131p almad\u0131\u011f\u0131n\u0131 kontrol eder. ANSWER SECTION<\/code> alt\u0131nda google.com<\/code> i\u00e7in bir veya daha fazla IP adresi g\u00f6rmelisiniz.<\/p>\n
nslookup<\/code> Komutu ile Test Etme (Alternatif)<\/h4>\n
nslookup<\/code> da DNS sorgular\u0131 i\u00e7in kullan\u0131labilir, ancak dig<\/code> daha ayr\u0131nt\u0131l\u0131 bilgi sa\u011flar ve genellikle daha \u00e7ok tercih edilir.<\/p>\n
nslookup www.example.com 192.168.1.10\nnslookup 192.168.1.100 192.168.1.10<\/code><\/pre>\n
Her iki komutta da do\u011fru IP adresleri veya alan adlar\u0131 d\u00f6nd\u00fcr\u00fclmelidir.<\/p>\n
Ba\u015fka Bir \u0130stemciden Test Etme<\/h4>\n
A\u011f\u0131n\u0131zdaki ba\u015fka bir bilgisayardan (\u00f6rne\u011fin, bir Windows veya ba\u015fka bir Linux makinesi) DNS sunucunuzu test etmek \u00f6nemlidir. \u0130stemcinin a\u011f ayarlar\u0131nda birincil DNS sunucusu olarak BIND sunucunuzun IP adresini (192.168.1.10<\/code>) yap\u0131land\u0131r\u0131n.<\/p>\n
Ard\u0131ndan, o istemciden ping www.example.com<\/code> veya nslookup www.example.com<\/code> gibi komutlar\u0131 \u00e7al\u0131\u015ft\u0131rarak \u00e7\u00f6z\u00fcmlemenin do\u011fru olup olmad\u0131\u011f\u0131n\u0131 kontrol edin.<\/p>\n
Ad\u0131m 9: G\u00fcvenlik \u0130pu\u00e7lar\u0131 ve En \u0130yi Uygulamalar<\/h3>\n
BIND sunucusu kurmak, a\u011f g\u00fcvenli\u011finiz i\u00e7in \u00f6nemli bir ad\u0131md\u0131r. G\u00fcvenli\u011fi art\u0131rmak i\u00e7in a\u015fa\u011f\u0131daki ipu\u00e7lar\u0131n\u0131 ve en iyi uygulamalar\u0131 g\u00f6z \u00f6n\u00fcnde bulundurun:<\/p>\n
*   allow-query<\/code> ve allow-recursion<\/code> K\u0131s\u0131tlamalar\u0131:<\/strong> named.conf<\/code> dosyas\u0131ndaki allow-query<\/code> ve allow-recursion<\/code> y\u00f6nergelerini yaln\u0131zca yerel a\u011f\u0131n\u0131zdaki veya g\u00fcvenilir istemcilerinizdeki IP adresleriyle s\u0131n\u0131rlay\u0131n. any<\/code> olarak b\u0131rakmak, sunucunuzu bir “a\u00e7\u0131k \u00e7\u00f6z\u00fcmleyici” (open resolver) haline getirir ve DDoS sald\u0131r\u0131lar\u0131 i\u00e7in k\u00f6t\u00fcye kullan\u0131labilir.
\n*   allow-transfer<\/code> K\u0131s\u0131tlamalar\u0131:<\/strong> E\u011fer ikincil (slave) DNS sunucular\u0131n\u0131z varsa, zone<\/code> bloklar\u0131nda allow-transfer<\/code> y\u00f6nergesini kullanarak b\u00f6lge transferlerine yaln\u0131zca yetkili ikincil sunucular\u0131n IP adreslerinden izin verin.
\n*   Root Hints Dosyas\u0131n\u0131 G\u00fcncel Tutun:<\/strong> \/var\/named\/named.ca<\/code> (veya named.root.hints<\/code>) dosyas\u0131ndaki k\u00f6k sunucu ipu\u00e7lar\u0131, BIND’\u0131n internetteki di\u011fer alan adlar\u0131n\u0131 \u00e7\u00f6zebilmesi i\u00e7in gereklidir. Bu dosya nadiren de\u011fi\u015fse de, zaman zaman g\u00fcncellendi\u011finden emin olun.
\n*   BIND G\u00fcncellemelerini Takip Edin:<\/strong> ISC (Internet Systems Consortium), BIND i\u00e7in d\u00fczenli olarak g\u00fcvenlik g\u00fcncellemeleri ve yamalar yay\u0131nlar. Sistem g\u00fcncellemelerinizi d\u00fczenli olarak yaparak (\u00f6rne\u011fin, sudo yum update -y<\/code>) BIND’\u0131n en son ve en g\u00fcvenli s\u00fcr\u00fcm\u00fcn\u00fc kulland\u0131\u011f\u0131n\u0131zdan emin olun.
\n*   G\u00fcnl\u00fck Kay\u0131tlar\u0131n\u0131 \u0130zleyin:<\/strong> BIND’\u0131n g\u00fcnl\u00fck kay\u0131tlar\u0131n\u0131 (\/var\/log\/messages<\/code> veya named.conf<\/code>‘ta yap\u0131land\u0131rd\u0131\u011f\u0131n\u0131z \u00f6zel g\u00fcnl\u00fck dosyalar\u0131) d\u00fczenli olarak kontrol edin. Anormal aktiviteler veya hata mesajlar\u0131, potansiyel g\u00fcvenlik sorunlar\u0131n\u0131 veya yap\u0131land\u0131rma hatalar\u0131n\u0131 g\u00f6sterebilir.
\n*   CHROOT Ortam\u0131nda \u00c7al\u0131\u015ft\u0131rma (Geli\u015fmi\u015f):<\/strong> BIND’\u0131 bir chroot (change root) ortam\u0131nda \u00e7al\u0131\u015ft\u0131rmak, bir sald\u0131rgan\u0131n BIND’\u0131 ele ge\u00e7irmesi durumunda sistemin geri kalan\u0131na eri\u015fimini k\u0131s\u0131tlar. Bu, daha karma\u015f\u0131k bir yap\u0131land\u0131rma gerektirir ancak g\u00fcvenli\u011fi \u00f6nemli \u00f6l\u00e7\u00fcde art\u0131r\u0131r. CentOS 6’da BIND genellikle varsay\u0131lan olarak chroot’ta \u00e7al\u0131\u015f\u0131r (\/var\/named\/chroot<\/code>). Kontrol etmek i\u00e7in \/etc\/sysconfig\/named<\/code> dosyas\u0131ndaki ROOTDIR<\/code> ayar\u0131na bakabilirsiniz.
\n*   DNSSEC Etkinle\u015ftirme:<\/strong> DNS Security Extensions (DNSSEC), DNS verilerinin b\u00fct\u00fcnl\u00fc\u011f\u00fcn\u00fc ve do\u011frulu\u011funu sa\u011flamak i\u00e7in kriptografik imzalar kullan\u0131r. named.conf<\/code> dosyas\u0131nda dnssec-enable yes;<\/code> ve dnssec-validation yes;<\/code> ayarlar\u0131n\u0131 etkinle\u015ftirerek DNSSEC do\u011frulamas\u0131n\u0131 a\u00e7abilirsiniz. Bu, DNS \u00f6nbellek zehirlenmesi (cache poisoning) gibi sald\u0131r\u0131lara kar\u015f\u0131 koruma sa\u011flar.
\n*   rndc<\/code> G\u00fcvenli\u011fi:<\/strong> rndc<\/code> (remote name daemon control) arac\u0131, BIND sunucusunu uzaktan y\u00f6netmek i\u00e7in kullan\u0131l\u0131r. rndc.key<\/code> dosyas\u0131 yetkisiz eri\u015fimi engellemek i\u00e7in do\u011fru izinlere sahip olmal\u0131 ve gizli tutulmal\u0131d\u0131r. Genellikle bu dosya sadece named<\/code> kullan\u0131c\u0131s\u0131 ve root taraf\u0131ndan okunabilir olmal\u0131d\u0131r.<\/p>\n
Sorun Giderme<\/h3>\n
BIND kurulumu veya yap\u0131land\u0131rmas\u0131 s\u0131ras\u0131nda sorunlarla kar\u015f\u0131la\u015fabilirsiniz. \u0130\u015fte yayg\u0131n sorunlar ve \u00e7\u00f6z\u00fcm yollar\u0131:<\/p>\n
*   BIND servisi ba\u015flam\u0131yor:<\/strong>
\n    *   G\u00fcnl\u00fck kay\u0131tlar\u0131n\u0131 kontrol edin:<\/strong> En \u00f6nemli ad\u0131m, \/var\/log\/messages<\/code> dosyas\u0131n\u0131 kontrol etmektir. BIND’\u0131n neden ba\u015flamad\u0131\u011f\u0131n\u0131 veya hata verdi\u011fini g\u00f6steren ayr\u0131nt\u0131l\u0131 mesajlar i\u00e7erir. sudo tail -f \/var\/log\/messages<\/code> komutu ile canl\u0131 g\u00fcnl\u00fckleri izleyebilirsiniz.
\n    *   Yap\u0131land\u0131rma dosyas\u0131 hatalar\u0131:<\/strong> named-checkconf<\/code> ve named-checkzone<\/code> komutlar\u0131n\u0131 tekrar \u00e7al\u0131\u015ft\u0131rarak t\u00fcm yap\u0131land\u0131rma dosyalar\u0131n\u0131z\u0131n hatas\u0131z oldu\u011fundan emin olun.
\n       Dosya izinleri:<\/strong> \/etc\/named.conf<\/code> ve \/var\/named\/<\/code> dizinindeki b\u00f6lge dosyalar\u0131n\u0131n named<\/code> kullan\u0131c\u0131s\u0131 taraf\u0131ndan okunabilir oldu\u011fundan emin olun. sudo chown root:named \/var\/named\/<\/em>.zone<\/code> ve sudo chmod 640 \/var\/named\/*.zone<\/code> gibi komutlarla izinleri d\u00fczeltebilirsiniz.
\n    *   SELinux:<\/strong> SELinux’un BIND’\u0131 engellemedi\u011finden emin olun. Ge\u00e7ici olarak sudo setenforce 0<\/code> ile devre d\u0131\u015f\u0131 b\u0131rak\u0131p tekrar deneyin. E\u011fer bu i\u015fe yararsa, SELinux politikalar\u0131n\u0131 ayarlaman\u0131z veya kal\u0131c\u0131 olarak devre d\u0131\u015f\u0131 b\u0131rakman\u0131z gerekir (\u00fcretim ortam\u0131nda dikkatli olun).
\n    *   Port \u00e7ak\u0131\u015fmas\u0131:<\/strong> Ba\u015fka bir uygulaman\u0131n 53 numaral\u0131 portu kullan\u0131p kullanmad\u0131\u011f\u0131n\u0131 kontrol edin: sudo netstat -tulpn | grep :53<\/code>.
\n*   DNS \u00e7\u00f6z\u00fcmlemesi \u00e7al\u0131\u015fm\u0131yor:<\/strong>
\n    *   Firewall:<\/strong> 53 numaral\u0131 UDP ve TCP portlar\u0131n\u0131n g\u00fcvenlik duvar\u0131nda a\u00e7\u0131k oldu\u011fundan emin olun (iptables<\/code> kurallar\u0131n\u0131 kontrol edin).
\n    *   allow-query<\/code> ayar\u0131:<\/strong> \/etc\/named.conf<\/code> dosyas\u0131ndaki allow-query<\/code> y\u00f6nergesinin, sorgu yapan istemcinin IP adresini veya a\u011f\u0131n\u0131 i\u00e7erdi\u011finden emin olun.
\n    *   recursion<\/code> ayar\u0131:<\/strong> E\u011fer harici alan adlar\u0131n\u0131 \u00e7\u00f6zmek istiyorsan\u0131z, recursion yes;<\/code> ayar\u0131n\u0131n etkin oldu\u011fundan emin olun.
\n    *   resolv.conf<\/code>:<\/strong> Test etti\u011finiz istemcinin (veya sunucunun kendisinin) \/etc\/resolv.conf<\/code> dosyas\u0131nda BIND sunucunuzun IP adresinin nameserver<\/code> olarak belirtildi\u011finden emin olun.
\n    *   B\u00f6lge dosyas\u0131 hatalar\u0131:<\/strong> named-checkzone<\/code> ile b\u00f6lge dosyalar\u0131n\u0131zda hata olmad\u0131\u011f\u0131ndan emin olun. \u00d6zellikle SOA seri numaras\u0131, NS ve A kay\u0131tlar\u0131 do\u011fru olmal\u0131d\u0131r.
\n    *   \u00d6nbelle\u011fi temizle:<\/strong> Bazen yanl\u0131\u015f \u00f6nbelle\u011fe al\u0131nm\u0131\u015f veriler sorunlara neden olabilir. BIND’\u0131n \u00f6nbelle\u011fini temizlemek i\u00e7in sudo rndc reload<\/code> veya sudo service named restart<\/code> komutlar\u0131n\u0131 kullanabilirsiniz.<\/p>\n
Sonu\u00e7<\/h3>\n
Bu kapsaml\u0131 rehberde, CentOS 6 i\u015fletim sistemi \u00fczerinde BIND DNS sunucusunu ba\u015ftan sona nas\u0131l kuraca\u011f\u0131n\u0131z\u0131 ve temel birincil DNS sunucusu olarak nas\u0131l yap\u0131land\u0131raca\u011f\u0131n\u0131z\u0131 \u00f6\u011frendiniz. BIND paketlerini kurmaktan, SELinux ve g\u00fcvenlik duvar\u0131 ayarlar\u0131n\u0131 yap\u0131land\u0131rmaya, ileriye d\u00f6n\u00fck ve geriye d\u00f6n\u00fck b\u00f6lgeleri olu\u015fturmaya ve DNS \u00e7\u00f6z\u00fcmlemesini test etmeye kadar t\u00fcm ad\u0131mlar\u0131 ayr\u0131nt\u0131l\u0131 olarak ele ald\u0131k. Ayr\u0131ca, DNS sunucunuzun g\u00fcvenli\u011fini sa\u011flamak ve olas\u0131 sorunlar\u0131 gidermek i\u00e7in \u00f6nemli ipu\u00e7lar\u0131 ve en iyi uygulamalar sunduk.<\/p>\n
BIND, g\u00fc\u00e7l\u00fc ve esnek bir DNS sunucusu olup, do\u011fru yap\u0131land\u0131r\u0131ld\u0131\u011f\u0131nda a\u011f\u0131n\u0131z\u0131n temel bir bile\u015feni olarak g\u00fcvenilir bir hizmet sunar. Bu rehberdeki ad\u0131mlar\u0131 takip ederek, kendi a\u011f\u0131n\u0131z i\u00e7in sa\u011flam bir DNS altyap\u0131s\u0131 kurabilir ve y\u00f6netebilirsiniz. Unutmay\u0131n ki DNS y\u00f6netimi s\u00fcrekli dikkat ve d\u00fczenli bak\u0131m gerektiren bir s\u00fcre\u00e7tir. Yap\u0131land\u0131rmalar\u0131n\u0131z\u0131 d\u00fczenli olarak g\u00f6zden ge\u00e7irmek, g\u00fcvenlik g\u00fcncellemelerini takip etmek ve g\u00fcnl\u00fck kay\u0131tlar\u0131n\u0131 izlemek, DNS sunucunuzun sorunsuz ve g\u00fcvenli bir \u015fekilde \u00e7al\u0131\u015fmas\u0131n\u0131 sa\u011flaman\u0131n anahtar\u0131d\u0131r. CentOS 6 eski bir sistem olsa da, bu temel bilgiler DNS sunucular\u0131n\u0131n \u00e7al\u0131\u015fma prensiplerini anlamak ve y\u00f6netmek i\u00e7in sa\u011flam bir temel olu\u015fturmaktad\u0131r.<\/body><\/p>\n","protected":false},"excerpt":{"rendered":"BIND DNS Sunucusunu CentOS 6 \u00dczerine Kurulumu ve Yap\u0131land\u0131rmas\u0131 Alan Ad\u0131 Sistemi (DNS), internetin telefon rehberidir. \u0130nsanlar\u0131n hat\u0131rlamas\u0131 kolay alan adlar\u0131n\u0131 (\u00f6rne\u011fin, google.","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"csco_page_header_type":"","csco_page_load_nextpost":"","csco_page_subscribe_form":"","csco_page_contact_form":"","footnotes":""},"categories":[241],"tags":[],"class_list":{"0":"post-40315","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-linux","7":"cs-entry","8":"cs-video-wrap"},"yoast_head":"\nBIND DNS Sunucusunu CentOS 6 \u00dczerine Kurulumu ve Yap\u0131land\u0131rmas\u0131 - Kodlar\u0131n Gizemli D\u00fcnyas\u0131<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/fatihsoysal.com\/blog\/bind-dns-sunucusunu-centos-6-uzerine-kurulumu-ve-yapilandirmasi\/\" \/>\n<meta property=\"og:locale\" content=\"tr_TR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"BIND DNS Sunucusunu CentOS 6 \u00dczerine Kurulumu ve Yap\u0131land\u0131rmas\u0131\" \/>\n<meta property=\"og:description\" content=\"BIND DNS Sunucusunu CentOS 6 \u00dczerine Kurulumu ve Yap\u0131land\u0131rmas\u0131 Alan Ad\u0131 Sistemi (DNS), internetin telefon rehberidir. \u0130nsanlar\u0131n hat\u0131rlamas\u0131 kolay alan adlar\u0131n\u0131 (\u00f6rne\u011fin, google.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/fatihsoysal.com\/blog\/bind-dns-sunucusunu-centos-6-uzerine-kurulumu-ve-yapilandirmasi\/\" \/>\n<meta property=\"og:site_name\" content=\"Kodlar\u0131n Gizemli D\u00fcnyas\u0131\" \/>\n<meta property=\"article:published_time\" content=\"2026-02-26T02:40:59+00:00\" \/>\n<meta name=\"author\" content=\"Fatih Soysal\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Yazan:\" \/>\n\t<meta name=\"twitter:data1\" content=\"Fatih Soysal\" \/>\n\t<meta name=\"twitter:label2\" content=\"Tahmini okuma s\u00fcresi\" \/>\n\t<meta name=\"twitter:data2\" content=\"24 dakika\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/bind-dns-sunucusunu-centos-6-uzerine-kurulumu-ve-yapilandirmasi\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/bind-dns-sunucusunu-centos-6-uzerine-kurulumu-ve-yapilandirmasi\/\"},\"author\":{\"name\":\"Fatih Soysal\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"headline\":\"BIND DNS Sunucusunu CentOS 6 \u00dczerine Kurulumu ve Yap\u0131land\u0131rmas\u0131\",\"datePublished\":\"2026-02-26T02:40:59+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/bind-dns-sunucusunu-centos-6-uzerine-kurulumu-ve-yapilandirmasi\/\"},\"wordCount\":3575,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"articleSection\":[\"Linux\"],\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/bind-dns-sunucusunu-centos-6-uzerine-kurulumu-ve-yapilandirmasi\/#respond\"]}],\"copyrightYear\":\"2026\",\"copyrightHolder\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#organization\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/bind-dns-sunucusunu-centos-6-uzerine-kurulumu-ve-yapilandirmasi\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/bind-dns-sunucusunu-centos-6-uzerine-kurulumu-ve-yapilandirmasi\/\",\"name\":\"BIND DNS Sunucusunu CentOS 6 \u00dczerine Kurulumu ve Yap\u0131land\u0131rmas\u0131 - Kodlar\u0131n Gizemli D\u00fcnyas\u0131\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\"},\"datePublished\":\"2026-02-26T02:40:59+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/bind-dns-sunucusunu-centos-6-uzerine-kurulumu-ve-yapilandirmasi\/#breadcrumb\"},\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/bind-dns-sunucusunu-centos-6-uzerine-kurulumu-ve-yapilandirmasi\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/bind-dns-sunucusunu-centos-6-uzerine-kurulumu-ve-yapilandirmasi\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Anasayfa\",\"item\":\"https:\/\/fatihsoysal.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"BIND DNS Sunucusunu CentOS 6 \u00dczerine Kurulumu ve Yap\u0131land\u0131rmas\u0131\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/\",\"name\":\"Fatihsoysal.com\",\"description\":\"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim\",\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"tr\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\",\"name\":\"Fatih Soysal\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"tr\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"contentUrl\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"width\":512,\"height\":512,\"caption\":\"Fatih Soysal\"},\"logo\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\"},\"description\":\"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"BIND DNS Sunucusunu CentOS 6 \u00dczerine Kurulumu ve Yap\u0131land\u0131rmas\u0131 - Kodlar\u0131n Gizemli D\u00fcnyas\u0131","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/fatihsoysal.com\/blog\/bind-dns-sunucusunu-centos-6-uzerine-kurulumu-ve-yapilandirmasi\/","og_locale":"tr_TR","og_type":"article","og_title":"BIND DNS Sunucusunu CentOS 6 \u00dczerine Kurulumu ve Yap\u0131land\u0131rmas\u0131","og_description":"BIND DNS Sunucusunu CentOS 6 \u00dczerine Kurulumu ve Yap\u0131land\u0131rmas\u0131 Alan Ad\u0131 Sistemi (DNS), internetin telefon rehberidir. \u0130nsanlar\u0131n hat\u0131rlamas\u0131 kolay alan adlar\u0131n\u0131 (\u00f6rne\u011fin, google.","og_url":"https:\/\/fatihsoysal.com\/blog\/bind-dns-sunucusunu-centos-6-uzerine-kurulumu-ve-yapilandirmasi\/","og_site_name":"Kodlar\u0131n Gizemli D\u00fcnyas\u0131","article_published_time":"2026-02-26T02:40:59+00:00","author":"Fatih Soysal","twitter_card":"summary_large_image","twitter_misc":{"Yazan:":"Fatih Soysal","Tahmini okuma s\u00fcresi":"24 dakika"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/fatihsoysal.com\/blog\/bind-dns-sunucusunu-centos-6-uzerine-kurulumu-ve-yapilandirmasi\/#article","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/bind-dns-sunucusunu-centos-6-uzerine-kurulumu-ve-yapilandirmasi\/"},"author":{"name":"Fatih Soysal","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"headline":"BIND DNS Sunucusunu CentOS 6 \u00dczerine Kurulumu ve Yap\u0131land\u0131rmas\u0131","datePublished":"2026-02-26T02:40:59+00:00","mainEntityOfPage":{"@id":"https:\/\/fatihsoysal.com\/blog\/bind-dns-sunucusunu-centos-6-uzerine-kurulumu-ve-yapilandirmasi\/"},"wordCount":3575,"commentCount":0,"publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"articleSection":["Linux"],"inLanguage":"tr","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/fatihsoysal.com\/blog\/bind-dns-sunucusunu-centos-6-uzerine-kurulumu-ve-yapilandirmasi\/#respond"]}],"copyrightYear":"2026","copyrightHolder":{"@id":"https:\/\/fatihsoysal.com\/blog\/#organization"}},{"@type":"WebPage","@id":"https:\/\/fatihsoysal.com\/blog\/bind-dns-sunucusunu-centos-6-uzerine-kurulumu-ve-yapilandirmasi\/","url":"https:\/\/fatihsoysal.com\/blog\/bind-dns-sunucusunu-centos-6-uzerine-kurulumu-ve-yapilandirmasi\/","name":"BIND DNS Sunucusunu CentOS 6 \u00dczerine Kurulumu ve Yap\u0131land\u0131rmas\u0131 - Kodlar\u0131n Gizemli D\u00fcnyas\u0131","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/#website"},"datePublished":"2026-02-26T02:40:59+00:00","breadcrumb":{"@id":"https:\/\/fatihsoysal.com\/blog\/bind-dns-sunucusunu-centos-6-uzerine-kurulumu-ve-yapilandirmasi\/#breadcrumb"},"inLanguage":"tr","potentialAction":[{"@type":"ReadAction","target":["https:\/\/fatihsoysal.com\/blog\/bind-dns-sunucusunu-centos-6-uzerine-kurulumu-ve-yapilandirmasi\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/fatihsoysal.com\/blog\/bind-dns-sunucusunu-centos-6-uzerine-kurulumu-ve-yapilandirmasi\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Anasayfa","item":"https:\/\/fatihsoysal.com\/blog\/"},{"@type":"ListItem","position":2,"name":"BIND DNS Sunucusunu CentOS 6 \u00dczerine Kurulumu ve Yap\u0131land\u0131rmas\u0131"}]},{"@type":"WebSite","@id":"https:\/\/fatihsoysal.com\/blog\/#website","url":"https:\/\/fatihsoysal.com\/blog\/","name":"Fatihsoysal.com","description":"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim","publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"tr"},{"@type":["Person","Organization"],"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1","name":"Fatih Soysal","image":{"@type":"ImageObject","inLanguage":"tr","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","contentUrl":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","width":512,"height":512,"caption":"Fatih Soysal"},"logo":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/"},"description":"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.","url":"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/"}]}},"yoast_meta":{"yoast_wpseo_title":"","yoast_wpseo_metadesc":"","yoast_wpseo_canonical":""},"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/40315","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/comments?post=40315"}],"version-history":[{"count":1,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/40315\/revisions"}],"predecessor-version":[{"id":40316,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/40315\/revisions\/40316"}],"wp:attachment":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/media?parent=40315"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/categories?post=40315"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/tags?post=40315"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}