Template:Networking rutos manual dynamic dns: Difference between revisions

Latest revision as of 12:29, 5 April 2024

The information in this page is updated in accordance with firmware version .

Summary

Dynamic DNS (DDNS or DynDNS) 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 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.

Dynamic DNS Overview

By default, an unconfigured DDNS instance will be present in the Dynamic DNS Overview 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.

Editing a DDNS instance

To configure a DDNS instance, click the "Edit" 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]]

Field	Value	Description
Enabled	off \| on; Default: off	Turns the DDNS instance on or off.
Lookup hostname	host; Default: yourhost.example.com	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).
DDNS service provider	third party DNS service (chosen from list) \| -- custom --; Default: dyn.com*	Third party DNS service provider.
Domain	host; Default: yourhost.example.com	Hostname that will be linked with the device IP address.
Username	string; Default: your_username	User name required to login to the third party DNS service; used to periodically login to your DNS service account and make necessary updates.
Password	string; Default: your_password	Password required to login to the third party DNS service; used to periodically login to your DNS service account and make necessary updates.
IP address source	Custom \| Public \| Private \| Script; Default: Custom	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 Private.
Network	network interface; Default: lan	Specifies which interface's IP address should be bound to the hostname
Check Interval	integer [5..3600]; Default: 10 integer [300..3600]* integer [1..3600]**	Frequency at which the device will check whether it's IP address has changed. The minimal amount of time that can be specified is 5 minutes or 300 seconds. If selected interval is Seconds. *If selected interval is Hours.
Force Interval	integer [5..3600]; Default: 10 integer [1..3600]*	Frequency at which IP update requests are sent to the DNS provider. The minimal amount of time that can be specified is 5 minutes and not less than Check Interval. *If selected interval is Hours or Days.

* Supported DNS services
3322.org	able.or.kr	afraid.org-basicauth	afraid.org-keyauth	afraid.org-v2-basic	afraid.org-v2-token	all-inkl.com	bind-nsupdate
binero.se	changeip.com	cloudflare.com-v4	core-networks.de	ddns.com.br	ddnss.de	ddo.jp	desec.io
dhis.org	dnsdynamic.org	dnsever.com	dnsexit.com	dnshome.de	dnsmadeeasy.com	dnsmax.com	dnsomatic.com
dnspark.com	do.de	domopoli.de	dtdns.com	duckdns.org	duiadns.net	dy.fi	dyn.com
dyndns.it	dyndns.org	dyndnss.net	dyns.net	dynsip.org	dynu.com	dynv6.com	easydns.com
editdns.net	goip.de	google.com	he.net	joker.com	loopia.se	mydns.jp	myip.com.ua
myonlineportal.net	mythic-beasts.com	namecheap.com	nettica.com	noip.com	no-ip.pl	now-dns.com	nsupdate.info
nubem.com	opendns.com	oray.com	ovh.com	regfish.de	schokokeks.org	secure.camera	selfhost.de
sitelutions.com	spdns.de	spdyn.de	strato.com	system-ns.com	thatip.com	twodns.de	umedia.de
variomedia.de	xlhost.de	zerigo.com	zoneedit.com	zzzz.io

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]”

@@ Line 1: / Line 1: @@
 <!-- Template uses {{{name}}}, {{{series}}}-->
-{{Template:Networking_rutos_manual_fw_disclosure
+{{Template: Networking_device_manual_fw_disclosure
-| fw_version = {{{series}}}_R_00.02.03
 | 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>|}}
-__TOC__
+{{#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==
@@ Line 15: / Line 18: @@
 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==
@@ Line 22: / Line 32: @@
 clicking the "Add" button or you can edit the existing instance since it is not operational by default.
-[[File:Networking_rutx_manual_dynamic_dns_overview_v1.png]]
+[[File:Networking_rutos_manual_dynamic_dns_overview_v2.png|border|class=tlt-border]]
 ==Editing a DDNS instance==
@@ Line 28: / Line 38: @@
 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:
+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_rutx_manual_dynamic_dns_configuration_v2.png|border|class=tlt-border]]
+[[File:Networking_rutos_manual_dynamic_dns_details_for_network_v2_{{{network}}}.png|border|class=tlt-border]]
 <table class="nd-mantable">
@@ Line 75: / Line 86: @@
      <tr>
        	<td>Network</td>
-        	<td>network interface; Default: <b>WAN</b></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..600000]; Default: <b>10</b></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.</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..600000]; Default: <b>72</b></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.</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}}
+====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==