flo/nsupdate.info
1
0
Fork 0
Code Issues 1 Pull Requests 2 Packages Releases Activity

fix rest syntax in docs

Browse Source
This commit is contained in:
Thomas Waldmann 2014-08-31 17:46:16 +02:00
parent 4ef30e4fb8
commit fdaef03bba
1 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/user.rst
View File

@ -255,21 +255,22 @@ Recommended
Here are some clients that likely qualify: Here are some clients that likely qualify:
* ddclient * ddclient
- we offer configuration help for it, just copy & paste - we offer configuration help for it, just copy & paste
- good working, reliable - good working, reliable
- the official version is IPv4 only, IPv6 support needs a patched version - the official version is IPv4 only, IPv6 support needs a patched version
- Linux & other POSIX systems - Linux & other POSIX systems
* python-dyndnsc * python-dyndnsc
- IPv4 and v6 support - IPv4 and v6 support
- Mac OS X, Linux and FreeBSD - Mac OS X, Linux and FreeBSD
* whatever your router / gateway / firewall has for dyndns / ddns * whatever your router / gateway / firewall has for dyndns / ddns
- quality of update client implementations varies widely - quality of update client implementations varies widely
- running on the system that has your public IP makes updating your host when your IP changes easier - running on the system that has your public IP makes updating your host when your IP changes easier
- no need to run additional software on other machines in that network - no need to run additional software on other machines in that network
* nsupdate-info's browser-based updater * nsupdate-info's browser-based updater
- only for adhoc scenarios, not intended for long term use - only for adhoc scenarios, not intended for long term use
- runs in your browser with javascript - runs in your browser with javascript
@ -282,10 +283,11 @@ This likely causes unnecessary load on the service servers and network.
You should not use these: You should not use these:
* a cron job + wget or curl * a cron job + wget or curl
- will either send nochg updates frequently (your host will get flagged as abusive) - will either send nochg updates frequently (your host will get flagged as abusive)
- or it will be very slow reacting to IP changes - or it will be very slow reacting to IP changes
* your self-written not fully standards compliant update client software * your self-written not fully standards compliant update client software
- it looks simple first, but to fully comply is more effort - it looks simple first, but to fully comply is more effort
- if you're not willing to fully comply, then don't even start - if you're not willing to fully comply, then don't even start
- there are already enough badly implemented and also "almost compliant" updaters out there - there are already enough badly implemented and also "almost compliant" updaters out there