Dns reverse lookup not updating
You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue.The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data.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. The original PDC roles were seized due to major hardware failure, and transferred to what is now the PDC. I only know Novell DNS/DHCP, but do you need to designate an authoratative server for each zone - maybe it's not set correctly for the forward-lookup zones?This test will list MX records for a domain in priority order.
If there are missing entries, you likely have your DHCP missing one of two settings: This is required if you have DHCP installed on a Domain Controller.If you choose to participate, the online survey will be presented to you when you leave the Technet Web site. I have checked everything I can check, and I can find nothing different in the R1 or R2 schools that are and are not working. Some of the servers will not update the Reverse Lookup zones and as you can imagine spiceworks is upset about this.I have both R1 and R2 servers that will and will no update RL Zones, can someone point me in the right direction to try and figure this out?