help: there was only a link to the rtd documentation (now directly linked from a "Documentation" navbar entry)
and some duplicate router configuration that was also shown (even with the correct values) when adding a host.
the help page html was not valid due to the values inserted into the router configuration help.
help/documentation policy: add static help to the docs, add dynamic help directly at the places (in the views) where needed
there was only a link to the rtd documentation (now directly linked from a "Documentation" navbar entry) and
some duplicate router configuration that was also shown (even with the correct values) when adding a host.
the help page html was not valid due to the values inserted into the router configuration help.
help/documentation policy: add static help to the docs, add dynamic help directly at the places (in the views) where needed
as we reference the Domain as ForeignKey in the Host, it'll kill all Hosts that reference the deleted Domain also.
needs to be the PRE_delete signal as some of the data we need is already gone when using POST.
could happen if there once was a IPv6 connection, but now is not any more.
it now kills infos older than 3 minutes from the session.
it also shows the age of the infos now on the hosts overview view (but not on home view due to cosmetic reasons).
optimization: only request the fake images for ipv4/v6 detection if we don't have a fresh IP already.
added example settings for using detectip on (ip6-)localhost
wrap host view into container div (otherwise the top headline hangs out of the screen on the left)
make ipv6 addr a bit smaller, so it might better fit on not-so-wide screens
"public" field means that this zone can be used by every user (not just the owner) to create hosts there
"available" field means that the nameserver is operating and reachable
if a nameserver does not respond, we flag it in the database
(available = False) and stop talking to it for 5 minutes.
after 5 minutes, we flag it available = True again and retry talking to it
(and if not successful, flag it as unavailable again).
this avoids a unresponsive UI as we do a lot of ns queries from the templates
to get v4 and v6 addresses of our hosts from master nameservers.
we log a warning when setting unavailable and a info when setting available.
