Same IP Has Different Resolution Results Across Task Types

Problem description
The customer environment is IPv6, the page task settings are ProfilingPING, the data is normal, and PING can pass, but the IP is taken out separately, and the PING Task Type is used to PING the IP separately, an error is reported name or service not know

Page monitoring content, PING data is normal

PING monitoring data, data Exception

Cause of the problem

The client handles the IPv6 address problem. When the PING task tests the IPv6 address, the address problem causes it to be truncated. When doing the task, if the complete address is not accessed, an error will be reported for the incomplete address: name or service not know.

Solution

Temporary solution:
When monitoring IPv6 addresses, you need to manually add the "[]" symbol, for example: [2408:873c:XXXXXXX:7::3]

Final solution:

The problem with the client is only for some Probe. Upgrade the client to adapt to the IPv6 address. There is no need to manually fill in "[]". The background supports it by default; the support time will be around May 2025.

Same IP Has Different Resolution Results Across Task Types

Page monitoring content, PING data is normal#

PING monitoring data, data Exception#

Cause of the problem#

Solution#

Final solution:#

Page monitoring content, PING data is normal

PING monitoring data, data Exception

Cause of the problem

Solution

Final solution: