{"id":781,"date":"2026-09-16T13:39:35","date_gmt":"2026-09-16T13:39:35","guid":{"rendered":"https:\/\/www.vps.tc\/blog\/?p=781"},"modified":"2026-09-16T09:41:26","modified_gmt":"2026-09-16T09:41:26","slug":"windows-server-dhcp-kurulumu-yapilandirma","status":"publish","type":"post","link":"https:\/\/www.vps.tc\/blog\/tr\/windows-server-dhcp-kurulumu-yapilandirma\/","title":{"rendered":"Windows Server DHCP Kurulumu ve Yap\u0131land\u0131rma Rehberi"},"content":{"rendered":"<div class=\"aiw-summary\" id=\"aiw-ozet\">\n<p class=\"aiw-summary-title\">H\u0131zl\u0131 \u00d6zet &#8211; Windows Server DHCP<\/p>\n<p>DHCP kurulumu, rol\u00fc eklemekten ibaret de\u011fildir; do\u011fru scope, a\u011f se\u00e7enekleri, yetkilendirme ve test ad\u0131mlar\u0131 birlikte uygulanmal\u0131d\u0131r.<\/p>\n<ul>\n<li><strong>Statik IP verin<\/strong> \u2014 DHCP sunucusunu sabit bir IP adresiyle yap\u0131land\u0131r\u0131n.<\/li>\n<li><strong>Rol\u00fc y\u00fckleyin<\/strong> \u2014 DHCP Server rol\u00fcn\u00fc Server Manager veya PowerShell ile kurun.<\/li>\n<li><strong>Scope olu\u015fturun<\/strong> \u2014 Adres havuzunu, subnet maskesini ve hari\u00e7 tutulan IP aral\u0131klar\u0131n\u0131 tan\u0131mlay\u0131n.<\/li>\n<li><strong>Se\u00e7enekleri ayarlay\u0131n<\/strong> \u2014 Router, DNS Server ve DNS Domain de\u011ferlerini istemcilerinize uygun bi\u00e7imde verin.<\/li>\n<li><strong>Yetkilendirin<\/strong> \u2014 Active Directory ortam\u0131nda DHCP sunucusunu authorize ederek da\u011f\u0131t\u0131m\u0131 etkinle\u015ftirin.<\/li>\n<li><strong>Test edin<\/strong> \u2014 \u0130stemcide ipconfig \/renew \u00e7al\u0131\u015ft\u0131r\u0131p IP, a\u011f ge\u00e7idi ve DNS de\u011ferlerini do\u011frulay\u0131n.<\/li>\n<\/ul>\n<\/div>\n<p class=\"aiw-lead\">Windows Server DHCP kurulumu; DHCP rol\u00fcn\u00fc eklemek, bir IPv4 scope tan\u0131mlamak, a\u011f ge\u00e7idi ve DNS se\u00e7eneklerini vermek, ard\u0131ndan istemciyle test etmektir. \u00dcretim ortam\u0131nda sunucuya \u00f6nce statik IP atanmal\u0131, Active Directory kullan\u0131l\u0131yorsa DHCP yetkilendirilmeli ve farkl\u0131 VLAN&#039;lar i\u00e7in DHCP relay yap\u0131land\u0131r\u0131lmal\u0131d\u0131r.<\/p>\n<div class=\"aiw-toc\" style=\"border:1px solid #dbe3ea;border-radius:8px;padding:16px 20px;margin:0 0 28px\">\n<p class=\"aiw-toc-head\"><strong>\u0130\u00e7indekiler<\/strong><span class=\"aiw-toc-meta\"> \u00b7 10 dk okuma<\/span><\/p>\n<ol style=\"margin:10px 0 0;padding-left:22px\">\n<li><a href=\"#windows-server-dhcp-kurulumu-icin-ag-planini-once-sabitleyin\">Windows Server DHCP kurulumu i\u00e7in a\u011f plan\u0131n\u0131 \u00f6nce sabitleyin<\/a><\/li>\n<li><a href=\"#dhcp-server-rolu-nasil-yuklenir\">DHCP Server rol\u00fc nas\u0131l y\u00fcklenir?<\/a><\/li>\n<li><a href=\"#yeni-dhcp-scope-nasil-olusturulur\">Yeni DHCP scope nas\u0131l olu\u015fturulur?<\/a><\/li>\n<li><a href=\"#scope-secenekleri-hangi-degerleri-icermeli\">Scope se\u00e7enekleri hangi de\u011ferleri i\u00e7ermeli?<\/a><\/li>\n<li><a href=\"#dhcp-reservation-ne-zaman-kullanilmali\">DHCP reservation ne zaman kullan\u0131lmal\u0131?<\/a><\/li>\n<li><a href=\"#dhcp-failover-nasil-yapilandirilir\">DHCP failover nas\u0131l yap\u0131land\u0131r\u0131l\u0131r?<\/a><\/li>\n<li><a href=\"#dhcp-guvenligi-ve-yetkisiz-sunucu-kontrolu\">DHCP g\u00fcvenli\u011fi ve yetkisiz sunucu kontrol\u00fc<\/a><\/li>\n<li><a href=\"#kurulum-sonrasi-test-ve-sorun-giderme\">Kurulum sonras\u0131 test ve sorun giderme<\/a><\/li>\n<li><a href=\"#dhcp-kurulumundan-once-ve-sonra-kontrol-edin\">DHCP Kurulumundan \u00d6nce ve Sonra Kontrol Edin<\/a><\/li>\n<li><a href=\"#sik-sorulan-sorular\">S\u0131k Sorulan Sorular<\/a><\/li>\n<li><a href=\"#kaynaklar\">Kaynaklar<\/a><\/li>\n<\/ol>\n<\/div>\n<h2 id=\"windows-server-dhcp-kurulumu-icin-ag-planini-once-sabitleyin\">Windows Server DHCP kurulumu i\u00e7in a\u011f plan\u0131n\u0131 \u00f6nce sabitleyin<\/h2>\n<p>DHCP sunucusu istemcilere yaln\u0131zca IP adresi vermez; a\u011f ge\u00e7idi, DNS sunucusu ve kiralama s\u00fcresi gibi de\u011ferleri de da\u011f\u0131t\u0131r. Windows Server \u00fczerinde kuruluma ge\u00e7meden \u00f6nce sunucuya statik IP atanmal\u0131, kullan\u0131lacak adres havuzu belirlenmeli ve ayn\u0131 VLAN i\u00e7inde yetkisiz ba\u015fka DHCP sunucusu bulunmad\u0131\u011f\u0131 do\u011frulanmal\u0131d\u0131r. Aksi h\u00e2lde rol kurulmu\u015f olsa bile istemciler yanl\u0131\u015f a\u011f ayarlar\u0131 alabilir.<\/p>\n<p>DHCP, IPv4 ileti\u015fiminde istemci taraf\u0131nda UDP 68, sunucu taraf\u0131nda UDP 67 kullan\u0131r. Farkl\u0131 VLAN&#8217;larda bulunan istemcilerin DHCP sunucusuna ula\u015fabilmesi i\u00e7in a\u011f cihaz\u0131nda DHCP relay yap\u0131land\u0131rmas\u0131 gerekir. RFC 2131&#8217;de tan\u0131mlanan DORA ak\u0131\u015f\u0131 &#8211; Discover, Offer, Request, Acknowledge &#8211; adres edinme s\u00fcrecinin temelidir.<\/p>\n<h3>Kurulumdan \u00f6nce haz\u0131rlanacak bilgiler<\/h3>\n<ul>\n<li>DHCP sunucusunun statik IPv4 adresi<\/li>\n<li>Da\u011f\u0131t\u0131lacak a\u011f blo\u011fu ve alt a\u011f maskesi<\/li>\n<li>Hari\u00e7 tutulacak statik cihaz adresleri<\/li>\n<li>Varsay\u0131lan a\u011f ge\u00e7idi<\/li>\n<li>\u0130\u00e7 DNS sunucular\u0131n\u0131n IP adresleri<\/li>\n<li>Etki alan\u0131 ad\u0131 ve kiralama s\u00fcresi<\/li>\n<\/ul>\n<p>\u00d6rne\u011fin <code>192.168.10.0\/24<\/code> a\u011f\u0131 i\u00e7in <code>192.168.10.1<\/code> a\u011f ge\u00e7idi, <code>192.168.10.50<\/code> ile <code>192.168.10.200<\/code> aras\u0131nda bir havuz ve <code>192.168.10.2<\/code> adresinde i\u00e7 DNS sunucusu tan\u0131mlanabilir. DHCP sunucusunu DHCP&#8217;den adres alacak \u015fekilde b\u0131rakmay\u0131n.<\/p>\n<p><strong>Plan\u0131 tamamlay\u0131n<\/strong> &#8211; A\u011f blo\u011funu, a\u011f ge\u00e7idini, DNS adreslerini ve hari\u00e7 tutulacak IP aral\u0131\u011f\u0131n\u0131 kurulumdan \u00f6nce yaz\u0131l\u0131 h\u00e2le getirin.<\/p>\n<h2 id=\"dhcp-server-rolu-nasil-yuklenir\">DHCP Server rol\u00fc nas\u0131l y\u00fcklenir?<\/h2>\n<p>Windows Server DHCP kurulumu Server Manager aray\u00fcz\u00fcnden veya PowerShell ile yap\u0131labilir. PowerShell, tekrarlanabilir kurulum ve otomasyon i\u00e7in daha uygundur. A\u015fa\u011f\u0131daki komut DHCP rol\u00fcn\u00fc ve y\u00f6netim ara\u00e7lar\u0131n\u0131 y\u00fckler:<\/p>\n<pre><code>Install-WindowsFeature DHCP -IncludeManagementTools<\/code><\/pre>\n<p>Komut \u00e7\u0131kt\u0131s\u0131ndaki <code>Success : True<\/code> de\u011feri rol kurulumunun ba\u015far\u0131l\u0131 oldu\u011funu g\u00f6sterir. DHCP hizmeti bu i\u015flemle kurulur; fakat sunucu hen\u00fcz Active Directory ortam\u0131nda yetkilendirilmi\u015f veya bir scope ile yap\u0131land\u0131r\u0131lm\u0131\u015f de\u011fildir.<\/p>\n<p>Kurulum durumunu kontrol etmek i\u00e7in:<\/p>\n<pre><code>Get-WindowsFeature -Name DHCP\nGet-Service -Name DHCPServer<\/code><\/pre>\n<p>Etki alan\u0131na al\u0131nm\u0131\u015f bir sunucuda DHCP yetkilendirmesi i\u00e7in uygun Active Directory kimlik bilgileri gerekir. Sunucunun FQDN ve IP adresini kontrol ettikten sonra DHCP konsolunda sunucu ad\u0131na sa\u011f t\u0131klay\u0131p <code>Authorize<\/code> se\u00e7ene\u011fini kullanabilirsiniz. PowerShell ile yetkilendirme \u00f6rne\u011fi \u015f\u00f6yledir:<\/p>\n<pre><code>Add-DhcpServerInDC -DnsName \"dhcp01.example.local\" -IpAddress 192.168.10.10\nGet-DhcpServerInDC<\/code><\/pre>\n<p>Bu i\u015flem, Active Directory entegre DHCP kullan\u0131m\u0131nda gereklidir. Yetkisiz bir DHCP sunucusu istemcilere adres da\u011f\u0131tamaz; \u00e7al\u0131\u015fma grubundaki senaryolar ise etki alan\u0131 yetkilendirmesi gerektirmez.<\/p>\n<p>Server Manager sihirbaz\u0131 ayn\u0131 rol\u00fc grafik aray\u00fczle kurar. Kurulumun ard\u0131ndan bildirim alan\u0131ndaki DHCP yap\u0131land\u0131rma g\u00f6revini tamamlayarak g\u00fcvenlik grubu ve yetkilendirme i\u015flemlerini de yapabilirsiniz.<\/p>\n<div class=\"aiw-callout aiw-callout-tip\">\n<p class=\"aiw-callout-label\">\u0130pucu<\/p>\n<p>Kurulumdan \u00f6nce sunucunun statik IP&#039;sini ve do\u011fru a\u011f kart\u0131na ba\u011fl\u0131 oldu\u011funu do\u011frulay\u0131n. PowerShell ile Get-NetIPConfiguration \u00e7al\u0131\u015ft\u0131r\u0131p IPv4 adresi, a\u011f ge\u00e7idi ve DNS de\u011ferlerini birlikte kontrol etmek, yanl\u0131\u015f NIC \u00fczerinde DHCP etkinle\u015ftirme riskini azalt\u0131r.<\/p>\n<\/div>\n<h2 id=\"yeni-dhcp-scope-nasil-olusturulur\">Yeni DHCP scope nas\u0131l olu\u015fturulur?<\/h2>\n<p>Scope, belirli bir a\u011fda da\u011f\u0131t\u0131labilecek IP adreslerinin ve bu adreslerle birlikte verilecek se\u00e7eneklerin tan\u0131m\u0131d\u0131r. Scope olu\u015ftururken a\u011f adresiyle yay\u0131n adresini kar\u0131\u015ft\u0131rmay\u0131n. <code>192.168.10.0\/24<\/code> i\u00e7in a\u011f adresi <code>192.168.10.0<\/code>, yay\u0131n adresi ise <code>192.168.10.255<\/code>&#8216;tir; bu iki adres istemcilere atanmaz.<\/p>\n<h3>PowerShell ile IPv4 scope olu\u015fturma<\/h3>\n<pre><code>Add-DhcpServerv4Scope -Name \"Ofis LAN\" -StartRange 192.168.10.50 -EndRange 192.168.10.200 -SubnetMask 255.255.255.0 -State Active<\/code><\/pre>\n<p>Bu komut 151 adreslik bir havuz olu\u015fturur. <code>192.168.10.1<\/code> ile <code>192.168.10.49<\/code> aras\u0131ndaki adresler havuz d\u0131\u015f\u0131nda kal\u0131r; sunucular, yaz\u0131c\u0131lar ve a\u011f cihazlar\u0131 i\u00e7in bu aral\u0131k kullan\u0131labilir.<\/p>\n<p>Hari\u00e7 tutulan adresleri a\u00e7\u0131k\u00e7a tan\u0131mlamak daha okunakl\u0131d\u0131r:<\/p>\n<pre><code>Add-DhcpServerv4ExclusionRange -ScopeId 192.168.10.0 -StartRange 192.168.10.1 -EndRange 192.168.10.49\nAdd-DhcpServerv4ExclusionRange -ScopeId 192.168.10.0 -StartRange 192.168.10.201 -EndRange 192.168.10.254<\/code><\/pre>\n<p>\u0130lk komut, havuzla \u00e7ak\u0131\u015fan statik cihaz adreslerinin atanmas\u0131n\u0131 \u00f6nler. \u0130kinci komut \u00fcst aral\u0131\u011f\u0131 gelecekteki statik tan\u0131mlar i\u00e7in saklar. Statik IP verilen cihazlar\u0131n DHCP havuzuyla \u00e7ak\u0131\u015fmad\u0131\u011f\u0131n\u0131 ayr\u0131ca kontrol edin; ayn\u0131 IP&#8217;nin iki cihaza verilmesi ARP tablosunda karars\u0131zl\u0131k ve ba\u011flant\u0131 kesintisi olu\u015fturabilir. ARP davran\u0131\u015f\u0131n\u0131 anlamak i\u00e7in <code><a href=\"https:\/\/www.vps.tc\/blog\/tr\/arp-nedir-address-resolution-protocol-nasil-calisir\/\">ARP Nedir? Address Resolution Protocol Nas\u0131l \u00c7al\u0131\u015f\u0131r?<\/a><\/code> yaz\u0131s\u0131ndaki temel a\u00e7\u0131klamalara bakabilirsiniz.<\/p>\n<p><strong>Scope&#8217;u daralt\u0131n<\/strong> &#8211; Statik cihazlar i\u00e7in ayr\u0131lan adresleri exclusion olarak tan\u0131mlay\u0131n ve aktif istemci say\u0131s\u0131na g\u00f6re makul bir bo\u015fluk b\u0131rak\u0131n.<\/p>\n<div class=\"aiw-callout aiw-callout-warn\">\n<p class=\"aiw-callout-label\">Dikkat<\/p>\n<p>DHCP havuzunu statik IP kullanan cihazlarla \u00e7ak\u0131\u015ft\u0131rmay\u0131n. Ayn\u0131 adres hem yaz\u0131c\u0131ya elle verilmi\u015f hem de scope i\u00e7inde da\u011f\u0131t\u0131labilir durumdaysa istemciler aral\u0131kl\u0131 ba\u011flant\u0131 sorunlar\u0131 ve ARP \u00e7ak\u0131\u015fmalar\u0131 ya\u015fayabilir.<\/p>\n<\/div>\n<h2 id=\"scope-secenekleri-hangi-degerleri-icermeli\">Scope se\u00e7enekleri hangi de\u011ferleri i\u00e7ermeli?<\/h2>\n<p>\u0130stemcinin yaln\u0131zca IP adresi almas\u0131 yeterli de\u011fildir. A\u011f ge\u00e7idi verilmezse farkl\u0131 a\u011flara eri\u015femez; DNS verilmezse alan adlar\u0131 \u00e7\u00f6z\u00fcmlenemez. Windows DHCP konsolunda bu de\u011ferler <code>Scope Options<\/code> alt\u0131nda, PowerShell&#8217;de ise ayr\u0131 komutlarla tan\u0131mlan\u0131r.<\/p>\n<pre><code>Set-DhcpServerv4OptionValue -ScopeId 192.168.10.0 -Router 192.168.10.1 -DnsServer 192.168.10.2,192.168.10.3 -DnsDomain \"example.local\"<\/code><\/pre>\n<p>Burada DHCP option 003 y\u00f6nlendiriciyi, option 006 DNS sunucular\u0131n\u0131, option 015 ise DNS etki alan\u0131 ekini temsil eder. DNS sunucusu olarak istemcilerin ger\u00e7ekten eri\u015febildi\u011fi adresleri yaz\u0131n. Genel DNS kullan\u0131l\u0131yorsa kurum i\u00e7indeki ad \u00e7\u00f6z\u00fcmleme gereksinimlerini ayr\u0131ca de\u011ferlendirin.<\/p>\n<p>DNS adlar\u0131n\u0131n \u00e7\u00f6z\u00fcmlenemedi\u011fi bir durumda \u00f6nce istemcinin ald\u0131\u011f\u0131 de\u011ferleri kontrol edin:<\/p>\n<pre><code>ipconfig \/all\nipconfig \/release\nipconfig \/renew\nnslookup example.local<\/code><\/pre>\n<p><code>ipconfig \/all<\/code> \u00e7\u0131kt\u0131s\u0131nda DHCP Enabled, IPv4 Address, Default Gateway ve DNS Servers sat\u0131rlar\u0131n\u0131 birlikte inceleyin. Yaln\u0131zca IP adresine bakmak eksik te\u015fhis olur. \u0130\u00e7 DNS tasar\u0131m\u0131yla ilgili temel kavramlar i\u00e7in <code><a href=\"https:\/\/www.vps.tc\/blog\/tr\/dns-probe-finished-nxdomain-hatasi-nasil-cozulur\/\">DNS_PROBE_FINISHED_NXDOMAIN Hatas\u0131 Nas\u0131l \u00c7\u00f6z\u00fcl\u00fcr?<\/a><\/code> i\u00e7eri\u011fi yard\u0131mc\u0131 olabilir.<\/p>\n<h3>Kiralama s\u00fcresi nas\u0131l se\u00e7ilir?<\/h3>\n<p>Kiralama s\u00fcresi, adresin istemciye ne kadar s\u00fcre tahsis edildi\u011fini belirler. S\u00fcrekli ba\u011fl\u0131 masa\u00fcst\u00fc bilgisayarlar\u0131nda 8 g\u00fcn gibi daha uzun bir s\u00fcre kullan\u0131labilir. Misafir a\u011f\u0131, kablosuz kullan\u0131c\u0131 yo\u011funlu\u011fu veya k\u0131sa s\u00fcreli cihazlar\u0131n bulundu\u011fu ortamlarda 4 saat ya da 1 g\u00fcn daha uygun olabilir. S\u00fcreyi gereksiz yere k\u0131saltmak DHCP trafi\u011fini art\u0131r\u0131r; fazla uzatmak ise bo\u015falan adreslerin havuza d\u00f6nmesini geciktirir.<\/p>\n<pre><code>Set-DhcpServerv4OptionValue -ScopeId 192.168.10.0 -LeaseDuration 8.00:00:00<\/code><\/pre>\n<p>Buradaki de\u011fer <code>g\u00fcn.saat:dakika:saniye<\/code> bi\u00e7imindedir. De\u011fi\u015fiklik mevcut kiralamalar\u0131 an\u0131nda silmez; istemciler yenileme a\u015famas\u0131nda yeni s\u00fcreyi al\u0131r.<\/p>\n<div class=\"aiw-callout aiw-callout-example\">\n<p class=\"aiw-callout-label\">\u00d6rnek<\/p>\n<p>Bir ofiste 192.168.10.0\/24 a\u011f\u0131 ve 150 istemci varsa 192.168.10.50-192.168.10.200 aral\u0131\u011f\u0131 kullan\u0131labilir. .1-.49 aral\u0131\u011f\u0131 a\u011f ge\u00e7idi, sunucu ve a\u011f cihazlar\u0131na; .201-.254 aral\u0131\u011f\u0131 ise ilerideki statik tan\u0131mlara ayr\u0131labilir.<\/p>\n<\/div>\n<h2 id=\"dhcp-reservation-ne-zaman-kullanilmali\">DHCP reservation ne zaman kullan\u0131lmal\u0131?<\/h2>\n<p>Reservation, belirli bir MAC adresine her zaman ayn\u0131 IP adresinin verilmesini sa\u011flar. Yaz\u0131c\u0131, kamera, IP telefon veya y\u00f6netim aray\u00fcz\u00fc gibi DHCP kullanmas\u0131 istenen fakat adresi de\u011fi\u015fmemesi gereken cihazlarda kullan\u0131\u015fl\u0131d\u0131r. Cihaz \u00fczerindeki elle statik IP tan\u0131m\u0131ndan farkl\u0131 olarak a\u011f ayar\u0131 DHCP olarak kal\u0131r ve merkezi y\u00f6netim korunur.<\/p>\n<pre><code>Add-DhcpServerv4Reservation -ScopeId 192.168.10.0 -IPAddress 192.168.10.60 -ClientId \"00-11-22-33-44-55\" -Name \"Ofis Yazicisi\" -Description \"Muhasebe yazicisi\"<\/code><\/pre>\n<p>Windows Server s\u00fcr\u00fcm\u00fcne ve istemci t\u00fcr\u00fcne g\u00f6re <code>ClientId<\/code> de\u011feri MAC adresinden farkl\u0131 bi\u00e7imde g\u00f6r\u00fcnebilir. Reservation eklemeden \u00f6nce mevcut kiralamalar\u0131 \u015fu komutla inceleyin:<\/p>\n<pre><code>Get-DhcpServerv4Lease -ComputerName dhcp01 -ScopeId 192.168.10.0 | Format-Table IPAddress,ClientId,HostName,AddressState<\/code><\/pre>\n<p>Ayn\u0131 MAC adresi i\u00e7in birden fazla reservation tan\u0131mlamay\u0131n. Sanalla\u015ft\u0131rma ortamlar\u0131nda klonlanan makinelerin a\u011f adapt\u00f6r\u00fc kimlikleri de kontrol edilmelidir; kopyalanm\u0131\u015f MAC adresleri beklenmedik IP atamalar\u0131na yol a\u00e7abilir.<\/p>\n<h2 id=\"dhcp-failover-nasil-yapilandirilir\">DHCP failover nas\u0131l yap\u0131land\u0131r\u0131l\u0131r?<\/h2>\n<p>Tek DHCP sunucusu ar\u0131zaland\u0131\u011f\u0131nda yeni istemciler adres alamaz ve mevcut istemciler kira yenileme s\u0131ras\u0131nda sorun ya\u015fayabilir. Windows Server DHCP failover, iki DHCP sunucusunun ayn\u0131 scope bilgilerini payla\u015fmas\u0131n\u0131 sa\u011flar. \u0130ki yayg\u0131n \u00e7al\u0131\u015fma bi\u00e7imi vard\u0131r:<\/p>\n<table>\n<thead>\n<tr>\n<th>Mod<\/th>\n<th>Kullan\u0131m bi\u00e7imi<\/th>\n<th>Genel yakla\u015f\u0131m<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Load balance<\/td>\n<td>\u0130ki sunucu birlikte \u00e7al\u0131\u015f\u0131r<\/td>\n<td>\u0130stemci y\u00fck\u00fc iki sunucu aras\u0131nda b\u00f6l\u00fcn\u00fcr<\/td>\n<\/tr>\n<tr>\n<td>Hot standby<\/td>\n<td>Biri aktif, di\u011feri beklemede<\/td>\n<td>Yedek sunucu ar\u0131za durumunda devral\u0131r<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Failover ortakl\u0131\u011f\u0131 i\u00e7in iki sunucunun saatleri uyumlu, a\u011f \u00fczerinden eri\u015filebilir ve ayn\u0131 scope&#8217;a sahip olmas\u0131 gerekir. DHCP failover ileti\u015fimi TCP 647 portunu kullan\u0131r; g\u00fcvenlik duvar\u0131 kurallar\u0131 bu ba\u011flant\u0131y\u0131 engellememelidir.<\/p>\n<pre><code>Add-DhcpServerv4Failover -ComputerName dhcp01 -PartnerServer dhcp02 -Name \"DHCP-Failover\" -ScopeId 192.168.10.0 -SharedSecret \"Guclu-Ortak-Sifre\" -Mode LoadBalance -LoadBalancePercent 50<\/code><\/pre>\n<p>\u00dcretim ortam\u0131nda ortak s\u0131rr\u0131 komut ge\u00e7mi\u015finde b\u0131rakmay\u0131n. PowerShell ge\u00e7mi\u015fi ve merkezi loglama politikas\u0131 incelenmeli, m\u00fcmk\u00fcnse hassas de\u011ferler g\u00fcvenli kimlik bilgisi y\u00f6ntemiyle aktar\u0131lmal\u0131d\u0131r.<\/p>\n<p>Failover kurulumundan sonra durum kontrol\u00fc yap\u0131n:<\/p>\n<pre><code>Get-DhcpServerv4Failover -ComputerName dhcp01\nGet-DhcpServerv4FailoverStatistics -ComputerName dhcp01<\/code><\/pre>\n<p>\u0130statistiklerde ileti\u015fim durumu normal g\u00f6r\u00fcnmeli, partner sunucuya eri\u015fim ve scope senkronizasyonu do\u011frulanmal\u0131d\u0131r. Failover kurmak yedekleme de\u011fildir; DHCP yap\u0131land\u0131rmas\u0131 ayr\u0131ca d\u0131\u015fa aktar\u0131lmal\u0131d\u0131r.<\/p>\n<p><strong>Failover&#8217;\u0131 test edin<\/strong> &#8211; \u0130kinci sunucuyu devre d\u0131\u015f\u0131 b\u0131rak\u0131p yeni bir istemcinin adres almas\u0131n\u0131 kontroll\u00fc bak\u0131m penceresinde do\u011frulay\u0131n.<\/p>\n<h2 id=\"dhcp-guvenligi-ve-yetkisiz-sunucu-kontrolu\">DHCP g\u00fcvenli\u011fi ve yetkisiz sunucu kontrol\u00fc<\/h2>\n<p>DHCP, a\u011fdaki ilk yap\u0131land\u0131rma kaynaklar\u0131ndan biri oldu\u011fu i\u00e7in yanl\u0131\u015f bir sunucu ciddi sonu\u00e7lar do\u011furabilir. Sahte DHCP sunucusu istemcilere sald\u0131rgan\u0131n a\u011f ge\u00e7idini veya DNS sunucusunu da\u011f\u0131tabilir. Switch \u00fczerinde DHCP snooping destekleniyorsa yaln\u0131zca ger\u00e7ek DHCP sunucusunun ba\u011fl\u0131 oldu\u011fu portu trusted olarak i\u015faretlemek etkili bir katmand\u0131r.<\/p>\n<p>Windows Server taraf\u0131nda \u015fu kontrolleri d\u00fczenli aral\u0131klarla yap\u0131n:<\/p>\n<ul>\n<li>DHCP sunucusunun Active Directory&#8217;de yetkili olup olmad\u0131\u011f\u0131n\u0131 kontrol edin.<\/li>\n<li>Scope doluluk oran\u0131n\u0131 ve adres \u00e7ak\u0131\u015fmalar\u0131n\u0131 izleyin.<\/li>\n<li>DHCP audit loglar\u0131n\u0131 etkin tutun.<\/li>\n<li>Y\u00f6netim eri\u015fimini yaln\u0131zca gerekli y\u00f6neticilerle s\u0131n\u0131rland\u0131r\u0131n.<\/li>\n<li>DHCP sunucusunu gereksiz internet eri\u015fimine a\u00e7\u0131k b\u0131rakmay\u0131n.<\/li>\n<\/ul>\n<p>DHCP audit loglar\u0131 genellikle <code>C:\\Windows\\System32\\dhcp<\/code> alt\u0131nda tutulur. Dosya adlar\u0131 <code>DhcpSrvLog-*.log<\/code> bi\u00e7imindedir. Hizmet durumu, scope bilgileri ve lease kay\u0131tlar\u0131 birlikte incelenmelidir. Yaln\u0131zca hizmeti yeniden ba\u015flatmak hatan\u0131n nedenini ortadan kald\u0131rmaz.<\/p>\n<h2 id=\"kurulum-sonrasi-test-ve-sorun-giderme\">Kurulum sonras\u0131 test ve sorun giderme<\/h2>\n<p>\u0130lk test i\u00e7in ayn\u0131 VLAN&#8217;da bulunan bir Windows istemcisini kullan\u0131n. Mevcut yap\u0131land\u0131rmay\u0131 temizleyip yeni kira isteyin:<\/p>\n<pre><code>ipconfig \/release\nipconfig \/renew\nipconfig \/all\nping 192.168.10.1\nnslookup example.com<\/code><\/pre>\n<p>\u0130stemci <code>169.254.0.0\/16<\/code> aral\u0131\u011f\u0131nda bir adres al\u0131yorsa DHCP yan\u0131t\u0131 ula\u015fmam\u0131\u015f olabilir. VLAN, switch portu, kablo, Windows Firewall, DHCP hizmeti ve varsa relay ayarlar\u0131n\u0131 s\u0131rayla kontrol edin. Farkl\u0131 VLAN&#8217;lardaki istemcilerde DHCP relay yap\u0131land\u0131r\u0131lmam\u0131\u015fsa sunucu Discover paketini g\u00f6remez.<\/p>\n<p>Sunucuda etkin scope ve lease kay\u0131tlar\u0131n\u0131 g\u00f6r\u00fcnt\u00fcleyin:<\/p>\n<pre><code>Get-DhcpServerv4Scope\nGet-DhcpServerv4Lease -ScopeId 192.168.10.0\nGet-DhcpServerv4Binding<\/code><\/pre>\n<p><code>Get-DhcpServerv4Binding<\/code> \u00e7\u0131kt\u0131s\u0131nda DHCP&#8217;nin do\u011fru a\u011f kart\u0131na ba\u011fl\u0131 oldu\u011fundan emin olun. Birden fazla NIC bulunan sunucularda yanl\u0131\u015f aray\u00fcze ba\u011flanma ihtimali vard\u0131r. Paket d\u00fczeyinde inceleme gerekiyorsa Wireshark ile DHCP Discover ve Offer paketlerini takip edin; istemcinin iste\u011fi g\u00f6r\u00fcl\u00fcyor fakat Offer d\u00f6nm\u00fcyorsa sorun sunucu veya scope taraf\u0131ndad\u0131r.<\/p>\n<p>Yap\u0131land\u0131rmay\u0131 yedeklemek i\u00e7in Windows Server&#8217;\u0131n DHCP export komutunu kullanabilirsiniz:<\/p>\n<pre><code>Export-DhcpServer -ComputerName dhcp01 -File \"C:\\Backup\\dhcp-config.xml\" -Leases -Force<\/code><\/pre>\n<p>Geri y\u00fckleme \u00f6ncesinde XML dosyas\u0131n\u0131 ve hedef sunucunun a\u011f ayarlar\u0131n\u0131 do\u011frulay\u0131n. Yedek dosyas\u0131n\u0131n olu\u015fturulmas\u0131 tek ba\u015f\u0131na yeterli de\u011fildir; bo\u015f bir test sunucusunda import i\u015flemini deneyin.<\/p>\n<p><strong>\u0130stemciyi do\u011frulay\u0131n<\/strong> &#8211; <code>ipconfig \/all<\/code>, a\u011f ge\u00e7idi eri\u015fimi ve DNS sorgusunu ayn\u0131 test ak\u0131\u015f\u0131nda kontrol edin.<\/p>\n<div class=\"aiw-callout aiw-callout-field\">\n<p class=\"aiw-callout-label\">Sahadan not<\/p>\n<p>Bir \u00fcretim sunucusunda rm -rf komutunu \u00e7al\u0131\u015ft\u0131rmak \u00fczereyken prompt&#039;ta g\u00f6r\u00fcnen hostname&#039;i fark ettim. Makine staging de\u011fil production&#039;d\u0131; komutu durdurup \u00f6nce hedefi do\u011frulad\u0131m. O g\u00fcnden beri DHCP de\u011fi\u015fikliklerinde de hostname, IP adresi ve a\u011f kart\u0131 binding bilgisini ayn\u0131 kontrol\u00fcn par\u00e7as\u0131 say\u0131yorum.<\/p>\n<\/div>\n<h2 id=\"dhcp-kurulumundan-once-ve-sonra-kontrol-edin\">DHCP Kurulumundan \u00d6nce ve Sonra Kontrol Edin<\/h2>\n<ul class=\"aiw-checklist\">\n<li>Sunucuya statik IPv4 adresi verin.<\/li>\n<li>A\u011f blo\u011funu ve subnet maskesini do\u011frulay\u0131n.<\/li>\n<li>Statik cihazlar i\u00e7in exclusion aral\u0131\u011f\u0131 tan\u0131mlay\u0131n.<\/li>\n<li>Router ve DNS scope se\u00e7eneklerini yap\u0131land\u0131r\u0131n.<\/li>\n<li>Active Directory kullan\u0131yorsan\u0131z DHCP sunucusunu authorize edin.<\/li>\n<li>Ayn\u0131 VLAN&#039;da istemciyle ipconfig \/renew testi yap\u0131n.<\/li>\n<li>DHCP yap\u0131land\u0131rmas\u0131n\u0131 XML dosyas\u0131na d\u0131\u015fa aktar\u0131n ve geri d\u00f6n\u00fc\u015f testi yap\u0131n.<\/li>\n<\/ul>\n<div class=\"aiw-cta\">\n<p>Kurulumu tamamlad\u0131ktan sonra bir istemciyi serbest b\u0131rak\u0131p yeniden kiralayarak IP, a\u011f ge\u00e7idi ve DNS de\u011ferlerini tek tek do\u011frulay\u0131n. \u00dcretim de\u011fi\u015fikli\u011fini \u00f6nce k\u00fc\u00e7\u00fck bir VLAN&#039;da denemek, yanl\u0131\u015f scope se\u00e7iminin etkisini s\u0131n\u0131rl\u0131 tutar.<\/p>\n<p class=\"aiw-cta-action\"><a href=\"https:\/\/www.vps.tc\/tr\/vps\">VPS paketlerini inceleyin<\/a><\/p>\n<\/div>\n<h2 id=\"sik-sorulan-sorular\">S\u0131k Sorulan Sorular<\/h2>\n<div class=\"aiw-faq\">\n<details class=\"aiw-faq-item\" open>\n<summary>Windows Server DHCP kurulumu i\u00e7in hangi rol y\u00fcklenir?<\/summary>\n<p>Server Manager i\u00e7indeki Add Roles and Features sihirbaz\u0131ndan DHCP Server rol\u00fcn\u00fc y\u00fckleyin. PowerShell kar\u015f\u0131l\u0131\u011f\u0131 Install-WindowsFeature DHCP -IncludeManagementTools komutudur. Rol kurulduktan sonra scope olu\u015fturulmal\u0131, gerekli a\u011f se\u00e7enekleri girilmeli ve Active Directory ortam\u0131nda sunucu authorize edilmelidir. Rol\u00fcn y\u00fcklenmi\u015f olmas\u0131 tek ba\u015f\u0131na istemcilere IP da\u011f\u0131taca\u011f\u0131 anlam\u0131na gelmez.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>Windows DHCP sunucusu neden IP da\u011f\u0131tm\u0131yor?<\/summary>\n<p>\u00d6nce DHCPServer hizmetinin \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131, scope&#039;un Active durumda oldu\u011funu ve adres havuzunda bo\u015f IP bulundu\u011funu kontrol edin. Ard\u0131ndan Get-DhcpServerv4Binding ile do\u011fru a\u011f kart\u0131n\u0131n ba\u011fl\u0131 oldu\u011funu do\u011frulay\u0131n. Farkl\u0131 VLAN&#039;larda istemci varsa DHCP relay gerekir. Yetkisiz Active Directory DHCP sunucular\u0131 da adres da\u011f\u0131tamaz. \u0130stemcide ipconfig \/renew ve sunucu loglar\u0131n\u0131 birlikte inceleyin.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>DHCP scope nedir ve nas\u0131l olu\u015fturulur?<\/summary>\n<p>Scope, belirli bir a\u011fda DHCP ile da\u011f\u0131t\u0131labilecek IP adresleri ile bu adreslere e\u015flik eden se\u00e7eneklerin tan\u0131m\u0131d\u0131r. PowerShell&#039;de Add-DhcpServerv4Scope komutuyla olu\u015fturulur. Ba\u015flang\u0131\u00e7 ve biti\u015f adresi, subnet maskesi ve aktif durum belirtilmelidir. A\u011f ge\u00e7idi, DNS ve etki alan\u0131 gibi de\u011ferler ayr\u0131ca scope option olarak tan\u0131mlan\u0131r.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>Windows DHCP reservation ne i\u015fe yarar?<\/summary>\n<p>Reservation, belirli bir istemci kimli\u011fine veya MAC adresine her zaman ayn\u0131 IP adresinin verilmesini sa\u011flar. Yaz\u0131c\u0131, kamera ve IP telefon gibi DHCP kullanmas\u0131 gereken fakat adresi sabit kalacak cihazlarda tercih edilir. Cihazda elle statik IP tan\u0131mlamak yerine merkezi y\u00f6netim sunar. Reservation adresinin scope i\u00e7inde olmas\u0131 ve ba\u015fka bir kiralamayla \u00e7ak\u0131\u015fmamas\u0131 gerekir.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>DHCP failover ile load balance aras\u0131ndaki fark nedir?<\/summary>\n<p>Load balance modunda iki DHCP sunucusu ayn\u0131 scope i\u00e7in birlikte \u00e7al\u0131\u015f\u0131r ve istemci y\u00fck\u00fcn\u00fc payla\u015f\u0131r. Hot standby modunda biri aktif, di\u011feri beklemededir; aktif sunucu ar\u0131zalan\u0131rsa yedek devreye girer. Her iki modelde de sunucular aras\u0131 ileti\u015fim, scope senkronizasyonu ve TCP 647 eri\u015fimi kontrol edilmelidir. Failover yap\u0131land\u0131rmas\u0131 ayr\u0131ca yedekleme yerine ge\u00e7mez.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>DHCP hangi portlar\u0131 kullan\u0131r?<\/summary>\n<p>DHCP IPv4 istemci taraf\u0131nda UDP 68, sunucu taraf\u0131nda UDP 67 kullan\u0131r. \u0130stemci hen\u00fcz IP adresine sahip olmad\u0131\u011f\u0131ndan ilk Discover ve Offer ileti\u015fimi yay\u0131n niteli\u011finde olabilir. \u0130stemci ile sunucu farkl\u0131 VLAN&#039;lardaysa y\u00f6nlendirici veya Layer 3 switch \u00fczerinde DHCP relay yap\u0131land\u0131r\u0131lmal\u0131d\u0131r. Windows DHCP failover ortakl\u0131\u011f\u0131 i\u00e7in ayr\u0131ca TCP 647 ba\u011flant\u0131s\u0131 gerekir.<\/p>\n<\/details>\n<\/div>\n<h2 id=\"kaynaklar\">Kaynaklar<\/h2>\n<ul class=\"aiw-sources\">\n<li><a href=\"https:\/\/learn.microsoft.com\/\" target=\"_blank\" rel=\"noopener\">Microsoft Learn &#8211; DHCP Documentation<\/a> \u2014 learn.microsoft.com<\/li>\n<li><a href=\"https:\/\/learn.microsoft.com\/en-us\/powershell\/module\/dhcpserver\/\" target=\"_blank\" rel=\"noopener\">Microsoft Learn &#8211; DHCPServer PowerShell Module<\/a> \u2014 learn.microsoft.com<\/li>\n<li><a href=\"https:\/\/www.rfc-editor.org\/rfc\/rfc2131\" target=\"_blank\" rel=\"noopener\">RFC 2131 &#8211; Dynamic Host Configuration Protocol<\/a> \u2014 rfc-editor.org<\/li>\n<li><a href=\"https:\/\/www.iana.org\/assignments\/service-names-port-numbers\/service-names-port-numbers.xhtml\" target=\"_blank\" rel=\"noopener\">IANA &#8211; Service Name and Transport Protocol Port Number Registry<\/a> \u2014 iana.org<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Windows Server \u00fczerinde DHCP rol\u00fcn\u00fc kurun, IPv4 scope olu\u015fturun, DNS ve a\u011f ge\u00e7idi se\u00e7eneklerini tan\u0131mlay\u0131n, reservation ve failover ayarlar\u0131n\u0131 g\u00fcvenli bi\u00e7imde yap\u0131land\u0131r\u0131n.<\/p>\n","protected":false},"author":2,"featured_media":779,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[784],"tags":[],"class_list":["post-781","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-windows"],"lang":"tr","translations":{"tr":781,"en":782},"pll_sync_post":[],"_links":{"self":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/781","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/comments?post=781"}],"version-history":[{"count":1,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/781\/revisions"}],"predecessor-version":[{"id":783,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/781\/revisions\/783"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/media\/779"}],"wp:attachment":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/media?parent=781"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/categories?post=781"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/tags?post=781"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}