Dhcp not updating dns forward lookup zone

Rated 4.73/5 based on 690 customer reviews

Creating a forward lookup zone is only necessary when you create a DNS server that is not running on a domain controller or if you need to create a DNS domain that is not part of your Active Directory domain structure.

We have our DNS, DHCP, and AD running on one domain controller.

Running DNS on two 2008 R2 Servers setup as AD integrated for both Forward and all Reverse zones. In DNS the following was set: -Type AD Integrated -Replication All domain controllers in this domain -Dynamic Updates None (why that was like that who knows) -Scavenging is not in use yet I changed Dynamic updating to Secure and Non Secure since I was not sure how it would affect all the non windows servers currently in there.

The DNS suffix name is in there, the DNS and DHCP services are also all started and running on each client.

We also have a couple of subnets within our network.

The two main ones are 10.1.0.0 255.255.0.0 and 10.2.0.0 255.255.0.0 Both network segments have members that are joined to the AD "example.com".

ipconfig /registerdns Regards, Exchange_Geek The IP addresses are leased from DHCP. I cannot run ipconfig /registerdns since the machines in this subnet are Macs.

b) In dhcp IP4 properties: Advanced tab Credentials...

Provide user name, domain and password of an account, which has permissions to update DNS records.

I did however force a renewal of the lease and that works properly.

Also I will mention that the forward lookup zone gets populated just fine, it is just the reverse zone.

Leave a Reply