Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Replies 11 replies
  • Subscribers 0 subscribers
  • Views 6104 views
  • Users 0 members are here
Options
Suggested

[9.200][BUG] Namecheap DynDNS update status wrong

FlorianGee
Hi,

I just started experimenting with the DynDNS service of namecheap.com. It looks like the UTM thinks the update failed, although it succeeded. 

UTM says: 
DynDNS status is: The last update attempt failed.

DynDNS modified: Thu Jan 1 01:00:00 1970


Namecheap DNS says:
A-Record for a certain subdomain was successfully updated with the correct dynamic IP.

Is anybody having the same issue? [:S]
Parents
  • 0
    Hi there,
    How does your DynDNS config look like (printscreen). What does system.log say?
    Thanks
    Bianca
  • 0 in reply to Tinkerbell
    Hi,

    this is what the systemlog says: 
    2014:04:09-00:02:04 utm ddclient[16828]: WARNING:  file /var/cache/ddclient/ddclient.cache, line 6: Invalid Value for keyword 'ip' = ''

    2014:04:09-00:02:04 utm ddclient[16828]: WARNING:  file /var/cache/ddclient/ddclient.cache, line 10: Invalid Value for keyword 'ip' = ''

    2014:04:09-00:02:06 utm ddclient[16828]: WARNING:  SENT:    dynamicdns.park-your-domain.com/update

    2014:04:09-00:02:06 utm ddclient[16828]: WARNING:  REPLIED: HTTP/1.1 200 OK

    2014:04:09-00:02:06 utm ddclient[16828]: WARNING:   Cache-Control: private

    2014:04:09-00:02:06 utm ddclient[16828]: WARNING:   Content-Length: 429

    2014:04:09-00:02:06 utm ddclient[16828]: WARNING:   Content-Type: text/html

    2014:04:09-00:02:06 utm ddclient[16828]: WARNING:   Server: Microsoft-IIS/7.5

    2014:04:09-00:02:06 utm ddclient[16828]: WARNING:   Set-Cookie: ASPSESSIONIDSEQBSTCR=ENMECKIBIBEBINPBDEHBOHGB; secure; path=/

    2014:04:09-00:02:06 utm ddclient[16828]: WARNING:   X-Powered-By: ASP.NET

    2014:04:09-00:02:06 utm ddclient[16828]: WARNING:   Date: Tue, 08 Apr 2014 22:02:06 GMT

    2014:04:09-00:02:06 utm ddclient[16828]: WARNING:   Connection: close

    2014:04:09-00:02:06 utm ddclient[16828]: WARNING:   

    2014:04:09-00:02:06 utm ddclient[16828]: WARNING:   SETDNSHOSTeng1No Records updated. A record not Found;1380091No updates; A record not Found;true

    2014:04:09-00:02:06 utm ddclient[16828]: FAILED:   updating ******X: Invalid reply.


    Although the GUI and the log show errors during the update, the DNS-records at Namecheap get the proper updates. This is what the GUI looks like:
Reply
  • 0 in reply to Tinkerbell
    Hi,

    this is what the systemlog says: 
    2014:04:09-00:02:04 utm ddclient[16828]: WARNING:  file /var/cache/ddclient/ddclient.cache, line 6: Invalid Value for keyword 'ip' = ''

    2014:04:09-00:02:04 utm ddclient[16828]: WARNING:  file /var/cache/ddclient/ddclient.cache, line 10: Invalid Value for keyword 'ip' = ''

    2014:04:09-00:02:06 utm ddclient[16828]: WARNING:  SENT:    dynamicdns.park-your-domain.com/update

    2014:04:09-00:02:06 utm ddclient[16828]: WARNING:  REPLIED: HTTP/1.1 200 OK

    2014:04:09-00:02:06 utm ddclient[16828]: WARNING:   Cache-Control: private

    2014:04:09-00:02:06 utm ddclient[16828]: WARNING:   Content-Length: 429

    2014:04:09-00:02:06 utm ddclient[16828]: WARNING:   Content-Type: text/html

    2014:04:09-00:02:06 utm ddclient[16828]: WARNING:   Server: Microsoft-IIS/7.5

    2014:04:09-00:02:06 utm ddclient[16828]: WARNING:   Set-Cookie: ASPSESSIONIDSEQBSTCR=ENMECKIBIBEBINPBDEHBOHGB; secure; path=/

    2014:04:09-00:02:06 utm ddclient[16828]: WARNING:   X-Powered-By: ASP.NET

    2014:04:09-00:02:06 utm ddclient[16828]: WARNING:   Date: Tue, 08 Apr 2014 22:02:06 GMT

    2014:04:09-00:02:06 utm ddclient[16828]: WARNING:   Connection: close

    2014:04:09-00:02:06 utm ddclient[16828]: WARNING:   

    2014:04:09-00:02:06 utm ddclient[16828]: WARNING:   SETDNSHOSTeng1No Records updated. A record not Found;1380091No updates; A record not Found;true

    2014:04:09-00:02:06 utm ddclient[16828]: FAILED:   updating ******X: Invalid reply.


    Although the GUI and the log show errors during the update, the DNS-records at Namecheap get the proper updates. This is what the GUI looks like:
Children
Unfiltered HTML