[GH-ISSUE #75] document well-behaved / not-so-well-behaved update clients #73

Closed
opened 2026-02-26 09:35:24 +03:00 by kerem · 1 comment
Owner

Originally created by @ThomasWaldmann on GitHub (Nov 3, 2013).
Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/75

I started documenting some update clients we recommend / we do not recommend.

http://nsupdateinfo.readthedocs.org/en/latest/user.html#update-clients

The lists are rather short, if you know anything else to add there, either do a pull request or add it to this issue.

Update clients should have ipv4 and ipv6 support and be well-behaved (support dyndns2 protocol).

For well-behaved and popular ones, see also #86.

Originally created by @ThomasWaldmann on GitHub (Nov 3, 2013). Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/75 I started documenting some update clients we recommend / we do not recommend. http://nsupdateinfo.readthedocs.org/en/latest/user.html#update-clients The lists are rather short, if you know anything else to add there, either do a pull request or add it to this issue. Update clients should have ipv4 and ipv6 support and be well-behaved (support dyndns2 protocol). For well-behaved and popular ones, see also #86.
kerem 2026-02-26 09:35:24 +03:00
Author
Owner

@ThomasWaldmann commented on GitHub (Dec 29, 2015):

fine as is.

<!-- gh-comment-id:167818371 --> @ThomasWaldmann commented on GitHub (Dec 29, 2015): fine as is.
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#73
No description provided.