If a port number is included in the 'server' configuration item,
ddclient allows a port number to be specified by appending a colon
and the port number to the server's name or IPv4 address. However,
nsupdate does not support this syntax, it requires the port number
to be separated from the server name/address by whitespace.
Signed-off-by: Kevin P. Fleming <kevin@km6g.us>
The extra comma bleeds into the API request sent to Cloudflare and, as a
result, causes it to fail. Reordering the options and removing the comma
at the password fliield, fixes this problem.
This makes the Cloudflare support IPv6-aware.
Ideally, A and AAAA records would be updated in one shot, as CloudFlare has a 5 minute throttling limit for API calls that change records.
Merge pull request #56 from d235j/cloudflare-ipv6
Example config showing how to retrieve IP from fritzbox via UPnP
using ddclients cmd option. The script has been provided by @Rusk85
in pull request #45
Cloudflare Config fix from #44.
Specifying the `server` directive caused the Cloudflare protocol to use the wrong url when communicating with Cloudflare API v4. It works if the directive is removed.
fix nsupdate using wrong type for ipv6 addresses
nsupdate was failing because it was trying to set an A record with an ipv6 address. This will check for an ipv6 address and use the appropriate record type.
Add support for telling `nsupdate` to use TCP instead of UDP
By default, `nsupdate` uses UDP unless the update size is too large to fit in a UDP datagram, in which case it automatically switches to TCP. This change adds a `tcp` configuration option to the `nsupdate` protocol so that the user can force `nsupdate` to use TCP.
By default, `nsupdate` uses UDP unless the update size is too large to fit in a UDP datagram, in which case it automatically switches to TCP. This change adds a `tcp` configuration option to the `nsupdate` protocol so that the user can force `nsupdate` to use TCP.
Fix based on pull request #31 on github commited by @hank.
_original comments_
When FreeDNS was updating, I was noticing that it would send back an HTTP 200
with the text "Address [IP] has not changed", but ddclient was issuing a
failed status for this and logging a ton of text to syslog. I changed the
function a tiny bit to allow this to be a success status. I also reformatted
the code to all spaces instead of mixed spaces and tabs, but you can take that
or leave it - I don't really care, it was just a total whitespace disaster
before.
Before this update, freedns warnings would appear in the log even though
FreeDNS sent back a code 200 with a message indicating the IP address was
already correct. A simple regex change was all that was needed to make this a
success instead. Now, it looks like this:
DEBUG: server = freedns.afraid.org
SUCCESS: updating xxx.xxx.xxx good: IP address has not changed
Conflicts:
ddclient
Adding configurable TTL to Cloudflare
This change adds configurable TTL to cloudflare instead of just using hardcoded value of 1 which sets "automatic" TTL any time ddclient updates the IP address.
git-svn-id: svn+ssh://svn.code.sf.net/p/ddclient/code/trunk@195 3873ddee-7413-0410-b6c4-c2c57c1ab35a
Adding duckdns example
Duckdns example added to sample-etc_ddclient.conf
git-svn-id: svn+ssh://svn.code.sf.net/p/ddclient/code/trunk@194 3873ddee-7413-0410-b6c4-c2c57c1ab35a
