DNS tracking tools help you look up domain information, verify DNS records, and trace the network path between your computer and your website's server. These tools are essential for troubleshooting connectivity issues, verifying DNS propagation, and understanding how data travels across the internet to reach your hosting server.
OBHost provides built-in DNS tracking and network diagnostic tools through your hosting control panel, making it easy to monitor your domain's DNS configuration and network performance without needing external applications.
Understanding DNS Tracking Tools
DNS tracking tools provide critical network information that helps you manage and troubleshoot your website. These utilities allow you to verify that your domain is pointing to the correct server, check DNS record propagation, and identify potential connectivity issues along the network path.
The two primary DNS tracking functions available are Domain Lookup and Trace Route. Domain Lookup retrieves DNS records and server information for any domain, while Trace Route maps the network path between your computer and your server, showing each intermediate server (hop) along the way.
How to Use Domain Lookup
The Domain Lookup tool queries DNS servers to retrieve comprehensive information about a domain, including its IP address, mail server records, and complete zone information. This tool executes a DNS query that returns all publicly available DNS records for the specified domain.
To perform a domain lookup:
- Enter the domain name you want to look up in the text box (for example, example.com)
- Click the Look Up button
- Review the results, which display the domain's mail servers, IP address, and zone information
The zone information section shows detailed DNS records including A records (IP addresses), MX records (mail servers), NS records (nameservers), and other DNS entries associated with the domain. This information is valuable for verifying your DNS configuration and troubleshooting email delivery issues.
How to Use Trace Route
The Trace Route function maps the complete network path from your computer to your web server, showing every intermediate server (called a hop) that your data passes through. Each hop displays timing information that indicates how long it takes for data to reach that point in the network.
To trace the route to your server, simply click the Trace button. The interface will display a sequential list of all network hops, including:
- IP addresses of intermediate servers
- Hostname information for each hop
- Response time for each server along the path
- The total number of hops required to reach your destination
This information is particularly useful for identifying network bottlenecks, slow connections, or routing issues that might affect your website's performance. If you notice consistently high response times at a particular hop, it may indicate a network problem at that location.
Common Uses for DNS Tracking
DNS tracking tools serve multiple important purposes in website management. You can use these tools to verify that your domain's DNS changes have propagated across the internet after updating nameservers or DNS records. This is particularly important after transferring a domain or changing hosting providers.
The tools also help troubleshoot email delivery problems by showing your domain's MX (mail exchange) records. If emails aren't being delivered properly, checking your MX records through Domain Lookup can reveal configuration issues.
Network performance monitoring is another key use case. Running regular trace routes helps you establish baseline performance metrics and identify when network conditions change. Sudden increases in hop count or response times can alert you to potential connectivity issues before they significantly impact your users.
Interpreting DNS Lookup Results
When you perform a domain lookup, the results include several types of DNS records. A records map your domain name to an IP address, which is the actual numerical address of your web server. MX records specify which mail servers handle email for your domain, listed in priority order.
NS (nameserver) records indicate which DNS servers are authoritative for your domain. These should typically point to your hosting provider's nameservers. The zone information section may also include CNAME records (aliases), TXT records (used for verification and email authentication), and other specialized DNS entries.
Understanding these records helps you verify your DNS configuration is correct and identify any discrepancies that might cause website or email issues.
Troubleshooting with Trace Route
Trace route results help pinpoint where network problems occur. If a trace route shows request timeouts at a particular hop, the issue likely exists at that network segment. However, some routers are configured not to respond to trace route requests for security reasons, which may show as timeouts even when the network path is functioning normally.
Response times (measured in milliseconds) indicate network latency. While some variation is normal, consistently high latency or sudden spikes at specific hops suggest potential issues. Geographic distance affects latency, so international routes naturally show higher response times than local connections.
If you cannot complete a trace route to your server, this may indicate a network blockage, firewall restriction, or server connectivity issue that requires further investigation.
What information does Domain Lookup provide?
Domain Lookup provides the IP address associated with a domain, mail server (MX) records, nameserver information, and complete DNS zone data including A records, CNAME records, TXT records, and other DNS entries. This comprehensive information helps you verify DNS configuration and troubleshoot connectivity or email delivery issues.
Why would I need to trace the route to my server?
Tracing the route to your server helps diagnose network performance issues, identify where delays or packet loss occur along the network path, and verify that traffic is routing properly to your hosting server. It's particularly useful when troubleshooting slow website loading times or connectivity problems that might originate from network issues rather than server problems.
How long does DNS propagation take after making changes?
DNS propagation typically takes 24 to 48 hours to complete globally, though changes often become visible much sooner. You can use the Domain Lookup tool to check whether DNS changes have propagated by verifying that the returned records match your new configuration. Keep in mind that different locations worldwide may see changes at different times during the propagation period.
What does it mean if a trace route shows timeouts?
Timeouts in a trace route can indicate either network problems at that hop or simply that the router is configured not to respond to trace route requests for security purposes. If subsequent hops after the timeout still respond successfully, the connection is likely working fine and the timeout is just a security configuration. However, if all hops after a certain point time out, there may be a genuine network connectivity issue that requires investigation.
If you need assistance interpreting DNS tracking results or troubleshooting network issues, the OBHost support team is available 24/7 to help. Visit our contact page or email support@obhost.org for expert technical assistance with DNS and networking questions.
