TP-Link ER7206 Gateway No...
TP-Link ER7206 Gateway No Longer Updates Custom DDNS
- Casa
- Pannello di controllo
- Forum della Comunità
- Services
- Dynamic DNS Service
- TP-Link ER7206 Gateway No Longer Updates Custom DDNS
- Forum della Comunità
- TP-Link ER7206 Gateway No Longer Updates Custom DDNS
Argomento: TP-Link ER7206 Gateway No Longer Updates Custom DDNS
This was working, now it's not.
The TP-Link ER7206 router is using "Custom DNS" with the Update URL:
https://api.dynu.com/nic/update?username=[USERNAME]&password=[PASSWORD]&hostname=[DOMAIN]
There are 2 WAN ports (WAN and WAN/LAN3) that are configured as load balancing between two different ISP (Charter & Frontier).
But, the "Custom DNS" profile only allows one or the other, but not both and I've been using Charter.
About 2 months ago SNMP traps saying the update failed with "badauth" started coming in.
Today, I tried changing from Charter to Frontier and it is still "badauth". I'm back to Charter and no luck there either.
I added a new API key, and that didn't help.
Any clues?
The TP-Link ER7206 router is using "Custom DNS" with the Update URL:
https://api.dynu.com/nic/update?username=[USERNAME]&password=[PASSWORD]&hostname=[DOMAIN]
There are 2 WAN ports (WAN and WAN/LAN3) that are configured as load balancing between two different ISP (Charter & Frontier).
But, the "Custom DNS" profile only allows one or the other, but not both and I've been using Charter.
About 2 months ago SNMP traps saying the update failed with "badauth" started coming in.
Today, I tried changing from Charter to Frontier and it is still "badauth". I'm back to Charter and no luck there either.
I added a new API key, and that didn't help.
Any clues?
Rispondi con citazione |Segnalare
| Autore | Argomento: TP-Link ER7206 Gateway No Longer Updates Custom DDNS |
|---|---|
|
ticedoff8 Iscritto: 13/04/2021 |
martedì 27 ottobre 2026 14:01
This was working, now it's not.
The TP-Link ER7206 router is using "Custom DNS" with the Update URL: https://api.dynu.com/nic/update?username=[USERNAME]&password=[PASSWORD]&hostname=[DOMAIN] There are 2 WAN ports (WAN and WAN/LAN3) that are configured as load balancing between two different ISP (Charter & Frontier). But, the "Custom DNS" profile only allows one or the other, but not both and I've been using Charter. About 2 months ago SNMP traps saying the update failed with "badauth" started coming in. Today, I tried changing from Charter to Frontier and it is still "badauth". I'm back to Charter and no luck there either. I added a new API key, and that didn't help. Any clues? |
martedì 27 ottobre 2026 17:02
