DNS seed node resolution limits in Aerospike 6.x/7.x

DNS seed node resolution limits in Aerospike 6.x/7.x

The Aerospike client resolves seed node hostnames using the system resolver and does not support DNS SRV records. The client’s behavior when a hostname returns multiple IP addresses is not documented in the public reference. The goal is to understand whether the client will attempt to connect to all resolved IPs, how it handles unreachable addresses, and whether any configuration exists to influence this process.

Key constraints include the lack of built‑in retry logic for failed IPs and the absence of a documented fallback mechanism. Uncertainty remains about the selection order and the impact of network topology on connection success.

Specific questions:

• Does the Aerospike client attempt connections to all IPs returned by DNS for a seed hostname, or only the first?
• If some IPs are unreachable, does the client retry remaining addresses or fail immediately?
• Is there a configuration option to control or override this resolution behavior?