Retry on SocketError when calling resolv()

After running for a few more days in production, we changed it to retry the resolv() call should it fail rather than removing the node from the list of available servers.
So far this latest change appears to be working well in our production environments.

The only issue from a generic perspective is that it is has a hard-coded retry of 3. Is there a better way to configure it in Moped?