[GH-ISSUE #162] improve abuse handling - blacklist IP ranges #151

New issue

Closed

opened 2026-02-26 09:36:07 +03:00 by kerem · 0 comments

kerem commented

2026-02-26 09:36:07 +03:00

Owner

Originally created by @ThomasWaldmann on GitHub (Sep 12, 2014).
Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/162

there might be cases of (relatively) static IPs used for illegal purposes, but the owner of these IPs still uses dyndns in case he has to change them eventually.

currently the only way to deal with this is to keep the useraccount and the host records and flag the hosts as abuse_blocked. if one would remove the hosts and/or user accounts, the user might just create another account and recreate the hosts using the same hostnames.

if we could block specific IP ranges, a user would be unable to point any hostname to that IP.

Originally created by @ThomasWaldmann on GitHub (Sep 12, 2014). Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/162 there might be cases of (relatively) static IPs used for illegal purposes, but the owner of these IPs still uses dyndns in case he has to change them eventually. currently the only way to deal with this is to keep the useraccount and the host records and flag the hosts as abuse_blocked. if one would remove the hosts and/or user accounts, the user might just create another account and recreate the hosts using the same hostnames. if we could block specific IP ranges, a user would be unable to point any hostname to that IP.