The "Unable to resolve target system name" error occurs when the tracert (Windows) or traceroute (Linux/macOS) command cannot translate the domain name or hostname into an IP address. This is typically caused by DNS resolution issues, incorrect input, or network problems.

Verify the Domain Name or Hostname

  • Double-check the domain name or hostname for typos or errors.
  • Example:
    • tracert example.com

    instead of:

    tracert exampel.com
  • Ensure that the domain exists and is active by testing it in your web browser.

Test DNS Resolution with nslookup

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

nslookup example.com
  • If nslookup fails: This indicates a DNS issue.
  • If it succeeds: The problem might be specific to tracert.

Use an IP Address Instead of a Domain

To check if the issue is related to DNS, use the IP address directly with tracert:

tracert 93.184.216.34

If this works, the problem is related to DNS resolution.

Flush Your DNS Cache

Clearing your local DNS cache can resolve stale or incorrect DNS entries.

On Windows:

  1. Open Command Prompt as Administrator.
  2. Run:
    3. ipconfig /flushdns

On macOS:

  1. Open Terminal.
  2. Run:
    3. sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

On Linux:

  1. Restart the DNS service:
    2. sudo systemctl restart systemd-resolved

Change Your DNS Server

If the issue persists, switch to a reliable public DNS server.

Use Google Public DNS:

  • Primary: 8.8.8.8
  • Secondary: 8.8.4.4

Change DNS on Windows:

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

Check Network Connectivity

Ensure your device has internet access:

  1. Ping a known IP address (e.g., Google DNS server):
    2. ping 8.8.8.8
  2. If the ping fails, check your network connection.

Disable Firewall or Security Software

Firewalls or security software may block DNS requests. Temporarily disable them to check if they are the cause.

Inspect the hosts File

Your system hosts file may redirect the domain name incorrectly.

Edit the hosts File:

  • Windows: Open C:\Windows\System32\drivers\etc\hosts in a text editor.
  • Linux/macOS: Open /etc/hosts.

Look for an entry like this:

example.com 127.0.0.1

Remove any invalid entries and save the file.

Test from Another Network

Try running tracert from a different network or device to determine if the issue is specific to your system or network.

Contact Your ISP or System Administrator

If none of the above steps work, the issue might be with your ISP DNS servers or network configuration. Contact your ISP or system administrator for assistance.

Example of a Successful Tracert

C:\> tracert example.com

Tracing route to example.com [93.184.216.34]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 5 ms 5 ms 6 ms 203.0.113.1
3 20 ms 21 ms 20 ms 93.184.216.34