Difference between revisions of "Template:Networking rut manual dynamic dns"

From Teltonika Networks Wiki
(→‎See also: added address: dyndnss.net)
Line 1: Line 1:
−
__TOC__
+
{{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==
  
Line 6: Line 11:
 
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.  
−
 
 
−
{{Template: Networking_rutxxx_manual_fw_disclosure
 
−
| fw_version = {{{fw_version}}}
 
−
}}
 
  
 
==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==
Line 22: Line 26:
 
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">
Line 34: Line 40:
 
     <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>
−
    <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>
Line 103: Line 136:
 
==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]]
−
**dyndnss.net (3 Addresses free)
 
  
−
[[Category:{{{name}}}<nowiki> Services section]]</nowiki>
+
[[Category:{{{name}}} Services section]]

Revision as of 11:34, 16 September 2020

The information in this page is updated in accordance with the [[Media:_WEBUI.bin|]] 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 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 following 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 New configuration name and clicking the Add New button or you can edit the existing instance since it is not operational by default.

File:Networking rutxxx manual dynamic dns overview v1.png

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 router by default) and the table below provides information on the configuration fields contained in that page:

File:Networking rut9xx manual dynamic dns v1.png

no; default: no
field name value description
Enable yes | no; default: no Turns the DDNS instance On or Off.
Use HTTP Secure yes | no; default: no Enables SSL data encryption.
Use IPv6 for this configuration.
Status string; default: N/A 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.
Service third party DNS service (chosen from list*) | -- custom --; default: dyn.com Third party DNS service provider.
Lookup host 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).
Hostname host; default: yourhost.example.com Hostname that will be linked with the router's 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. 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 Private.
Custom: Network LAN | WAN | WAN2 | WAN3 | PPP | PPP_USB ; default: WAN Specifies which interface's IP address should be bound to the hostname.
Public: URL to detect host; default: http://checkip.dyndns.com URL which is used to get your device's public IP from.
Script: Script string; default: none User defined script your device which is used to get it's public IP from.
Script: Event Network network interfaces; default: WAN Network interface on which your script will be started.
IP renew interval integer [5..600000]; default: 10 Frequency at which the device will check whether it's IP address has changed.
IP renew interval unit Minutes | Hours | Days; default: Minutes Unit which is used in IP renew interval.
Force IP renew integer [5..600000]; default: 72 Frequency at which IP update requests are sent to the DNS provider.
Force IP renew unit Minutes | Hours | Days; default: Minutes Unit which is used in Force IP renew interval.


Template:Networking rutxxx manual dynamic dns supported dns services

See also

[[Category:{{{name}}} Services section]]

Retrieved from "https://wiki.teltonika-networks.com/index.php?title=Template:Networking_rut_manual_dynamic_dns&oldid=72043"