Like in request 2905241, should it be possible to pass manually (with an option in the command) a numeric IPv4 or IPv6.
In my application I cannot reserv a port to use the local server solution.
I've found such requests a bit curious, so please indulge me.
That is, if you know the ip, and you're going to update it manually, why do you need a dynamic dns program? That is, why don't you navigate to your dynamic dns service, and update your ip directly using your server's web interface? Alternatively, why not simply use a url in a web browser or some such?
Do you need it periodically update via forced update, for instance?
Please describe the scenario in which you need this, so I have a better idea about what's required.
Bryan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As of 02.24.49, this is in effect supported. And though this is an old request, as of 02.24.49, a response is now timely, and documentative.
You can cause the requested behavior with the custom DDNS server type by including the ($ALIAS) variable in parameter to --dyndns_server_url, along with the ip url parameter name, and corresponding ip. For example, assuming DDNS update url of /nic/update?, alias url parameter name of hostname, and ip url parameter name of myip:
For non basic auth DDNS servers, you can add to the url, ($USERNAME), ($PASSWORD) along with their corresponding url parameter names. For example, assuming user name url parameter name of usr, password url parameter name of pw:
I've found such requests a bit curious, so please indulge me.
That is, if you know the ip, and you're going to update it manually, why do you need a dynamic dns program? That is, why don't you navigate to your dynamic dns service, and update your ip directly using your server's web interface? Alternatively, why not simply use a url in a web browser or some such?
Do you need it periodically update via forced update, for instance?
Please describe the scenario in which you need this, so I have a better idea about what's required.
Bryan
Using web browser for automatic IP update is quite inconvenient. It's much better to do with an utility such as inadyn-mt.
As of 02.24.49, this is in effect supported. And though this is an old request, as of 02.24.49, a response is now timely, and documentative.
You can cause the requested behavior with the custom DDNS server type by including the ($ALIAS) variable in parameter to --dyndns_server_url, along with the ip url parameter name, and corresponding ip. For example, assuming DDNS update url of /nic/update?, alias url parameter name of hostname, and ip url parameter name of myip:
--dyndns_system custom@http_svr_basic_auth
--dyndns_server_name some.ddns_server.net
--dyndns_server_url /nic/update?hostname=($ALIAS)&myip=xxxx.xxxx.xxxx.xxxx
For non basic auth DDNS servers, you can add to the url, ($USERNAME), ($PASSWORD) along with their corresponding url parameter names. For example, assuming user name url parameter name of usr, password url parameter name of pw:
--dyndns_server_url /nic/update?hostname=($ALIAS)&myip=xxxx.xxxx.xxxx.xxxx&usr=($USERNAME)&pw=($PASSWORD)