Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1725
  • Last Modified:

What happens if I delete all of my DNS A and PTR records?

I have a slew of duplicate entries in my DNS on both of my domain controllers. Lots of A records for the same IP address in the forward lookup zone, and lots of PTR records for the same IP address in the reverse lookup zone. It looks like some of the entries have been there as long as the network has been in existence. I have it set up to scavenge records after 7 days, but that doesn't seem to be doing anything.

What happens if I just delete all of the A and PTR records from these zones? Will they regenerate gracefully? Or will I bring my network to a crashing, grinding halt?
0
J-J-White
Asked:
J-J-White
1 Solution
 
LBizzleCommented:
You will bring computer browsing on your network to a grinding halt for the most part. Besides enabling the scaveging which is a good idea (set it to whatever your DHCP lease time is +1 day). Then, do a force scavenge (right click on DNS server in the MCC and scavenge stale resource records, then give it a couple of 4 hours) after that it's a manual process for the most part; there are tools out there but if you sort by IP address and remove any you know are duplicates (beware of aliases purposely using the same IP address, hopefully you or another admin would have created them and know better and USUALLY only applies to servers or web\Intranet addresses).
0
 
Chris DentPowerShell DeveloperCommented:

I disagree about it bringing everything to a grinding halt.

The impact will be low, you will have to ensure that critical servers register immediately after deletion by running "ipconfig /all" and restarting the NetLogon Service on each of your DCs.

The domain will survive quite happily without client records for a few hours / days. Especially PTR records, they're not required for anything at all, they just help things go more smoothly.

The records will regenerate gracefully over a short time. Typically between 24 hours and half of your DHCP lease duration (so 24 hours to 4 days if you use the default DHCP lease of 8 days, and DHCP updates DNS).

That doesn't apply to manually created DNS entries. If you delete one of those you would have to put it back by hand.

> I have it set up to scavenge records after 7 days, but that doesn't seem to be doing anything.

If you've only just done that don't expect it to do it right away. When you first enable Scavenging on a zone (and set the Aging limits) a lock is placed on the zone preventing records from being Scavenged for the duration of a Refresh Interval (7 days by default). This is to give all network clients a chance to update their records before anything is removed.

The MS networking team did a blog on Scavenging which is worth reading, the title is most appropriate :)

http://blogs.technet.com/networking/archive/2008/03/19/don-t-be-afraid-of-dns-scavenging-just-be-patient.aspx

I have some scripts for reporting on the state of records and associated time stamp values in MS DNS if you want to pick through them.

Chris

PS Computer Browsing is a title normally reserved for looking at computers / the network using "My Places Network". Absolutely nothing you do in DNS would effect that, but I suspect the naming is coincidence :)
0
 
J-J-WhiteAuthor Commented:
Thanks for an exceptional answer. :)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now