I have enabled ageing and scavenging on one of our servers. I set the
forward and reverse zones to scavenge with 15 days no refresh and 15 days
refresh. I set the server to scavenge with 15 days no refresh and 15 days
refresh. I checked the box on the server properties advanced tab to start
scavenging and do it every 7 days. The date on the zone for eligible to be
scavenged was today at 3am. When I came in this morning the date is now 4/15
but it doesn't appear that anything was deleted. I do not have any messages
in the event log related to DNS. DNS is AD integrated. What am I missing
here?

"KG" <KG@discussions.microsoft.com> wrote in message
news:A59A4C56-F7B9-4C0F-967C-2CB10D6A6CD3@microsoft.com...
>I have enabled ageing and scavenging on one of our servers. I set the
> forward and reverse zones to scavenge with 15 days no refresh and 15 days
> refresh. I set the server to scavenge with 15 days no refresh and 15 days
> refresh. I checked the box on the server properties advanced tab to start
> scavenging and do it every 7 days. The date on the zone for eligible to
> be
> scavenged was today at 3am. When I came in this morning the date is now
> 4/15
> but it doesn't appear that anything was deleted. I do not have any
> messages
> in the event log related to DNS. DNS is AD integrated. What am I missing
> here?

With 15 + 15 (norefresh + refresh) or 30 days on the zone/records you
shouldn't
see anything leave for at least a month. Then it will be another 0-15 days
before
the Server runs the scavenger.

By any chance does the scavenging interval need to be less than the number of
days between reboots? Our DNS server reboots every 7 days. Our scavenging
interval is also 7 days. The date the zone can be scavenged gets changed
when the server reboots. Then a day or two later DNS scavenging should run
but nothing happens. I don't even get a message saying that it ran but
didn't do anything. I have tested this on our lab network and when I set the
scavenging interval to less than the reboot interval it seems to work. When
I make the 2 the same scavenging doesn't seem to take place.

TIA

"Herb Martin" wrote:

>
> "KG" <KG@discussions.microsoft.com> wrote in message
> news:A59A4C56-F7B9-4C0F-967C-2CB10D6A6CD3@microsoft.com...
> >I have enabled ageing and scavenging on one of our servers. I set the
> > forward and reverse zones to scavenge with 15 days no refresh and 15 days
> > refresh. I set the server to scavenge with 15 days no refresh and 15 days
> > refresh. I checked the box on the server properties advanced tab to start
> > scavenging and do it every 7 days. The date on the zone for eligible to
> > be
> > scavenged was today at 3am. When I came in this morning the date is now
> > 4/15
> > but it doesn't appear that anything was deleted. I do not have any
> > messages
> > in the event log related to DNS. DNS is AD integrated. What am I missing
> > here?
>
> With 15 + 15 (norefresh + refresh) or 30 days on the zone/records you
> shouldn't
> see anything leave for at least a month. Then it will be another 0-15 days
> before
> the Server runs the scavenger.
>
>
>

"KG" <KG@discussions.microsoft.com> wrote in message
news:0EA532C8-AB09-412E-B24A-6B8DFEB339AA@microsoft.com...
> By any chance does the scavenging interval need to be less than the number
> of
> days between reboots?

No.

> Our DNS server reboots every 7 days.

But why? There is an old admins tale that this is somehow needed but
healthy machines do NOT require it.

> Our scavenging
> interval is also 7 days. The date the zone can be scavenged gets changed
> when the server reboots. Then a day or two later DNS scavenging should
> run
> but nothing happens. I don't even get a message saying that it ran but
> didn't do anything. I have tested this on our lab network and when I set
> the
> scavenging interval to less than the reboot interval it seems to work.
> When
> I make the 2 the same scavenging doesn't seem to take place.

There is nothing (particularly) wrong with reducing the Scavening Period,
it is reducing the Refresh and NoRefresh intervals that gets people in
trouble.

> TIA
>
> "Herb Martin" wrote:
>
>>
>> "KG" <KG@discussions.microsoft.com> wrote in message
>> news:A59A4C56-F7B9-4C0F-967C-2CB10D6A6CD3@microsoft.com...
>> >I have enabled ageing and scavenging on one of our servers. I set the
>> > forward and reverse zones to scavenge with 15 days no refresh and 15
>> > days
>> > refresh. I set the server to scavenge with 15 days no refresh and 15
>> > days
>> > refresh. I checked the box on the server properties advanced tab to
>> > start
>> > scavenging and do it every 7 days. The date on the zone for eligible
>> > to
>> > be
>> > scavenged was today at 3am. When I came in this morning the date is
>> > now
>> > 4/15
>> > but it doesn't appear that anything was deleted. I do not have any
>> > messages
>> > in the event log related to DNS. DNS is AD integrated. What am I
>> > missing
>> > here?
>>
>> With 15 + 15 (norefresh + refresh) or 30 days on the zone/records you
>> shouldn't
>> see anything leave for at least a month. Then it will be another 0-15
>> days
>> before
>> the Server runs the scavenger.
>>
>>
>>

Ok. I changed the scavenge frequency to 3 days and now it scavenged both
zones. However, it appears to have only scavenged one zone properly and did
almost nothing to the second zone. The date for this zone can be scavenged
after is now 5/10/2008. What sets this date? Am I correct in understanding
that if this date is beyond the date scavenging runs that nothing will be
scavenged in that zone?

"Herb Martin" wrote:

>
> "KG" <KG@discussions.microsoft.com> wrote in message
> news:0EA532C8-AB09-412E-B24A-6B8DFEB339AA@microsoft.com...
> > By any chance does the scavenging interval need to be less than the number
> > of
> > days between reboots?
>
> No.
>
> > Our DNS server reboots every 7 days.
>
> But why? There is an old admins tale that this is somehow needed but
> healthy machines do NOT require it.
>
> > Our scavenging
> > interval is also 7 days. The date the zone can be scavenged gets changed
> > when the server reboots. Then a day or two later DNS scavenging should
> > run
> > but nothing happens. I don't even get a message saying that it ran but
> > didn't do anything. I have tested this on our lab network and when I set
> > the
> > scavenging interval to less than the reboot interval it seems to work.
> > When
> > I make the 2 the same scavenging doesn't seem to take place.
>
> There is nothing (particularly) wrong with reducing the Scavening Period,
> it is reducing the Refresh and NoRefresh intervals that gets people in
> trouble.
>
> > TIA
> >
> > "Herb Martin" wrote:
> >
> >>
> >> "KG" <KG@discussions.microsoft.com> wrote in message
> >> news:A59A4C56-F7B9-4C0F-967C-2CB10D6A6CD3@microsoft.com...
> >> >I have enabled ageing and scavenging on one of our servers. I set the
> >> > forward and reverse zones to scavenge with 15 days no refresh and 15
> >> > days
> >> > refresh. I set the server to scavenge with 15 days no refresh and 15
> >> > days
> >> > refresh. I checked the box on the server properties advanced tab to
> >> > start
> >> > scavenging and do it every 7 days. The date on the zone for eligible
> >> > to
> >> > be
> >> > scavenged was today at 3am. When I came in this morning the date is
> >> > now
> >> > 4/15
> >> > but it doesn't appear that anything was deleted. I do not have any
> >> > messages
> >> > in the event log related to DNS. DNS is AD integrated. What am I
> >> > missing
> >> > here?
> >>
> >> With 15 + 15 (norefresh + refresh) or 30 days on the zone/records you
> >> shouldn't
> >> see anything leave for at least a month. Then it will be another 0-15
> >> days
> >> before
> >> the Server runs the scavenger.
> >>
> >>
> >>
>
>
>

I didn't answer your other questions.

We reboot once a week because in the past it was found that servers tend to
encounter fewer issues when they are rebooted weekly. Not going to justify
it that's just the way it is. Old admin's tales tend to die hard if at all.

It does seem to make a difference if the time between scavenging runs is
less than the reboot schedule. In the testing I have done scavenging will
run if the period is less than the number of days between reboots. I think
it has something to do with when the zone gets reloaded which may occur when
the server reboots.

Thanks for your .

"Herb Martin" wrote:

>
> "KG" <KG@discussions.microsoft.com> wrote in message
> news:0EA532C8-AB09-412E-B24A-6B8DFEB339AA@microsoft.com...
> > By any chance does the scavenging interval need to be less than the number
> > of
> > days between reboots?
>
> No.
>
> > Our DNS server reboots every 7 days.
>
> But why? There is an old admins tale that this is somehow needed but
> healthy machines do NOT require it.
>
> > Our scavenging
> > interval is also 7 days. The date the zone can be scavenged gets changed
> > when the server reboots. Then a day or two later DNS scavenging should
> > run
> > but nothing happens. I don't even get a message saying that it ran but
> > didn't do anything. I have tested this on our lab network and when I set
> > the
> > scavenging interval to less than the reboot interval it seems to work.
> > When
> > I make the 2 the same scavenging doesn't seem to take place.
>
> There is nothing (particularly) wrong with reducing the Scavening Period,
> it is reducing the Refresh and NoRefresh intervals that gets people in
> trouble.
>
> > TIA
> >
> > "Herb Martin" wrote:
> >
> >>
> >> "KG" <KG@discussions.microsoft.com> wrote in message
> >> news:A59A4C56-F7B9-4C0F-967C-2CB10D6A6CD3@microsoft.com...
> >> >I have enabled ageing and scavenging on one of our servers. I set the
> >> > forward and reverse zones to scavenge with 15 days no refresh and 15
> >> > days
> >> > refresh. I set the server to scavenge with 15 days no refresh and 15
> >> > days
> >> > refresh. I checked the box on the server properties advanced tab to
> >> > start
> >> > scavenging and do it every 7 days. The date on the zone for eligible
> >> > to
> >> > be
> >> > scavenged was today at 3am. When I came in this morning the date is
> >> > now
> >> > 4/15
> >> > but it doesn't appear that anything was deleted. I do not have any
> >> > messages
> >> > in the event log related to DNS. DNS is AD integrated. What am I
> >> > missing
> >> > here?
> >>
> >> With 15 + 15 (norefresh + refresh) or 30 days on the zone/records you
> >> shouldn't
> >> see anything leave for at least a month. Then it will be another 0-15
> >> days
> >> before
> >> the Server runs the scavenger.
> >>
> >>
> >>
>
>
>

"KG" <KG@discussions.microsoft.com> wrote in message
news:FB987998-0682-43DC-A630-6888C35E6E49@microsoft.com...
> Ok. I changed the scavenge frequency to 3 days and now it scavenged both
> zones. However, it appears to have only scavenged one zone properly and
> did
> almost nothing to the second zone. The date for this zone can be
> scavenged
> after is now 5/10/2008. What sets this date? Am I correct in
> understanding
> that if this date is beyond the date scavenging runs that nothing will be
> scavenged in that zone?

Correct. And each zones Refresh/NoRefresh intervals are separate
from all other zones (although they can be set at the same time.)

> "Herb Martin" wrote:
>
>>
>> "KG" <KG@discussions.microsoft.com> wrote in message
>> news:0EA532C8-AB09-412E-B24A-6B8DFEB339AA@microsoft.com...
>> > By any chance does the scavenging interval need to be less than the
>> > number
>> > of
>> > days between reboots?
>>
>> No.
>>
>> > Our DNS server reboots every 7 days.
>>
>> But why? There is an old admins tale that this is somehow needed but
>> healthy machines do NOT require it.
>>
>> > Our scavenging
>> > interval is also 7 days. The date the zone can be scavenged gets
>> > changed
>> > when the server reboots. Then a day or two later DNS scavenging should
>> > run
>> > but nothing happens. I don't even get a message saying that it ran but
>> > didn't do anything. I have tested this on our lab network and when I
>> > set
>> > the
>> > scavenging interval to less than the reboot interval it seems to work.
>> > When
>> > I make the 2 the same scavenging doesn't seem to take place.
>>
>> There is nothing (particularly) wrong with reducing the Scavening Period,
>> it is reducing the Refresh and NoRefresh intervals that gets people in
>> trouble.
>>
>> > TIA
>> >
>> > "Herb Martin" wrote:
>> >
>> >>
>> >> "KG" <KG@discussions.microsoft.com> wrote in message
>> >> news:A59A4C56-F7B9-4C0F-967C-2CB10D6A6CD3@microsoft.com...
>> >> >I have enabled ageing and scavenging on one of our servers. I set
>> >> >the
>> >> > forward and reverse zones to scavenge with 15 days no refresh and 15
>> >> > days
>> >> > refresh. I set the server to scavenge with 15 days no refresh and
>> >> > 15
>> >> > days
>> >> > refresh. I checked the box on the server properties advanced tab to
>> >> > start
>> >> > scavenging and do it every 7 days. The date on the zone for
>> >> > eligible
>> >> > to
>> >> > be
>> >> > scavenged was today at 3am. When I came in this morning the date is
>> >> > now
>> >> > 4/15
>> >> > but it doesn't appear that anything was deleted. I do not have any
>> >> > messages
>> >> > in the event log related to DNS. DNS is AD integrated. What am I
>> >> > missing
>> >> > here?
>> >>
>> >> With 15 + 15 (norefresh + refresh) or 30 days on the zone/records you
>> >> shouldn't
>> >> see anything leave for at least a month. Then it will be another 0-15
>> >> days
>> >> before
>> >> the Server runs the scavenger.
>> >>
>> >>
>> >>
>>
>>
>>

"KG" <KG@discussions.microsoft.com> wrote in message
news:94363460-9435-4F96-B286-226F5180D629@microsoft.com...
>I didn't answer your other questions.
>
> We reboot once a week because in the past it was found that servers tend
> to
> encounter fewer issues when they are rebooted weekly. Not going to
> justify
> it that's just the way it is. Old admin's tales tend to die hard if at
> all.

Pretty much the reason (i.e., old admin tales).

If you have real reasons, something is WRONG with your servers,
a bad driver or service usually.

> It does seem to make a difference if the time between scavenging runs is
> less than the reboot schedule. In the testing I have done scavenging will
> run if the period is less than the number of days between reboots. I
> think
> it has something to do with when the zone gets reloaded which may occur
> when
> the server reboots.
>
> Thanks for your .
>
> "Herb Martin" wrote:
>
>>
>> "KG" <KG@discussions.microsoft.com> wrote in message
>> news:0EA532C8-AB09-412E-B24A-6B8DFEB339AA@microsoft.com...
>> > By any chance does the scavenging interval need to be less than the
>> > number
>> > of
>> > days between reboots?
>>
>> No.
>>
>> > Our DNS server reboots every 7 days.
>>
>> But why? There is an old admins tale that this is somehow needed but
>> healthy machines do NOT require it.
>>
>> > Our scavenging
>> > interval is also 7 days. The date the zone can be scavenged gets
>> > changed
>> > when the server reboots. Then a day or two later DNS scavenging should
>> > run
>> > but nothing happens. I don't even get a message saying that it ran but
>> > didn't do anything. I have tested this on our lab network and when I
>> > set
>> > the
>> > scavenging interval to less than the reboot interval it seems to work.
>> > When
>> > I make the 2 the same scavenging doesn't seem to take place.
>>
>> There is nothing (particularly) wrong with reducing the Scavening Period,
>> it is reducing the Refresh and NoRefresh intervals that gets people in
>> trouble.
>>
>> > TIA
>> >
>> > "Herb Martin" wrote:
>> >
>> >>
>> >> "KG" <KG@discussions.microsoft.com> wrote in message
>> >> news:A59A4C56-F7B9-4C0F-967C-2CB10D6A6CD3@microsoft.com...
>> >> >I have enabled ageing and scavenging on one of our servers. I set
>> >> >the
>> >> > forward and reverse zones to scavenge with 15 days no refresh and 15
>> >> > days
>> >> > refresh. I set the server to scavenge with 15 days no refresh and
>> >> > 15
>> >> > days
>> >> > refresh. I checked the box on the server properties advanced tab to
>> >> > start
>> >> > scavenging and do it every 7 days. The date on the zone for
>> >> > eligible
>> >> > to
>> >> > be
>> >> > scavenged was today at 3am. When I came in this morning the date is
>> >> > now
>> >> > 4/15
>> >> > but it doesn't appear that anything was deleted. I do not have any
>> >> > messages
>> >> > in the event log related to DNS. DNS is AD integrated. What am I
>> >> > missing
>> >> > here?
>> >>
>> >> With 15 + 15 (norefresh + refresh) or 30 days on the zone/records you
>> >> shouldn't
>> >> see anything leave for at least a month. Then it will be another 0-15
>> >> days
>> >> before
>> >> the Server runs the scavenger.
>> >>
>> >>
>> >>
>>
>>
>>