Era Host hosting
EraHost – Free Domain, Cheap Hosting!
Client Area
Support 24/7
Menu

Unable to Resolve Target System Name Error

3 min read
15.08.2025

The error "Unable to resolve target system name" typically occurs when a network command, such as ping, tracert, or other tools, cannot translate the hostname or domain name into an IP address. This issue is related to DNS (Domain Name System) resolution.

Unable to Resolve Target System
Cross-tool DNS fail — unified diagnostic: resolver chain, NXDOMAIN, cache.

For closely related DNS / target-resolution topics, see Tracert — Unable to Resolve (original), Fix "EAI_NONAME" — Complete DNS Resolution, SSH ssh_init: host not found, and Tracert — Verify Hostname.

Common Causes of the Error

1. Incorrect Hostname or Domain Name

The hostname or domain name you entered may be misspelled or invalid.

2. DNS Resolution Issues

Your device cannot communicate with the configured DNS server, or the server itself is down.

3. Nonexistent Domain

The domain name does not exist or has expired.

4. Firewall or Network Restrictions

A firewall or network setting is blocking DNS requests.

5. Local Configuration Issues

Misconfigured or missing entries in the system hosts file.

Linux VDS
High performance for your projects
  • Root access and flexible setup
  • Control panel
  • NVMe disks
  • DDR5
Linux VDS

Steps to Resolve the Issue

Verify the Hostname or Domain Name

  • Double-check for typos or errors in the hostname or domain name.
  • For example, ensure you are using:
  • example.com

    instead of:

    example.cmo
  • Test accessing the domain in your web browser to confirm it resolves properly.

Check DNS Resolution

Use the nslookup command to check if the domain resolves to an IP address:

nslookup example.com
  • If nslookup fails, the issue is likely DNS-related.

Test with a Different DNS Server

Switch to a reliable public DNS server like Google DNS or Cloudflare:

  • Google DNS:
    • Primary: 8.8.8.8
    • Secondary: 8.8.4.4
  • Cloudflare DNS:
    • Primary: 1.1.1.1
    • Secondary: 1.0.0.1

Steps to Change DNS (Windows):

  1. Open Control Panel > Network and Sharing Center > Change adapter settings.
  2. Right-click your active network connection and select Properties.
  3. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
  4. Choose Use the following DNS server addresses:
    • Preferred: 8.8.8.8
    • Alternate: 8.8.4.4

Flush DNS Cache

Clear the local DNS cache to remove any stale entries:

On Windows:

ipconfig /flushdns

On macOS:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

On Linux:

Restart the DNS service:

sudo systemctl restart systemd-resolved

Ping an IP Address

Test network connectivity by pinging a known IP address (e.g., Google DNS server):

ping 8.8.8.8
  • If the ping is successful, your internet connection is working, and the issue is specific to DNS resolution.

Check Local hosts File

Ensure no incorrect entries are present in the hosts file.

Location of hosts File:

  • Windows: C:\Windows\System32\drivers\etc\hosts
  • Linux/macOS: /etc/hosts

Check for entries redirecting the target hostname to an invalid IP.

Verify Network Configuration

Ensure your device is connected to the correct network and has valid network settings:

  • Check your IP configuration:
  • ipconfig (Windows)
    ifconfig (Linux/macOS)

Check for Firewall or Security Software Interference

Disable any firewalls or antivirus software temporarily to ensure they are not blocking DNS requests.

Test from Another Device or Network

  • Use another device or network to test if the issue is specific to your system or network.

Contact Domain Registrar or Hosting Provider

  • If the issue persists, contact the domain registrar to verify the domain status and DNS configuration.
Frequently asked questions
`dig +short @8.8.8.8 example.com` (public DNS bypass). If returns IP, your DNS server is broken; switch resolvers. If also returns nothing, the hostname genuinely doesn't exist (registrar lapse, typo). Public resolver as authoritative test bypasses local issues.
Tool uses different resolver. Browser uses OS resolver; tracert might use a different path. Or browser cached old success while tracert hit fresh failure. Or app has its own DNS library (Go binaries often bypass system resolver). Test with multiple tools using same resolver (`dig @` matches what's actually being used).
If your network blocks outbound 53 (DNS), only the network's specified resolver works. Trying to switch to 1.1.1.1 fails — DNS-over-HTTPS or DNS-over-TLS may work where plain 53 doesn't. Configure DoH/DoT in OS or browser to bypass blocked port 53.
Yes. /etc/resolv.conf nameserver entries are tried in order. If first is dead and timeout is long, slow lookups. Tune timeout: `options timeout:2 attempts:1` reduces wait. Or prune dead resolvers.
Related articles
Unable to Resolve Target System Name in Tracert
Unable to Resolve Target System Name with Tracert: Steps to Resolve
Tracert: "Unable to Resolve Target System Name"