diff --git a/nsupdate/accounts/templates/accounts/delete_user.html b/nsupdate/accounts/templates/accounts/delete_user.html index a6380f3..227ddab 100644 --- a/nsupdate/accounts/templates/accounts/delete_user.html +++ b/nsupdate/accounts/templates/accounts/delete_user.html @@ -4,11 +4,11 @@ {% block content %}
- {% blocktrans %}We reserve the right to remove any account or hostname(s) that are - related to unfair use of the service - at any time and without prior notice.{% endblocktrans %} + {% blocktrans trimmed %} + We reserve the right to remove any account or hostname(s) that are + related to unfair use of the service - at any time and without prior notice. + {% endblocktrans %}
- {% blocktrans %}Visit the - nsupdate.info project on GitHub to:{% endblocktrans %} + {% blocktrans trimmed %} + Visit the + nsupdate.info project on GitHub to: + {% endblocktrans %}
{% trans "You can't change the domain name. If you want to have another domain name, you have to delete this domain and create a new one." %}
- {% blocktrans %}Please note that update algorithm and update secret need to match. - Just create a new secret after submitting this form with a changed update algorithm.{% endblocktrans %} + {% blocktrans trimmed %} + Please note that update algorithm and update secret need to match. + Just create a new secret after submitting this form with a changed update algorithm. + {% endblocktrans %}
- {% blocktrans %}We'll generate a ready-to-use configuration for your name server, - filled out with all values (including a new secret).{% endblocktrans %} + {% blocktrans trimmed %} + We'll generate a ready-to-use configuration for your name server, + filled out with all values (including a new secret). + {% endblocktrans %}
- {% blocktrans %}We'll create a new shared secret - if you had one before, it will become invalid. - You have to use the new secret in your name server configuration.{% endblocktrans %} + {% blocktrans trimmed %} + We'll create a new shared secret - if you had one before, it will become invalid. + You have to use the new secret in your name server configuration. + {% endblocktrans %}
- {% blocktrans %}Here you can add new domains (zones) which you control (and this is only useful if you - have some own zone which you can update automatically).{% endblocktrans %} + {% blocktrans trimmed %} + Here you can add new domains (zones) which you control (and this is only useful if you + have some own zone which you can update automatically). + {% endblocktrans %}
- {% blocktrans %}You need to be able to configure the primary master nameserver of the zone so it accepts - dynamic updates (via RFC 2136 "dynamic update" protocol) if the correct update secret is presented.{% endblocktrans %} + {% blocktrans trimmed %} + You need to be able to configure the primary master nameserver of the zone so it accepts + dynamic updates (via RFC 2136 "dynamic update" protocol) if the correct update secret is presented. + {% endblocktrans %}
{% trans "We'll show you configuration examples after you add a domain." %} diff --git a/nsupdate/main/templates/main/generate_secret.html b/nsupdate/main/templates/main/generate_secret.html index 9df0bab..88e222f 100644 --- a/nsupdate/main/templates/main/generate_secret.html +++ b/nsupdate/main/templates/main/generate_secret.html @@ -6,7 +6,13 @@
{% blocktrans %}New secret generated for you. We store it hashed, so save it now, or you have to generate a new one again. Everytime you visit this page a new secret will be generated and the old one becomes invalid.{% endblocktrans %}
++ {% blocktrans trimmed %} + New secret generated for you. + We store it hashed, so save it now, or you have to generate a new one again. + Everytime you visit this page a new secret will be generated and the old one becomes invalid. + {% endblocktrans %} +
{% trans "Secret:" %} {{ update_secret }}
- {% blocktrans %}Empowered by Python and Django,
- we love to write clean and secure code.{% endblocktrans %}
+ {% blocktrans trimmed %}
+ Empowered by Python and Django,
+ we love to write clean and secure code.
+ {% endblocktrans %}
- {% blocktrans %}We'll generate a ready-to-use configuration for your router / update - client, filled out with all values (including a new secret).{% endblocktrans %} + {% blocktrans trimmed %} + We'll generate a ready-to-use configuration for your router / update + client, filled out with all values (including a new secret). + {% endblocktrans %}
- {% blocktrans %}We'll create a new secret - if you had one before, it will become invalid. - You have to use the new secret in your router / update client configuration.{% endblocktrans %} + {% blocktrans trimmed %} + We'll create a new secret - if you had one before, it will become invalid. + You have to use the new secret in your router / update client configuration. + {% endblocktrans %}
- {% blocktrans %}We can update additional host records (for other hosts in same network) - when we receive an update for this host.{% endblocktrans %} + {% blocktrans trimmed %} + We can update additional host records (for other hosts in same network) + when we receive an update for this host. + {% endblocktrans %}
{% blocktrans %}Usually you configure your router to follow the dyndns2 protocol. - But if you know what you are doing, and you want to update manually, you can do it here.{% endblocktrans %} +
+ {% blocktrans trimmed %}
+ Usually you configure your router to follow the dyndns2 protocol.
+ But if you know what you are doing, and you want to update manually, you can do it here.
+ {% endblocktrans %}
{% trans "We populated the input fields for the new addresses with your currently detected remote addresses." %}
{% trans "Here you can add new hosts (like routers, PCs, servers, ...)." %}
-{% blocktrans %}You need to be able to configure one of your machines so it sends dyndns2 compatible - updates to us when your IP changes. Routers usually have some builtin software that does - this, but you can also use some software on another system (like a PC or server).{% endblocktrans %} +
+ {% blocktrans trimmed %} + You need to be able to configure one of your machines so it sends dyndns2 compatible + updates to us when your IP changes. Routers usually have some builtin software that does + this, but you can also use some software on another system (like a PC or server). + {% endblocktrans %}
- {% blocktrans %}Just make sure your update client either is customizable well enough or has specific - support for our service.{% endblocktrans %} + {% blocktrans trimmed %} + Just make sure your update client either is customizable well enough or has specific + support for our service. + {% endblocktrans %}
{% trans "We'll show you configuration examples after you add a host." %} diff --git a/nsupdate/main/templates/main/includes/tabbed_router_configuration.html b/nsupdate/main/templates/main/includes/tabbed_router_configuration.html index 2451616..7c49a54 100644 --- a/nsupdate/main/templates/main/includes/tabbed_router_configuration.html +++ b/nsupdate/main/templates/main/includes/tabbed_router_configuration.html @@ -15,24 +15,28 @@
- {% blocktrans %} + {% blocktrans trimmed %} Usually, you should configure one system on your network to update the DNS. This can be either your router or a host on your network and it will run some software - called the update client.{% endblocktrans %} + called the update client. + {% endblocktrans %}
- {% blocktrans %} + {% blocktrans trimmed %} We have some specific configuration hints for some devices and update clients, - please see the tabs above. If you don't find yours there, use the generic hints below.{% endblocktrans %} + please see the tabs above. If you don't find yours there, use the generic hints below. + {% endblocktrans %}
- {% blocktrans %}
+ {% blocktrans trimmed %}
Important note about security and compatibility:
For update URLs, we always give the https (not: http) URL as that will use an encrypted connection
to transfer your data (including your update secret). Depending on your update client (router firmware or
PC software) and the specific nsupdate.info-based service, https might be not supported.
So, if it does not work, you have the choice of using a different update client and/or a different service,
- or transmitting your data using an unencrypted connection (using http: instead of https:).
{% endblocktrans %}
+ or transmitting your data using an unencrypted connection (using http: instead of https:).
+ {% endblocktrans %}
+
On {{ WWW_HOST }} https is {% if not WE_HAVE_TLS %}not {% endif %}supported.
{% trans "Your update client has to do the following steps:" %} @@ -78,10 +83,13 @@
Homepage: https://www.pfsense.org
- {% blocktrans %}Please note: if the pfSense WAN interface does not have + {% blocktrans trimmed %} + Please note: if the pfSense WAN interface does not have your public IP and does not notice your public IP changing, the update will be done delayed (default: daily at 01:01). You can tweak this by editing /etc/crontab from where it invokes @@ -264,49 +273,53 @@ config service "ipv4ddns"
{% blocktrans %}When we receive an update for your main host, we compute your network address - from it. To compute your related host's IPs, we just add the interface ID to the network address. - Then we update the DNS records for the related host with these addresses.{% endblocktrans %} +
+ {% blocktrans trimmed %} + When we receive an update for your main host, we compute your network address + from it. To compute your related host's IPs, we just add the interface ID to the network address. + Then we update the DNS records for the related host with these addresses. + {% endblocktrans %}
{% trans "Here you can add related hosts (e.g. other machines on same LAN)." %}
-{% blocktrans %}When we receive an update for your main host, we compute your network address - from it. To compute your related host's IPs, we just add the interface ID to the network address. - Then we update the DNS records for the related host with these addresses.{% endblocktrans %} +
+ {% blocktrans trimmed %} + When we receive an update for your main host, we compute your network address + from it. To compute your related host's IPs, we just add the interface ID to the network address. + Then we update the DNS records for the related host with these addresses. + {% endblocktrans %}
diff --git a/nsupdate/main/templates/main/update.html b/nsupdate/main/templates/main/update.html index 6dd9742..f6ee29c 100644 --- a/nsupdate/main/templates/main/update.html +++ b/nsupdate/main/templates/main/update.html @@ -5,7 +5,9 @@- {% blocktrans %}Host {{ hostname }} will get automatically updated as long as you keep this window open.{% endblocktrans %} + {% blocktrans trimmed %} + Host {{ hostname }} will get automatically updated as long as you keep this window open. + {% endblocktrans %}