8,823
edits
Changes
Template:Networking rutos manual dynamic dns rut2 rut9 (view source)
Revision as of 08:08, 9 April 2024
, 9 AprilCreated page with "<!-- Template uses {{{name}}}, {{{series}}}--> {{Template: Networking_device_manual_fw_disclosure | series = {{{series}}} | name = {{{name}}} | fw_version ={{Template: Netwo..."
<!-- Template uses {{{name}}}, {{{series}}}-->
{{Template: Networking_device_manual_fw_disclosure
| series = {{{series}}}
| name = {{{name}}}
| fw_version ={{Template: Networking_device_manual_latest_fw
| series = {{{series}}}
| name = {{{name}}}
}}
}}
{{#ifeq: {{{series}}} | RUT9 |<br><i><b>Note</b>: <b>[[{{{name}}} Dynamic DNS (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_device_manual_latest_fw | series = RUT9XX}} and earlier) user manual page.</i>|}}
{{#ifeq: {{{series}}} | RUT2 |<br><i><b>Note</b>: <b>[[{{{name}}} Dynamic DNS (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_device_manual_latest_fw | series = RUT2XX}} and earlier) user manual page.</i>|}}
==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.
The 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 chapter is an overview of the Dynamic DNS section for {{{name}}} devices.
{{#switch: {{{series}}}
| #default =
| TRB2|RUT36X|RUT30X|RUT9|TCR1|RUT2|RUT2M|RUT9M|TRB2M|RUT301|RUT361|RUT14X =
<u><b>
Note:</b> Dynamic DNS is additional software that can be installed from the <b>System → [[{{{name}}} Package Manager|Package Manager]]</b> page.</u>
}}
==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 name and
clicking the "Add" button or you can edit the existing instance since it is not operational by default.
[[File:Networking_rutos_manual_dynamic_dns_overview_v2.png|border|class=tlt-border]]
==Editing a DDNS instance==
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 device by default) and the table below provides information on the configuration fields contained in that page:
[[File:Networking_rutos_manual_dynamic_dns_details_for_network_v2_{{{network}}}.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enabled</td>
<td>off | on; Default: <b>off</b></td>
<td>Turns the DDNS instance on or off.</td>
</tr>
<tr>
<td>Lookup hostname</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 <i>nslookup/host</i> command).</td>
</tr>
<tr>
<td>DDNS service provider</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>
</tr>
<tr>
<td>Domain</td>
<td>host; Default: <b>yourhost.example.com</b></td>
<td>Hostname that will be linked with the device IP address.</td>
</tr>
<tr>
<td>Username</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>
</tr>
<tr>
<td>Password</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>
</tr>
<tr>
<td>IP address source</td>
<td>Custom | Public | Private | Script; 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. For example, if your device 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 <i>Private</i>.</td>
</tr>
<tr>
<td>Network</td>
<td>network interface; Default: <b>{{#ifeq:{{{series}}}|RUTX|wan|lan}}</b></td>
<td>Specifies which interface's IP address should be bound to the hostname</td>
</tr>
<tr>
<td>Check Interval</td>
<td>integer [5..3600]; Default: <b>10</b></br>integer [300..3600]<span class="asterisk">*</span></br>integer [1..3600]<span class="asterisk">**</span></td>
<td>Frequency at which the device will check whether it's IP address has changed.<br>The minimal amount of time that can be specified is 5 minutes or 300 seconds.</br><span class="asterisk">*</span>If selected interval is Seconds.</br><span class="asterisk">**</span>If selected interval is Hours.</td>
</tr>
<tr>
<td>Force Interval</td>
<td>integer [5..3600]; Default: <b>10</b></br>integer [1..3600]<span class="asterisk">*</span></td>
<td>Frequency at which IP update requests are sent to the DNS provider.<br>The minimal amount of time that can be specified is 5 minutes and not less than <b>Check Interval</b>.</br><span class="asterisk">*</span>If selected interval is Hours or Days.</td>
</tr>
</table>
<br>
{{Template: Networking_rutx_manual_dynamic_dns_supported_dns_services_rut2_rut9}}
====cloudflare.com====
'''Note:''' To use subdomains with '''Cloudfare''' services, you must use the @ symbol.
service_name cloudflare.com-v4
domain [Your domain, here: example.com]
username Bearer
password [Your API token]
To use subdomains (CNAME or A records), use the format below when filling your credentials:
domain {subdomain}@[zone]
Examples:
If the hostname is “sample.example.com”, the “domain” field would be “[email protected]”
If the hostname is “dev1.sample.example.com”, the “domain” field would be “[email protected]”
If using Cloudflare's “Subdomain Support”, your zone may already be “foo.example.com”, so if the DDNS hostname is “bar.foo.example.com” the domain field would be “[email protected]”
==See also==
* Dynamic DNS configuration examples for specific providers:
** [[noip.com DDNS configuration|noip.com]]
** [[dnsdynamic.org DDNS configuration|dnsdynamic.org]]
** [[dynu.com DDNS configuration|dynu.com]]
** [[dyn.com DDNS configuration|dyn.com]]
[[Category:{{{name}}} Services section]]
{{Template: Networking_device_manual_fw_disclosure
| series = {{{series}}}
| name = {{{name}}}
| fw_version ={{Template: Networking_device_manual_latest_fw
| series = {{{series}}}
| name = {{{name}}}
}}
}}
{{#ifeq: {{{series}}} | RUT9 |<br><i><b>Note</b>: <b>[[{{{name}}} Dynamic DNS (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_device_manual_latest_fw | series = RUT9XX}} and earlier) user manual page.</i>|}}
{{#ifeq: {{{series}}} | RUT2 |<br><i><b>Note</b>: <b>[[{{{name}}} Dynamic DNS (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_device_manual_latest_fw | series = RUT2XX}} and earlier) user manual page.</i>|}}
==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.
The 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 chapter is an overview of the Dynamic DNS section for {{{name}}} devices.
{{#switch: {{{series}}}
| #default =
| TRB2|RUT36X|RUT30X|RUT9|TCR1|RUT2|RUT2M|RUT9M|TRB2M|RUT301|RUT361|RUT14X =
<u><b>
Note:</b> Dynamic DNS is additional software that can be installed from the <b>System → [[{{{name}}} Package Manager|Package Manager]]</b> page.</u>
}}
==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 name and
clicking the "Add" button or you can edit the existing instance since it is not operational by default.
[[File:Networking_rutos_manual_dynamic_dns_overview_v2.png|border|class=tlt-border]]
==Editing a DDNS instance==
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 device by default) and the table below provides information on the configuration fields contained in that page:
[[File:Networking_rutos_manual_dynamic_dns_details_for_network_v2_{{{network}}}.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enabled</td>
<td>off | on; Default: <b>off</b></td>
<td>Turns the DDNS instance on or off.</td>
</tr>
<tr>
<td>Lookup hostname</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 <i>nslookup/host</i> command).</td>
</tr>
<tr>
<td>DDNS service provider</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>
</tr>
<tr>
<td>Domain</td>
<td>host; Default: <b>yourhost.example.com</b></td>
<td>Hostname that will be linked with the device IP address.</td>
</tr>
<tr>
<td>Username</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>
</tr>
<tr>
<td>Password</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>
</tr>
<tr>
<td>IP address source</td>
<td>Custom | Public | Private | Script; 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. For example, if your device 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 <i>Private</i>.</td>
</tr>
<tr>
<td>Network</td>
<td>network interface; Default: <b>{{#ifeq:{{{series}}}|RUTX|wan|lan}}</b></td>
<td>Specifies which interface's IP address should be bound to the hostname</td>
</tr>
<tr>
<td>Check Interval</td>
<td>integer [5..3600]; Default: <b>10</b></br>integer [300..3600]<span class="asterisk">*</span></br>integer [1..3600]<span class="asterisk">**</span></td>
<td>Frequency at which the device will check whether it's IP address has changed.<br>The minimal amount of time that can be specified is 5 minutes or 300 seconds.</br><span class="asterisk">*</span>If selected interval is Seconds.</br><span class="asterisk">**</span>If selected interval is Hours.</td>
</tr>
<tr>
<td>Force Interval</td>
<td>integer [5..3600]; Default: <b>10</b></br>integer [1..3600]<span class="asterisk">*</span></td>
<td>Frequency at which IP update requests are sent to the DNS provider.<br>The minimal amount of time that can be specified is 5 minutes and not less than <b>Check Interval</b>.</br><span class="asterisk">*</span>If selected interval is Hours or Days.</td>
</tr>
</table>
<br>
{{Template: Networking_rutx_manual_dynamic_dns_supported_dns_services_rut2_rut9}}
====cloudflare.com====
'''Note:''' To use subdomains with '''Cloudfare''' services, you must use the @ symbol.
service_name cloudflare.com-v4
domain [Your domain, here: example.com]
username Bearer
password [Your API token]
To use subdomains (CNAME or A records), use the format below when filling your credentials:
domain {subdomain}@[zone]
Examples:
If the hostname is “sample.example.com”, the “domain” field would be “[email protected]”
If the hostname is “dev1.sample.example.com”, the “domain” field would be “[email protected]”
If using Cloudflare's “Subdomain Support”, your zone may already be “foo.example.com”, so if the DDNS hostname is “bar.foo.example.com” the domain field would be “[email protected]”
==See also==
* Dynamic DNS configuration examples for specific providers:
** [[noip.com DDNS configuration|noip.com]]
** [[dnsdynamic.org DDNS configuration|dnsdynamic.org]]
** [[dynu.com DDNS configuration|dynu.com]]
** [[dyn.com DDNS configuration|dyn.com]]
[[Category:{{{name}}} Services section]]
