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)

Hi Leon,

        Thanks for your feedback, I will send you PM for more details purpose.

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.

Hi Apurv, so yes at the core it was addressed by sorting out the authentication issues. However, it was complicated by some other factors.

As per our PM I believe most of this would be addressed in the documentation; however, the logs were not helpful at all.

Please improve the log entries and include information on what they possibly mean in the documentation along with guidance on possible solutions including how to clear the XG Cache.

Hello,

After the Refresh1 contained the fix for the WAN DDNS bug, I have noticed that there is a noticeable delay before it actually registers.

After deleting and recreating the DDNS entry it was 45 seconds before it initiated a connection.

Leon Friend2 said:

As per our PM I believe most of this would be addressed in the documentation; however, the logs were not helpful at all.

Please improve the log entries and include information on what they possibly mean in the documentation along with guidance on possible solutions including how to clear the XG Cache.

I can imagine that troubleshooting the issue alone was almost impossible. Logging shall be improved into next major release (18.5). Please Sophos take it under consideration.

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 – 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.

Hi Andrew, Apologies I can't find your request to do a direct reply but in short, the resolution on my end for Namecheap DDNS was to delete the entry and recreate it. the key is that the username needs to be your domain name.

Now the reason for deleting the profile and recreating it is that there is an odd backend timer that means if you just update the password it might not start working for 24 - 48 hours.