# Troubleshoot Unresolved Target Domain Error

{% hint style="danger" %}
**At a Glance**: 🌐 This error in Pynt indicates that the domain name of your API target cannot be resolved, preventing the security scan from running. Use this guide to troubleshoot and resolve domain name resolution issues, ensuring your scans can be completed successfully.
{% endhint %}

***

## Error: The target domain was unresolved

### What Happened?

The host for the test is not reachable from Pynt’s container.

Pynt couldn’t resolve the test target’s domain name to an IP or otherwise couldn’t communicate with the server.

### How to Resolve?

1. **Use "localhost"** instead of IP (e.g., "127.0.0.1") for a server running locally.
2. **Select Correct Environment**: Ensure the correct environment is selected in Postman UI.
3. **Verify Domain Reachability**: Run the test collection in Postman and confirm there are no "DNS Lookup Failed" errors.
4. **Check from Docker**: Run the following commands in a terminal to check if the domain is accessible from the Docker container:

```bash
docker run -it alpine:latest /bin/sh
ping <THE TEST DOMAIN>
```

Ensure no "Name or service not known" error messages are received.

***

{% hint style="info" %}
For additional support, visit [Pynt Community Support](https://www.pynt.io/community).
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.pynt.io/documentation/api-security-testing/pynt-scans-troubleshooting/pynt-for-postman-troubleshooting/troubleshoot-unresolved-target-domain-error.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.