Scavenging and Aging

[George Lob]

I have a win2000SP4 DC with a Standard Primary zone for the internal domain.
As soon as I enable Scavenge stale resource records in the Zone
Scavenging/Aging Properties menue, my zone disappears after a few minutes.
No errors in the event logs. Does anyone know why this is happening?

 

[Ace Fekay [MVP]]

In

I have a win2000SP4 DC with a Standard Primary zone for the internal
domain. As soon as I enable Scavenge stale resource records in the
Zone Scavenging/Aging Properties menue, my zone disappears after a
few minutes. No errors in the event logs. Does anyone know why this
is happening?

The zone 'disappears'? Do you mean certain records or your zone that you
have created is no longer in the list under Forward Lookup Zones? And what
does a few minutes mean? Does it re-appear? If it does, are all the records
still there?

Sorry for these questions, but never heard this happening before, unless
someone else has.

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.

 

[George Lob]

The zone that I created is no longer in the list under Forward Lookup Zones.

No longer than 10 minutes, I have not timed it.

No, it does not reappear. The only way to get it back is create a new zone
and just use an existing file.

All the records are there if I do the step above.

"Ace Fekay [MVP]"

 

[Ace Fekay [MVP]]

In

The zone that I created is no longer in the list under Forward Lookup
Zones.

No longer than 10 minutes, I have not timed it.

No, it does not reappear. The only way to get it back is create a new
zone and just use an existing file.

All the records are there if I do the step above.

Sorry, I've never seen this predicament, other than making the zone AD
Integrated on antoher machine, then deleting it on the other machine, then I
can see it deleting it on the first machine.

Maybe someone else has seen this with a single machine environment, as I
assume you have.

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.

 

[George Lob]

I can see that happening if you have it set up as Active Directory
Integrated. I do have a second DNS server set up as Standard Secondary. When
the zone disappears from the Primary, it also disappears from the secondary.
This only happens if, and only if, I activate scavenging, otherwise the zone
works fine.


"Ace Fekay [MVP]"

 

[George Lob]

Is there anything I can look at that may give me an idea as to what is
causing it? There is nothing in the log files.

"Ace Fekay [MVP]"

 

[Ace Fekay [MVP]]

In

Is there anything I can look at that may give me an idea as to what is
causing it? There is nothing in the log files.

If you have two DC/DNS servers, just make the zone AD Integrated. At least
it will be consistent.

Ace

 

[Ace Fekay [MVP]]

In

I can see that happening if you have it set up as Active Directory
Integrated. I do have a second DNS server set up as Standard
Secondary. When the zone disappears from the Primary, it also
disappears from the secondary. This only happens if, and only if, I
activate scavenging, otherwise the zone works fine.

I would make the zone on the first server AD Integrated instead of a
Primary. Any reason you need it to be a Primary and not AD Integrated? It
may have something to do with that. It's easier to use AD Integrated zones,
since the data is in the AD database and replicates based on AD's
replication topology, if they are in the same zone (Win2k) or forest (W2k3).

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.

 

[George Lob]

Ace, my problem, in case anyone has a disappearing zone, was solved with
Ryan White's post on 7/15/2004 which you can see at:

<URL:http://groups.google.com./groups?selm=e6060aa8.0407151753.39bd65d6@po
sting.google.com>

From: (e-mail address removed) (Ryan White)
"Ace Fekay [MVP]"

 

[Ace Fekay [MVP]]

In

Ace, my problem, in case anyone has a disappearing zone, was solved
with Ryan White's post on 7/15/2004 which you can see at:

<URL:http://groups.google.com./groups?selm=e6060aa8.0407151753.39bd65d6@po
sting.google.com>

Glad you found it and thanks for posting that. I believe there was another
post as well about this with a dupe entry in the MSDNS folder, which
actually showed up as a "CNF" entry, which means it was a dupe conflicting
entry, which deleting it took care of it. I can't remember where or who
posted that at this time...

But glad you found it!

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.