Support cloud-based FluentD deployment

This means supporting:
1. Server host resolving to multiple IPs.
2. Refreshing server host IPs at A/AAAA/CNAME record TTL expiration.
3. Supporting fail-over to the next host available
4. Supporting round-robin load balancing

The issue names no files, tests, or entry points. Start by locating the server-host resolution, connection, retry, and balancing logic in the Python logger, then review how DNS TTLs and multiple addresses can be represented. Done means supporting multiple IPs, TTL refresh, fail-over, and round-robin behavior with coverage for each.

索引モデルが issue の本文から書いたものです。