(Msg. 1) Posted: Tue Jan 22, 2008 5:53 pm
Post subject: DNS Archived from groups: microsoft>public>win2000>dns (more info?)
Hello, I have several DC's (Win2003 Sp1 R2) which are virtual servers. We
have seen that a lot of host records (A) are not being deleted automatically
and reverse lookup records not at all. Then we have several host associated
with the same IP address. We have just enabled the scavenge process on the
reverse lookup zones with a "refresh interval" of 7 days. So if I understand
how everything works, every host records (RR) that have a timestamp of more
than 7 days will be automatically deleted, right ? (except records that were
manually added ). My problem is that I have forced a scavenging on my AD
integrated zone but nothing happens. I can see that the record has an old
timestamp (sometimes from 2004-2006 !) but it remains in my DNS. Do you have
any idea why these records are not deleting ?
(Msg. 2) Posted: Wed Jan 23, 2008 12:27 am
Post subject: Re: DNS [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
In news:A64B7FB3-8CA4-4AF1-AEA7-5F3B82FBFC1F@microsoft.com,
Dmain Help <DmainHelp.TakeThisOut@discussions.microsoft.com> typed:
> Hello, I have several DC's (Win2003 Sp1 R2) which are virtual
> servers. We have seen that a lot of host records (A) are not being
> deleted automatically and reverse lookup records not at all. Then we
> have several host associated with the same IP address. We have just
> enabled the scavenge process on the reverse lookup zones with a
> "refresh interval" of 7 days. So if I understand how everything
> works, every host records (RR) that have a timestamp of more than 7
> days will be automatically deleted, right ? (except records that were
> manually added ). My problem is that I have forced a scavenging on my
> AD integrated zone but nothing happens. I can see that the record has
> an old timestamp (sometimes from 2004-2006 !) but it remains in my
> DNS. Do you have any idea why these records are not deleting ?
If DHCP is installed on a DC, I can understand this happening. I would read
thru this link for a full understanding of the registration process, as well
as concerning DHCP on a DC and how to configure it by putting it in the
DNSUpdateProxy group so it is able to update current hostnames with their
new IPs.
All times are: Eastern Time (US & Canada) (change)
Page 1 of 1
You can post new topics in this forum You can reply to topics in this forum You can edit your posts in this forum You can delete your posts in this forum You can vote in polls in this forum