TRB Noip.com DDNS configuration
Introduction
Dynamic DNS (DDNS or DynDNS) is a service, that automatically and periodically updates your DNS records when your IP address changes. 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 a guide on configuring a noip.com provider DDNS instance on TRB gateway.
Prerequisites
You will need:
- One TRB gateway
- At least one end device (PC, Laptop) to configure the gateway and DDNS provider
- Static or Dynamic Public IP address
How to know what IP address you have?
There is one mandatory precondition for DDNS to work, you must have a Static or Dynamic Public IP address. One of the easiest ways to check what IP address you have is to simply visit a website such as www.whatismyipaddress.com and compare the IP address shown there to the one you see in the gateway's WebUI. There are many ways how you can check what IP address your device has, a couple of those are:
- Go to gateway's WebUI Overview page and check that in one of the widgets.
- Go to Network → Interfaces page and check what IP address your WAN interface has.
If the IP address shown in www.whatismyipaddress.com is different to the one you see in the WebUI, it means that you're using a Shared Public IP and you won't be able to reach your device even if you would use DDNS.
Noip.com configuration
The first thing you will need to do is to visit the DDNS provider website. You can access it by entering www.noip.com/login to your internet browser's URL bar.
Then you will need to log in to your account. If you don't have a registered account yet, you will need to create one. You can do that by clicking the register button.
When you will log in to the website, you will be automatically forwarded to the Dashboard page, there you can create a new configuration by simply typing the hostname you want to use and then clicking the Add Hostname button.
You can preview the list of hosts you have created by clicking the Active button.
If you are using the device you are trying to set up as your WAN source when visiting this website, it should automatically assign your IP address to that hostname you have just created. If it does not, or you are using a different WAN source, you can change the IP address by pressing the Modify button.
Note: The IP/Target should be the same as the gateway's public IP.
TRB configuration
Log in to the gateway's WebUI by entering its LAN IP address to your internet browser's URL bar and then go Services → Dynamic DNS.
There create a new DDNS configuration by writing the Name and clicking Add button. Then you will be automatically forwarded to the new configuration settings.
Now apply the following configuration:
- Check the Enable box.
- Type your Lookup hostname.
- Select DDNS Service provider: no-ip.com
- Type your noip Domain.
- Type your noip Username.
- Type your noip Password.
- Set IP address source to Public.
- Click Save & Apply button.
Wait for about 5 minutes from the time you saved the changes. In the Status column, you should see the last time the DDNS was updated and whether the service is running. (If it does not change for a while, try changing the Check and Force intervals in DDNS settings, or reboot your gateway).
Results
One of the easiest ways to check whether the DDNS service works is by trying to access the gateway's WebUI by using it. In order to enable remote HTTP/HTTPS access go to System → Administration and after that click on Access Control. There check Enable remote HTTP/HTTPS access boxes and click Save
Try to access the gateway by entering the hostname in your internet browser's URL bar.
Note: you won't be able to access your gateway's WebUI through WAN if you are using the same device as your WAN source. You will need to use a different WAN source to do that.