Project

General

Profile

Actions
Copy link

Bug #6778

closed

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

Added by James Thresher about 8 years ago. Updated almost 8 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Jim Pingle
Category:
Dynamic DNS
Target version:
2.4.0
Start date:
09/08/2016
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
All
Affected Architecture:

Description

When using Dynamic DNS with CloudFlare if the domain name used has a second level TLD such as .co.uk 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.

Actions
Copy link
 #1

Updated by Jim Thompson about 8 years ago

  • Assignee set to Jim Pingle
Actions
Copy link
 #2

Updated by Jim Pingle about 8 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.

Actions
Copy link
 #3

Updated by Jim Pingle about 8 years ago

  • Status changed from Confirmed to Feedback
  • % Done changed from 0 to 100
Actions
Copy link
 #4

Updated by Jim Pingle almost 8 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.

Actions
Copy link

Also available in: Atom PDF