0
When on windows 10 in cmd.exe a ping is made to cryptopia.co.nz, I get one of the following results:
Pinging cryptopia.co.nz [45.60.13.241] with 32 bytes of data:
Reply from 45.60.13.241: bytes=32 time=7ms TTL=54
Reply from 45.60.13.241: bytes=32 time=12ms TTL=54
Reply from 45.60.13.241: bytes=32 time=12ms TTL=54
Reply from 45.60.13.241: bytes=32 time=10ms TTL=54
Ping statistics for 45.60.13.241:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 12ms, Average = 10ms
or
Pinging cryptopia.co.nz [45.60.11.241] with 32 bytes of data:
Reply from 45.60.11.241: bytes=32 time=111ms TTL=55
Reply from 45.60.11.241: bytes=32 time=110ms TTL=55
Reply from 45.60.11.241: bytes=32 time=114ms TTL=55
Reply from 45.60.11.241: bytes=32 time=111ms TTL=55
Ping statistics for 45.60.11.241:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 110ms, Maximum = 114ms, Average = 111ms
These two pings were carried out with 1 second inbetween. I thought my computers DNS cache would keep the adress resolved the first time, why isn´t it? Is there a way I can force the system to use the IP with 13 in it for all operations? It´s got a much better ping time.
Sounds like a case of a load balancer. What do you find unusual? Google does the same thing – Ramhound – 2018-04-11T11:15:59.300
1“Is there a way I can force the system to use the IP with 13 in it for all operations?” - You can’t – Ramhound – 2018-04-11T11:16:34.687
But if this domain is in my DNS cache, why is it not picking the IP it was first resolved to the next time? – Corey Hart – 2018-04-11T13:45:14.357
The two A records you received are probably both cached for exactly the same amount of time, and your local resolver arbitrarily picks one. There are other scenarios but in this case, the server returned two A records at the same time, at least for me. – tripleee – 2018-04-11T14:02:52.873