Project

General

Profile

Bug #9361

Cloudflare Not Allowing "*" Hostname Entry in Dynamic DNS

Added by Will Rutherford 9 months ago. Updated 6 months ago.

Status:
Feedback
Priority:
Normal
Category:
Dynamic DNS
Target version:
Start date:
03/01/2019
Due date:
% Done:

100%

Estimated time:
Affected Version:
2.4.4_2
Affected Architecture:
amd64

Description

Cloudflare allows wildcard A records and the pfSense DDNS page has a wildcard checkbox (since 2.3?), but it will throw an "invalid hostname" error if you provide a "*". This can be circumvented with a direct edit on the config xml, but it's certainly not ideal.

History

#1 Updated by Tom Embt 9 months ago

My comments about Route53 on #9053 likely also apply to Cloudflare here. Assuming so, the solution would differ slightly because Cloudflare is a "split domain" type.

#2 Updated by Tom Embt 9 months ago

https://github.com/pfsense/pfsense/pull/4053

- hide wildcard and MX checkboxes since neither are used by the Cloudflare code
- update the call to is_domain() to have a truthy second argument, allowing wildcards for cloudflare and cloudflare-v6

Unlike the recent related Route53 and Linode edits, i have not tested this change.

#3 Updated by Renato Botelho 6 months ago

  • Status changed from New to Feedback
  • Assignee set to Renato Botelho
  • Target version set to 2.5.0
  • % Done changed from 0 to 100

PR has been merged. Thanks!

Also available in: Atom PDF