Bound Host Does Not Take Effect and Host IP Outside List Appears

Problem description

The Synthetic task, settings hosts, is not a Host, but a batch of Host polling. However, looking at the Host list, there are Host IPs that are not in the list. I question whether this function is effective?

Problem analysis

(1) Check the commonalities and find that they are all on higher versions of Chrome (90 and above). Chrome 79 version is normal.
(2) From the scheduling view, this phenomenon occurs when the higher version of Chrome polls the Host and fails to poll IPv6 Host.

Cause of the problem

On higher versions of Chrome, Probe does not support IPv6;
Therefore, when the higher version Probe receives a Host with specified IPv6, it will not be Hosted to the corresponding Host;
Probe will use IPv4 by default, DNS will not be restricted, and the resolved Host may not be in the specified list.

Solution

Temporary solution:
If you want to host polling with both IPv4 and IPv6 Host, it is recommended to separate settings;
Create two tasks and specify them respectively. The IPv4 task is normal settings, and the IPv6 task will exclude all except Chrome 79;

Final solution:

Tuning in background scheduling, when polling to IPv6 Host, the schedule is sent to Chrome 79 Probe.

Bound Host Does Not Take Effect and Host IP Outside List Appears

Problem description#

Problem analysis#

Cause of the problem#

Solution#

Final solution:#

Problem description

Problem analysis

Cause of the problem

Solution

Final solution: