This article covers a behavior change in discovery_server 8.31 and later which affects how the dns_name field is populated in the CM_COMPUTER_SYSTEM table of the UIM database. It also covers a few issues that may arise as a side effect of that and how to work around those problems.
In UIM 8.2 and prior, the discovery_server and agent engaged in specific behavior related to the "dns_name" field in CM_COMPUTER_SYSTEM which has changed in 8.31 and may impact other product areas and integrations.
Specifically, the "old" 8.2 behavior behaved in two ways:
This led to several issues with correlation, where machines were mistakenly correlated based on a dns_name that wasn't really their PrimaryDnsName.
In 8.31, this behavior has changed this way:
The ultimate result of this change is that dns_name will now only be populated with an actual DNS Name, but as a drawback, it may be populated less frequently (e.g. show a NULL value more frequently) than users expect or desire.
Many users may not notice this change, depending on how the environment is configured, but so far we have seen the following impacts:
To mitigate these issues, we have the following options currently available: