nslookup - DNS mess

[wysiwygger]

Hi,

I'm running a Windows Server 2003 Standard in an active directory domain.

If I ping computer1 I receive 192.168.1.10.
Nslookup for computer1 shows me: 192.168.1.10.

Now I do a nslookup for 192.168.1.10 and receive computer2 with 192.168.1.10.

DNS Forward Lookup zone shows computer1 - 192.168.1.10
Reverse Lookup Zone shows 192.168.1.10 - computer2

I was of the opinion the PTR record gets updated automatically if you tick the box "update associated PTR record" is checked in the forward lookup zone?
Does this mean I now have to go through everything and delete old PTR records?

Please help....

 

[ADB100]

It looks like you haven't enabled scavenging on the server or the zones. Dynamic DNS updates are flagged as delete-able when stale, however unless the scavenger is enabled on the server and the zone the old records will remain. From the DNS management console right click the server(s) and select properties, then the advanced tab. There is a checkbox to enable scavenging. You must then also enable scavenging on each zone, there is a quick way to enable it for all zones though - right click the server and you have the option to set aging/scavenging for all zones. You can also initiate a manual scavenge from here as well.
I have been trying to find a best practise guide for what timers to set as I assume you should tie it in with DHCP lease times, I haven't found one yet though. If anyone has one that would be good?

Cheers

Andy

 

[wysiwygger]

Hi,

Thanks for your reply.
this option wasn't set, so I assume this is what caused the confusion.
I also ran a manual scavenge and have only got 11 records out of 50+ left in my reverse lookup zone.
I assume the missing records will be appear again once their lease is expired?