{"id":8579,"date":"2023-03-15T13:53:09","date_gmt":"2023-03-15T13:53:09","guid":{"rendered":"https:\/\/www.geekdecoder.com\/?p=8579"},"modified":"2023-03-15T13:53:09","modified_gmt":"2023-03-15T13:53:09","slug":"using-traceroute-on-linux-and-tracert-on-windows","status":"publish","type":"post","link":"https:\/\/www.qbytes.cloud\/index.php\/2023\/03\/15\/using-traceroute-on-linux-and-tracert-on-windows\/","title":{"rendered":"Using Traceroute on Linux and Tracert on Windows and Other Great Linux Network Tools"},"content":{"rendered":"\n<p>So, you load you website and the browser just spins. You then do a ping and notice that you have data loss. What&#8217;s up? Let&#8217;s check into the traceroute tool to see how to explain network data loss.<\/p>\n\n\n\n<!--more-->\n\n\n\n<p><strong>What is Traceroute and Tracert?<\/strong><\/p>\n\n\n\n<p><strong>Traceroute<\/strong><\/p>\n\n\n\n<p>In Linux, traceroute is a command-line tool used to trace the path taken by packets from the source computer to a destination server or website on a network. It works by sending packets with varying Time-to-Live (TTL) values to the destination, and as the packets move through each router on the path, the router decrements the TTL value and returns an ICMP &#8220;Time Exceeded&#8221; message when the TTL reaches zero. The traceroute program then displays the IP address and hostname of the router, along with the round-trip time (RTT) for each packet. This information can be used to identify network connectivity issues and troubleshoot network problems.<\/p>\n\n\n\n<p><strong>What is Tracert?<\/strong><\/p>\n\n\n\n<p>Tracert (short for Trace Route) is a command-line tool available in Microsoft Windows operating systems that allows users to track the path taken by an IP packet from its source to its destination. Tracert works by sending a series of packets with increasing &#8220;time to live&#8221; (TTL) values, which are then returned by each subsequent router along the path to their source. This allows the user to identify the route taken by the packet and pinpoint any problems or slowdowns along the way. Tracert can be useful for troubleshooting network issues, identifying network bottlenecks, and diagnosing connectivity problems.<\/p>\n\n\n\n<p><strong>When do you need to use traceroute or tracert?<\/strong><\/p>\n\n\n\n<p>Traceroute (in Linux) and Tracert (in Windows) are both network diagnostic tools that are used to identify the path taken by data packets between your computer and a particular destination. They both use ICMP packets to track the route and display information about each hop along the way, such as the IP address and round-trip time.<\/p>\n\n\n\n<p>You can use Traceroute or Tracert in a variety of situations, such as:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Troubleshooting network connectivity issues: Traceroute and Tracert can be used to identify where data packets are being lost or delayed when trying to connect to a particular website or service.<\/li>\n\n\n\n<li>Analyzing network performance: By looking at the round-trip time for each hop, you can identify which hops are causing latency and potential performance issues.<\/li>\n\n\n\n<li>Identifying potential security threats: Traceroute and Tracert can also be used to identify potential security threats or attackers by analyzing the path and identifying any unexpected or unknown hops<\/li>\n\n\n\n<li>Complete route list. You will see all the routers on the way, with their IP addresses and the time it took. You can better understand the network.<\/li>\n\n\n\n<li>Route timing. See how much time does it take to finish the query. Is it ok for you? What can you do to speed it up? You can have a starting point for improvements.<\/li>\n\n\n\n<li>Check if you can reach a target. See if there is a connection between your device and the hostname or IP address<\/li>\n\n\n\n<li>See problematic slow router. You can see how much time it took in each hop. So you can see a spot that significantly slows your network. You can fix the problem or add more presence in the area.<\/li>\n\n\n\n<li>Run when your site is slow for you but not other people.\n<ul class=\"wp-block-list\">\n<li><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<p>Overall, you can use Traceroute or Tracert whenever you need to diagnose or troubleshoot network connectivity or performance issues.<\/p>\n\n\n\n<p>Let&#8217;s do some checking.<\/p>\n\n\n\n<p>Linux Traceroute<\/p>\n\n\n\n<p>Check to see if Traceroute is installed.<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: java; title: ; notranslate\" title=\"\">\ntraceroute -V\nModern traceroute for Linux, version 2.0.22\nCopyright (c) 2008  Dmitry Butskoy,   License: GPL v2 or any later\n<\/pre><\/div>\n\n\n<p>If you do not see the above, install by running the following:<\/p>\n\n\n\n<p>Ubuntu\/Debian<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\nsudo apt install traceroute\n<\/pre><\/div>\n\n\n<p>or<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\nsudo apt install iputils\n<\/pre><\/div>\n\n\n<p>CentOS\/Rocky<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: java; title: ; notranslate\" title=\"\">\nsudo yum -y install traceroute\n<\/pre><\/div>\n\n\n<p>Or with DNF.<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\nsudo dnf -y install traceroute\n<\/pre><\/div>\n\n\n<p>Using traceroute command<\/p>\n\n\n\n<p>The simple command is as follows:<\/p>\n\n\n\n<p>traceroute DomainName<\/p>\n\n\n\n<p>Like below:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: java; title: ; notranslate\" title=\"\">\ntraceroute google.com\n<\/pre><\/div>\n\n\n<p>Output<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\ntraceroute to google.com (142.250.138.101), 30 hops max, 60 byte packets\n 1  192.168.0.1 (192.168.0.1)  1.657 ms  1.571 ms  1.572 ms\n 2  cpe-70-123-176-1.austin.res.rr.com (70.123.176.1)  15.939 ms  16.191 ms  16.316 ms\n 3  * * *\n 4  lag-19.ausxtxir02r.netops.charter.com (24.93.50.172)  22.514 ms  22.286 ms  22.636 ms\n 5  lag-22.rcr01hstqtx02.netops.charter.com (24.175.41.48)  22.924 ms  22.703 ms *\n 6  * * *\n 7  * * *\n 8  * * *\n 9  * * *\n10  108.170.228.91 (108.170.228.91)  38.762 ms * *\n11  * * *\n12  * * *\n13  142.250.234.115 (142.250.234.115)  44.963 ms * *\n14  * * *\n15  * * *\n16  * * *\n17  * * *\n18  * * *\n19  * * *\n20  * * *\n21  * * *\n22  * * *\n23  rw-in-f101.1e100.net (142.250.138.101)  28.585 ms  39.137 ms  38.768 ms\n<\/pre><\/div>\n\n\n<p>Traceroute will send three packets, but you can change this behavior by using -q option.<\/p>\n\n\n\n<p>For example, let&#8217;s change the number of packets to 5:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\ntraceroute -q 5 google.com\n<\/pre><\/div>\n\n\n<p>Here are the options that you can use.<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: bash; title: ; notranslate\" title=\"\">\nOptions:\n  -4                          Use IPv4\n  -6                          Use IPv6\n  -d  --debug                 Enable socket level debugging\n  -F  --dont-fragment         Do not fragment packets\n  -f first_ttl  --first=first_ttl\n                              Start from the first_ttl hop (instead from 1)\n  -g gate,...  --gateway=gate,...\n                              Route packets through the specified gateway\n                              (maximum 8 for IPv4 and 127 for IPv6)\n  -I  --icmp                  Use ICMP ECHO for tracerouting\n  -T  --tcp                   Use TCP SYN for tracerouting (default port is 80)\n  -i device  --interface=device\n                              Specify a network interface to operate with\n  -m max_ttl  --max-hops=max_ttl\n                              Set the max number of hops (max TTL to be\n                              reached). Default is 30\n  -N squeries  --sim-queries=squeries\n                              Set the number of probes to be tried\n                              simultaneously (default is 16)\n  -n                          Do not resolve IP addresses to their domain names\n  -p port  --port=port        Set the destination port to use. It is either\n                              initial udp port value for &quot;default&quot; method\n                              (incremented by each probe, default is 33434), or\n                              initial seq for &quot;icmp&quot; (incremented as well,\n                              default from 1), or some constant destination\n                              port for other methods (with default of 80 for\n                              &quot;tcp&quot;, 53 for &quot;udp&quot;, etc.)\n  -t tos  --tos=tos           Set the TOS (IPv4 type of service) or TC (IPv6\n                              traffic class) value for outgoing packets\n  -l flow_label  --flowlabel=flow_label\n                              Use specified flow_label for IPv6 packets\n  -w MAX,HERE,NEAR  --wait=MAX,HERE,NEAR\n                              Wait for a probe no more than HERE (default 3)\n                              times longer than a response from the same hop,\n                              or no more than NEAR (default 10) times than some\n                              next hop, or MAX (default 5.0) seconds (float\n                              point values allowed too)\n  -q nqueries  --queries=nqueries\n                              Set the number of probes per each hop. Default is\n                              3\n  -r                          Bypass the normal routing and send directly to a\n                              host on an attached network\n  -s src_addr  --source=src_addr\n                              Use source src_addr for outgoing packets\n  -z sendwait  --sendwait=sendwait\n                              Minimal time interval between probes (default 0).\n                              If the value is more than 10, then it specifies a\n                              number in milliseconds, else it is a number of\n                              seconds (float point values allowed too)\n  -e  --extensions            Show ICMP extensions (if present), including MPLS\n  -A  --as-path-lookups       Perform AS path lookups in routing registries and\n                              print results directly after the corresponding\n                              addresses\n  -M name  --module=name      Use specified module (either builtin or external)\n                              for traceroute operations. Most methods have\n                              their shortcuts (`-I&#039; means `-M icmp&#039; etc.)\n  -O OPTS,...  --options=OPTS,...\n                              Use module-specific option OPTS for the\n                              traceroute module. Several OPTS allowed,\n                              separated by comma. If OPTS is &quot;help&quot;, print info\n                              about available options\n  --sport=num                 Use source port num for outgoing packets. Implies\n                              `-N 1&#039;\n  --fwmark=num                Set firewall mark for outgoing packets\n  -U  --udp                   Use UDP to particular port for tracerouting\n                              (instead of increasing the port per each probe),\n                              default port is 53\n  -UL                         Use UDPLITE for tracerouting (default dest port\n                              is 53)\n  -D  --dccp                  Use DCCP Request for tracerouting (default port\n                              is 33434)\n  -P prot  --protocol=prot    Use raw packet of protocol prot for tracerouting\n  --mtu                       Discover MTU along the path being traced. Implies\n                              `-F -N 1&#039;\n  --back                      Guess the number of hops in the backward path and\n                              print if it differs\n  -V  --version               Print version info and exit\n  --help                      Read this help and exit\n<\/pre><\/div>\n\n\n<p>How to read traceroute<\/p>\n\n\n\n<p>The first line gives us the following info. The destination and its IP address. The number of hops traceroute will try before giving up. The size of the UDP packets we\u2019re sending.<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: java; title: ; notranslate\" title=\"\">\ntraceroute to google.com (142.250.114.102), 30 hops max, 60 byte packets\n<\/pre><\/div>\n\n\n<p><br>All of the other lines contain information about the hops.<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\ncpe-70-123-176-1.austin.res.rr.com (70.123.176.1)  15.939 ms  16.191 ms  16.316 ms\n<\/pre><\/div>\n\n\n<p>The format of each hop line is as follows. The name of the device or the IP address. <\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: java; title: ; notranslate\" title=\"\">\ncpe-70-112-176-1.austin.res.rr.com\n<\/pre><\/div>\n\n\n<p>The IP address.<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\n(70.112.176.1)\n<\/pre><\/div>\n\n\n<p>The time it took round trip for each of the three tests. <\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: java; title: ; notranslate\" title=\"\">\n28.585 ms  39.137 ms  38.768 ms\n<\/pre><\/div>\n\n\n<p>If an asterisk is here, it means there wasn\u2019t a response for that test. <\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\nlag-22.rcr01hstqtx02.netops.charter.com (24.175.41.48)  22.924 ms  22.703 ms *\n<\/pre><\/div>\n\n\n<p>If the device doesn\u2019t respond at all, you\u2019ll see three asterisks, and no device name or IP address.<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\n7  * * *\n<\/pre><\/div>\n\n\n<p>Let&#8217;s dig in for a deep dive<\/p>\n\n\n\n<p>Hop 1: The first hop is the gateway of the Router on the local network. This is how our UDP packets leave the local network and get on the internet.<\/p>\n\n\n\n<p>Hop 2: This is the gateway for the ISP connection.<\/p>\n\n\n\n<p>Hop 3: This device didn\u2019t respond. Perhaps it was configured never to send ICMP packets. Or, perhaps it did respond but was too slow, so&nbsp;<code>traceroute<\/code>&nbsp;timed out. You can check again to see if there is reply.<\/p>\n\n\n\n<p>Hop 4: We get the hostname, IP and all 3 tests are successful<\/p>\n\n\n\n<p>Hop 5: We get the hostname, IP and only 2 tests are successful. This could indicate packet loss.<\/p>\n\n\n\n<p>Hop 6-9: These devices didn\u2019t respond. Perhaps it was configured never to send ICMP packets (Anonymous). Or, perhaps it did respond but was too slow, so&nbsp;<code>traceroute<\/code>&nbsp;timed out. You can check again to see if there is reply.<\/p>\n\n\n\n<p>Hop 10: We get the hostname, IP and only 1 test is successful. This could indicate packet loss.<\/p>\n\n\n\n<p>Hop 11-12: These devices didn\u2019t respond (Anonymous). Perhaps it was configured never to send ICMP packets. Or, perhaps it did respond but was too slow, so&nbsp;<code>traceroute<\/code>&nbsp;timed out. You can check again to see if there is reply.<\/p>\n\n\n\n<p>Hop 13: We get the hostname, IP and only 1 test is successful. This could indicate packet loss.<\/p>\n\n\n\n<p>Hop 14-22: These devices didn\u2019t respond. Perhaps it was configured never to send ICMP packets (Anonymous). Or, perhaps it did respond but was too slow, so&nbsp;<code>traceroute<\/code>&nbsp;timed out. You can check again to see if there is reply.<\/p>\n\n\n\n<p>Hop 23: We reached our destination. <\/p>\n\n\n\n<p>Summary. Mixed signals as we we able to reach the destination in 23 Hops. The time was in 3 results as 28.585 ms 39.137 ms 38.768 ms.<\/p>\n\n\n\n<p><strong>Tracert in Windows<\/strong><\/p>\n\n\n\n<p>To run Tracert in Windows, Hit the Windows key + R and type cmd &#8211; Hit enter.<\/p>\n\n\n\n<p>In the command prompt run the following:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\ntracert google.com\n<\/pre><\/div>\n\n\n<p>Output<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\nC:\\&gt;tracert google.com\n\nTracing route to google.com &#x5B;2607:f8b0:4000:80a::200e]\nover a maximum of 30 hops:\n\n  1     1 ms     1 ms     1 ms  2603-8081-2301-3b54-0000-0000-0000-0001.res6.spectrum.com &#x5B;2603:8081:2301:3b54::1]\n  2    21 ms    13 ms    18 ms  2605:6000:ffc0:8b::1\n  3    11 ms    12 ms    16 ms  lag-63.hcr01rdrktxaz.netops.charter.com &#x5B;2605:6000:0:4::e:3379]\n  4     *        *       13 ms  lag-19.ausutxla01r.netops.charter.com &#x5B;2605:6000:0:4::c:14a]\n  5     *        *        *     Request timed out.\n  6    29 ms    38 ms    29 ms  2001:4860:1:1::2458\n  7    50 ms    31 ms    28 ms  2607:f8b0:8326::1\n  8    28 ms    32 ms    25 ms  2001:4860:0:1::5692\n  9    29 ms    28 ms    30 ms  2001:4860:0:11e3::2\n 10     *       51 ms     *     2001:4860::c:4001:e559\n 11    30 ms    35 ms    29 ms  2001:4860::1:0:c6ea\n 12    29 ms    39 ms    27 ms  2001:4860:0:1::5703\n 13    30 ms    42 ms    30 ms  dfw25s42-in-x0e.1e100.net &#x5B;2607:f8b0:4000:80a::200e]\n<\/pre><\/div>\n\n\n<p>As you can see the Windows Tracert is similar to Linux Traceroute.<\/p>\n\n\n\n<p>The Resutls are printed first with the name of the router listed next<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\n3    11 ms    12 ms    16 ms  lag-63.hcr01rdrktxaz.netops.charter.com\n<\/pre><\/div>\n\n\n<p>As we can see, Traceroute and Tracert are useful tools that can explain network latency. <\/p>\n\n\n\n<p><strong>Other Tools to consider.<\/strong><\/p>\n\n\n\n<p><strong>MTR (Linux and macOS)<\/strong>.<\/p>\n\n\n\n<p>MTR (My traceroute) is a network diagnostic tool used in Linux operating systems. It combines the functionality of the &#8216;traceroute&#8217; and &#8216;ping&#8217; commands to provide a more comprehensive view of the network path between two endpoints. MTR sends packets to the destination host and then reports the statistics of the packets as they traverse each hop in the path.<\/p>\n\n\n\n<p>MTR continuously sends packets to the destination host, making it useful for monitoring network performance over time. It displays information such as the round-trip time (RTT), packet loss, and network hops with details like IP addresses and hostnames. This makes it an effective tool for diagnosing network problems and identifying potential bottlenecks or connectivity issues.<\/p>\n\n\n\n<p>Install Debian\/Ubuntu<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\nsudo apt install mtr -y\n<\/pre><\/div>\n\n\n<p>CentOS\/Rocky<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\nsudo yum install mtr -y\n<\/pre><\/div>\n\n\n<p>Or<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: java; title: ; notranslate\" title=\"\">\nsudo dnf install mtr -y\n<\/pre><\/div>\n\n\n<p>Usage<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: java; title: ; notranslate\" title=\"\">\nmtr domain.com\n<\/pre><\/div>\n\n\n<p>The MTR command is an improved traceroute command that can give more statistics and data for lost packets (percentage).<\/p>\n\n\n\n<p>Dig (Linux and macOS)<\/p>\n\n\n\n<p>&#8216;Dig&#8217; stands for Domain Information Groper. It is a command-line tool in Linux and other Unix-like operating systems used to perform DNS (Domain Name System) lookups. It provides information about DNS records such as A, MX, CNAME, TXT, and NS records, among others.<\/p>\n\n\n\n<p>Install<\/p>\n\n\n\n<p>Install Debian\/Ubuntu<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\nsudo apt install dnsutils -y\n<\/pre><\/div>\n\n\n<p>CentOS\/Rocky<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\nsudo yum install bind-utils -y\n<\/pre><\/div>\n\n\n<p>Or<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\nsudo dnf install bind-utils -y\n<\/pre><\/div>\n\n\n<p>Usage<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\ndig +trace domain.com\n<\/pre><\/div>\n\n\n<p>If you already use the Dig command, you can use it for tracing the route too.<\/p>\n\n\n\n<p><a href=\"https:\/\/sourceforge.net\/projects\/openvisualtrace\/\" target=\"_blank\" rel=\"noreferrer noopener\">Open Visual Traceroute<\/a> (Linux, macOS, and Windows)<br>This one is for people who want a visual interface. <\/p>\n\n\n\n<p><strong>Nmap (Linux, macOS, Windows, BSD, and more).<\/strong><\/p>\n\n\n\n<p>Network Mapper (Nmap) is a free, open-source network security scanning tool. By sending IP packets and analyzing the responses, Nmap can discover information about hosts and services on remote computer networks.<\/p>\n\n\n\n<p>Nmap can also audit the security of a device, identify the vulnerabilities of your network, or perform an inventory check with relative ease.<\/p>\n\n\n\n<p>Install<\/p>\n\n\n\n<p>Install Debian\/Ubuntu<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\nsudo apt install nmap -y\n<\/pre><\/div>\n\n\n<p>CentOS\/Rocky<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\nsudo yum install nmap -y\n<\/pre><\/div>\n\n\n<p>Or<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\nsudo dnf install nmap -y\n<\/pre><\/div>\n\n\n<p>Usage ***Please use this responsibly! Don not scan IP or domains multiple times.<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\nsudo nmap domain.com\n<\/pre><\/div>\n\n\n<p>The results are very similar to the traceroute command. <\/p>\n\n\n\n<p><strong>Tracepath<\/strong><\/p>\n\n\n\n<p>Tracepath is a command-line utility in Linux and other Unix-like operating systems that is used to trace the network path to a destination host. It works by sending packets to the destination host with increasing TTL (time-to-live) values and receiving ICMP (Internet Control Message Protocol) error messages from each hop along the way.<\/p>\n\n\n\n<p>Install<\/p>\n\n\n\n<p>Install Debian\/Ubuntu<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\nsudo apt install iputils-tracepath -y\n<\/pre><\/div>\n\n\n<p>CentOS\/Rocky &#8211; tracepath is part of the traceroute install<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\nsudo yum install traceroute-y\n<\/pre><\/div>\n\n\n<p>Or<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\nsudo dnf install traceroute -y\n<\/pre><\/div>\n\n\n<p>Usage<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\ntracepath domain-name.com\n<\/pre><\/div>\n\n\n<p><strong>The nslookup command<\/strong><\/p>\n\n\n\n<p>When managing connectivity issues, DNS name resolution is often a source of headaches. The nslookup utility helps you check and troubleshoot DNS name resolution.<\/p>\n\n\n\n<p>This command is available with the bind-utils package.<\/p>\n\n\n\n<p>Install<\/p>\n\n\n\n<p>Install Debian\/Ubuntu<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\nsudo apt install dnsutils -y\n<\/pre><\/div>\n\n\n<p>CentOS\/Rocky &#8211; tracepath is part of the traceroute install<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\nsudo yum install bind-utils -y\n<\/pre><\/div>\n\n\n<p>Or<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\nsudo dnf install bind-utils -y\n<\/pre><\/div>\n\n\n<p>Usage<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\nnslookup domain.com\n<\/pre><\/div>\n\n\n<p>I hope you enjoyed this. If you have any questions, let us know via chat.<\/p>\n\n\n\n<div class=\"wp-block-media-text alignwide is-stacked-on-mobile\" style=\"grid-template-columns:15% auto\"><figure class=\"wp-block-media-text__media\"><img loading=\"lazy\" decoding=\"async\" width=\"187\" height=\"249\" src=\"https:\/\/qbytes.cloud\/wp-content\/uploads\/2021\/01\/roger-hat.png\" alt=\"\" class=\"wp-image-5665 size-full\"\/><\/figure><div class=\"wp-block-media-text__content\">\n<p>R. Pringle, AKA &#8220;The Geekdecoder,&#8221; is a 20 year veteran Systems Administrator and the founder of Geekdecoder.com &#8211; a self-help knowledge-base web site for Linux, Web Hosting, Technology and Server Administration.<\/p>\n<\/div><\/div>\n","protected":false},"excerpt":{"rendered":"<p>So, you load you website and the browser just spins. You then do a ping and notice that you have data loss. What&#8217;s up? Let&#8217;s check into the traceroute tool to see how to explain network data loss.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2,116],"tags":[],"class_list":["post-8579","post","type-post","status-publish","format-standard","hentry","category-administration","category-traceroute"],"_links":{"self":[{"href":"https:\/\/www.qbytes.cloud\/index.php\/wp-json\/wp\/v2\/posts\/8579","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.qbytes.cloud\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.qbytes.cloud\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.qbytes.cloud\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.qbytes.cloud\/index.php\/wp-json\/wp\/v2\/comments?post=8579"}],"version-history":[{"count":0,"href":"https:\/\/www.qbytes.cloud\/index.php\/wp-json\/wp\/v2\/posts\/8579\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.qbytes.cloud\/index.php\/wp-json\/wp\/v2\/media?parent=8579"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.qbytes.cloud\/index.php\/wp-json\/wp\/v2\/categories?post=8579"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.qbytes.cloud\/index.php\/wp-json\/wp\/v2\/tags?post=8579"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}