Introduction
This FAQ provides guidance on the Dynamic DNS (DDNS) functionality available on Fusion AIO 1.0 Gateways using the Omada App. DDNS enables users to maintain reliable remote access to gateways, servers, NAS devices, VPNs, surveillance systems, and other network services, even when public IP addresses change dynamically.
By automatically updating a domain name to reflect the gateway's current public IP address, DDNS eliminates the need to manually track IP address changes and provides a consistent hostname for remote connectivity. Fusion Gateway supports both TP-Link DDNS and multiple third-party DDNS providers, allowing users to select the service that best fits their deployment requirements.
This article explains how to configure DDNS using the Omada App, including provider selection, binding modes, domain configuration, verification, and troubleshooting considerations.
Requirements
- Fusion AIO Gateway
- Omada App 5.2.1 or greater
Configuration Steps
Step 1. Open the Omada App, open the Site of the Fusion Gateway and navigate to Settings > Dynamic DNS.
Step 2. Select Add Dynamic DNS.
Step 3. Select Service Provider > Choose the appropriate service provider: TP-Link DDNS or Third-Party DDNS. Select Done.
Note: The Service Provider setting supports the selection of either TP-Link DDNS or Third-Party DDNS. Third-Party DDNS includes both predefined third-party service providers and a Custom option. When TP-Link DDNS is selected, additional configuration items specific to the TP-Link DDNS service are displayed for setup and management.
If Third-Party DNS is selected, several new options will appear.
TP-Link DDNS
TP-Link DDNS is a built-in Dynamic DNS service that automatically associates your changing public IP address with a fixed hostname, allowing consistent remote access to your network. The service integrates with TP-Link's DDNS platform and requires Cloud Access to be enabled. TP-Link DDNS is unavailable when Cloud Access is disabled.
Other Service Provider options:
- DynDNS: A commercial Dynamic DNS provider that allows remote access to your network using a hostname instead of an IP address.
- NO-IP: A popular Dynamic DNS service offering free and paid hostnames for accessing devices behind a changing IP address.
- Peanuthull: A third-party Dynamic DNS provider supported by some routers, primarily used by customers who already have a Peanuthull DDNS account.
- Comexe: A third-party Dynamic DNS service that provides hostname-to-IP updates for remote network access.
- Custom: Allows manual configuration of a Dynamic DNS provider that is not listed, using custom update URLs and authentication settings.
This is an example of the customization options after selecting Custom for DNS Service Provider. Other options differ slightly, depending on the Service Provider selected.
Add Dynamic DNS
- Interface: Choose the WAN/Internet connection whose public IP address will be associated with the DDNS hostname.
- Domain: Enter the hostname registered with your DDNS provider.
- Username: Enter the username or account email associated with your DDNS provider.
- Password: Enter the password, API key, or update token required by your DDNS provider.
- Update URL: Specify the DDNS provider's update endpoint used to submit IP address updates (typically required for Custom DDNS providers).
- Update Interval: Defines how often the router checks for IP address changes and updates the DDNS service. A custom Time interval can be selected here.
Step 4. If using TP-Link DDNS, select Binding Mode and choose the preferred Binding Mode. Select either Auto or Manual. When selecting Manual, an Interface option will appear.
Note: Only when the service provider is TP-Link DDNS, can Binding Mode be selected.
Binding Mode:
The Binding Mode setting supports two options, Auto and Manual, with Auto selected by default. When Auto mode is selected, the backend dynamically determines the appropriate WAN interface and automatically binds the DDNS service to a single domain.
- When selecting Manual:
- Users can manually bind WAN and Domain to create multiple entries, with a maximum of one per WAN, and domain names for different entries cannot be duplicated.
- By default, only one domain is displayed; supports adding multiple entries, manifested as a Domain List
Step 5. Configure the Domain and any remaining fields (this depends on the selected Service Provider). The Domain is the hostname registered with your Dynamic DNS service. It is the address that will automatically update to point to your current public IP address. Select Save when complete.
Domain:
The Domain field specifies the hostname that will be associated with your router's public IP address. DDNS automatically updates this hostname whenever your public IP changes, allowing you to access your network using a consistent address (for example, myvpn.tplinkdns.com) instead of having to remember or track a changing IP address.
Verification
Once configuration is complete the new DDNS entry will be added to the Dynamic DNS page. Multiple DDNS may be configured.
Dynamic DDNS Configuration
Dynamic DNS is displayed in two sections: TP-Link DDNS and Third-Party.
- The number of WAN-to-domain mappings that DDNS can support is determined by the number of available WAN ports. WAN ports using DS-Lite or MAP-E dialing methods are not supported for creating WAN-to-domain mappings. Each DDNS entry must be associated with a dedicated WAN interface that has its own public IP address.
Green Check Circle indicates Connected or Normal connection.
Green Loading Circle icon indicates a pending or configuring connection status.
Red Exclamation Circle indicates Disconnected or Abnormal connection.
- Clicking the Red Exclamation Circle will show a popup with an error message.
All status indicators are clickable to display the current status of the Dynamic DNS service.
Conclusion
We have successfully learned how to configure DDNS using the Omada App with Fusion Gateway.
QA
Q1: What is Dynamic DNS (DDNS)?
A: DDNS automatically updates a hostname to match your current public IP address, allowing reliable remote access to your network and devices even when your ISP changes your IP address.
Q2: Which DDNS providers are supported in the Omada App?
A: The Omada App supports TP-Link DDNS and several third-party providers, including DynDNS, NO-IP, Peanuthull, Comexe, and Custom DDNS services.
Q3: What is the difference between Auto and Manual Binding Mode?
A: Auto mode automatically binds the DDNS domain to the active WAN interface and provides failover support. Manual mode lets you bind a specific domain to a specific WAN interface.
Q4: What is the DDNS Provider Domain?
A: The DDNS Provider Domain is the hostname registered with your DDNS provider (for example, myhome.ddns.net) that will be updated to point to your current public IP address.
Q5: What do the DDNS status icons mean?
A: A Green Check Circle indicates the DDNS service is connected and operating normally, a Red Exclamation Circle indicates a connection or configuration issue and a Green Loading Circle indicates a pending or configuring connection status.
Q6: Can I configure multiple DDNS entries?
A: Yes. The number of WAN-to-domain mappings that DDNS can support is determined by the number of available WAN ports. WAN ports using DS-Lite or MAP-E dialing methods are not supported for creating WAN-to-domain mappings. Each DDNS entry must be associated with a dedicated WAN interface that has its own public IP address.
To learn more about each function and configuration, please visit Support Home to download or check the manual for your product.
