You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
The text was updated successfully, but these errors were encountered:
libpaf would need to poll DNS to see if the number or contents of records for a particular domain changes. In essence, the DNS hostname will provide the same information as are in the domain file (i.e., a list of server addresses. but minus "extra" such as tlsCertificateFile).
Polling frequency should be determined by the DNS TTL.
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).
The text was updated successfully, but these errors were encountered: