pfSense

It's probable that other dyndns providers also accept hostnames including dots, since it's legal A record syntax. This could be more pervasive than just Namecheap. In that case, splitting host/domain into two fields on the page for all dyndns providers would be a good solution. Much easier to just implode for providers that don't separate hostname and domain in their update syntax.

Except that would break everyone's current settings unless we tried to be smart with some upgrade code (which could still guess wrong).

Another way (one I'll probably commit at least for now) since Namecheap only supports .co.uk / .org.uk / .me.uk is something like this:

$dparts = explode(".", $this->_dnsHost);
$domain_part_count = ($dparts[count($dparts)-1] == "uk") ? 3 : 2;
$domain_offset = count($dparts) - $domain_part_count;
$hostname = implode(".", array_slice($dparts, 0, $domain_offset));
$domain = implode(".", array_slice($dparts, $domain_offset));

Other providers would not be affected because none of the other providers require separate hostname and domain parameters except for Namecheap, so it would still be redesigning the whole page to support one provider.

Applied in changeset 89bbb204ad58c4d0250ebabf34ebec1996a53088.

can anyone confirm this is fixed?

Pardon me for re-opening this old bug, but I've finally gotten tired of manually updating my "dynamic" DNS entry hosted by namecheap.com's service.

My "domain" with namecheap is a delegated sub-domain, within which I have several hosts.

For example, the domain is dyn.example.com
I have a host: host1
The complete FQDN is host1.dyn.example.com

The current script, as noted in this bugfix, extracts the domain portion by counting "." characters. But that doesn't work for me, as the domain is like the .uk example, but it's a .com.

I understand the hesitation to update the GUI for just this one provider who requires the domain and host entries separated. Could perhaps a non-allowed character be used as a sentinel for the break between host and domain, and the dyndns.class file will split on that? Then the only GUI update might be an added instruction sentence for namecheap users.

For example, I might enter in the pfSense GUI the hostname host1/dyn.example.com to indicate which part is which.