How to configure Custom DDNS on Omada Gateway via Omada Controller
Contents
Objective
This article introduces how to configure the Custom DDNS feature on Omada gateway via Omada Controller.
Requirements
- Omada Gateway series
- Omada Software Controller / Hardware Controller / Cloud-Based Controller
Introduction
DDNS, most commonly known as Dynamic DNS, is an automatic method of refreshing a name server. It can dynamically update DNS records via DDNS service provider without human interaction. The Custom DDNS feature allows you to user-define the DDNS service provider. Most Internet service providers (ISPs) assign a dynamic IP address to the gateway. However, the IP address can change at any time, and you don't know when it will change. In this case, you might need the DDNS feature on the gateway to allow you to access your gateway using the domain name instead of remembering the IP address. Omada Gateway has listed four DDNS service providers: Peanuthull, Comexe, DynDNS, and Noip. If you want to use a service provider other than these four, you can use the Custom DDNS feature.
Configuration
Step 1. Log in to the Controller via web browser, go to Settings > Services > Dynamic DNS, and click Create New Dynamic DNS Entry.
Step 2. Click the Service Provider drop list and choose Custom. Then select the Interface to set the WAN port you want to use for DDNS.
Step 3. Register with any service provider such as Duck DNS, ChangeIP, and Dynv6. Get your username, password, and domain name and enter the Username, Password and Domain Name of your account.
Step4. Choose the Interval Mode and Update Interval to define how often the update requests will send to DDNS server. It’s recommended to set a shorter interval than the WAN IP update cycle. If you find the update is not timely, further reduce the interval value as you need.
There are two options for Interval Mode, Fixed and Custom:
- Fixed: You can choose a fixed value at Update Interval. The minimum interval is 1 hour.
- Custom: If you want an update time shorter than 1 hour, check this option and configure the value in Update Interval.
- The Update Interval is generally to be set to 1 hour to meet most update requirements.
Step 5. Get the Update URL from your DDNS service provider and fill in the Update-URL. Click Create.
You need to check with your DDNS provider for the Update URL and fill it in according to the required format.
For example, the URL provided by GOIP is: https://www.goip.de/setip?username=XXXXX&password=XXXXX&subdomain=XXXXX&ip=XXXXX
Then you need to change it to the following URL: https://www.goip.de/setip?username=[USERNAME]&password=[PASSWORD]&subdomain=[DOMAIN]&ip=[IP]
Note: Generally, in the final URL, replace the fields for your username, password, domain and IP with [USERNAME], [PASSWORD], [DOMAIN] and [IP]. Make sure the four fields have been capitalized and enclosed in brackets.
Here we list some free providers for examples:
DDNS Service Provider |
Update URL |
Duck DNS |
https://[USERNAME]:[PASSWORD]@www.duckdns.org/update?domains=[DOMAIN]&token=xxx |
FreeDNS.afraid.org |
http://[USERNAME]:[PASSWORD]@freedns.afraid.org/nic/update?hostname=[DOMAIN]&myip=[IP] |
EasyDNS |
http://[USERNAME]:[PASSWORD]@api.cp.easydns.com/dyn/tomato.php?hostname=[DOMAIN]&myip=[IP] |
ChangeIP |
http://[USERNAME]:[PASSWORD]@nic.changeip.com/nic/update?hostname=[DOMAIN] |
Dynv6 |
http://[USERNAME]:[PASSWORD]@dynv6.com/api/update?hostname=[DOMAIN]&token=gkSVdSh6w1XvGoTJ7z6G-mzxscnfD_&ipv4=[IP] |
DNSExit |
http://update.dnsexit.com/RemoteUpdate.sv?login=[USERNAME]&password=[PASSWORD]&host=[DOMAIN] |
duiadns |
https://[USERNAME]:[PASSWORD]@ip.duiadns.net/dynamic.duia?host=[DOMAIN]&password=[PASSWORD] |
Verification
Step 1. Go to Insights > Dynamic DNS to check the STATUS of DDNS.
Note: The STATUS will show the return code from your service provider, which is different for each service provider. You need to check with your DDNS provider for the meaning of each return code.
Step 2. Use nslookup command to check if the DDNS is working.
For example, if your DDNS domain name is xxxxx.changeip.co, then you could input “nslookup xxxxx. changeip.co” at the command prompt window, and then press enter to check if the correct IP address can be resolved.
Here is an example using the Windows command prompt.
Conclusion
You have now successfully configured Custom DDNS on Omada Gateway.
Get to know more details of each function and configuration please go to Download Center to download the manual of your product.
FAQ
Why is the DDNS domain name not my Gateway WAN IP address?
Re: Since the DDNS domain name is bound to the real public IP address, if your gateway's WAN IP address is a private address or CGNAT address, the IP address bound to the DDNS will differ from your Gateway WAN IP address. For LTE gateways working in 3G/4G mode, a SIM card is used to access the Internet. If the WAN IP is not a public IP, the front NAT is on your ISP side, so you cannot open the relevant ports on the front NAT product. Please contact your ISP to see if they can directly assign a public IP address to you.
Is this faq useful?
Your feedback helps improve this site.
TP-Link Community
Still need help? Search for answers, ask questions, and get help from TP-Link experts and other users around the world.