Windows dns reverse lookup not updating
For more information about Event Viewer, see "Troubleshooting Tools" earlier in this chapter.
Use the following process to verify that your DNS server is started and can answer queries.
KB article 837061 goes over the processing of expired pointer records.
We bumped the queue length up to the maximum to make sure that the DHCP server could do the updates quickly.
If you use a third-party DNS server to support Active Directory, you must perform configuration tasks manually, and doing so, you might cause common configuration errors that prevent DNS and Active Directory from working properly.
We enabled scavenging on one server, then turned that server’s scavenger off for the first step in the process.If you use either the Configure DNS Server wizard or the Active Directory Installation wizard to install your Windows 2000 DNS server, most configuration tasks are performed automatically and you can avoid many common configuration errors, but you might still want to perform the tests in this section.Before checking anything else, check the event log for errors.It would be possible to apply this to all client machines, but you would still need to have the servers refreshing their host and pointer records.The first week that the final changes were applied, the customer’s calls to helpdesk for this issue were down to one per day.The client starts a VPN session and continues working… Lets count: The Ethernet connection from the office has one. The worker calls the helpdesk to get assistance with some application on the machine.Then, their spouse needs to use the computer, so the VPN connection gets dropped. The Wireless connection may have several, depending on how many subnets the worker crossed going to that conference room, and the VPN may have several of them. The help desk tries to connect, but finds that they are hitting someone else’s machine.Machines refresh their host records every 24 hours.Because of that, we really don’t want to lower the scavenging period below 2 days to avoid touching all the machines. Also, DNS time stamps are not updated in Active Directory until you turn on Scavenging on a zone.One of my customers was getting calls like that 8-10-20 times a day. We need to actually manage the address space properly. Before starting anything, we made sure that scavenging was not enabled on ANY of the DNS servers in the environment.It was bad enough that they got orders to ”Fix that problem! Since this is a production network, we had to carefully do this step by step, avoiding any disruption to operations. I sent the customer info on scavenging – which covers the basics.