[GH-ISSUE #478] hosts *.urown.cloud and *.dnsupdate.info getting flagged as abusive #351

Closed
opened 2026-02-26 10:31:00 +03:00 by kerem · 1 comment
Owner

Originally created by @ThomasWaldmann on GitHub (Apr 8, 2021).
Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/478

A bug showed due to #476:

because the whole zone is offline, it can not be updated.

because the update does not work, routers are sending the same update (same IP) again and again and thus get flagged as abusive:

Issue: The abuse flag for your host was set.

Explanation:
The abuse flag usually gets set if your update client sends way too many updates although your IP address did not change.

Your update client sent XX faulty updates since we last checked.
Originally created by @ThomasWaldmann on GitHub (Apr 8, 2021). Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/478 A bug showed due to #476: because the whole zone is offline, it can not be updated. because the update does not work, routers are sending the same update (same IP) again and again and thus get flagged as abusive: ``` Issue: The abuse flag for your host was set. Explanation: The abuse flag usually gets set if your update client sends way too many updates although your IP address did not change. Your update client sent XX faulty updates since we last checked. ```
kerem closed this issue 2026-02-26 10:31:00 +03:00
Author
Owner

@ThomasWaldmann commented on GitHub (Apr 12, 2023):

the zones are gone.

<!-- gh-comment-id:1505294863 --> @ThomasWaldmann commented on GitHub (Apr 12, 2023): the zones are gone.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nsupdate.info-nsupdate-info#351
No description provided.