Telegram Bot
Tracert Unable to Resolve — How to Verify Hostname or Domain
4 min read
The error "Unable to resolve target system name" in tracert is often caused by an invalid or unreachable hostname or domain name. Here is how to verify and troubleshoot the issue.
For closely related tracert / DNS topics, see Tracert — Unable to Resolve (original), Unable to Resolve Target System Name (sibling), Steps to Resolve, and Unable to Resolve Target System Name Error.
Check the Hostname/Domain Name Format
- Correct Format: Ensure the domain name is in the proper format without prefixes like http:// or https://.
- Example:
tracert example.comtracert http://example.comPing the Domain
Use the ping command to test if the hostname or domain name resolves to an IP address.
ping example.comExpected Output: If the domain resolves, you will see responses with the IP address.
Pinging example.com [93.184.216.34] with 32 bytes of data:
Reply from 93.184.216.34: bytes=32 time=12ms TTL=57If Ping Fails: The hostname cannot be resolved. Proceed with further troubleshooting.
Use nslookup to Check DNS Resolution
Run the nslookup command to check if the domain resolves to an IP address.
nslookup example.comExpected Output:
Server: dns.google
Address: 8.8.8.8
Non-authoritative answer:
Name: example.com
Address: 93.184.216.34If nslookup Fails: The domain name may not exist, or there may be an issue with your DNS server.
Verify the Domain Status
Check if the domain is valid, active, and registered using an online WHOIS lookup tool:
- WHOIS Lookup: https://whois.domaintools.com/
Search for the domain to confirm:
- It is registered and active.
- Its DNS records are properly configured.
Use an Online DNS Checker
Use online DNS tools to verify the domain DNS resolution:
- DNS Checker: https://dnschecker.org/
Enter the domain and check its A record (IPv4 address) globally.
Try with an IP Address
To rule out DNS issues, use an IP address instead of a hostname in the tracert command:
tracert 93.184.216.34If the IP works but the hostname does not, the issue lies with DNS resolution.
Ensure Internet Connectivity
Check if your system has an active internet connection:
- Open a browser and try accessing a known website, such as
https://google.com.
Test with a Different DNS Server
If the issue persists, switch to a public DNS server like Google DNS or Cloudflare DNS.
How to Change DNS on Windows:
- Go to Control Panel > Network and Sharing Center > Change Adapter Settings.
- Right-click your active network connection and choose Properties.
- Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
- Enter the following DNS servers:
- Google DNS: Preferred DNS: 8.8.8.8, Alternate DNS: 8.8.4.4
- Cloudflare DNS: Preferred DNS: 1.1.1.1, Alternate DNS: 1.0.0.1
Common Scenarios and Fixes
| Scenario | Command | Fix |
|---|---|---|
| Typo in the domain name | tracert exapmle.com |
Correct to tracert example.com. |
| DNS resolution issue | ping example.com fails |
Switch to a public DNS server. |
| Domain is expired | nslookup example.com fails |
Verify the domain status in WHOIS. |
| DNS misconfiguration | DNS records are missing | Check and update DNS settings for domain. |
Example Outputs and What They Mean
- Successful Resolution:
- Failure to Resolve:
Pinging example.com [93.184.216.34] with 32 bytes of data:
Reply from 93.184.216.34: bytes=32 time=12ms TTL=57The domain is valid, and DNS is resolving correctly.
Ping request could not find host example.com. Please check the name and try again.Indicates DNS resolution failure. Check your DNS settings or verify the domain existence.
By following these steps, you should be able to resolve the "Unable to resolve target system name" error in tracert.
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