chuchuchu wrote: this concept is sinking in, but taking longer than I would like and not feeling very confident that i know it inside and out. here is my basic understanding, and if anyone can explain it to me i would like that: only used with dynamic updates. aging enabled first at server level, this applies timestamp to dynamic dns record. then no-refresh (if scavenging enabled at server level and zone level) ticks away during this time not allowing updates, after no-refresh the refresh ticks away during which updates are allowed, if auto scavenging is enabled and record not updated it is blasted out of the dns DB. so if host b gets an ip and the computer name changes it can't update it's dns record until after the no-refresh interval has passed?? this seems odd since the default is 7 days? also, the auto scavenge option has a time to run as well, does this countdown start after the expiration of the "refresh" counter or is this just every "x" days? Thanks, Got five weeks until D-Day and I am just trying to iron out any kinks.