StumpedTechy
MIS
Okay let me give you all the facts up until about 6 months we ran hardcoded PC's across the board. We then got more and more laptops and are finding it easier to now run DHCP. One issue I have is we are running DHCP off a Cicso PIX router and not off the Windows 2003 server (making it so we can't force the DNS deletion when the lease is up). Also important to know is we have a bunch of subnets as each location is on its own vlan (while this does not matter as I will tell you the same problem is happening with the local LAN with the hosting DNS server). Each subnet is listed on its own in the reverse lookup zones.
I just now went into DNS and noticed that our records are not being updated within DNS. We had some records that are in our forward lookup zones that were 3 months old + that have no computername any longer even on the network. In the reverse lookup zones there is more of the same where we have multiple records with the same IP.
This is happening in both forward and reverse lookup zones and is on 2 different DNS servers. Now scavenging was already set for the forward lokup zones for 7 days abut the reverse lookup zone was NOT enabled. We went ahead and enabled it and then I did a forced Scavenge Stale resource records on both servers at the same time.
This did part of what I wanted but did not fix the entire problem. In the forward lookup zones the A records that were stale are now gone (at least the main ones that caused me to notice the problem to begin with). In the reverse lookup zones there are still a TON of duplicates - PTR records for 2 different PC's on the same IP and PTR records for 1 PC on 2 different IP's
Now to sum it up and how to fix this -
1) Why isn't the forward lookup zone scavenging anything more than 7 days out to begin with?
2) Why won't the reverse lookup zones scavenge all of the old stuff now that I have it set to 7 days scavenging?
Note some of these records date back over a year and I know they are stale but they are not being scavenged.
I just now went into DNS and noticed that our records are not being updated within DNS. We had some records that are in our forward lookup zones that were 3 months old + that have no computername any longer even on the network. In the reverse lookup zones there is more of the same where we have multiple records with the same IP.
This is happening in both forward and reverse lookup zones and is on 2 different DNS servers. Now scavenging was already set for the forward lokup zones for 7 days abut the reverse lookup zone was NOT enabled. We went ahead and enabled it and then I did a forced Scavenge Stale resource records on both servers at the same time.
This did part of what I wanted but did not fix the entire problem. In the forward lookup zones the A records that were stale are now gone (at least the main ones that caused me to notice the problem to begin with). In the reverse lookup zones there are still a TON of duplicates - PTR records for 2 different PC's on the same IP and PTR records for 1 PC on 2 different IP's
Now to sum it up and how to fix this -
1) Why isn't the forward lookup zone scavenging anything more than 7 days out to begin with?
2) Why won't the reverse lookup zones scavenge all of the old stuff now that I have it set to 7 days scavenging?
Note some of these records date back over a year and I know they are stale but they are not being scavenged.