Cloudflare Update removes "Proxied" setting. #3

New Issue

saavagebueno · 2025-11-20T04:18:33-05:00

saavagebueno commented

2025-11-20 04:18:33 -05:00

Originally created by @qwacko on GitHub (May 6, 2019).

When this tool updates the IP address of a cloudflare DNS entry, the fact that the domain is being proxied (or passed through the cloudflare CDN) is cancelled, exposing the target IP address directly to the internet.

I have tried this a few different ways, but this always seems to be the case.

Originally created by @qwacko on GitHub (May 6, 2019). When this tool updates the IP address of a cloudflare DNS entry, the fact that the domain is being proxied (or passed through the cloudflare CDN) is cancelled, exposing the target IP address directly to the internet. I have tried this a few different ways, but this always seems to be the case.

saavagebueno closed this issue

2025-11-20 04:18:33 -05:00

saavagebueno commented

2025-11-20 04:18:34 -05:00

@qdm12 commented on GitHub (May 6, 2019):

I am not sure what your problem is, but it seems quite related to the proxied option that you can see here in the Cloudflare API

Whether the record is receiving the performance and security benefits of Cloudflare

If this is what you need, I'll promptly add it to the configuration options so you can use it. Let me know if this is what you are talking about. Thanks !

@qdm12 commented on GitHub (May 6, 2019): I am not sure what your problem is, but it seems quite related to the `proxied` option that you can see [here in the Cloudflare API](https://api.cloudflare.com/#dns-records-for-a-zone-update-dns-record) > Whether the record is receiving the performance and security benefits of Cloudflare If this is what you need, I'll promptly add it to the configuration options so you can use it. Let me know if this is what you are talking about. Thanks !

saavagebueno commented

2025-11-20 04:18:34 -05:00

@qwacko commented on GitHub (May 6, 2019):

Yes you are right that is the correct point. I did a little testing and the "proxied" parameter is currently being set to false by the updater, but it should instead store the current value and retain it. If this isn't possible then I guess a setting in the config.json file would be best.

@qwacko commented on GitHub (May 6, 2019): Yes you are right that is the correct point. I did a little testing and the "proxied" parameter is currently being set to false by the updater, but it should instead store the current value and retain it. If this isn't possible then I guess a setting in the config.json file would be best.

saavagebueno commented

2025-11-20 04:18:34 -05:00

@qdm12 commented on GitHub (May 7, 2019):

I have added the proxied parameter. Simply add it to the JSON file as boolean like so:

{
  "provider": "cloudflare",
  "someotherparam":"someothervalue",
  "proxied": true
}

@qdm12 commented on GitHub (May 7, 2019): I have added the `proxied` parameter. Simply add it to the JSON file as boolean like so: ```json { "provider": "cloudflare", "someotherparam":"someothervalue", "proxied": true } ```

saavagebueno referenced this issue

2025-11-20 04:25:17 -05:00

[PR #3] [MERGED] Total code refactoring and added Dreamhost support #573

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/ddns-updater#3