This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Dynamic DNS on 9.400 - not sure it's working

Hi,

I have a new 9.400 build at home, from scratch with settings manually re-entered.

I have been using the DynDNS setup in the UTM, with OpenDNS and NameCheap.

In 9.400, it constantly says "DynDNS status is: An update attempt is in progress." for both services.

The system.log regularly says

2016:04:04-10:42:58 fw ddclient[23926]: WARNING:  file /var/cache/ddclient/ddclient.cache, line 3: Invalid Value for keyword 'ip' = ''
2016:04:04-10:42:58 fw ddclient[23926]: WARNING:  file /var/cache/ddclient/ddclient.cache, line 4: Invalid Value for keyword 'ip' = ''
2016:04:04-10:42:58 fw ddclient[23926]: WARNING:  file /var/cache/ddclient/ddclient.cache, line 5: Invalid Value for keyword 'ip' = ''
2016:04:04-10:42:58 fw ddclient[23926]: WARNING:  file /var/cache/ddclient/ddclient.cache, line 6: Invalid Value for keyword 'ip' = ''
2016:04:04-10:42:58 fw ddclient[23926]: WARNING:  file /var/cache/ddclient/ddclient.cache, line 7: Invalid Value for keyword 'ip' = ''
2016:04:04-10:43:04 fw ddclient[23926]: SUCCESS:  updating bg-astaro: good: IP address set to 100.9x.x.x
2016:04:04-10:43:04 fw ddclient[23926]: WARNING:  skipping update of * from <nothing> to 100.9x.x.x.
2016:04:04-10:43:04 fw ddclient[23926]: WARNING:   last updated <never> but last attempt on Mon Apr  4 10:42:32 2016 failed.
2016:04:04-10:43:04 fw ddclient[23926]: WARNING:   Wait at least 5 minutes between update attempts.
2016:04:04-10:43:04 fw ddclient[23926]: WARNING:  skipping update of @ from <nothing> to 100.9x.x.x.
2016:04:04-10:43:04 fw ddclient[23926]: WARNING:   last updated <never> but last attempt on Mon Apr  4 10:42:32 2016 failed.
2016:04:04-10:43:04 fw ddclient[23926]: WARNING:   Wait at least 5 minutes between update attempts.
2016:04:04-10:43:04 fw ddclient[23926]: WARNING:  skipping update of fw from <nothing> to 100.9x.x.x.
2016:04:04-10:43:04 fw ddclient[23926]: WARNING:   last updated <never> but last attempt on Mon Apr  4 10:42:32 2016 failed.
2016:04:04-10:43:04 fw ddclient[23926]: WARNING:   Wait at least 5 minutes between update attempts.
2016:04:04-10:43:04 fw ddclient[23926]: WARNING:  skipping update of home from <nothing> to 100.9x.x.x.
2016:04:04-10:43:04 fw ddclient[23926]: WARNING:   last updated <never> but last attempt on Mon Apr  4 10:42:32 2016 failed.
2016:04:04-10:43:04 fw ddclient[23926]: WARNING:   Wait at least 5 minutes between update attempts.
2016:04:04-10:43:04 fw ddclient[23926]: WARNING:  skipping update of www from <nothing> to 100.9x.x.x.
2016:04:04-10:43:04 fw ddclient[23926]: WARNING:   last updated <never> but last attempt on Mon Apr  4 10:42:32 2016 failed.
2016:04:04-10:43:04 fw ddclient[23926]: WARNING:   Wait at least 5 minutes between update attempts.

So, I'm not sure if it's working or not.

Thanks,

Barry



This thread was automatically locked due to age.
Parents
  • Hi Barry,

    Greetings.

    We had a reported Bug which reflected the same log lines. This was resolved in v9.200. 

    Just curious if DynDNS certificate is still valid. 

    If you have configured a namecheap account with aliases the UTM shows the status "The last update attempt failed" because of an error in the system.log.

    This error happens because the UTM sends the wrong request to the namecheap server.

    Thanks

    Sachin Gurung

    Sachin Gurung
    Team Lead | Sophos Technical Support
    Knowledge Base  |  @SophosSupport  |  Video tutorials
    Remember to like a post.  If a post (on a question thread) solves your question use the 'This helped me' link.

  • Hi Sachin,

    The log is above, but I am using the same configuration as was previously working on a previous 9.3x UTM.

    Which certificate are you referring to?

    Thanks,
    Barry

Reply Children
  • Hi Barry,

    Are you using any certificate in conjunction to DyDNS. I read it in the comments section when the issue was reported in our database. As the previous issue was something related to SSL certificate. I don't feel that in your case but I was curious. 

    I feel the issue has come up again, I request you to raise a case with support to check this and the previous Bug ID was NUTML-8190. 

    Thanks

    Sachin Gurung

    Sachin Gurung
    Team Lead | Sophos Technical Support
    Knowledge Base  |  @SophosSupport  |  Video tutorials
    Remember to like a post.  If a post (on a question thread) solves your question use the 'This helped me' link.

  • Hi, no, I haven't set up any certificates for NameCheap or OpenDNS dynamic DNS services.

    I'm currently just a Home User; I'm assuming there (still) is no support for home users, right?

    Thanks

  • My IP has changed and this still isn't working.

    I shutdown the firewall last night for a scheduled power outage; here's the system log from this morning:

    2016:04:25-07:36:40 fw syslog-ng[4911]: syslog-ng starting up; version='3.4.7'
    2016:04:25-07:36:41 fw ntpd[4657]: Listen normally on 10 tun0 10.242.2.1:123
    2016:04:25-07:36:41 fw ntpd[4657]: new interface(s) found: waking up resolver
    2016:04:25-07:36:43 fw dns-resolver[4564]: DNS server failed to contact!
    2016:04:25-07:36:44 fw dns-resolver[4564]: DNS server failed to contact!
    2016:04:25-07:36:54 fw ddclient[5860]: WARNING:  file /var/cache/ddclient/ddclient.cache, line 3: Invalid Value for keyword 'ip' = ''
    2016:04:25-07:36:54 fw ddclient[5860]: WARNING:  file /var/cache/ddclient/ddclient.cache, line 4: Invalid Value for keyword 'ip' = ''
    2016:04:25-07:36:54 fw ddclient[5860]: WARNING:  file /var/cache/ddclient/ddclient.cache, line 6: Invalid Value for keyword 'ip' = ''
    2016:04:25-07:36:54 fw ddclient[5860]: WARNING:  file /var/cache/ddclient/ddclient.cache, line 7: Invalid Value for keyword 'ip' = ''
    2016:04:25-07:36:54 fw ddclient[5860]: WARNING:  file /var/cache/ddclient/ddclient.cache, line 8: Invalid Value for keyword 'ip' = ''
    2016:04:25-07:36:54 fw ddclient[5860]: WARNING:  cannot connect to checkip.dyndns.org:80 socket: IO::Socket::INET: Bad hostname 'checkip.dyndns.org'
    2016:04:25-07:36:54 fw ddclient[5860]: WARNING:  cannot connect to dynamicdns.park-your-domain.com:443 socket: IO::Socket::SSL: getaddrinfo: Name or service not known IO::Socket::INET6 configuration failed
    2016:04:25-07:36:54 fw ddclient[5860]: FAILED:   updating *: Could not connect to dynamicdns.park-your-domain.com.
    2016:04:25-07:37:05 fw snmpd[4563]: Received TERM or STOP signal...  shutting down...
    2016:04:25-07:37:05 fw snmpd[6690]: NET-SNMP version 5.7.3
    2016:04:25-07:37:05 fw ntpd[4657]: receive: Unexpected origin timestamp from 24.9.13.14
    2016:04:25-07:37:09 fw system: System was restarted
    2016:04:25-07:37:43 fw dns-resolver[4564]: No change to REF_DefaultSophosUTMSupportHost :: dispatch.apu.sophos.com
    2016:04:25-07:37:43 fw dns-resolver[4564]: No change to REF_NetDnsSmtpgmailc :: smtp.gmail.com
    2016:04:25-07:37:43 fw dns-resolver[4564]: Updating REF_NtpPool :: pool.ntp.org

    It looks like it tried to run ddclient before the internet connection was up!

    After that, it did update OpenDNS but not NameCheap:



    2016:04:25-07:40:01 fw /usr/sbin/cron[7382]: (root) CMD (   /usr/local/bin/reporter/system-reporter.pl)
    2016:04:25-07:40:01 fw /usr/sbin/cron[7383]: (root) CMD (/var/mdw/scripts/pmx-blocklist-update)
    2016:04:25-07:40:07 fw ddclient[7450]: WARNING:  file /var/cache/ddclient/ddclient.cache, line 3: Invalid Value for keyword 'ip' = ''
    2016:04:25-07:40:07 fw ddclient[7450]: WARNING:  file /var/cache/ddclient/ddclient.cache, line 4: Invalid Value for keyword 'ip' = ''
    2016:04:25-07:40:07 fw ddclient[7450]: WARNING:  file /var/cache/ddclient/ddclient.cache, line 6: Invalid Value for keyword 'ip' = ''
    2016:04:25-07:40:07 fw ddclient[7450]: WARNING:  file /var/cache/ddclient/ddclient.cache, line 7: Invalid Value for keyword 'ip' = ''
    2016:04:25-07:40:07 fw ddclient[7450]: WARNING:  file /var/cache/ddclient/ddclient.cache, line 8: Invalid Value for keyword 'ip' = ''
    2016:04:25-07:40:08 fw ddclient[7450]: SUCCESS:  updating barry-astaro: good: IP address set to 100.9.136.4


    2016:04:25-07:42:50 fw ddclient[7603]: WARNING:  skipping update of * from <nothing> to 100.9.136.4.
    2016:04:25-07:42:50 fw ddclient[7603]: WARNING:   last updated <never> but last attempt on Mon Apr 25 07:36:53 2016 failed.
    2016:04:25-07:42:50 fw ddclient[7603]: WARNING:   Wait at least 5 minutes between update attempts.
    2016:04:25-07:42:50 fw ddclient[7603]: WARNING:  skipping update of @ from <nothing> to 100.9.136.4.
    2016:04:25-07:42:50 fw ddclient[7603]: WARNING:   last updated <never> but last attempt on Mon Apr 25 07:36:53 2016 failed.
    2016:04:25-07:42:50 fw ddclient[7603]: WARNING:   Wait at least 5 minutes between update attempts.
    2016:04:25-07:42:50 fw ddclient[7603]: WARNING:  skipping update of fw from <nothing> to 100.9.136.4.
    2016:04:25-07:42:50 fw ddclient[7603]: WARNING:   last updated <never> but last attempt on Mon Apr 25 07:36:53 2016 failed.
    2016:04:25-07:42:50 fw ddclient[7603]: WARNING:   Wait at least 5 minutes between update attempts.
    2016:04:25-07:42:50 fw ddclient[7603]: WARNING:  skipping update of home from <nothing> to 100.9.136.4.
    2016:04:25-07:42:50 fw ddclient[7603]: WARNING:   last updated <never> but last attempt on Mon Apr 25 07:36:53 2016 failed.
    2016:04:25-07:42:50 fw ddclient[7603]: WARNING:   Wait at least 5 minutes between update attempts.
    2016:04:25-07:42:50 fw ddclient[7603]: WARNING:  skipping update of www from <nothing> to 100.9.136.4.
    2016:04:25-07:42:50 fw ddclient[7603]: WARNING:   last updated <never> but last attempt on Mon Apr 25 07:36:53 2016 failed.
    2016:04:25-07:42:50 fw ddclient[7603]: WARNING:   Wait at least 5 minutes between update attempts.
    2016:04:25-07:43:01 fw /usr/sbin/cron[7774]: (root) CMD (/sbin/audld.plx --nosys --trigger)
    2016:04:25-07:43:24 fw syslog-ng[4911]: Configuration reload request received, reloading configuration;

    I really need to get this working, at least manually; How can I reset the locks and force it to run?

    Thanks,

    Barry

  • Hi Barry,

    I request you to contact our support team "support@sophos.com", to get details on the Bug ID NUTLM-3472. 

    Thanks

    Sachin Gurung

    Sachin Gurung
    Team Lead | Sophos Technical Support
    Knowledge Base  |  @SophosSupport  |  Video tutorials
    Remember to like a post.  If a post (on a question thread) solves your question use the 'This helped me' link.