@Clive_A 

Thank you for your reply. I have spend several hours with IONOS in attempting to resolve this issue. According to TP-Link's support website (community.tp-link.com/en/business/forum/topic/636198) there are several examples of configuring the update URL to accommodate the key or token:

EasyDNS:

http://[USERNAME]:[PASSWORD]@api.cp.easydns.com/dyn/tomato.php?hostname=[DOMAIN]&myip=[IP]

Dynu:

https://api.dynu.com/nic/update?hostname=[DOMAIN]&alias=your-alias-if-any&username=[USERNAME]&password=[PASSWORD]

DNS-O-MATCI

https://[USERNAME]:[PASSWORD]@updates.dnsomatic.com/nic/update?hostname=[DOMAIN]

OVH:

https://[USERNAME]:[PASSWORD]@ovh.com/nic/update?system=dyndns&hostname=[DOMAIN]&myip=[IP]

Joker:

https://svc.joker.com/nic/update?username=[USERNAME]&password=[PASSWORD]&myip=[IP]&hostname=[DOMAIN]

ChangeIP:

https://[USERNAME]:[PASSWORD]@nic.changeip.com/nic/update?hostname=[DOMAIN]&myip=[IP]

Ipv64:

https://[USERNAME]:[PASSWORD]@ipv64.net/nic/update?key=your-key&hostname=[DOMAIN]

Dynv6:

http://[USERNAME]:[PASSWORD]@dynv6.com/api/update?hostname=[DOMAIN]&token=your-token&password=[password]sipv4=[IP]

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]

The question still stands as asked... 

When placing the string into the Update URL box, it cuts off the last part of the string, which looks like is a string length limitation on the ER605. 

Has anyone successfully utilized IONOS for this function? I already use DyDNS for updating my DDNS but I am attempting to minimize the number of disparate resources currently in use for my setups. Looking at the examples above, it looks like the ER605 does have the ability  to utilize the key or token.

  @bssanders 

Hi, sorry but I have no experience with IONOS.

I do use FreeDNS (no token, just login and password) and it works without any issues.

I also use DuckDNS and it works as well. This one require TOREK, for me it is 36 characters and there's no issue with lentgh.

I do recall however that I had an issue with password field there. It could handle only 32 characters, my (auto generated) password was 36 so I had to skip using dedicated field and put the pass directly into the update link instead...

But still, whole link was handled properly by TP-Link system.

I know it doesn't help much, sorry. :(

  @RaRu 

Thanks for your reply. I am hoping that someone will have experience with this issue. I have also placed an inquiry with TP-Link directly (response in 24 hours!) several days ago and no feedback as of yet.

  @bssanders 

bssanders wrote

  @Clive_A 

 

Thank you for your reply. I have spend several hours with IONOS in attempting to resolve this issue. According to TP-Link's support website (community.tp-link.com/en/business/forum/topic/636198) there are several examples of configuring the update URL to accommodate the key or token:

 

EasyDNS:

http://[USERNAME]:[PASSWORD]@api.cp.easydns.com/dyn/tomato.php?hostname=[DOMAIN]&myip=[IP]

 

Dynu:

https://api.dynu.com/nic/update?hostname=[DOMAIN]&alias=your-alias-if-any&username=[USERNAME]&password=[PASSWORD]

 

DNS-O-MATCI

https://[USERNAME]:[PASSWORD]@updates.dnsomatic.com/nic/update?hostname=[DOMAIN]

 

OVH:

https://[USERNAME]:[PASSWORD]@ovh.com/nic/update?system=dyndns&hostname=[DOMAIN]&myip=[IP]

 

Joker:

https://svc.joker.com/nic/update?username=[USERNAME]&password=[PASSWORD]&myip=[IP]&hostname=[DOMAIN]

 

ChangeIP:

https://[USERNAME]:[PASSWORD]@nic.changeip.com/nic/update?hostname=[DOMAIN]&myip=[IP]

 

Ipv64:

https://[USERNAME]:[PASSWORD]@ipv64.net/nic/update?key=your-key&hostname=[DOMAIN]

 

Dynv6:

http://[USERNAME]:[PASSWORD]@dynv6.com/api/update?hostname=[DOMAIN]&token=your-token&password=[password]sipv4=[IP]

 

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]

 

The question still stands as asked... 

When placing the string into the Update URL box, it cuts off the last part of the string, which looks like is a string length limitation on the ER605. 

 

Has anyone successfully utilized IONOS for this function? I already use DyDNS for updating my DDNS but I am attempting to minimize the number of disparate resources currently in use for my setups. Looking at the examples above, it looks like the ER605 does have the ability  to utilize the key or token.

No. It does not utilize the key/token.

Your DDNS service provider uses the token/key. You simply fill in the blank key in the format. The key/token part is untouched or used by our router.

What does our router utilize? It utilizes the username and password, which is what I am repeating and emphasizing.

Check with your provider if they could use a username and password method.

All the information above is provided by the forum users who contacted their provider and confirmed that they require both username and password and the key/token.

If you don't try to work with your provider, I am not able to confirm what format their server accepts.

Regarding the string length, in standalone, there is a limit and we are aware of that.

In controller mode, the string length should be longer, as I recall. Most contributions from the forum users are under the controller managed context.

  @bssanders 

Thanks to the Omada Case Portal Support group, this issue has been resolved. Specically, the Update URL required has the construction of the following syntax:

(http) + ://[USERNAME]:[PASSWORD]@ipv4.api.hosting.ionos.com/dns/v1/dyndns?q=YOUR_TOKEN&hostname=[DOMAIN]&myip=[IP]

Note that for IONOS functionality, the token (or key) is utilized by using the "q=" with your provided token (or key) that IONOS created with the API function. I might suggest that you ADD the IONOS string to use in the following topic (community.tp-link.com/en/business/forum/topic/636198) so as if anyone should be looking for a solution it is easy to find.

Lastly, to Clive_A your reply is confusing as I understand the functionality of the router DDNS setting. I was asking for syntax assistance knowing that there would be a specific construction that would trigger the update. IONOS uses an API function to create the Update URL. I am hoping that this will make it easier for someone in the future to find the exact structure which allows the router to function with DDNS from IONOS.

Thanks to all for your help.

  @bssanders 

Thanks for your presistence to solve this :)