my-knownhost:manage-services:vps-control:vps-actions:find-node

How do I find which node my VPS is on?

Sometimes, it is useful to be able to find the name of the specific node your VPS is on. For example, you may want to know if any announcements are applicable to your server, or if you need to log into the Console.

Via My Knownhost

The most reliable way to determine which node your VPS is on is by using the My Knownhost client area of our website.

  1. First, you will need to log into the Client Portal Dashboard.
  2. From the Client Portal Dashboard, click "Manage" next to the relevant vps.
  3. At the left, click "Server Actions"
  4. Note the name of the node
  5. The node name is shown in three parts: the type, the number, and the data center. In this example, we have
          ssd28tx
        

    The standard form of the node name has a hyphen between the number and the data center, like this:

          ssd28-tx
        

Via Traceroute

The node name can sometimes be determined from the results of a traceroute run to the VPS. For example, here are example results from a traceroute to a VPS. Remember to run this from your local machine, not from within the VPS, and replace 162.X.X.116 with the IP address of your VPS:1)

[[email protected] ~]$ traceroute 162.X.X.116
traceroute to 162.X.X.116 (162.X.X.116), 30 hops max, 60 byte packets
 1  rrcs-24-73-185-85.se.biz.rr.com (24.73.185.85)  17.688 ms  18.745 ms  21.412 ms
 2  10.201.128.1 (10.201.128.1)  38.177 ms  39.162 ms  38.349 ms
 3  ten7-0-1.bham10-ser1.bhn.net (72.31.207.38)  38.798 ms  38.959 ms  39.536 ms
 4  72-31-207-194.net.bhntampa.com (72.31.207.194)  41.166 ms * ten0-0-0-3.bham01-car1.bhn.net (72.31.206.232)  41.339 ms
 5  72-31-207-144.net.bhntampa.com (72.31.207.144)  41.526 ms  43.054 ms *
 6  66.109.6.220 (66.109.6.220)  53.620 ms  33.067 ms  41.663 ms
 7  0.ae0.pr0.atl20.tbone.rr.com (66.109.6.171)  40.007 ms  41.815 ms  41.782 ms
 8  * * *
 9  * * *
10  COLO4-DALLA.ear1.Dallas1.Level3.net (8.9.232.74)  58.910 ms 4.15.32.134 (4.15.32.134)  59.322 ms COLO4-DALLA.ear1.Dallas1.Level3.net (8.9.232.74)  59.428 ms
11  Jcore4.0.dal.colo4.com (206.123.64.222)  43.110 ms Jcore3.0.dal.colo4.com (206.123.64.234)  42.877 ms Jcore4.0.dal.colo4.com (206.123.64.222)  43.143 ms
12  72.249.129.125 (72.249.129.125)  43.952 ms  51.262 ms  51.159 ms
13  ssd05-tx.privatesystems.net (67.222.0.105)  43.456 ms  51.297 ms  53.838 ms
14  host.XXXXX.net (162.X.X.116)  51.030 ms  41.969 ms  41.750 ms

We are looking for the second to last hop. In this case, the line looks like this:

13  ssd05-tx.privatesystems.net (67.222.0.105)  43.456 ms  51.297 ms  53.838 ms

Notice how between the hop number and the IP address, it gives the name as ssd05-tx.privatesystems.net. The node name itself is ssd05-tx.

1)
Note that if you are using Windows, the command might be tracert instead of traceroute.
my-knownhost/manage-services/vps-control/vps-actions/find-node.txt · Last modified: 2017/11/09 19:27 by Daniel P.