-
Notifications
You must be signed in to change notification settings - Fork 476
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
options backup pool and DNS refresh #151
Comments
@M5M400 you are correct, the miner will resolve the DNS only once (if successful) and store the result. Restarting the miner is a quick fix for that. Nice solution would be to flush the cached result every second failure. |
@M5M400 I actually found was talking out of my tailpipe here when I read the code. Are you sure that wasn't the local OS cache? |
Not entirely sure and perfectly possible. Let's close that one. |
Or leave it open for the "backup pool" feature ;) |
being stupid |
any update on backup pool? I would like using my smaller pool but with all these DDos attacks going around smaller pools I almost have to stick to nano pool. SGminer supports backup pool along with Claymore. |
I'm really liking the idea of a backup pool option too |
Hi,
I've had some problems with supportXMR.com pool lately, as the new server I added kept going dark. It would have been tremendously useful for the miners if stak products would
a) allow for the configuration of a backup pool server (for obvious reasons)
b) ditch cached DNS / re-resolve DNS before a reconnect attempt (my DNS TTL is set to 5 minutes and I set it back to the IP of the old server, but miners keep connecting to the crashed box)
The text was updated successfully, but these errors were encountered: