vCenter DNS reverse lookup status is not passed has been observe in Aria Operations version : 8.18.5

Products

• VCF Operations

Issue/Introduction

An alert indicating vCenter DNS reverse lookup status is not passed appears within Aria Operations.
The reverse lookup configuration works correctly at the DNS level; however, Aria Operations flags the condition as failed due to a case-sensitivity mismatch between forward and reverse lookup results.
The customer environment uses upper case hostnames in the VCF configuration, while DNS records remain in lower case, resulting in inconsistencies detected by the reverse lookup verification logic.

 

Environment

Aria Operations version : 8.18.5 (24967118)

Cause

Testing shows that nslookup returns the DNS name in the same case as the query used. When forward lookup is executed using uppercase, the returned DNS name displays in uppercase; when executed in lowercase, the return value is lowercase.
In the JSON output collected by Aria Operations, from 

• /usr/lib/vmware-vcops/user/plugins/inbound/VMwareInfrastructureHealthAdapter/work/Health-results.json

several components return mixed-case hostnames. Some entries appear in uppercase and others in lowercase. Aria Operations DNS reverse lookup checks perform a direct string comparison and treat case differences as mismatches.
When the resolved DNS name casing does not match the expected hostname casing, the check is marked as failed and produces a yellow warning alert.
Because the VCF configuration uses uppercase hostnames and DNS records use lowercase, the case mismatch is expected and cannot be modified on the customer side.

Resolution

As the casing logic for DNS name comparison cannot be modified in the product, customers may exclude the DNS reverse lookup symptom from the alert using Aria Operations policies.

Steps in the Aria Operations UI:

1. Go to Operations → Configurations → Alert Definitions.

2. Search for the alert vCenter app health is affected.

3. Select the three-dot menu and choose Clone.

4. The cloned alert appears as (Copy of) vCenter app health is affected. Rename it as required.

5. Edit the cloned alert and open 2 – Symptoms / Conditions.

6. Remove the symptom vCenter DNS reverse lookup status is not passed by selecting the X beside it.

7. Click Update to save.

Next, update the policy:

1. In the search bar, enter vCenter App [VMware Infrastructure Health].

2. Select the relevant vCenter App object.

3. Select Policy in the upper-right and choose View Policy.

4. Click Edit Policy.

5. Filter for vCenter app health is affected.

6. Deactivate the original alert definition.

7. Activate the cloned and modified alert definition.

This removes the case-sensitive reverse lookup symptom from the health evaluation while retaining other vCenter health-related checks.