I usually recommend customers to turn on Query Monitoring (just logging what is queried and what is not queried), but do not enable DNS Scavenging (automatically delete what NIOS determines to be “old” or “stale”). This way, after a period of time, customers can manually review the entries that are flagged as potentially not used or Reclaimable.

For example, turn on Query Monitoring for a month. After a month, review the records that have NOT been queried in the last month. Determine if you want to remove those records (or wait longer than one month).

Enabling query monitoring to keep track of “Last Queried Time”. It builds data to be used later.

It is recommended to enabled query monitoring but n

Tagging (not auto-deleting) will not impact production. All it does is change the “Reclaimable” attribute from No to Yes.

You then use a Smart Folder to view which entries have been tagged as “Reclaimable”.

By default, DNS scavenging in the Infoblox does not delete anything. All it does is set the DB field “reclaimable” from No to Yes for any records meeting the scavenging parameters.

It is possible to set scavenging to “Reclaim” dynamic records that are identified. That is a deletion of those records.

Scavenging will never delete static records. It will only ever mark them as reclaimable. You would then have to find and delete those - a smart folder is the best way to do this.

Scavenging can be run manually against a zone, a view, or the Grid. It can also be scheduled to run on a recurring basis.

And the parameter settings can get pretty sophisticated, because you can nest rules. For example, you could treat static and dynamic records differently when scavenging.

e.g. mark static records that haven’t been queried in a year and mark dynamic records that haven’t been queried in 90 days.

DNS Scavenging in the Infoblox is nothing like the way Microsoft does it, which centers on one parameter - time of last dynamic update.