[GH-ISSUE #413] db perf issue with auth errors #301

New issue

Open

opened 2026-02-26 10:30:41 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 10:30:41 +03:00

Owner

Originally created by @ThomasWaldmann on GitHub (Apr 9, 2019).
Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/413

some bad dyndns clients just retry again and again in case of e.g. authentication errors.

as we count auth errors in the Host record, this writes to the DB all the time ...

workaround: kill the Host record for such abusers, so there is no record to count something in.

fix: don't count.

Originally created by @ThomasWaldmann on GitHub (Apr 9, 2019). Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/413 some bad dyndns clients just retry again and again in case of e.g. authentication errors. as we count auth errors in the Host record, this writes to the DB all the time ... workaround: kill the Host record for such abusers, so there is no record to count something in. fix: don't count.

kerem commented

2026-02-26 10:30:42 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Apr 9, 2019):

there is also an issue with the recorded api_auth_result_msg - due to the timestamp in there, this is always a new message that also needs a db write.

@ThomasWaldmann commented on GitHub (Apr 9, 2019): there is also an issue with the recorded `api_auth_result_msg` - due to the timestamp in there, this is always a new message that also needs a db write.

kerem commented

2026-02-26 10:30:42 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Apr 15, 2019):

also added BAD_HOSTS set in configuration, to block abusive hosts early, before they access the database.

@ThomasWaldmann commented on GitHub (Apr 15, 2019): also added BAD_HOSTS set in configuration, to block abusive hosts early, before they access the database.