CloudFlare Dynamic DNS fails when domain name uses a Second Level TLD
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.
#2 Updated by Jim Pingle 4 months 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.