Dhcp not updating dns on domain controller
Keep in mind with AD integrated zones the SOA rotates among the DCs because of the multimaster feature. For non-joined machines, it must be manually configured or scripted. If using DHCP Option 015 (Connection Specific Suffix), it must match the zone name and have "Use This Connection’s DNS Suffix in DNS Registration" along with "Register This Connection’s Addresses in DNS" checked in the NIC’s IPv4, Advanced, DNS tab. If the SOA is not available or resolvable, it won’t register.For Windows 2008 and all newer operating systems, IPv6 must not be disabled.If disabled, it will cause other problems: The Cable Guy – Support for IPv6 in Windows Server 2008 R2 and Windows 7, by Joseph Davies, Microsoft, Inc.Now that DHCP services are migrated, I crafted a new domain controller named “DC1” using a Windows Server 2012 R2 image.I had to start with this server because there was already a “DC2” server and I didn’t want to run with a single domain controller.It will not go back to the first one unless you restart the machine, restart the DNS Client service, or set a registry entry to cut the query TTL to 0.The rule is to ONLY use your internal DNS server(s) and configure a forwarder to your ISP’s DNS for efficient Internet resolution.
DHCP Option 006 MUST only be the internal DNS server(s) you want to use, otherwise if using an ISP’s DNS or your router, expect undesired results. The Primary DNS Suffix on the machine MUST match the zone name in DNS. This is default and expected behavior, but if there are any DCs that have any problems, and the client resolved the SOA to that DC, it may not accept the update. The zone in DNS must NOT be a single lable name, such as "DOMAIN" instead of the required minimum of two hierarchal levels such as domain.com, domain.local, domain.me, domain.you, etc.Quoted by Joseph Davies, MSFT: "IPv6 is a mandatory part of the Windows operating system and it is enabled and included in standard Windows service and application testing during the operating system development process.Because Windows was designed specifically with IPv6 present, Microsoft does not perform any testing to determine the effects of disabling IPv6.I use a small /29 subnet to route from the Meraki to the HP (VLAN 99).I constructed a relay to 1.1, which is the internal (southbound) L3 address on my Meraki, to handle DHCP requests from the lab’s VLAN 10 and VLAN 20.