SFOS 18.0.0 EAP1-Refresh1 DDNS Fails on PPPoE Interface (DDNS update for host [DDNS Host] was Failed. Last Updated with IP 0.0.0.0. Failure Reason: noconnect)

Question

When using DDNS via Namecheap on v18 EAP1-Refresh1 over a PPPoE Interface DDNS Fails to register with log entry as below 
 DDNS update for host [DDNS Host] was Failed. Last Updated with IP 0.0.0.0. Failure Reason: noconnect

Apurv Patel · Answer

Hi Leon, 
 Thanks for the device access. 
 As per our discussion in PM after entered the password again, your Namecheap DDNS successfully connected to the server. 
 Please get back to us if you face any issue again.

PMParth · Answer

In earlier versions, you might have experienced stability issues with Dynamic DNS client in XG. 
 In v18, we have upgraded to enhanced DDC service - making DDNS more stable, secure and flexible. The DDC offers HTTPS-based DDNS. This also enables us to rapidly introduce new DDNS providers. We have added five more DDNS providers in v18 &ndash; No-IP, DNS-O-Static, Google DNS, Namecheap, and FreeDNS. Plus, you would have experienced very stable working with DDNS in v18. 
 With DDC service, we rely on DDC to parse different error codes by DDNS provider to log it in the system. For example - if you use DynDNS, you would get comprehensive set of logs related to error in each step. Namecheap has limited error parsing capability with DDC as of now. Though not on the immediate backlog, we would consider improving this in a future release. 
 Thank you. 
 Parth.