In the containerized ZooKeeper environment, we encounter stability issues with DNS resolution. As per the documentation's recommendation, we have configured the electionPortBindRetry parameter to be set to 0, which theoretically should make ZooKeeper keep retrying the resolution indefinitely. However, the observed behavior is that ZooKeeper does not actually attempt to retry DNS resolution; instead, it persistently relies on the initial failed result. This discrepancy between the expected retry behavior and the actual implementation of DNS resolution creates a significant operational challenge.