Delete Static Reverse DNS Entries
We have a number of static entries in our reverse dns zone for PCs. These PCs were upgraded from W2K to XP and now I'm seeing the XP machines in forward and two entries for them in reverse - one static and the other dynamic.
For example in Forward - WXP-Machine1=192.168.1.115
In Reverse - 192.168.1.115 = W2K-Machine 1 (static) and 192.168.1.115=WXP-Machine1
This is AD integrated with DC doing DHCP and DNS. Scavenging is turned on. Under 30 machines total.
Would it work to delete the Reverse DNS zone and then recreate it? Any other suggestions
Thanks
For example in Forward - WXP-Machine1=192.168.1.115
In Reverse - 192.168.1.115 = W2K-Machine 1 (static) and 192.168.1.115=WXP-Machine1
This is AD integrated with DC doing DHCP and DNS. Scavenging is turned on. Under 30 machines total.
Would it work to delete the Reverse DNS zone and then recreate it? Any other suggestions
Thanks
ASKER
Could you please explain a bit more on the scripting approach. I have both 2008 Server and Vista boxes available.
Windows 2008 / Remote Server Admin Tools (Vista) adds a column to the DNS console which allows you to see the record time-stamp. If the record is static it says so.
That means you can simply order by the Time Stamp column then select those and delete the lot if that's what you need.
The scripting approach would only do the same, still want it?
Chris
ASKER
Yes, the timestamp column is showing and those entries I want to remove do show static. In fact, I have deleted them numerous times, but they always come back. Is there some type of ownership or security on them that recreates these entries?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I think these records were carryover from long ago (Windows 2000 server/Windows sbs 2003/Windows sbs 2008). It's time to get them cleaned out.
I'm just surprised they're coming back. That's not really normal behaviour unless the hosts exist on the network, and if they do I'd expect them to come back with time-stamps.
It's possible to delete them via AD rather than DNS, which really gets rid of them, but it shouldn't be necessary.
Chris
ASKER
The W2K hosts no longer exist. The W2K computers are not listed in AD. However, the NICs exists as these PCs were updated to XP and given new names. The W2K systems were not removed from the domain prior to updating. The WXP PCs are getting forward and reverse dynamically. However, the W2K version must have been set up as static somewhere along the line and just won't release. I figure this must be all tied to the NIC MAC. I wonder if I put new NICs in those systems if this problem would clear up?
It would be worth checking DHCP. DNS won't have anything to do with the MAC address.
Chris
ASKER
I checked DHCP and found this - the Scope has the DNS tab set to dynamically update DNS. In SBS 2008, the next level up is either IPv4 or IPv6. DNS can also be set at that level and is not. Would it be advantageous to set it at that level, too. Can it be set at both or is limited to one or the other?
ASKER
Thank you Chris for your help. However, the problem is not solved.
Deleting the zone would certainly work, bit of a sledgehammer approach though. Mind you, the other option involves scripting it (unless you happen to have a 2008 / Vista box available).
Chris