Time values in AD are stored as 64-bit 100msec intervals since Jan 1, 1601. That date looks like time zero + 7 days. I'm guessing that somewhere there a 0 is showing up in the calculation where it shouldn't.
Gil Kirkpatrick CTO, NetPro -----Original Message----- From: Myrick, Todd (NIH/CIT) [mailto:[EMAIL PROTECTED] Sent: Thursday, September 04, 2003 8:24 AM To: '[EMAIL PROTECTED]' Subject: [ActiveDir] DNS Zone Scavaging information We are seeing reports that for the following attribute. The DNS zone becomes available for scavenging at: 1/7/1601 Obviously 1601 is way to much in the past to start a scavenging process. Does anyone know what might cause it to be reported this way. The Date and Time on the Server are up to date. I did see a reference to BIOS needing to be up to date. Any other bright ideas? I have a DNS admin that is chomping at the bit to install SP4. Toddler List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
