[GH-ISSUE #414] db perf issues with frequent ip changers #305

New issue

Open

opened 2026-02-26 10:30:42 +03:00 by kerem · 1 comment

kerem commented

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

Owner

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

i noticed that there are multiple machines out there, which seem to update 1 identical dyndns Host with their private IP address (of 10.233.*.*).

as this is a whole set of IP addresses, each of the machines updates the Host entry (e.g. last update v4 entry) and the DNS (A record) all the time.

our automatic abuse mechanism does not even trigger as it is a "new" IP address (not really, always from same set, but we only know the current one to compare).

workaround: delete Host entry, delete User who does such stupid abusive stuff.

Originally created by @ThomasWaldmann on GitHub (Apr 9, 2019). Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/414 i noticed that there are multiple machines out there, which seem to update 1 identical dyndns Host with their private IP address (of `10.233.*.*`). as this is a whole set of IP addresses, each of the machines updates the Host entry (e.g. `last update v4` entry) and the DNS (`A` record) all the time. our automatic abuse mechanism does not even trigger as it is a "new" IP address (not really, always from same set, but we only know the current one to compare). workaround: delete Host entry, delete User who does such stupid abusive stuff.

kerem commented

2026-02-26 10:30:43 +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.