[macOS] Connection failure after upgrade: Primary seeder (br00) down & empty DNS fallback list

[Tsunekazu]

Description
I recently upgraded to the latest version of Bison Relay on macOS. Upon launching, the client is unable to connect to the network.

While the primary seeder (br00) appears to be having server-side issues (certificate errors and connection refused), the critical issue seems to be that my client has no fallback seeds. The logs show an empty DNS seed list [], meaning the client cannot failover to a working node.

Other users report their clients are working (presumably because they are successfully failing over), suggesting the upgrade process may have cleared or failed to populate the fallback seeder list on my machine.

Expected Behavior
If the primary seeder (br00) is unreachable, the client should attempt to connect to other seeders in the DNS list/hardcoded fallback list.

Actual Behavior
The client retries br00 indefinitely and fails to find a bootstrapper because the list is empty.

Logs
Plaintext

2025-12-15 18:17:18.650 [ERR] CONN: Error connecting to server: failed to query seeder: Get "https://br00.bisonrelay.com:12345/api/live": tls: failed to verify certificate: x509: “localhost” certificate is not standards compliant
2025-12-15 18:17:29.104 [ERR] CONN: Error connecting to server: failed to query seeder: Get "https://br00.bisonrelay.com:12345/api/live": dial tcp 45.32.162.169:12345: connect: connection refused
...
2025-12-15 18:17:57.701 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: []
2025-12-15 18:17:57.701 [ERR] DISC: Unable to query bootstrapper BOLT-0010 DNS Seed: []: empty dns seeder
2025-12-15 18:17:57.701 [ERR] SRVR: No addresses returned by boostrappers. Bumping attempt count.