Telegram Bot
Tracert: "Unable to Resolve Target System Name"
3 min read
The error "tracert unable to resolve target system name" occurs when the tracert (or traceroute on Linux/Mac) command is unable to resolve the hostname or domain name you provided to its corresponding IP address.
For other DNS-resolution and network-diagnostic topics, see Fix "EAI_NONAME" Error — Complete DNS Resolution Guide and Fix EAI_NONAME in FileZilla — DNS Resolution.
Possible Causes
Incorrect Hostname or Domain Name
The hostname or domain name you entered is misspelled or invalid.
DNS Resolution Issues
The system cannot resolve the hostname to an IP address because of a DNS configuration problem.
Network Connectivity Problems
Your computer cannot connect to the internet or to a DNS server.
Expired or Non-Existent Domain
The domain name may have expired or is not registered.
Firewall Restrictions
A firewall may be blocking DNS queries or the tracert command.
Steps to Resolve the Issue
Verify the Hostname or Domain Name
- Double-check the hostname or domain name for typos.
- Example of valid usage:
tracert example.comtracert http://example.com # InvalidTest DNS Resolution
- Use the
pingcommand to check if the hostname resolves to an IP address:
ping example.comping also fails, the issue is likely related to DNS.Use an IP Address Instead
- If the hostname cannot be resolved, try the
tracertcommand with an IP address:
tracert 8.8.8.8Flush DNS Cache
Clear your local DNS cache to resolve potential conflicts.
Windows:
- Open Command Prompt as Administrator.
- Run:
ipconfig /flushdnsMac:
- Open Terminal.
- Run:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderLinux:
- Open Terminal.
- Restart the DNS service:
sudo systemctl restart systemd-resolvedChange DNS Server
If the issue persists, switch to a reliable public DNS server like Google DNS or Cloudflare DNS.
Steps to Change DNS in Windows:
- Go to Control Panel > Network and Sharing Center > Change Adapter Settings.
- Right-click your active network connection and select Properties.
- Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
- Use these DNS server addresses:
- Google DNS: 8.8.8.8 and 8.8.4.4
- Cloudflare DNS: 1.1.1.1 and 1.0.0.1
Check Internet Connectivity
- Ensure your computer is connected to the internet:
- Open a browser and try accessing a website like
https://google.com.
Check Firewall or Antivirus Settings
- Ensure your firewall or antivirus is not blocking the
tracertcommand or DNS traffic.
Verify the Domain Status
- Use an online tool like WHOIS Lookup to check if the domain is active or expired.
Use an Online Traceroute Tool
- If all else fails, use an online traceroute tool to test the domain:
Example Scenarios and Fixes
- Misspelled Domain Name:
- Command:
tracert exapmle.com - Fix: Correct the spelling to
tracert example.com.
- Command:
- DNS Issue:
- Command:
tracert example.comfails. - Fix: Flush DNS cache and switch to Google DNS.
- Command:
- Firewall Blocking Tracert:
- Command: Tracert fails for all domains.
- Fix: Temporarily disable the firewall and try again.
Additional Tools for Troubleshooting
- nslookup:
- Check if the domain resolves to an IP address:
nslookup example.com - dig (Linux/Mac):
- Query DNS servers for the domain:
dig example.com - Check Logs:
- Review system logs for DNS or connectivity errors.
USD - United States Dollar
EUR - Euro
GBP - British Pound
CAD - Canadian Dollar
CHF - Swiss Franc
JPY - Japanese Yen
AUD - Australian Dollar
RUB - Russian Ruble
TRY - Turkish Lira
CNY - Chinese Yuan
INR - Indian Rupee
UAH - Ukrainian Hryvnia