1
Votes

Why wont TPLink support "Direct URL" DDNS updating? It's more secure and private...

 
1
Votes

Why wont TPLink support "Direct URL" DDNS updating? It's more secure and private...

Why wont TPLink support "Direct URL" DDNS updating? It's more secure and private...
Why wont TPLink support "Direct URL" DDNS updating? It's more secure and private...
Saturday - last edited Monday

DDNS methods include: sending username password and domain in the clear; and "direct-URL" method where a token is sent from the gateway and automatically picks up the source IP. 

 

Why doesn't TP-LInk support the direct-URL method? 

 

I use afraid/OpenDNS and it would be much easier and more secure to support this (quite easy) method, under custom as an option, or just add an entry of "Direct URL Custom"

 

I don't like exposing my OpenDNS password in the DDNS access.

#1
Options
1 Reply
Re:Why wont TPLink support "Direct URL" DDNS updating? It's more secure and private...
Monday - last edited Monday

  @Babylonfive 

Thank you for your post. At present, we indeed do not support the direct-URL (token-only, no-password) DDNS update method. However, your request has been forwarded to the Requests & Suggestions module, which means it may be evaluated for inclusion in a future release.Your feedback and ideas are truly valued. At this point, we can’t confirm whether this enhancement will be rolled out  or provide a timeline, but rest assured, I’ve noted your request and will forward it to the development team. If you have any additional suggestions, don’t hesitate to drop them here; we’re always glad to pass them along.

#2
Options