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

updated docs

Browse Source
This commit is contained in:
Thomas Waldmann 2013-11-24 12:17:56 +01:00
parent e9605535b8
commit 9ae7a7fabe
1 changed files with 11 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docs/user.rst
View File

@ -46,7 +46,7 @@ We detect your addresses by 2 means:
* your current remote address (where your accesses to the web interface come from) - the IP detected this way is
immediately visible on the web interface.
* if we don't already have the IP address from the remote address, we use an invisible fake "image" that your browser
loads from an IPv4-only or IPv6-only server - the IP detected by this method usually shows up after a few seconds.
loads from an IPv4-only or IPv6-only server - the IP detected by this method usually shows up after a few seconds.
We do some optimizations to not load these images too frequently, but also try to make sure we do not show you outdated
information about your current IP addresses.
@ -82,6 +82,16 @@ IP v4 and v6 addresses work completely independently of each other, you need to
both. If you want to be specific about which IP address you update, use our IPv4-only or IPv6-only host to make sure
it is the v4 (or v6) address.
After configuring a new update client, please keep an eye one the Faults column on the overview page.
It shows 2 values: C: <client faults> S: <server faults>
An increasing number of client faults usually means you (or the software you use) are doing something wrong
(e.g. sending updates although your IP address did not change). If you see that, please fix it!
An increasing number of server faults means there is either something wrong with the nameserver or the
connection to it or it is rejecting the updates for your hostname.
Domains
-------
If you control an own nameserver / zone, you can use the service to dynamically update it with your router / update