Major Description
Noticed this while documenting the workflow to replace a dead master, which currently bypasses Raft config changes in favor of having the replacement master "masquerade" as the dead master via DNS changes.
Internally we never rebuild consensus peer proxies in the event of network failure; we assume that the peer will return at the same location. Nominally this is reasonable; allowing peers to change host/port information on the fly is tricky and has yet to be implemented. But, we should at least retry the DNS resolution; not doing so forces the workflow to include steps to restart the existing masters, which creates a (small) availability outage.