Windows dns reverse lookup not updating Online chat adultwork

HI, Seems to be there is an issue with the reverse lookup zone , there are only Names Server type of records available for the servers, execpt that nothing is there no PTR record is there ??Zone is Active Directory Intergrated and Dynamic updates are set to SECURE ONLY.Use the ipconfig /registerdns entry on Server that does not have a PTR record as it should record in the event log success or failure of DNS registration....should also indicate the reasons for failed registration. In DNS right click on the Reverse Lookup Zones Click Add New Zone, this will bring up the New Zone Wizard Select Primary Zone radio Button Click Next Select To all domain controllers in Active directory domain "ABC.com" Click Next IPV4 Reverse Lookup Click Next Select Reverse lookup zone name used the first 3 octets of the ip range I am in ie: 192.168.1 Allow both secure and no secure clicked next FINISH ZONE = 1.168.192.Default zones are in there 0, 127, 255 The solution for this issue is to set the following setting on the ipv4 properties of the client PC's network adapter: 1. If you want more information you may find the following useful: I have recently began using spiceworks to monitor my systems and the report told me I had issues with my reverse DNS entries.

I've stumbled upon a strange behaviour with Windows machines, which seems to be fairly consistent between all Windows versions from Vista/2008 to 8.1/2012 R2; it doesn't happen instead when using Windows XP or Windows Server 2003.

We're a friendly computing community, bustling with knowledgeable members to help solve your tech questions.

Please join our friendly community by clicking the button below - it only takes a few seconds and is totally free.

The problem is this: when the network adapter is configured for DHCP and the DHCP server doesn't register DNS records on behalf of its clients (because it can't, or because it's not configured to do so), then in the TCP/IP settings of the network interface: As much as it may appear strange, this is the only solution to ensure Windows will register both the A and the PTR records for a DHCP network connection; otherwise, it will only register the A record.

I ran into the same issue years ago the following group policy settings are how I resolved it.

Leave a Reply