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

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-22-2020 03:29 AM
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
- Labels:
-
Discovery
-
Service Mapping

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-22-2020 06:23 AM
Hi,
what about trusted host list on machine?
Is that server a trusted host?
Thanks,
Ashutosh

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-22-2020 07:00 AM
For WinRM to work, do all windows hosts need to be in a trusted host list on the midserver host? That doesn't sound right!
Thx,
Sanya

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-22-2020 07:27 AM
Hi,
what i know is if that is not then it will try Reverse DNS.
You can try with one Server, add it to trusted host and then test.
Thanks,
Ashtosh