What would you consider the best practice for the max_connect_errors setting of mySQL?

We had a case where a host failed 10 consecutive times to connect to the db and entered the "black list". This required a manual action to flush the mysql server before that app server could connect to the db again.

Would you just increase the default max_connect_errors setting of mysql (that's what we did as a quickfix)? Would you schedule a flush e.g. every X minutes?

Or is there a way to exclude internal IP addresses from the max_connect_errors limit? (But this is not ideal either - the check is there to enhance security after all.)

link|improve this question

50% accept rate
The first thing i'd check is : why did my app server fail 10 consecutive times to connect to the db ? – m0ntassar Jan 31 at 11:38
feedback

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
or
required, but never shown

Browse other questions tagged or ask your own question.