mirror of
https://github.com/nsupdate-info/nsupdate.info.git
synced 2026-04-25 16:45:55 +03:00
[GH-ISSUE #129] support offline mode? #122
Labels
No labels
bug
bug
duplicate
easy
easy
enhancement
enhancement
invalid
needs help
pull-request
scalability
security
task
urgent
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nsupdate.info-nsupdate-info#122
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ThomasWaldmann on GitHub (Jan 10, 2014).
Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/129
dyndns2 api has a "offline" flag - shall we support this?
@elnappo commented on GitHub (Jan 15, 2014):
+1
#130 +1
@ThomasWaldmann commented on GitHub (Jan 16, 2014):
After trying to find out more about this "offline" status, it still seems to be rather vaguely defined.
Usually it is offered as paid feature (by noip and dyn) that somehow redirects to a different IP / URL when offline status is active, so that either some "this site is offline" message can be shown or some other content specified by the user.
To support "offline" on dns level, we would just give another IP as answer if the client is offline.
The IP would be either:
a) a (fallback-)IP provided by the user
b) an IP from the nsupdate.info service provider (with a http server just telling "it's offline" as response to ANY request)
I find a) of limited usefulness, but at least it might have some use case. Of course, the client could just send a normal update with myip=FALLBACKIP and the result would be the same.
b) is even more useless and requires additional resources (separate IP + respond-to-all web server) at the service provider, just to tell "it is not online", what everybody would have guessed anyway if there's no response because the IP is offline.
So, I guess I'll put this feature on HOLD status until someone can provide a real usecase.
If somebody has a paid dyn or noip subscribtion and can tell us usecases for the offline mode and what options there shall be, please do tell.
@ThomasWaldmann commented on GitHub (Jan 16, 2014):
Just another note why the offline flag doesn't help for deletion of A or AAAA record:
We need the capability to selective delete the A or AAAA (or both) records.
Just sending offline=YES would not allow to specifically delete only one of these records as without further information, the server would not know which one.
@elnappo commented on GitHub (Jan 16, 2014):
okay, sounds like -1 for this ;) but still +1 for #130 ;)
@ThomasWaldmann commented on GitHub (Aug 27, 2014):
seem like useless and there's also no big interest in this. thus, closing this for now.
in case somebody reopens: please give a usecase and describe the scenario precisely.