Dynu Custom DDNS compatib...
Dynu Custom DDNS compatibility with TP-Link Omada
- Casa
- Pannello di controllo
- Forum della Comunità
- Services
- Dynamic DNS Service
- Dynu Custom DDNS compatibility with TP-Link Omada
- Forum della Comunità
- Dynu Custom DDNS compatibility with TP-Link Omada
Argomento: Dynu Custom DDNS compatibility with TP-Link Omada
Hello,
I am trying to use Dynu Dynamic DNS with a TP-Link ER707-M2 router managed by Omada Controller.
Environment
TP-Link ER707-M2
Firmware: 1.4.2 Build 20260509 Rel.32107
Omada Controller: 6.2.10.17
Hostname: XXXX.mywire.org
I have verified the following:
The hostname resolves correctly.
The Dynu API works correctly.
Running:
curl "https://api.dynu.com/nic/update?hostname=XXXX.mywire.org&password=<IP_UPDATE_PASSWORD>"
returns good or nochg.
The router has Internet connectivity and can successfully ping api.dynu.com.
I also configured a Webhook.site URL instead of the Dynu API to verify whether the router sends any HTTP request.
Webhook.site never receives any request ("Waiting for the first request"), while the router reports the DDNS status as "Offline".
My questions are:
Have you seen compatibility issues with TP-Link Omada ER707-M2 Custom DDNS?
Is there any known workaround?
Do you know of any customers successfully using Dynu Custom DDNS with an ER707-M2?
Does Dynu require any URL format or HTTP behavior that is incompatible with TP-Link Omada Custom DDNS?
At the moment I am using a Linux cron job to update Dynu successfully, but I would prefer to use the router's native DDNS implementation.
Thank you.
I am trying to use Dynu Dynamic DNS with a TP-Link ER707-M2 router managed by Omada Controller.
Environment
TP-Link ER707-M2
Firmware: 1.4.2 Build 20260509 Rel.32107
Omada Controller: 6.2.10.17
Hostname: XXXX.mywire.org
I have verified the following:
The hostname resolves correctly.
The Dynu API works correctly.
Running:
curl "https://api.dynu.com/nic/update?hostname=XXXX.mywire.org&password=<IP_UPDATE_PASSWORD>"
returns good or nochg.
The router has Internet connectivity and can successfully ping api.dynu.com.
I also configured a Webhook.site URL instead of the Dynu API to verify whether the router sends any HTTP request.
Webhook.site never receives any request ("Waiting for the first request"), while the router reports the DDNS status as "Offline".
My questions are:
Have you seen compatibility issues with TP-Link Omada ER707-M2 Custom DDNS?
Is there any known workaround?
Do you know of any customers successfully using Dynu Custom DDNS with an ER707-M2?
Does Dynu require any URL format or HTTP behavior that is incompatible with TP-Link Omada Custom DDNS?
At the moment I am using a Linux cron job to update Dynu successfully, but I would prefer to use the router's native DDNS implementation.
Thank you.
Rispondi con citazione |Segnalare
| Autore | Argomento: Dynu Custom DDNS compatibility with TP-Link Omada |
|---|---|
|
mystic889 Iscritto: 30/06/2026 |
martedì 30 giugno 2026 23:30
Hello,
I am trying to use Dynu Dynamic DNS with a TP-Link ER707-M2 router managed by Omada Controller. Environment TP-Link ER707-M2 Firmware: 1.4.2 Build 20260509 Rel.32107 Omada Controller: 6.2.10.17 Hostname: XXXX.mywire.org I have verified the following: The hostname resolves correctly. The Dynu API works correctly. Running: curl "https://api.dynu.com/nic/update?hostname=XXXX.mywire.org&password=<IP_UPDATE_PASSWORD>" returns good or nochg. The router has Internet connectivity and can successfully ping api.dynu.com. I also configured a Webhook.site URL instead of the Dynu API to verify whether the router sends any HTTP request. Webhook.site never receives any request ("Waiting for the first request"), while the router reports the DDNS status as "Offline". My questions are: Have you seen compatibility issues with TP-Link Omada ER707-M2 Custom DDNS? Is there any known workaround? Do you know of any customers successfully using Dynu Custom DDNS with an ER707-M2? Does Dynu require any URL format or HTTP behavior that is incompatible with TP-Link Omada Custom DDNS? At the moment I am using a Linux cron job to update Dynu successfully, but I would prefer to use the router's native DDNS implementation. Thank you. |
martedì 7 luglio 2026 02:01
