Video Series on Advance Networking with Windows Server 2019: Step by step video guide on How to Configure DHCP Fail-over using two DHCP servers running on Windows Server 2019. Follow my blogs: msftwebcast.com
Nice video, a question for you : in a DHCP failover environment (load balance), if something is changed in the scope setup (DNS tab for example) ,is this automatic replicated to the failover server or do I have to manually replicate? Thanks in advance
First of all sorry that I didn't cover that information in the video. When we first time configure the fail-over relationship on the scope, all the details from the scope are copied to the other DHCP server including lease info and scope options. But then after if you change any scope options, it will not sync automatically. You have to manually sync that using replicate scope option or PowerShell cmdlet.
You might have to add a second ip-helper-address on your switches or routers if your relaying across VLANs (meaning you are assigning DHCP from one vlan to others devices on other VLANs)
it was once recommended to have dhcp dns on the DC, now MS advise not to have DHCP on the DC due to security vulnerabilities and load on the servers. DHCP failover as described in this video was also something microsoft advised against using back when it was first implemented. are we saying that this is now the best way to setup DHCP resilience? what about having two DHCP servers in a windows cluster?
DHCP service wont create any load on existing DC+DNS server. It will use minimal of resources. If you have spare server the you can install DHCP service on it. But most of small environments are still using DC+DNS+DHCP setup.
@@MSFTWebCast hi, i'm new to windows server and i learned a lot from your videos . If I install a dhcp service on another spare server do I need first to join our domain controller?
@@MSFTWebCast Since, there are two DHCP servers involve in fail-over only one server can mention in router. If that server fail-over to other server there can be a issue, isn't it?
Follow this video: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-eTzHH8CQX_8.html and ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-xOyS1gZ0Lrg.html
@@MSFTWebCast Say I forget to add load balance, in a rush, or just forget. Can the setup let the admin know hey you forget to set up load balance for this scope. Or if for some reason you did set up load balance but it's not syncing for what ever reason. I really would not know unless I had manually check.
See DHCP fail-over feature is optional, its up-to us whether we want to enable or not. 1. When you create DHCP scope, it wont show you anything about DHCP fail-over feature. If you want, you need to manually start the process to configure DHCP fail-over on specific DHCP scope. 2. While configuring fail-over, if you dont select the partner DHCP server, the wizard wont allow you to click next. 3. If DHCP server is not syncing with partner DHCP then you can manually force DHCP server for sync using "Replicate Scope" and "Replicate Relationship" option on DHCP scope. (Time stamp 9:04 in the video) If anything else, let me know.
There is no DNS failover, but if you are using the DNS with Domain Controller then all domain controllers from your domain have the same DNS data copy and they also replicate with each other. To balance DNS request load, you can also setup a secondary DNS server with read-only copy of dns zone files.
You need to configure vlans on your router. Like creating sub-interface on cisco router with dot1q encapsulation. For multiple vlans, you can create separate scopes on DHCP server (with different subnet mask). Note: If you create multiple sub-interface on router then you also need to configure DHCP relay agent (IP helper address) on router.
assalomualaykum again me:) Mrs If my client didnt take dhcp what can i do? I follow this video but my client Win 7 didnt take.I checked ping it worked. Please if you know smth tell me!!!
You mean client is not getting IP address from DHCP? In that case, 1) Check DHCP server and DHCP client are connected to the same Local lan, 2) Make sure that DHCP scope is active and 3) for advance troubleshooting you can install Wireshark Packet Capturing tool and monitor the DHCP (DORA) packets.
