For TLS or TCP type server addresses, libpaf should resolve the DNS name and connect to all IPv4 and IPv6 addresses, treating each A och AAA record as a separate server.
Current libpaf relies on XCM for name resolution, which in turn relies on glibc and the system's configuration, and picks one addresses out of those available for a particular DNS FQDN.
Considering the change in semantics, this new behavior should only be exhibited if it is explicitly enabled (in the domains file).
For TLS or TCP type server addresses, libpaf should resolve the DNS name and connect to all IPv4 and IPv6 addresses, treating each A och AAA record as a separate server.
Current libpaf relies on XCM for name resolution, which in turn relies on glibc and the system's configuration, and picks one addresses out of those available for a particular DNS FQDN.
Considering the change in semantics, this new behavior should only be exhibited if it is explicitly enabled (in the domains file).