Why is Discovery attempting for Reverse DNS when we have set the property WMI is trusted host name source: True

[ngsanya]

We have set the property  WMI is trusted host name source: to True. 

But in the discovery logs for some hosts we are seeing the following error;

TrustedHosts on MID server host does not include the target host, FQDN cannot be determined via reverse DNS lookup, and connecting to target IP address failed.

Doesn't this mean MID Server is trying to do a Reverse DNS lookup? Why is Reverse DNS lookup coming in to picture when WMI is set as trusted host name source?

Thx,
Sanya

[Ashutosh Munot1]

HI,

check this out:

https://hi.service-now.com/kb_view.do?sysparm_article=KB0747683

This explains in details why this happens.

Thanks,
shutosh

[ngsanya]

Thanks Ashutosh, 

I have checked that already. But my question is why is attempting Reverse DNS.

Shouldn't it take name from WMI? Why use Reverse DNS at all.

Hope this question clarifies?

Thx,
Sanya

[Ashutosh Munot1]

Hi,

I would like to first check the WinRM service on the machine where it fails and gives this error. It that is disable then Reverse DNS will be used or else it will use WMI hostname.

Are you on Orlando?

Also ,I think then this has to do with WMI collector which is modified in Orlando and New York.

Thanks,
Ashutosh

[ngsanya]

WinRM port is open and accepting connections.

We are on Newyork.

Thx,
Sanya