9,561
edits
Changes
Template:Networking rut manual dynamic dns (view source)
Revision as of 12:30, 24 October 2023
, 12:30, 24 October 2023Text replacement - "\{\{Template: Networking_rutos_manual_fw_disclosure (.*) (.*) (.*) (.*) (.*) \}\}" to "{{Template: Networking_device_manual_fw_disclosure | series = {{{series}}} | name = {{{name}}} | fw_version ={{Template: Networking_device_manual_latest_fw | series = {{{series}}} | name = {{{name}}} }} }}"
{{Template: Networking_rutxxx_manual_fw_disclosure
{{Template: Networking_device_manual_fw_disclosure
| fw_version = {{#switch: {{{series}}}
| series = {{{series}}}
| name = {{{name}}}
| fw_version ={{Template: Networking_device_manual_latest_fw
| series = {{{series}}}
| series = {{{series}}}
| name = {{{name}}}
}}
}}
}}
==Summary==
==Summary==
<b>Dynamic DNS</b> (<b>DDNS</b> or <b>DynDNS</b>) is a method of automatically updating a name server in the Domain Name System (DNS). This is most often utilized when the end user has a [[Private_and_Public_IP_Addresses#Dynamic_IP_address|dynamic IP address]] and wants to bind it to a static hostname.
<b>Dynamic DNS</b> (<b>DDNS</b> or <b>DynDNS</b>) is a method of automatically updating a name server in the Domain Name System (DNS). This is most often utilized when the end user has a [[Private_and_Public_IP_Addresses#Dynamic_IP_address|dynamic IP address]] and wants to bind it to a static hostname.
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 {{{name}}} device 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 following is an overview of the Dynamic DNS section for {{{name}}} devices.
This chapter of the user manual provides an overview of the Dynamic DNS page 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
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.
(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:Networking_rutxxx_manual_dynamic_dns_overview_v1.png]]
[[File:Networking_rut_manual_dynamic_dns.png|border|class=tlt-border]]
==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
The figure below is an example of the edit page of the default DDNS instance called "Myddns" (already present in this device by default) and the table below
"Myddns" (already present in the router by default) and the table below
provides information on the configuration fields contained in that page:
provides information on the configuration fields contained in that page:
[[File:Networking_rut9xx_manual_dynamic_dns_v1.png]]
[[File:Networking_rut_manual_dynamic_dns_configuration.png|border|class=tlt-border]]
<table class="nd-mantable">
<table class="nd-mantable">
<td>Enables SSL data encryption.</td>
<td>Enables SSL data encryption.</td>
</tr>
</tr>
{{#ifeq:{{{series}}}|RUT2|
{{#ifeq:{{{series}}}|RUT2XX|
<tr>
<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>
<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 DDNS 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 device has not been able to establish a connection to the DDNS service provider.</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 IP address of this device.</td>
</tr>
</tr>
<tr>
<tr>
<tr>
<tr>
<td>IP address source</td>
<td>IP address source</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><span style="color: tomato; font-weight: bold;">Custom</span> | <span style="color: #0b85fb; font-weight: bold;">Public</span> | Private | <span style="color: #0bac53; 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>
</tr>
</tr>
<tr>
<tr>
<td><span style="color: dodgerblue; font-weight: bold;">Public:</span> URL to detect</td>
<td><span style="color: #0b85fb; font-weight: bold;">Public:</span> URL to detect</td>
<td>host; default: <b>http://checkip.dyndns.com</b></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>
<td>URL which is used to get your device's public IP from.</td>
</tr>
</tr>
<tr>
<tr>
<td><span style="color: mediumseagreen; font-weight: bold;">Script:</span> Script</td>
<td><span style="color: #0bac53; font-weight: bold;">Script:</span> Script</td>
<td>string; default: <b>none</b></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>
<td>User defined script your device which is used to get it's public IP from.</td>
</tr>
</tr>
<tr>
<tr>
<td><span style="color: mediumseagreen; font-weight: bold;">Script:</span> Event Network</td>
<td><span style="color: #0bac53; font-weight: bold;">Script:</span> Event Network</td>
<td>network interfaces; default: <b>WAN</b></td>
<td>network interfaces; default: <b>WAN</b></td>
<td>Network interface on which your script will be started.</td>
<td>Network interface on which your script will be started.</td>
</table>
</table>
<br>
<br>
<table class="nd-othertables">
<tr>
<th colspan="8"><span class="asterisk">*</span> SUPPORTED DNS SERVICES</th>
</tr>
<tr>
<td style="width: 143px; font-weight: normal;">3322.org</td>
<td style="width: 143px;">able.or.kr</td>
<td style="width: 142px;">afraid.org-basicauth</td>
<td style="width: 142px;">afraid.org-keyauth</td>
<td style="width: 142px;">all-inkl.com</td>
<td style="width: 142px;">bind-nsupdate</td>
<td style="width: 142px;">binero.se</td>
<td style="width: 142px;">changeip.com</td>
</tr>
<tr>
<td style="font-weight: normal;">cloudflare.com-v4</td>
<td>core-networks.de</td>
<td>ddns.com.br</td>
<td>ddnss.de</td>
<td>ddo.jp</td>
<td>desec.io</td>
<td>dhis.org</td>
<td>[[dnsdynamic.org DDNS configuration|dnsdynamic.org]]</td>
</tr>
<tr>
<td style="font-weight: normal;">dnsexit.com</td>
<td>dnshome.de</td>
<td>dnsmadeeasy.com</td>
<td>dnsmax.com</td>
<td>dnsomatic.com</td>
<td>dnspark.com</td>
<td>do.de</td>
<td>domopoli.de</td>
</tr>
<tr>
<td style="font-weight: normal;">dtdns.com</td>
<td>duckdns.org</td>
<td>duiadns.net</td>
<td>dy.fi</td>
<td>[[dyn.com DDNS configuration|dyn.com]]</td>
<td>dyndns.it</td>
<td>dyndns.org</td>
<td>dyndnss.net</td>
</tr>
<tr>
<td style="font-weight: normal;">dyns.net</td>
<td>dynsip.org</td>
<td>[[dynu.com DDNS configuration|dynu.com]]</td>
<td>dynv6.com</td>
<td>easydns.com</td>
<td>editdns.net</td>
<td>goip.de</td>
<td>google.com</td>
</tr>
<tr>
<td style="font-weight: normal;">he.net</td>
<td>joker.com</td>
<td>loopia.se</td>
<td>mydns.jp</td>
<td>myonlineportal.net</td>
<td>mythic-beasts.com</td>
<td>namecheap.com</td>
<td>nettica.com</td>
</tr>
<tr>
<td style="font-weight: normal;">[[noip.com DDNS configuration|noip.com]]</td>
<td>no-ip.pl</td>
<td>now-dns.com</td>
<td>nsupdate.info</td>
<td>nubem.com</td>
<td>opendns.com</td>
<td>oray.com</td>
<td>ovh.com</td>
</tr>
<tr>
<td style="font-weight: normal;">regfish.de</td>
<td>schokokeks.org</td>
<td>secure.camera</td>
<td>selfhost.de</td>
<td>sitesolutions.com</td>
<td>spdns.de</td>
<td>spdyn.de</td>
<td>strato.com
</td>
</tr>
<tr>
<td style="font-weight: normal;">system-ns.com</td>
<td>thatip.com</td>
<td>twodns.de</td>
<td>umedia.de</td>
<td>variomedia.de</td>
<td>xlhost.de</td>
<td>zerigo.com</td>
<td>zoneedit.com</td>
</tr>
<tr>
<td style="font-weight: normal;">zzzz.io</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
</table>
==See also==
==See also==
