the difference about namespace of ipv4 and ipv6

HI all:
In the scenario where multiple clock sources are configured, we encounter some problems. One IPv4 server and one IPv6 server are the clock source of local stratum 10. As I mentioned last time, the two servers are generated by different hosts using network namespaces. The command output shows that the status of the clock source is maybe in error.
[root@localhost ~]# chronyc sources -a -v

  .-- Source mode  '^' = server, '=' = peer, '#' = local clock.
/ .- Source state '*' = current best, '+' = combined, '-' = not combined,
| /             'x' = may be in error, '~' = too variable, '?' = unusable.
||                                                 .- xxxx [ yyyy ] +/- zzzz
||      Reachability register (octal) -.           |  xxxx = adjusted offset,
||      Log2(Polling interval) --.      |          |  yyyy = measured offset,
||                                \     |          |  zzzz = estimated error.
||                                 |    |           \
MS Name/IP address         Stratum Poll Reach LastRx Last sample
===============================================================================
^x 11.11.99.134                 10   1   377     2   -842ms[ -842ms] +/-   81us
^x 1111:1111::1:7e0d            10   1   377     0    +86ms[  +86ms] +/-  127us
When trust is configured for only one clock source, current best is displayed, and X is displayed for the other clock source.
[root@localhost ~]# chronyc sources
MS Name/IP address         Stratum Poll Reach LastRx Last sample
===============================================================================
^x 11.11.54.34                  10   1   377     1   -674ms[ -674ms] +/-   79us
^* 1111:1111::1:f9f             10   1   377     0  +8459ns[  +19us] +/-  121us
Configure two trusts and change them to X at the same time. The two clock sources marked as trust do not respond to each other. Therefore, both clock sources are displayed as false clock sources.
[root@localhost ~]# chronyc sources -a -v

  .-- Source mode  '^' = server, '=' = peer, '#' = local clock.
/ .- Source state '*' = current best, '+' = combined, '-' = not combined,
| /             'x' = may be in error, '~' = too variable, '?' = unusable.
||                                                 .- xxxx [ yyyy ] +/- zzzz
||      Reachability register (octal) -.           |  xxxx = adjusted offset,
||      Log2(Polling interval) --.      |          |  yyyy = measured offset,
||                                \     |          |  zzzz = estimated error.
||                                 |    |           \
MS Name/IP address         Stratum Poll Reach LastRx Last sample
===============================================================================
^x 11.11.93.143                 10   1    77     0   -325ms[ -325ms] +/-   90us
^x 1111:1111::1:753d            10   1    77     0   +678ms[ +678ms] +/-  130us
If two IPv4 local clock sources are used and the trust command is used, both clock sources can be displayed properly.
[cid:[email protected]]
[cid:[email protected]]
I wonder what the difference is?

The IPv4 namespace is on the 9.82.168.154 host, and the IPv6 namespace is on the 9.82.203.28 host.