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

Unable to Resolve Target System Name in Tracert

3 min read
26.09.2025

The error "Unable to resolve target system name" in the tracert (or traceroute on Linux/Mac) command occurs when the system cannot resolve the hostname or domain name provided to its corresponding IP address.

Tracert Unable to Resolve
tracert DNS-fail — verify DNS resolves before tracing path.

For closely related tracert / DNS topics, see Tracert — Unable to Resolve (original), Fix "EAI_NONAME" — Complete DNS Resolution Guide, and SSH ssh_init — Flush DNS Cache.

Possible Causes

Incorrect Hostname or Domain Name

The domain name entered is incorrect or does not exist.

DNS Resolution Issues

The system cannot resolve the hostname to an IP address due to DNS configuration problems.

Network Connectivity Problems

The system cannot connect to the DNS server to resolve the hostname.

Firewall or Security Restrictions

The traceroute command is blocked by firewall rules or network policies.

Expired Domain

The domain name provided may no longer be active or registered.

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

How to Fix the Issue

Verify the Domain or Hostname

  • Ensure the domain or hostname is typed correctly.
  • Example:
  • tracert example.com
  • Incorrect usage:
  • tracert http://example.com
  • Fix: Remove http:// or https://.

Test DNS Resolution

  • Use the ping command to check if the system can resolve the hostname:
  • ping example.com
  • If this also fails, there is likely a DNS issue.

Use an IP Address Instead

  • If the hostname cannot be resolved, use the server IP address directly:
  • tracert 192.168.1.1

Check Your Internet Connection

  • Ensure the system has an active internet connection.
  • Test by accessing a known website like google.com.

Flush DNS Cache

Clear your system DNS cache to resolve possible conflicts.

On Windows:

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

Change DNS Server

If the issue persists, try using a public DNS server like Google DNS or Cloudflare DNS.

  • 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. Go to Control Panel > Network and Sharing Center > Change adapter settings.
  2. Right-click on your active network and select Properties.
  3. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
  4. Enter the public DNS server addresses.

Check the Firewall

  • Ensure your firewall or antivirus software is not blocking tracert.
  • Temporarily disable the firewall to test if it resolves the issue.

Verify Domain Status

  • Use a tool like WHOIS Lookup to check if the domain is still active.

Example Fix Scenarios

  1. Typo in Domain Name:
    • Command: tracert exapmle.com
    • Fix: Correct the spelling to example.com.
  2. DNS Issue:
    • Command: tracert example.com fails.
    • Fix: Switch to Google DNS and try again.
  3. Blocked by Firewall:
    • Command: tracert returns "Unable to resolve".
    • Fix: Temporarily disable the firewall and test.

Testing Tools

  1. DNS Lookup Tools:
    • Use nslookup to manually check DNS resolution:
    • nslookup example.com
  2. Online DNS Tools:
  3. Online Traceroute Tools:
Frequently asked questions
tracert -d skips reverse-DNS lookups for each hop. tracert by IP starts with already-known target IP. Both produce similar output minus hostname labels. Use -d for speed; use IP when target name doesn't resolve at all.
pathping uses different mechanism — sequential pings with reverse-lookup stages. Slower but more diagnostic. If tracert fails immediately and pathping makes progress, the issue might be tracert's specific name-resolution implementation. Rare but happens with certain OS versions.
mtr (Linux/Mac) or WinMTR (Windows). Combines ping and traceroute, shows per-hop loss percentages over time. Far more useful for diagnosing intermittent packet loss. Modern incident response usually uses mtr instead of one-shot tracert.
OS-level DNS cache mismatch. Browser/ping see new value; tracert reads stale. Flush: Windows `ipconfig /flushdns`, Linux `resolvectl flush-caches`, macOS `sudo killall -HUP mDNSResponder`. After flush, retry tracert.
Related articles
Unable to Resolve Target System Name Error
Unable to Resolve Target System Name with Tracert: Steps to Resolve
Tracert: "Unable to Resolve Target System Name"