[GH-ISSUE #161] improve abuse handling - remove dns records #152

New issue

Closed

opened 2026-02-26 09:36:07 +03:00 by kerem · 2 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/161

currently, in cases of severe abuse (e.g. using the service for illegal activities), one can set abuse_blocked flag for a host via the django admin (btw, this should be preferred over just deleting the host because otherwise the abuser can just recreate it).

but: if a dns record for that host was already established, setting the abuse_blocked flag won't remove the record from dns. one also can not use the normal web ui because it only lists the hosts owned by the user (even if the user is the nsupdate.info site admin).

so there should be a new view(?) to do abuse_blocked flagging AND dns records removal.
maybe even some handler (without a view) is enough, that checks whether abuse_blocked has been set and if so, also kills the dns records.

Originally created by @ThomasWaldmann on GitHub (Sep 12, 2014). Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/161 currently, in cases of severe abuse (e.g. using the service for illegal activities), one can set abuse_blocked flag for a host via the django admin (btw, this should be preferred over just deleting the host because otherwise the abuser can just recreate it). but: if a dns record for that host was already established, setting the abuse_blocked flag won't remove the record from dns. one also can not use the normal web ui because it only lists the hosts owned by the user (even if the user is the nsupdate.info site admin). so there should be a new view(?) to do abuse_blocked flagging AND dns records removal. maybe even some handler (without a view) is enough, that checks whether abuse_blocked has been set and if so, also kills the dns records.

kerem

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

closed this issue
added the
enhancement
label

kerem commented

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

Author

Owner

@ThomasWaldmann commented on GitHub (Oct 27, 2014):

maybe alternatively it could be also implemented in the model. intercept save, check if abuse_blocked was set and then also delete from dns.

@ThomasWaldmann commented on GitHub (Oct 27, 2014): maybe alternatively it could be also implemented in the model. intercept save, check if abuse_blocked was set and then also delete from dns.

kerem commented

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

Author

Owner

@ThomasWaldmann commented on GitHub (Oct 27, 2014):

fixed by 57bf826756

@ThomasWaldmann commented on GitHub (Oct 27, 2014): fixed by 57bf82675664d8d9fd2a80c8eb7c21bcbad1ac2d