This article applies to FlexNet Manager Suite cloud and on-premises implementations 2019 R2 and later.
With FlexNet Manager Suite 2019 R2, new functionality has been added to FlexNet Beacon 14.0.x and later that can be invoked with the use of the SQL file attached to this article in order to reduce FlexNet Beacon engine’s DNS lookups so that there are limited reads outside a particular FlexNet Beacon’s assigned subnet. As background, FlexNet Beacon executes DNS read calls when a FlexNet inventory agent requests a policy file, and when a discovery rule runs.
There are two settings in the compliance database that control FlexNet Beacon engine’s DNS lookups:
If you wish to use the default values shown above, you can skip the following instructions that allow you to set different values in order to take advantage of reducing Flexnet Beacon engine's DNS lookups.
The following steps need to be executed on the database server.
To reduce FlexNet Beacon engine's DNS lookups:
Oct 21, 2019 07:41 AM
We don't assign subnet to beacons. Do I need to set @scopeToBeaconSubnet = 'True' to make "Reducing FlexNet Beacon engine's DNS Lookups" working?