To provide a 30,000’ view of what’s involved, we start by creating a regular, non-Administrator, local user account on the server that will be used to configure the DHCP scope to use as credentials for registration. The first thing we need is a Windows Server with the DHCP and DNS services installed and running. Use Windows DHCP to Force Register All Leases Without credentials, the device will update, but it may not be able to update its old record, which then you may wind up with duplicate host entries in the zone. The credentials allows DHCP to own the record, so in case the device leaves and returns at a later date and gets a new IP, the DHCP service can update the old host record in DNS with the new IP. We can do this by using the DHCP service on a non-AD joined Windows Server configured with DHCP credentials, DHCP Option 015, and configured to force all leases to register into the zone whether the device has the ability to register on its own or not. To register your Windows computers and non-Windows devices, an easier way to go about it is to use Windows Server DHCP to register all leases into the DNS zone. However, that will only be good for your Windows computers. One way is to force the Primary DNS Suffix on your Windows workgroup computers by using a registry script (outlined later below). There are actually a number of ways to get this to work. After all, non-Windows devices, such as phones and tables, do not have such a setting to configure. We can make this work without a Primary DNS Suffix. Neither do other devices, such as mobile phones, tablets and other non-Microsoft products. However, workgroup computers normally do not have a Primary DNS Suffix, unless you’ve already manually configured all of them. If you weren’t aware of this basic requirement, you can catch up on how Dynamic DNS registration works by reading my other blog:ĪD & Dynamic DNS Updates Registration Rules of engagement When you join a computer to a domain, one of the many things that occur on the computer is that the Primary DNS Suffix is automatically configured, which matches the name of the AD DNS domain name, which should also be identical to the DNS zone name.Īnd further, as we already know, that’s what a computer needs to register into a zone with the same name. Therefore, that means none of your Windows computers have been configured with a Primary DNS Suffix. So the machines and devices you want to register into DNS are not in an Active Directory. Ace Fekay, MCT, MVP, MCSE 2012/Cloud, MCITP EA, MCTS Windows 2008/R2, Exchange 2007 & 2010, Exchange 2010 Enterprise Administrator, MCSE 2003/2000, MCSA Messaging 2003Īctive Directory, Exchange and Windows Infrastructure Engineer and Janitor
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |