Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Ping what is wrong with you!?
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Ping what is wrong with you!?

ATHKATHK Member

So I just logged into one of my VPS's to ping another (been experiencing packet loss latley)

ping google.com

PING google.com (74.125.224.38) 56(84) bytes of data. 64 bytes from lax17s01-in-f6.1e100.net (74.125.224.38): icmp_req=1 ttl=57 time=0.406 ms 64 bytes from lax17s01-in-f6.1e100.net (74.125.224.38): icmp_req=2 ttl=57 time=0.396 ms 64 bytes from lax17s01-in-f6.1e100.net (74.125.224.38): icmp_req=3 ttl=57 time=0.350 ms 64 bytes from lax17s01-in-f6.1e100.net (74.125.224.38): icmp_req=4 ttl=57 time=0.687 ms 64 bytes from lax17s01-in-f6.1e100.net (74.125.224.38): icmp_req=5 ttl=57 time=0.389 ms ^C --- google.com ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4004ms rtt min/avg/max/mdev = 0.350/0.445/0.687/0.124 ms

ping lowendtalk.com

PING lowendtalk.com (190.93.243.207) 56(84) bytes of data. 64 bytes from 190.93.243.207: icmp_req=1 ttl=56 time=0.421 ms 64 bytes from 190.93.243.207: icmp_req=2 ttl=56 time=0.409 ms 64 bytes from 190.93.243.207: icmp_req=3 ttl=56 time=0.421 ms ^C --- lowendtalk.com ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 0.409/0.417/0.421/0.005 ms

ping confor.ml Oops forgot about cloud flare being active on this

PING confor.ml (108.162.196.103) 56(84) bytes of data. 64 bytes from 108.162.196.103: icmp_req=2 ttl=56 time=0.359 ms 64 bytes from 108.162.196.103: icmp_req=3 ttl=56 time=0.405 ms 64 bytes from 108.162.196.103: icmp_req=4 ttl=56 time=0.405 ms ^C --- confor.ml ping statistics --- 4 packets transmitted, 3 received, 25% packet loss, time 3001ms rtt min/avg/max/mdev = 0.359/0.389/0.405/0.031 ms

ping direct.confor.ml

PING dc-67e2db4e.confor.ml (198.23.240.167) 56(84) bytes of data. 64 bytes from www.pakoelektrik1.us (198.23.240.167): icmp_req=1 ttl=62 time=0.233 ms 64 bytes from www.pakoelektrik1.us (198.23.240.167): icmp_req=2 ttl=62 time=0.260 ms 64 bytes from www.pakoelektrik1.us (198.23.240.167): icmp_req=3 ttl=62 time=0.168 ms 64 bytes from www.pakoelektrik1.us (198.23.240.167): icmp_req=4 ttl=62 time=0.250 ms 64 bytes from www.pakoelektrik1.us (198.23.240.167): icmp_req=5 ttl=62 time=0.112 ms ^C --- dc-67e2db4e.confor.ml ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4003ms rtt min/avg/max/mdev = 0.112/0.204/0.260/0.058 ms
`

Any ideas? this has never happened before to me atleast.

Comments

  • unless im missing something, there is only 1 packet lost ?

  • What what he's trying to show is the time ;)

  • Sorry I was in a rush, I didn't really explain what I wanted to show..

    For some reason ping is displaying odd and random domain names..

    confor.ml is my domain name and it seems to be resolving to "www.pakoelektrik1.us"

    64 bytes from www.pakoelektrik1.us (198.23.240.167): icmp_req=1 ttl=62 time=0.233 ms

    While on another server it resolves to the correct IP address.

  • nunimnunim Member
    edited October 2013

    What's your hosts file look like? Resolvers? I would say that all domains are resolving to local host so it's a host or nameserver problem.

    Try pinging an IP address.

  • its just the PTR records. ask your provider to change them

  • @cloromorpho

    So pretty much I am just opening a ticket saying those exact words, and they should understand :) ?

  • tell hem to check the PTR or rDNS records of your IP. (i dont know if there is a diference between PTR and rDNS)

  • Here's the response I got.

    Hello,

    I haven't seeing any issues with your IP as its working fine without any issues.Whereas,If you want to set rDNS for your IP then let us know the exact domain name to set.

    FYI:-
    --- {IP REMOVED} ping statistics ---

    2 packets transmitted, 2 received, 0% packet loss, time 1716ms
    rtt min/avg/max/mdev = 386.038/410.637/435.237/24.607 ms

  • Do a traceroute to one of these targets?
    I can think of several possible scenarios of how to achieve this, but all sound strange.
    One would be if you have some strange DNAT rules on your VPS that DNATs all icmp ping packets to localhost for strange reason.
    Another would be if your host is doing this, for some strange reason.

  • @ATHK said:
    Here's the response I got.

    So give them the domain name you want to show up in your PTR record. Usually this is your mail server's hostname because that is where it is most useful.

  • This is stupid.. I've never done this before and it's been fine and dandy..

  • @rds100

    traceroute google.com

    traceroute to google.com (74.125.224.37), 30 hops max, 60 byte packets 1 host.colocrossing.com (198.23.242.2) 0.034 ms 0.011 ms 0.011 ms 2 67.215.251.213.static.quadranet.com (67.215.251.213) 0.525 ms 0.618 ms 0.680 ms 3 colo-lax8 (96.44.180.41) 0.345 ms 0.455 ms 0.513 ms 4 core02 (96.44.180.246) 0.290 ms 0.370 ms 0.426 ms 5 google.com.any2ix.coresite.com (206.223.143.41) 0.523 ms 0.521 ms 0.516 ms 6 64.233.174.41 (64.233.174.41) 0.923 ms 0.383 ms 0.359 ms 7 209.85.252.149 (209.85.252.149) 0.726 ms 1.176 ms 1.150 ms 8 lax17s01-in-f5.1e100.net (74.125.224.37) 0.452 ms 0.432 ms 0.415 ms

    ping google.com

    PING google.com (74.125.224.38) 56(84) bytes of data. 64 bytes from lax17s01-in-f6.1e100.net (74.125.224.38): icmp_req=1 ttl=57 time=0.386 ms 64 bytes from lax17s01-in-f6.1e100.net (74.125.224.38): icmp_req=2 ttl=57 time=0.387 ms ^C --- google.com ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 0.386/0.386/0.387/0.019 ms

  • Ok, google has a cache server pretty close, maybe even in the same datacenter. Could be normal to have such low ping. Do you get such low pings to all IPs you try to ping?

  • rm_rm_ IPv6 Advocate, Veteran

    @rds100 I don't think you read the whole thread before replying. His issue is simply an old rDNS on the last IP, not ping itself.

    Thanked by 1rds100
  • @rds100

    ping lifehacker.com

    'PING lifehacker.com (199.27.77.129) 56(84) bytes of data.
    64 bytes from 199.27.77.129: icmp_req=1 ttl=53 time=9.41 ms
    64 bytes from 199.27.77.129: icmp_req=2 ttl=53 time=9.46 ms
    64 bytes from 199.27.77.129: icmp_req=3 ttl=53 time=9.39 ms
    64 bytes from 199.27.77.129: icmp_req=4 ttl=53 time=9.44 ms
    64 bytes from 199.27.77.129: icmp_req=5 ttl=53 time=9.40 ms
    64 bytes from 199.27.77.129: icmp_req=6 ttl=53 time=9.39 ms
    ^C
    --- lifehacker.com ping statistics ---
    7 packets transmitted, 6 received, 14% packet loss, time 6005ms
    rtt min/avg/max/mdev = 9.395/9.420/9.468/0.083 ms'

    traceroute lifehacker.com

    'traceroute to lifehacker.com (199.27.77.129), 30 hops max, 60 byte packets
    1 host.colocrossing.com (198.23.242.2) 0.032 ms 0.014 ms 0.012 ms
    2 67.215.251.213.static.quadranet.com (67.215.251.213) 0.996 ms 1.070 ms 1.147 ms
    3 colo-lax8 (96.44.180.41) 0.277 ms 0.360 ms 0.357 ms
    4 66.186.197.173 (66.186.197.173) 0.318 ms 0.338 ms 0.396 ms
    5 any2ix.coresite.com (206.223.143.150) 0.261 ms 0.247 ms 0.242 ms
    6 xe-4-2-0.cr1.sjc1.us.nlayer.net (69.22.142.9) 7.982 ms 8.034 ms 7.956 ms
    7 199.27.77.3 (199.27.77.3) 7.917 ms 7.879 ms 7.863 ms
    8 199.27.77.129 (199.27.77.129) 7.847 ms 7.882 ms 9.400 ms'

    ping confor.ml

    'PING confor.ml (198.23.240.167) 56(84) bytes of data.
    64 bytes from www.pakoelektrik1.us (198.23.240.167): icmp_req=1 ttl=62 time=0.218 ms
    64 bytes from www.pakoelektrik1.us (198.23.240.167): icmp_req=2 ttl=62 time=0.193 ms
    64 bytes from www.pakoelektrik1.us (198.23.240.167): icmp_req=3 ttl=62 time=0.201 ms
    64 bytes from www.pakoelektrik1.us (198.23.240.167): icmp_req=4 ttl=62 time=0.133 ms
    ^C
    --- confor.ml ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 3003ms
    rtt min/avg/max/mdev = 0.133/0.186/0.218/0.033 ms'

    Same weird domain resolving on my .ml...

  • @rm_ said:
    rds100 I don't think you read the whole thread before replying. His issue is simply an old rDNS on the last IP, not ping itself.

    Was working two days ago no ip change..

  • rds100rds100 Member
    edited October 2013

    @rm_ yes, seems so. I thought he was baffled by the low pings, at least that's what i understood from the thread starter post.

    @ATHK So you just open a ticket and say - please change the rDNS (PTR) of my IP 198.23.240.167 to "confor.ml."

  • rm_rm_ IPv6 Advocate, Veteran
    edited October 2013

    @ATHK Maybe some other customer requested their rDNS to be set, and the provider made a mistake and set it for the wrong (your) IP instead. The solution has been explained to you above, contact the provider and ask them to change it:

    Please set the rDNS (PTR) record of IP 198.23.240.167 to "confor.ml"

  • Not arguing the solution and if you read the other posts I opened a ticket which they've done confor.ml is on another VPS (same provider) the one being pinged from was the one I assumed had the issue?

    I have multiple domains pointing to these two servers do I list each one for the provider or just a primary?

Sign In or Register to comment.