Troubleshooting Custom DDNS Is Not Working
This Article Applies to:
All routers with custom DDNS.
Application Scenario:
Issue Description:
Unable to sync with the DDNS server and resolve the domain name shows incorrect IP address.
After configuring the custom DDNS, the status shows offline or disconnected.
Troubleshooting:
1. Examine your Username and Password.
Confirm your Username and Password for the sync is correct. So that the server can successfully sync with your correct credentials.
2. Double-check the Update-URL.
The Update-URL format could be wrong. Contact your DDNS service provider for the correct Update-URL format. Or search on their FAQ or manual. Their URL may change after a period of time. Any posts are not as accurate as their latest FAQ or manual.
Update URL: Enter the URL provided by your DDNS service provider in format of “http://[USERNAME]:[PASSWORD]@api.cp.easydns.com/dyn/tomato.php?hostname=[DOMAIN]&myip=[IP]”. The router will automatically update user information to the service provider.
3. Check if your DDNS provider offers a token to your URL format.
Certain DDNS providers will insert a token to identify the registration. If there is a token, you need to input the token in the Update-URL. For the detailed steps, refer to the provider's FAQ or manual.
4. Check the DDNS server status with your DDNS provider.
Before raising the issue to the community or support, confirm the server status with your DDNS provider.
Note:
1. WAN Status should be Online. If it is Offline, the DDNS is not gonna sync correctly.
2. Common DDNS providers' URLs in Omada Controller:
Ipv64:
https://[USERNAME]:[PASSWORD]@ipv64.net/nic/update?key=your-key&hostname=[DOMAIN]
Dynv6:
GoIP:
https://www.goip.de/setip?username=[USERNAME]&password=[PASSWORD]&subdomain=[DOMAIN]&ip=[IP]
FreeDNS:
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]
Dynu:
DNS-O-MATCI
https://[USERNAME]:[PASSWORD]@updates.dnsomatic.com/nic/update?hostname=[DOMAIN]
Update Log:
Feb 20th, 2024:
Update the format.
Jan 11th, 2024:
Update the format.
Recommended Threads:
Troubleshooting Custom DDNS Is Not Working
Feedback:
- If this was helpful, welcome to give us Kudos by clicking the upward triangle below.
- If there is anything unclear in this solution post, please feel free to comment below.
- If you encounter such an issue, please follow the troubleshooting above to check your settings. Besides, ensure your Omada Controller and Gateway are running with the latest firmware.
- If the issue still exists after you try the suggestion above, please feel free to comment below or contact our support team with a detailed description of your issue and the steps you have tried.
Thank you in advance for your valuable feedback!
------------------------------------------------------------------------------------------------
Have other off-topic issues to report?
Welcome to > Start a New Thread < and elaborate on the issue for assistance.