Project

General

Profile

Actions

Bug #6005

closed

CloudFlare dyndns API changes other record settings

Added by Jeffrey Dvornek over 5 years ago. Updated over 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Dynamic DNS
Target version:
Start date:
03/16/2016
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.2.x
Affected Architecture:

Description

The update to the CloudFlare API implemented in #4737 hardcodes the 'proxiable' and 'proxied' parameters to false.

The 'proxiable' parameter is a read only value and should not be set on update.
The 'proxied' parameter controls whether CloudFlare services are enabled for the host; setting to false ensures that every time a DNS update propagates, CloudFlare services are disabled.

I believe a sufficient fix would be to simply remove these parameters from the update request.

Actions #1

Updated by Chris Buechler over 5 years ago

  • Category set to Dynamic DNS
  • Status changed from New to Resolved
  • Target version set to 2.3

this was fixed in December in e93a7c71db7b35512591028316f15f579cd57cf7

Actions #2

Updated by Chris Buechler over 5 years ago

  • Affected Version set to 2.2.x
Actions

Also available in: Atom PDF