The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Added IPs not working

Discussion in 'General Discussion' started by jeffdilegge, Jan 16, 2013.

  1. jeffdilegge

    jeffdilegge Registered

    Joined:
    Jan 16, 2013
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    Root Administrator
    I have a VPS with godaddy and they are stumped, as am I. I am wondering if they just did not assign the right IPs. Here is what I have, any ideas? I added in WHM when the server was setup.

    root@ip-72-167-247-90 [~]# ifconfig -a
    eth0 Link encap:Ethernet HWaddr 00:18:51:50:6F:BC
    inet addr:72.167.247.90 Bcast:72.167.247.255 Mask:255.255.255.0
    inet6 addr: fe80::218:51ff:fe50:6fbc/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:29990 errors:0 dropped:0 overruns:0 frame:0
    TX packets:3559 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:1716563 (1.6 MiB) TX bytes:1765423 (1.6 MiB)

    eth0:cp1 Link encap:Ethernet HWaddr 00:18:51:50:6F:BC
    inet addr:50.63.179.17 Bcast:50.63.179.255 Mask:255.255.255.0
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

    eth0:cp2 Link encap:Ethernet HWaddr 00:18:51:50:6F:BC
    inet addr:50.63.179.116 Bcast:50.63.179.255 Mask:255.255.255.0
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:697 errors:0 dropped:0 overruns:0 frame:0
    TX packets:697 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:153528 (149.9 KiB) TX bytes:153528 (149.9 KiB)

    venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 -00
    BROADCAST POINTOPOINT NOARP MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
     
  2. jeffdilegge

    jeffdilegge Registered

    Joined:
    Jan 16, 2013
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    Root Administrator
    Any ideas would be greatly appreciated.

    I even had it reprovisioned and new IPs assigned, still the 2 add-on IPs do not work... no ssh, ftp or anything.
     
  3. NixTree

    NixTree Well-Known Member

    Joined:
    Aug 19, 2010
    Messages:
    386
    Likes Received:
    1
    Trophy Points:
    18
    Location:
    Gods Own Country
    cPanel Access Level:
    Root Administrator
    Well...any trace to IP 50.63.179.17 is never reaching godaddy's network; so it must be a network routing issue.

    $ traceroute 50.63.179.17
    traceroute to 50.63.179.17 (50.63.179.17), 30 hops max, 60 byte packets
    1 192.168.1.10 (192.168.1.10) 0.184 ms 0.153 ms 0.159 ms
    2 115.119.78.161.static-hyderabad.vsnl.net.in (115.119.78.161) 0.312 ms 0.310 ms 0.306 ms
    3 115.119.213.177.static-Ernakulam.tcisl.net.in (115.119.213.177) 3.414 ms 3.814 ms 4.097 ms
    4 121.240.2.54 (121.240.2.54) 44.652 ms 43.681 ms 45.334 ms
    5 121.240.2.57 (121.240.2.57) 39.913 ms 40.560 ms 39.266 ms
    6 ix-0-100.tcore1.MLV-Mumbai.as6453.net (180.87.38.5) 41.826 ms 38.773 ms 39.189 ms
    7 if-9-5.tcore1.WYN-Marseille.as6453.net (80.231.217.17) 161.593 ms if-2-2.tcore2.MLV-Mumbai.as6453.net (180.87.38.2) 178.736 ms if-9-5.tcore1.WYN-Marseille.as6453.net (80.231.217.17) 176.446 ms
    8 if-6-2.tcore1.L78-London.as6453.net (80.231.130.5) 163.450 ms 163.772 ms 164.701 ms
    9 Vlan704.icore1.LDN-London.as6453.net (80.231.130.10) 164.013 ms if-9-2.tcore2.L78-London.as6453.net (80.231.200.14) 160.347 ms Vlan704.icore1.LDN-London.as6453.net (80.231.130.10) 160.708 ms
    10 ge-2-1-0.mpr1.lhr2.uk.above.net (195.66.224.76) 157.823 ms 162.899 ms 162.439 ms
    11 ge-7-0-0.mpr1.lhr2.uk.above.net (64.125.28.25) 158.598 ms 159.319 ms Vlan704.icore1.LDN-London.as6453.net (80.231.130.10) 168.921 ms
    12 xe-5-2-0.cr1.dca2.us.above.net (64.125.26.21) 263.858 ms 263.214 ms ge-2-1-0.mpr1.lhr2.uk.above.net (195.66.224.76) 158.322 ms
    13 ge-7-0-0.mpr1.lhr2.uk.above.net (64.125.28.25) 155.977 ms xe-2-2-0.cr1.iah1.us.above.net (64.125.29.37) 265.477 ms ge-7-0-0.mpr1.lhr2.uk.above.net (64.125.28.25) 157.612 ms
    14 xe-0-0-0.cr2.iah1.us.above.net (64.125.30.66) 267.390 ms xe-5-2-0.cr1.dca2.us.above.net (64.125.26.21) 264.408 ms xe-0-0-0.cr2.iah1.us.above.net (64.125.30.66) 269.738 ms
    15 xe-1-1-0.mpr4.phx2.us.above.net (64.125.30.149) 274.619 ms xe-2-2-0.cr1.iah1.us.above.net (64.125.29.37) 261.908 ms 262.259 ms
    16 xe-0-0-0.cr2.iah1.us.above.net (64.125.30.66) 267.239 ms 268.743 ms 209.66.64.6.t01121-04.above.net (209.66.64.6) 266.109 ms
    17 xe-1-1-0.mpr4.phx2.us.above.net (64.125.30.149) 281.356 ms be39.trmc0215-01.ars.mgmt.phx3.gdg (184.168.0.73) 256.958 ms 257.686 ms
    18 209.66.64.6.t01121-04.above.net (209.66.64.6) 281.034 ms be39.trmc0215-01.ars.mgmt.phx3.gdg (184.168.0.73) 258.274 ms 254.928 ms
    19 be39.trmc0215-01.ars.mgmt.phx3.gdg (184.168.0.73) 255.485 ms 258.581 ms *
    20 be39.trmc0215-01.ars.mgmt.phx3.gdg (184.168.0.73) 256.421 ms * 257.875 ms
    21 * * *
    22 * * *
    23 * * *
    24 * * *
    25 * * *
    26 * * *
    27 * * *
    28 * * *
    29 * * *
    30 * * *


    See the traceroute result for your working IP from my end

    $ traceroute 72.167.247.90
    traceroute to 72.167.247.90 (72.167.247.90), 30 hops max, 60 byte packets
    1 192.168.1.10 (192.168.1.10) 0.196 ms 0.151 ms 0.131 ms
    2 115.119.78.161.static-hyderabad.vsnl.net.in (115.119.78.161) 0.295 ms 0.283 ms 0.271 ms
    3 115.119.213.177.static-Ernakulam.tcisl.net.in (115.119.213.177) 2.896 ms 3.256 ms 3.662 ms
    4 121.240.2.54 (121.240.2.54) 51.693 ms 50.963 ms 51.229 ms
    5 121.240.2.57 (121.240.2.57) 39.698 ms 38.836 ms 39.227 ms
    6 ix-0-100.tcore1.MLV-Mumbai.as6453.net (180.87.38.5) 46.947 ms 43.589 ms 38.348 ms
    7 if-9-5.tcore1.WYN-Marseille.as6453.net (80.231.217.17) 159.190 ms 163.574 ms 164.443 ms
    8 if-2-2.tcore2.WYN-Marseille.as6453.net (80.231.217.2) 161.345 ms 158.498 ms 156.630 ms
    9 if-9-2.tcore2.L78-London.as6453.net (80.231.200.14) 158.574 ms 161.707 ms 161.015 ms
    10 * * *
    11 te4-2-10G.ar7.lon3.gblx.net (64.215.195.237) 163.667 ms 164.251 ms 188.784 ms
    12 64.210.13.110 (64.210.13.110) 252.918 ms 253.827 ms 255.483 ms
    13 ip-97-74-253-94.ip.secureserver.net (97.74.253.94) 265.348 ms 265.680 ms 264.108 ms
    14 ip-97-74-253-94.ip.secureserver.net (97.74.253.94) 262.682 ms 266.257 ms 263.020 ms
    15 ip-97-74-253-98.ip.secureserver.net (97.74.253.98) 257.910 ms 261.271 ms 259.119 ms
    16 ip-97-74-254-134.ip.secureserver.net (97.74.254.134) 263.413 ms 257.304 ms 256.116 ms
    17 ip-72-167-247-90.ip.secureserver.net (72.167.247.90) 255.817 ms 255.346 ms 256.282 ms

    So I suggest you to contact Godaddy's support people and ask them whether the IP blocke is correctly routed.
     
Loading...

Share This Page