Windows 2016 dns not updating from dhcp

1a) Even if these are enabled, you might need to make sure the DHCP server has permissions to update DNS records.

If your DHCP server is also a domain controller, then you are probably fine, if not, then you may want to see if the DHCP server is a member of the "Dns Update Proxy" group in AD.

windows 2016 dns not updating from dhcp-12windows 2016 dns not updating from dhcp-51windows 2016 dns not updating from dhcp-60

PTR record registration for IPv4 address [192.168.1.50] and FQDN net failed with error 9004 (ENS request not supported by name server).

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years.

the screen shot you shown is for standard primary zone on master dns server, the zone is not AD integrated because it is not as DC Hence if you are worried of this dns server of not updating records, it won't update automatically DNS records only can be updated (automatically) on AD DNS server with zones having dynamic update enabled scavenging need to be enabled on AD DNS server and not on master dns server, if it is enabled on AD DNS server, your AD DNS server should keep DNS up to date My ultimate goal here is to have my DHCP server register DNS names for DHCP clients -- for example my Wireless access point gets IP Address from DHCP Server and then DHCP registers them in DNS -- not AD DNS just regular DNS Are you saying DHCP can only register AD DNS automatically? I have a DHCP Scope for a subnet with specific scope options that include: DNS Servers and DNS Domain name (ie. A client requests IP Address DHCP registers that new devices DNS name in the zone but in the subdomain test since that was defined in the DNS Domain name scope options.

Then FQDN would be something like The real thing I'm trying to accomplish is this: Right now I have a subnet / scope for Wireless access points who use DHCP for IP Addressing -- I'd like them to get an address and then DHCP register their DNS name so they can be accessed like: ap01The Wireless AP gets a DHCP lease -- I see it as ap01but nothing is automatically updating on the DNS side.

However, the reverse DNS entries ("PTR" Records) are not.

The reverse lookup zone exists, and I can add entries to it manually, but it doesn't automatically populate.

I'm afraid that you're going to have to approach this from the client end.

Changing the timeouts is only going to help clients the next time they check in, which is usually after half the existing lease time, or sometimes during boot.

Also make sure your DNS server are listed on the Name Servers tab. Ok so given that your DHCP server is not registering the records on behalf of the clients, and aside from your windows clients not being set to register with DNS on their NICs (which you should verify in TCP/IP properties on the client NIC), I would check the security settings on your reverse zone to make sure clients are allowed to register in the reverse zone.

This article covers the default security settings for DNS zones: the settings are jacked up (or even if they are fine), you might try just blowing away the reverse zone and recreating it since you basically have a non-functioning reverse zone as it is...

Then check the Security tab on the Reverse Zone and make sure that group is authorized to create all child objects (DNS records) 2) If your statically-configured hosts are not updating the reverse zone, make sure their NICs are configured to register their IP in DNS (Windows hosts are enabled for this by default).

Tags: , ,