Bug #6778

CloudFlare Dynamic DNS fails when domain name uses a Second Level TLD

Added by James Thresher almost 4 years ago. Updated over 3 years ago.

Dynamic DNS
Target version:
Start date:
Due date:
% Done:


Estimated time:
Affected Version:
Affected Architecture:


When using Dynamic DNS with CloudFlare if the domain name used has a second level TLD such as the update will fail.

The cause is the following line within /etc/inc/dyndns.class (About line number 733)

$bottom_host_name = $host_names[count($host_names)-2] . "." . $host_names[count($host_names)-1];

This assumes that the zone name for CloudFlare will always be the highest two components of the host name.

Associated revisions

Revision 2446fffa (diff)
Added by Jim Pingle almost 4 years ago

Convert CloudFlare and GratisDNS dynamic DNS over to split hostname and domain name fields, like Namecheap. Otherwise they could both break with subdomains or international TLDs with many parts. Fixes #6778


#1 Updated by Jim Thompson almost 4 years ago

  • Assignee set to Jim Pingle

#2 Updated by Jim Pingle almost 4 years ago

  • Status changed from New to Confirmed
  • Target version set to 2.4.0
  • Affected Version changed from 2.3.2 to All

Both CloudFlare and GratisDNS used the same logic that Namecheap used to use, which has several potential problems. I converted them over to match Namecheap with separate Hostname and Domain name fields, to avoid this and future problems.

#3 Updated by Jim Pingle almost 4 years ago

  • Status changed from Confirmed to Feedback
  • % Done changed from 0 to 100

#4 Updated by Jim Pingle over 3 years ago

  • Status changed from Feedback to Resolved

No confirmation, but no complaints. Other posts on the forum indicate CloudFlare is working in general on 2.4 now.

Also available in: Atom PDF