[cifs-protocol] 2106010040000444 [MS-DNSP] StartScavenging RPC call

Sreekanth Nadendla srenaden at microsoft.com
Tue Jun 1 03:52:33 UTC 2021


Dochelp in Bcc

Hello Douglas, thank you for your question regarding the MS-DNSP specification. We have created incident 2106010040000444  to track the investigation. One of the open specifications team member will contact you shortly.

Regards,
Sreekanth Nadendla
Microsoft Windows Open Specifications

-----Original Message-----
From: Douglas Bagnall <douglas.bagnall at catalyst.net.nz> 
Sent: Monday, May 31, 2021 10:45 PM
To: Interoperability Documentation Help <dochelp at microsoft.com>; cifs-protocol at lists.samba.org
Subject: [EXTERNAL] [MS-DNSP] StartScavenging RPC call

hi Dochelp,

I would like some clarification of the StartScavenging Operation as mentioned in 3.1.4.1 R_DnssrvOperation (and implied in R_DnssrvOperation2, etc).

The fullest description of the call is:

> If pszOperation is StartScavenging, the server MUST initiate a resource record scavenging cycle on the DNS server, and return success.

While in another place (3.1.1.1.1, discussing ScavengingInterval), it says

> If the value is non-zero and a StartScavenging operation is initiated, the value is ignored and scavenging begins immediately.

The terms I would like clarification on are "resource record scavenging"
and "begins immediately".

Does "resource record scavenging" refer to:

a) turning stale dynamic records into DNS tombstones when aging is enabled for the zone and server.

b) removing tombstoned nodes and records after the appropriate time.

c) both a) and b).

d) something else?


Does "begins immediately" imply a scavengable DNS resource should disappear within a few seconds on an unloaded server with a very small zone? Or does the "resource record scavenging cycle" have aspects that mean this is not expected?

cheers,
Douglas


More information about the cifs-protocol mailing list