Dynamic DNS with NameCheap appears to be failing: WARNING: file /var/cache/ddclient/ddclient.cache, line 5: Invalid Value for keyword 'ip' = ''

This has been reported by other but I see no indication that Sophos has addressed it

At issue may be the hostname field.

The UTM suggests the following on this field:

"Hostname (not with type Open DNS IP update): Enter the domain name you received from your DynDNS service provider (e.g., example.dyndns.org). Note that you need not adhere to a particular syntax for the hostname to be entered here. What you must enter here exclusively depends on what your DynDNS service provider requires. Apart from that, you can also use your DynDNS hostname as the gateway's main hostname, which, however, is not mandatory.

DynDNS is not being used, NameCheap is and had been selected.  They do not provide some predefined hostname for each customer as DynDns does (for some reason).  Therefore it's not at all clear what is meant by this.  From other posts I've attempted to use @ instead.  The logs initially showed improvement but eventually fell back to failing:

I've also noticed that after one saves edits there is a field called Wildcard with a red X button and a greyed-button.  One might assume it's green with a check mark if activated.  This button is not a web interactive button and using @ for the hostname does not seem to affect anything.  How might one activate "WildCard" in the NameCheap scenario?

More information:

I contacted NameCheap support and was escalated to a DNS guy. [?]

He led me through a process on their site:  Dashboard -> Manage (domain) -> Advanced DNS -> Dynamic DNS

This was "interesting".  Here under Dynamic DNS it has the user create an entry for Dynamic DNS which has the following fields:

1. Host
2. IP Address
3. TTL (a drop-down selection menu)

I pointed out to the support tech that asking for an ip address for dynamic DNS was an interesting approach.  I looked up my internet-apparent address and entered that as well as using a locally (UTM) resolved hostname.

Just to investigate their take on dns engineering, I downloaded their windows client and found immediately that it does not support HTTP proxies.  It just throws a proxy authentication error showing it recognizes the existence of a proxy but can't handle the authentication part.  Not a good sign.  I opened a gaping hole in my infrastructure to support this client and the update on the client appears stuck for over 20 min now.  I'm not at all comfortable with this so I'm shutting down the client.  The techs were all called Igor and Ivan so my level of trust is dwindling. Looking back at The Sophos UTM settings for NameCheap, I changed the name on the Sophos settings to match what I have on the DynDNS settings at NameCheap.  Still failing.