0
edits
Changes
Template:Networking rut manual dynamic dns (view source)
Revision as of 11:34, 16 September 2020
, 11:34, 16 September 2020no edit summary
{{Template: Networking_rutxxx_manual_fw_disclosure
| fw_version = {{#switch: {{{series}}}
| RUT2 = {{{series}}}XX_R_00.01.12 <!-- remove XX for next version -->
| RUT9 = {{{series}}}_R_00.06.07}}
| series = {{{series}}}
}}
==Summary==
==Summary==
The router is compatible with many different third party DNS services that provide the possibility to create a custom hostname and bind it to an IP address. The DDNS service periodically updates the IP address information of the hostname, making sure that the device remains reachable via the same hostname even in cases when its IP address has changed.
The router is compatible with many different third party DNS services that provide the possibility to create a custom hostname and bind it to an IP address. The DDNS service periodically updates the IP address information of the hostname, making sure that the device remains reachable via the same hostname even in cases when its IP address has changed.
This chapter is an overview of the Dynamic DNS section for {{{name}}} devices.
This following is an overview of the Dynamic DNS section for {{{name}}} devices.
==Dynamic DNS Overview==
==Dynamic DNS Overview==
By default, an unconfigured DDNS instance will be present in the <b>Dynamic DNS Overview</b> page (the figure below is an example of this). You can create more DDNS instances by entering a <b>New configuration name</b> and clicking the <b>Add new</b> button or you can edit the existing instance since it is not operational by default.
By default, an unconfigured DDNS instance will be present in the <b>Dynamic DNS Overview</b> page
(the figure below is an example of this). You can create more DDNS instances by entering a
<b>New configuration name</b> and clicking the <b>Add New</b> button or you can
edit the existing instance since it is not operational by default.
[[File:{{{file_dynamic_dns_overview}}}]]
[[File:Networking_rutxxx_manual_dynamic_dns_overview_v1.png]]
==Editing a DDNS instance==
==Editing a DDNS instance==
To configure a DDNS instance, click the <b>Edit</b> button located next to it.
To configure a DDNS instance, click the <b>Edit</b> button located next to it.
The figure below is an example of the edit page of the default DDNS instance called "MyDDNS" (already present in the router by default) and the table below provides information on the configuration fields contained in that page:
The figure below is an example of the edit page of the default DDNS instance called
"Myddns" (already present in the router by default) and the table below
provides information on the configuration fields contained in that page:
[[File:{{{file_dynamic_dns_configuration}}}]]
[[File:Networking_rut9xx_manual_dynamic_dns_v1.png]]
<table class="nd-mantable">
<table class="nd-mantable">
<tr>
<tr>
<td>Enable</td>
<td>Enable</td>
<td>yes | no; Default: <b>no</b></td>
<td>yes | no; default: <b>no</b></td>
<td>Turns the DDNS instance ON or OFF</td>
<td>Turns the DDNS instance On or Off.</td>
</tr>
</tr>
<tr>
<tr>
<td>Use HTTP Secure</td>
<td>Use HTTP Secure</td>
<td>yes | no; Default: <b>no</b></td>
<td>yes | no; default: <b>no</b></td>
<td>Enables SSL data encryption</td>
<td>Enables SSL data encryption.</td>
</tr>
</tr>
{{#ifeq:{{{series}}}|RUT2|
<tr>
<td>Use IPv6</td>
<td>Use IPv6</td>
<td>yes | no; Default: <b>no</b></td>
<td>yes | no; default: <b>no</b></td>
<td>Use IPv6 for this configuration</td>
<td>Use IPv6 for this configuration.</td>
</tr>
</tr>
|}}
<tr>
<tr>
<td>Status</td>
<td>Status</td>
<td>string; Default: <b>N/A</b></td>
<td>string; default: <b>N/A</b></td>
<td>Data on the last status update of the DDNS instance. When status is shown as "N/A", it means that the router has not been able to establish a connection to the DNS service provider</td>
<td>Data on the last status update of the DDNS instance. When status is shown as "N/A", it means that the router has not been able to establish a connection to the DDNS service provider.</td>
</tr>
</tr>
<tr>
<tr>
<td>Service</td>
<td>Service</td>
<td>third party DNS service (chosen from list<span class="asterisk">*</span>) | -- custom --; Default: <b>dyn.com</b></td>
<td>third party DNS service (chosen from list<span class="asterisk">*</span>) | -- custom --; default: <b>dyn.com</b></td>
<td>Third party DNS service provider</td>
<td>Third party DNS service provider.</td>
</tr>
</tr>
<tr>
<tr>
<td>Lookup host</td>
<td>Lookup host</td>
<td>host; Default: <b>yourhost.example.com</b></td>
<td>host; default: <b>yourhost.example.com</b></td>
<td>Fully qualified domain name (FQDN) of your defined host. This is required to verify what the hostname's current IP address at DNS is (using ''nslookup/host'' command)</td>
<td>Fully qualified domain name (FQDN) of your defined host. This is required to verify what the hostname's current IP address at DNS is (using ''nslookup/host'' command).</td>
</tr>
</tr>
<tr>
<tr>
<td>Hostname</td>
<td>Hostname</td>
<td>host; Default: <b>yourhost.example.com</b></td>
<td>host; default: <b>yourhost.example.com</b></td>
<td>Hostname that will be linked with the router's IP address</td>
<td>Hostname that will be linked with the router's IP address.</td>
</tr>
</tr>
<tr>
<tr>
<td>Username</td>
<td>Username</td>
<td>string; Default: <b>your_username</b></td>
<td>string; default: <b>your_username</b></td>
<td>User name required to login to the third party DNS service; used to periodically login to your DNS service account and make necessary updates.</td>
<td>User name required to login to the third party DNS service; used to periodically login to your DNS service account and make necessary updates.</td>
</tr>
</tr>
<tr>
<tr>
<td>Password</td>
<td>Password</td>
<td>string; Default: <b>your_password</b></td>
<td>string; default: <b>your_password</b></td>
<td>Password required to login to the third party DNS service; used to periodically login to your DNS service account and make necessary updates.</td>
<td>Password required to login to the third party DNS service; used to periodically login to your DNS service account and make necessary updates.</td>
</tr>
</tr>
<tr>
<tr>
<td>IP address source</td>
<td>IP address source</td>
<td>Custom | Public | Private | Script; Default: <b>Custom</b></td>
<td><span style="color: tomato; font-weight: bold;">Custom</span> | <span style="color: dodgerblue; font-weight: bold;">Public</span> | Private | <span style="color: mediumseagreen; font-weight: bold;">Script</span>; default: <b>Custom</b></td>
<td>Defines the source to read the system's IPv4-Address from, that will be sent to the DNS provider. So if, for example, your RUT has a Private IP (i.e., 10.140.56.57) on its WAN interface, then you can send this exact IP to DDNS server by selecting <b>Private</b></td>
<td>Defines the source to read the system's IPv4-Address from, that will be sent to the DNS provider. So if, for example, your RUT has a Private IP (i.e., 10.140.56.57) on its WAN interface, then you can send this exact IP to DDNS server by selecting <b>Private</b>.</td>
</tr>
<tr>
<td><span style="color: tomato; font-weight: bold;">Custom:</span> Network</td>
<td>LAN | WAN | WAN2 | WAN3 | PPP | PPP_USB ; default: <b>WAN</b></td>
<td>Specifies which interface's IP address should be bound to the hostname.</td>
</tr>
<tr>
<td><span style="color: dodgerblue; font-weight: bold;">Public:</span> URL to detect</td>
<td>host; default: <b>http://checkip.dyndns.com</b></td>
<td>URL which is used to get your device's public IP from.</td>
</tr>
<tr>
<td><span style="color: mediumseagreen; font-weight: bold;">Script:</span> Script</td>
<td>string; default: <b>none</b></td>
<td>User defined script your device which is used to get it's public IP from.</td>
</tr>
</tr>
<tr>
<tr>
<td>Network</td>
<td><span style="color: mediumseagreen; font-weight: bold;">Script:</span> Event Network</td>
<td>LAN | Wired (WAN) | WiFi (WAN3) | Mobile (PPP) | ETH1V6 | WWAN0V6 | WLAN0V6 ; Default: <b> Wired (WAN)</b></td>
<td>network interfaces; default: <b>WAN</b></td>
<td>Specifies which interface's IP address should be bound to the hostname</td>
<td>Network interface on which your script will be started.</td>
</tr>
</tr>
<tr>
<tr>
<td>IP renew interval</td>
<td>IP renew interval</td>
<td>integer [5..600000]; Default: <b>10</b></td>
<td>integer [5..600000]; default: <b>10</b></td>
<td>Frequency at which the device will check whether it's IP address has changed</td>
<td>Frequency at which the device will check whether it's IP address has changed.</td>
</tr>
<tr>
<td>IP renew interval unit</td>
<td>Minutes | Hours | Days; default: <b>Minutes</b></td>
<td>Unit which is used in IP renew interval.</td>
</tr>
</tr>
<tr>
<tr>
<td>Force IP renew</td>
<td>Force IP renew</td>
<td>integer [5..600000]; Default: <b>72</b></td>
<td>integer [5..600000]; default: <b>72</b></td>
<td>Frequency at which IP update requests are sent to the DNS provider</td>
<td>Frequency at which IP update requests are sent to the DNS provider.</td>
</tr>
<tr>
<td>Force IP renew unit</td>
<td>Minutes | Hours | Days; default: <b>Minutes</b></td>
<td>Unit which is used in Force IP renew interval.</td>
</tr>
</tr>
</table>
</table>
==See also==
==See also==
*Dynamic DNS configuration examples for specific providers:
* Dynamic DNS configuration examples for specific providers:
**[[noip.com DDNS configuration|noip.com]]
** [[noip.com DDNS configuration|noip.com]]
**[[dnsdynamic.org DDNS configuration|dnsdynamic.org]]
** [[dnsdynamic.org DDNS configuration|dnsdynamic.org]]
**[[dynu.com DDNS configuration|dynu.com]]
** [[dynu.com DDNS configuration|dynu.com]]
**[[dyn.com DDNS configuration|dyn.com]]
** [[dyn.com DDNS configuration|dyn.com]]
[[Category:{{{name}}}<nowiki> Services section]]</nowiki>
[[Category:{{{name}}} Services section]]
