Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Discovery fails with error TrustedHosts on MID server host does not include the target host - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Discovery fails with error TrustedHosts on MID server host does not include the target host
KB0747683

Discovery fails with error TrustedHosts on MID server host does not include the target host


3576 Views Last updated : Jul 24, 2025 public Copy Permalink
KB Summary by Now Assist

Issue

Symptoms

During the classification phase, we can see the 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. "

The Input payload will be like the below screenshot, exhibiting the error.

Release

  • All releases (subject to customer's environment)

Cause

The reason for such behaviour is because Reverse DNS is disabled.

If we take an example of the discovery process, here is what happens - The mid server tries to Establish a PowerShell session that is ready to authenticate to the remote host.

  • Check that the WinRM service is listening on the remote host.
  • Get the list of TrustedHosts on a local machine.

1) If the list is retrievable, and the remote host is in the list, then nothing else needs to be done.

2) If list retrieval fails (usually due to "access denied" when SYSTEM account doesn't have permissions to enumerate the list)

  • Check that MID host is on a domain.

1)If true, then attempt to reverse DNS lookup of target IP to get FQDN

2)If the reverse lookup is successful, then set the result as the target host. Nothing else needs to be done.

 

Resolution

The below steps can be followed in order to solve the problem and obtain temporary relief.

IMP Note: The solution below is for providing temporary relief and may become a maintenance overhead if the no of IPs or the FQDNs is high in number.

  1. On the MID server host, navigate to c:\Windows\System32\Drivers\etc\hosts.
  2. Open the hosts file and add the details of the IP and the FQDN so that it acts as a reference that looking up to the reverse DNS. Once you add the details, it looks like the below.
  3. Save the file and perform Discovery.

 

 


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

Attachments

Attachments

  • Pasted image.png
  • Pasted image.png

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.