Reverse lookup zone in dns is not updating
To make it possible for DNS clients to perform a reverse lookup for a host, you perform two steps: After you create the zone, you manage it much as you would a forward lookup zone.
Also, like a forward lookup zone, a reverse lookup zone can be integrated with Active Directory Domain Services (AD DS), and it can be mirrored by secondary and stub zones.
The host (A) records for one or more clients contain incorrect IP address, preventing name resolution, when a Windows Server 2003 DHCP (Dynamic Host Configuration Protocol) server is configured to update A records and PTR records in DNS.
This behavior can occur if there is no reverse lookup zone for the IP subnet, or if the reverse lookup zone is not configured to allow dynamic updates.
That's why both backends don't yet cover all the features that you can setup with the Microsoft DNS tools.
If you discover problems or missing features, please open a bug report/feature request at https://bugzilla.samba.org/.
The internal DNS backend currently needs a restart of Samba to take effect.
Complete a brief survey to get a complimentary 70-page whitepaper featuring the best methods and solutions for your virtual environment, as well as hypervisor-specific management advice from Tech Target experts.
Configure it to allow dynamic updates by using the DNS tab of the Scope Properties of DHCP Manager and setting one or both of the following: Dynamically update DNS A and PTR records for DHCP clients that do not request updates.It's not just for resolving IP addresses into names and vice versa.Clients find their Domain Controller/s and other important AD services by DNS queries, this means that your clients must use your Domain Controller/s as their nameservers.If you're running Samba as Active Directory Domain Controller, you also have to administer a DNS server.You will already find general information on the internal DNS and the BIND DLZ module and documentation about Bind as DNS Backend in the Wiki.