There is an option to unselect/disable Reverse DNS lookup but this is only applicable for monitored DHCP nodes and all our nodes have static IP-addresses and not in a domain/DNS, so this does not work for us.
Normally you only want reverse lookup to check if a node has not changed from IP-address when using DHCP.
The discover-offer-request-acknowledge (RFC standard) changed to request-acknowledge (Microsoft Style).
So a Nack from DHCP server will let the client request another IP from DHCP which in its turn might not trigger the options refresh or the Reverse lookup renewal.
Thus reading the option in Solarwinds tells me that I can turn on (Enable) reverse lookup voor DHCP Clients to make sure that the reregistration in the REVERSE lookup has been succesfully changed as well, hence we see the correct node.
All other systems, using static IP addressing, should not suffer from this problem and therefore not be resolved using DNS.
So this is not a feature request but an engineering fault in the software ,but we are advised by Solarwinds engineer to submit this as an Feature Request.
