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.

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.

Steps to Resolve the Issue

1

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.
2

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.
3

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
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
5

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.
6

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.

7

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)
8

Check for Firewall or Security Software Interference

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

9

Test from Another Device or Network

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

Contact Domain Registrar or Hosting Provider

  • If the issue persists, contact the domain registrar to verify the domain status and DNS configuration.