Thread Info
  • State Suggested Answer
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 6 subscribers
  • Views 3787 views
  • Users 0 members are here
Options
Suggested

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)

Leon Friend2

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

Parents Reply Children
  • 0 in reply to Apurv Patel

    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.

  • 0 in reply to Apurv Patel

    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.

    Regards,

    Gavin Daniels. DipIT(Networking)

     

     
  • 0 in reply to Leon Friend2

    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.

  • 0 in reply to Leon Friend2

    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.

Unfiltered HTML