Cloudflare DynDNS update error
-
Try applying the change in this diff and see if it works for you: Updated cf-ttl.diff
EDIT: Updated diff
-
@jimp said in Cloudflare DynDNS update error:
https://redmine.pfsense.org/issues/10196
My Google-fu has failed me!
@jimp said in Cloudflare DynDNS update error:
Try applying the change in this diff and see if it works for you: cf-ttl.diff
I reverted my patch and tried to apply this one, but it failed to update the address with the following log:
/services_dyndns_edit.php: phpDynDNS (vr): PAYLOAD: { "result": null, "success": false, "errors": [ { "code": 1000, "message": "There was an unknown error." } ], "messages": [] }
The Cloudflare API requires an integer for the ttl, so I changed your patch this way and it worked:
"ttl" => empty($this->_dnsTTL) ? 1 : int($this->_dnsTTL)
-
OK, I'll change it that way. Thanks!
-
Actually it looks like that should be
(int) $this->_dnsTTL
orintval($this->_dnsTTL)
. -
You're right. I think
int("123")
is deprecated. -
I updated the diff in my previous post above
-
Is it also working for manually update? I tried to "Save and force update" again and I have stillt the same issue. I used this diff:
https://redmine.pfsense.org/attachments/2922/cf-ttl.diff
/services_dyndns_edit.php: phpDynDNS (@): UNKNOWN ERROR - Invalid TTL. Must be between 120 and 2,147,483,647 seconds, or 1 for automatic
-
It should not matter how it is triggered. Make sure that diff actually applied (edit /etc/inc/dyndns.class and see if the TTL line is there)
-
@jimp said in Cloudflare DynDNS update error:
I updated the diff in my previous post above
Thanks.
(it appears the changes on Redmine still has the old non-integer ttl, though). -
@LucaTNT said in Cloudflare DynDNS update error:
(it appears the changes on Redmine still has the old non-integer ttl, though).
That's the initial commit -- that will never update. There is an additional commit below which makes the integer change.
-
@jimp TIL. Thanks for the quick help!
-
This post is deleted! -
Is this cloudflare-ddns-update.sh in case running by cron able to solving Your problem?
Any comments from @jimp ?
-
That is not relevant to pfSense. The problem stated in this thread is solved in our repository.