It's a known issue and basically means this timestamp value has not been set. It's equivalent of NULL for timestamps.
--please don't forget to upvote
and Accept as answer
if the reply is helpful--
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi everyone,
I facing one stange issue but i don't know how to overcome it.
I configuring DNS aging and Scaveging, however when configuration windows open, i found one thing abnormal. It show "the zone can be scavenged after 1/1/1601 7:00:00 AM?"
I wordering if i enable this setting, it will delete all my dns records?
Any of you have experience about this issue, please help me one!
Thanks,
Br,
It's a known issue and basically means this timestamp value has not been set. It's equivalent of NULL for timestamps.
--please don't forget to upvote
and Accept as answer
if the reply is helpful--
Hi there,
No, it will not delete your records.
It's an epoch. It's the first year of the 400-year cycle in the Gregorian calendar which we were in when Windows NT was first created.
Essentially it's an arbitrary date chosen as a starting point for calculating a number of different fields which are not stored as dates themselves.
For the value you're looking at, Available for Scavenging Time, it's stored as the number of hours since the epoch. And in your case, the value is 0 (uninitialized).
When it's operational it means the next time your zone can be scavenged. On the first configuration that'll be the current date plus the value of the refresh interval. It's extended by the Automatic Scavenging Interval there-after.
--If the reply is helpful, please Upvote and Accept it as an answer–