• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 995
  • Last Modified:

Can anyone tell me what a value in the dwTimeStamp value of DNSCMD output is?

If you execute Microsoft's DNSCMD.EXE and ask for detailed informaiton you will find a value in the information called dwTimeStamp (i.e. dwTimeStamp  = 3554631 ([15: 0: 0] [ 7/ 6/2006]).  I know that the 15:0:0 is 15:0:0 ZULU time but can anyone tell me what th 3554631 means?
0
wchull
Asked:
wchull
  • 6
  • 4
  • 2
  • +2
1 Solution
 
PberSolutions ArchitectCommented:
I believe that is the DNS aging information.
0
 
star_trekCommented:
It is the scavenging time.
0
 
PberSolutions ArchitectCommented:
Further to my previous post...

This value is set on all DDNS records.  It can also be set if you manually age records.  It does not come into play unless you have scavenging turned on in DNS.  This timestamp indicates how old the record is since it was last refreshed and scavenging will remove records tha are older.

this might help:
http://technet2.microsoft.com/WindowsServer/en/Library/20fbbd82-0cea-4a74-9634-fdd993f4c4f41033.mspx?mfr=true
0
Microsoft Certification Exam 74-409

VeeamĀ® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

 
wchullAuthor Commented:
Thanks for the reply but that I know.  What I'm trying to determine is what the 3554631 means in regard to an actual date and/or time the record was registered or when the record is scheduled to be scavenged.
0
 
NJComputerNetworksCommented:
dwTimeStamp
System time at which the input event was generated, in milliseconds. This value wraps around approximately every 50 days. See Remarks
0
 
NJComputerNetworksCommented:
Remarks
The system time returned in dwTimeStamp comes from the same clock used by the Microsoft Win32 GetTickCount or timeGetTime functions, but it produces potentially more precise values. For example, on Microsoft Windows 95, the GetTickCount timer is updated only every 55 milliseconds, but the dwTimeStamp value is accurate to within 1 millisecond. Therefore, if you call GetTickCount and it returns n, and you then receive an event with a timestamp of n + n1, you cannot assume that the event took place exactly n1 milliseconds after the call to GetTickCount.
0
 
PberSolutions ArchitectCommented:
I found the same documentation in MSDN.  I don't think it pertains to this situation $!#@$ M$.

It would seem to be the timestamp the records was last updated

3554631 ([15: 0: 0] [ 7/ 6/2006]).  
3554635 ([19: 0: 0] [ 7/ 6/2006])

It wouls seem to be based on hours as per above. I think we have to look at RFC's for this one.
0
 
wchullAuthor Commented:
OK...

I'm still confused bu Let's see if we can put some of this together.  I know that if I look at he properties of the DNS host record the  Record Time Stamp for this record will show up as 7/6/2006 10:00:00 AM.  The 15:0:0 is the time of day in the Universal Time mode which ignores all daylight savings time but to calculate the correct time for the Central Daylight Time in the US I need to subtract 5 hours (15 - 5) to get the time.  But is the 355361 just a different representation of 7/6/2006 10:00:00 AM?

Here is the reason I want to know....  We have Windows XP machines set to self register themselves in DNS and when they connect to the company via VPN a record is added to DNS.  When the clients disconnect there is nothing to automaticaaly remove the DNS entry so it stays in DNS dispite the fact that VPN issues that same address to another VPN client (whose record was also registered in DNS).  We have scavenging turned on but we can't get rid of the records fast enought so we are trying to run a VBScript around the output of DNSCMD to determine which records are stale based on a newer time stamp on for the same IP address.  In order to get the full dwtimeStamp I have to get the DNS records detail however if I can determine how the 355361 value equates to the date and time in the record I could speed up the proesss by only asking for the type A records which only provides the 355361 value as opposed to the full date and time.
0
 
PberSolutions ArchitectCommented:
We had a similar problem with laptops vpning in and getting dual A records.  We fixed the problem letting DHCP do DNS updates and not the clients themselves.  As soon as the VPN client would drop the VPN concentrator would do a release on the IP and DHCP would clear out the record.  You can configure teh VPN interface on the client to not register DNS and make the DHCP zone update DNS.  
0
 
wchullAuthor Commented:
We may need to try something in that direction but we are attempting to look at a work-around to get us by for a while.  Our problem is that the clents typically have a small DHCP addresss range in their remote offices and this address pool is not shared with VPN.  If the client is not in their office but can connect via VPN then they still register in DNS but in the VPN address range.
0
 
wchullAuthor Commented:
Solution:

From another post on another forum it appers that the 3554631 number in the dwtimestamp is the number of hours from 1/1/1601 at 00:00:00 AM.  I took this information and used it in a VBScript function shown below and it calculated the date to be 7/6/2006 3:00:00 PM and since 3:00:00 PM is really 15:00:00 on the 24 hour clock this matched up with the rest of values ([15: 0: 0] [ 7/ 6/2006]) in the dwtimeStamp.  

DateInterval = 3554631
testdate = DateAdd("h",DateInterval,"1/1/1601 00:00:00 AM")
WScript.Echo testdate

This will help out as to get the dwtimestamp thru the DNSCMD function I was having to use the /detail argument which enumerates a lot more info than needed and I then had to use a bunch of VBScript to parse out the date.  Instead of going to all this trouble I can get the dateinterval by removing the /detail argument so my command string looks like this:

C:>dnscmd.exe c1dcl021 /enumrecords my.domain.com @ /child /type a /continue

With this info I can now create my own scavenging script for DNS that will keep our VPN address ranges down to 1 address.

Thanks for the help.
0
 
PberSolutions ArchitectCommented:
I think wchull did find the solution to the question, thus should be awared the points.
0
 
PberSolutions ArchitectCommented:
Sorry didn't see he was the author.  I'll be quiet now. (:
0
 
DarthModCommented:
PAQed with points refunded (50)

DarthMod
Community Support Moderator
0

Featured Post

Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

  • 6
  • 4
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now