DHCP migration from BIND to Windows Server

Need to migrate DHCP from old BIND box to Windows DC Server 2016.  Anyone can point to the right direction and steps required?
Also, lots of users are on Ubuntu and Macs.  Do they require an additional DHCP client to communicate with Windows DHCP Server or should be good by default?
Thanks in advance!!
LVL 17
Tiras25Asked:
Who is Participating?
 
Joseph HornseyPresident and JanitorCommented:
If you do run into problems with older machines, you can always enable BOOTP on the Windows DHCP server.  You shouldn't have to do that, though.

Migrating DHCP is easy:

1. Recreate the Scope on the new server
2. Shut down the old server
3. Activate the Scope on the new server
4. Have everyone reboot

The authenticated DNS thing refers to whether DNS allows DHCP clients to update their own records.  In other words, when a client gets a new IP, it sends an update to the DNS server so the zone stays fresh.  You can implement this or not; it's up to you.  It's implemented on the WIndows DNS Server app; not DHCP.

Regardless, all clients will still get their DNS settings via DHCP and all clients will be able to resolve DNS.
0
 
Cliff GaliherCommented:
Unless you have a very complex setup, just recreate your Scopes and scope settings.  There is no good way to migrate existing leases, but in a well functioning network, that won't be needed either.

DHCP is an RFC standard and windows doesn't really step outside of it.  No special client required.
0
 
nappy_dThere are a 1000 ways to skin the technology cat.Commented:
DHCP in general will work cross platform regardless of the OS.  

No additional client is required.

HOWEVER, since you have a Windows DC serving as DHCP, you will also have DNS on this box and Active Directory.  Depending on your configuration, you may need unauthenticated dns updates with your non-Windows clients.

There are benefits and disavantages to unauthenticated dns updates on a windows server.  CLICK HERE

That being said, if your Linux and Mac OS client join AD, this should not be an issue.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
Tiras25Author Commented:
Thanks guys.  No, I don't really need ubuntu and macs to join Windows AD.  
Yes, I will have DNS on DC also.  Do I really need an unauthenticated DNS?  DHCP should provide all that data to the client regardless of OS I assume.  Correct?

How would you suggest to failover to Windows DHCP in real life to have it transparent to the users?
0
 
nociSoftware EngineerCommented:
BIND  == DNS
DHCP != BIND...

In windows the default is that all client systems self manage their DNS records..., under AD accounts.
So eitehr you need to find out how DHCP server will update the DNS or you will need to intergrate a lot of systems under AD.
(or use fixed addresses & reservations  + fixed DNS records for those).
0
 
Tiras25Author Commented:
Thanks!  Quick q.  What's the equivalent ipconfig /release /renew for mac and ubuntu OS?
0
 
nociSoftware EngineerCommented:
Most linux systems: ifup eth0 / ifdown eth0 (if the interface is eth0).
on some linux system YMMV though (Gentoo; rc-service net.eth0 restart)

If you are restarting from remote (like ssh into system and then renew use:
nohup bash -c "ifdown eth0 ; ifup eth0"

The nohup should prevent killing the shell by the ifdown

For MAC? it might be ifup/ifdown, i realy have noclue.
0
 
Joseph HornseyPresident and JanitorCommented:
Also, you can just reboot them. :)
0
 
nappy_dThere are a 1000 ways to skin the technology cat.Commented:
On the Mac you would also use the ipconfig command
0
 
Tiras25Author Commented:
Thanks guys.   DNS is actually getting migrated also.  It is part of AD anyways and cannot be deactivated.
Any different route should I take to mograte DHCP and DNS all-together?
0
 
nappy_dThere are a 1000 ways to skin the technology cat.Commented:
If you are moving everything to AD, then there is no other necessary route, just make sure that your servers know the IP address of the AD DNS box(es).

Sometimes, if you do not want AD, DNS and DHCP on the same server, you could place DHCP on a different server other than the DC.
0
 
Tiras25Author Commented:
Thx nappy.   I'm planning DNS on Domain Controllers.  Integrated.  DHCP on DC as well.
0
 
nappy_dThere are a 1000 ways to skin the technology cat.Commented:
With everything being on you DC it should be fairly straight forward of the best practices are followed.
0
 
Tiras25Author Commented:
Doing a cutover to AD DNS and DHCP tonight.  Will let you know how its going.  Thanks!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.