DynDNS is not working

betatester · 15 November 2019 06:54

Hello,

with Core 135 i wood like to use the IPFire DynDNS Service with https://www.nsupdate.info/

But i looks like it don´t work, the IP not update… the Login are correct, with my FritzBox it works

Were are the logs located to take a look what happens?

Regrads

BetaTester

ms · 15 November 2019 09:59

You will find this on the web UI as usual under “System Logs” and then select “Dynamic DNS”.

betatester · 15 November 2019 11:25

Okay, here are many in there

|13:35:01|ddns[3556]:|Further updates will be withheld until 2019-11-15 00:03:27.420212|
|---|---|---|
|13:40:01|ddns[4321]:|An update has not been performed because earlier updates failed for massaguana. nsupdate.info|
|13:40:01|ddns[4321]:|Last failure message:|
|13:40:01|ddns[4321]:|DDNSAuthenticationError: Authentication against the server has failed|
|13:40:01|ddns[4321]:|Further updates will be withheld until 2019-11-15 00:03:27.420212|
|13:45:01|ddns[4637]:|An update has not been performed because earlier updates failed for massaguana. nsupdate.info|
|13:45:01|ddns[4637]:|Last failure message:|
|13:45:01|ddns[4637]:|DDNSAuthenticationError: Authentication against the server has failed|
|13:45:01|ddns[4637]:|Further updates will be withheld until 2019-11-15 00:03:27.420212|
|13:50:01|ddns[4872]:|An update has not been performed because earlier updates failed for massaguana. nsupdate.info|
|13:50:01|ddns[4872]:|Last failure message:|
|13:50:01|ddns[4872]:|DDNSAuthenticationError: Authentication against the server has failed|
|13:50:01|ddns[4872]:|Further updates will be withheld until 2019-11-15 00:03:27.420212|
|13:55:01|ddns[5100]:|An update has not been performed because earlier updates failed for massaguana. nsupdate.info|
|13:55:01|ddns[5100]:|Last failure message:|
|13:55:01|ddns[5100]:|DDNSAuthenticationError: Authentication against the server has failed|
|13:55:01|ddns[5100]:|Further updates will be withheld until 2019-11-15 00:03:27.420212|
|14:00:01|ddns[5332]:|An update has not been performed because earlier updates failed for massaguana. nsupdate.info|
|14:00:01|ddns[5332]:|Last failure message:|
|14:00:01|ddns[5332]:|DDNSAuthenticationError: Authentication against the server has failed|
|14:00:01|ddns[5332]:|Further updates will be withheld until 2019-11-15 00:03:27.420212|
|14:05:01|ddns[5607]:|An update has not been performed because earlier updates failed for massaguana. nsupdate.info|
|14:05:01|ddns[5607]:|Last failure message:|
|14:05:01|ddns[5607]:|DDNSAuthenticationError: Authentication against the server has failed|
|14:05:01|ddns[5607]:|Further updates will be withheld until 2019-11-15 00:03:27.420212|
|14:10:01|ddns[5836]:|An update has not been performed because earlier updates failed for massaguana. nsupdate.info|
|14:10:01|ddns[5836]:|Last failure message:|
|14:10:01|ddns[5836]:|DDNSAuthenticationError: Authentication against the server has failed|
|14:10:01|ddns[5836]:|Further updates will be withheld until 2019-11-15 00:03:27.420212|
|14:15:01|ddns[6067]:|An update has not been performed because earlier updates failed for massaguana. nsupdate.info|
|14:15:01|ddns[6067]:|Last failure message:|
|14:15:01|ddns[6067]:|DDNSAuthenticationError: Authentication against the server has failed|
|14:15:01|ddns[6067]:|Further updates will be withheld until 2019-11-15 00:03:27.420212|
|14:20:01|ddns[6296]:|An update has not been performed because earlier updates failed for massaguana. nsupdate.info|
|14:20:01|ddns[6296]:|Last failure message:|
|14:20:01|ddns[6296]:|DDNSAuthenticationError: Authentication against the server has failed|
|14:20:01|ddns[6296]:|Further updates will be withheld until 2019-11-15 00:03:27.420212|
|02:35:01|ddns[11453]:|Further updates will be withheld until 2019-11-15 12:05:02.589007|
|---|---|---|
|02:40:01|ddns[11685]:|An update has not been performed because earlier updates failed for massaguana. nsupdate.info|
|02:40:01|ddns[11685]:|Last failure message:|
|02:40:01|ddns[11685]:|DDNSAuthenticationError: Authentication against the server has failed|
|02:40:01|ddns[11685]:|Further updates will be withheld until 2019-11-15 12:05:02.589007|
|02:45:01|ddns[11912]:|An update has not been performed because earlier updates failed for massaguana. nsupdate.info|
|02:45:01|ddns[11912]:|Last failure message:|
|02:45:01|ddns[11912]:|DDNSAuthenticationError: Authentication against the server has failed|
|02:45:01|ddns[11912]:|Further updates will be withheld until 2019-11-15 12:05:02.589007|
|02:50:01|ddns[12145]:|An update has not been performed because earlier updates failed for massaguana. nsupdate.info|
|02:50:01|ddns[12145]:|Last failure message:|
|02:50:01|ddns[12145]:|DDNSAuthenticationError: Authentication against the server has failed|
|02:50:01|ddns[12145]:|Further updates will be withheld until 2019-11-15 12:05:02.589007|
|02:55:01|ddns[12374]:|An update has not been performed because earlier updates failed for massaguana. nsupdate.info|
|02:55:01|ddns[12374]:|Last failure message:|
|02:55:01|ddns[12374]:|DDNSAuthenticationError: Authentication against the server has failed|
|02:55:01|ddns[12374]:|Further updates will be withheld until 2019-11-15 12:05:02.589007|
|03:00:01|ddns[12617]:|An update has not been performed because earlier updates failed for massaguana. nsupdate.info|
|03:00:01|ddns[12617]:|Last failure message:|
|03:00:01|ddns[12617]:|DDNSAuthenticationError: Authentication against the server has failed|
|03:00:01|ddns[12617]:|Further updates will be withheld until 2019-11-15 12:05:02.589007|
|03:05:01|ddns[12926]:|An update has not been performed because earlier updates failed for massaguana. nsupdate.info|
|03:05:01|ddns[12926]:|Last failure message:|
|03:05:01|ddns[12926]:|DDNSAuthenticationError: Authentication against the server has failed|

roberto · 15 November 2019 13:40

Do you have the DDNS configured correctly ?. Based on this, the password set in the nsupdate.info configuration fails.

Try to correct it and if it still does not work, access via SSH using PUTTY and execute the following:

ddns -d update-all --force

This command executes the synchronization of the DDns in verbose mode.

Copy the entire output and paste it so we can see what error it gives. (Check that what you paste is not the password or any clear sensitive data).

Tell us something.

Regards.

betatester · 16 November 2019 13:55

here is the result:

[root@ipfire ~]# ddns -d update-all --force

Debugging mode enabled

Registered new provider: All-inkl.com (all-inkl.com)

Registered new provider: ChangeIP.com (changeip.com)

Registered new provider: DDNSS (ddnss.de)

Registered new provider: desec.io (desec.io)

Registered new provider: DHS International (dhs.org)

Registered new provider: Lightning Wire Labs DNS Service (dns.lightningwirelabs.com)

Registered new provider: DNSmadeEasy.com (dnsmadeeasy.com)

Registered new provider: DNS Park (dnspark.com)

Registered new provider: Domain-Offensive (do.de)

Registered new provider: Google Domains (domains.google.com)

Registered new provider: domopoli.de (domopoli.de)

Registered new provider: DtDNS (dtdns.com)

Registered new provider: Duck DNS (duckdns.org)

Registered new provider: dy.fi (dy.fi)

Registered new provider: Dyn (dyndns.org)

Registered new provider: DyNS (dyns.net)

Registered new provider: Dynu (dynu.com)

Registered new provider: EasyDNS (easydns.com)

Registered new provider: eNom Inc. (enom.com)

Registered new provider: EntryDNS (entrydns.net)

Registered new provider: freedns.afraid.org (freedns.afraid.org)

Registered new provider: it's DNS (itsdns.de)

Registered new provider: Joker.com Dynamic DNS (joker.com)

Registered new provider: Loopia AB (loopia.se)

Registered new provider: myonlineportal.net (myonlineportal.net)

Registered new provider: Namecheap (namecheap.com)

Registered new provider: No-IP (no-ip.com)

Registered new provider: NOW-DNS (now-dns.com)

Registered new provider: BIND nsupdate utility (nsupdate)

Registered new provider: nsupdate.info (nsupdate.info)

Registered new provider: OpenDNS (opendns.com)

Registered new provider: OVH (ovh.com)

Registered new provider: Regfish GmbH (regfish.com)

Registered new provider: Schokokeks (schokokeks.org)

Registered new provider: Selfhost.de (selfhost.de)

Registered new provider: servercow.de (servercow.de)

Registered new provider: SPDYN (spdns.org)

Registered new provider: Strato AG (strato.com)

Registered new provider: TwoDNS (twodns.de)

Registered new provider: Udmedia GmbH (udmedia.de)

Registered new provider: Variomedia (variomedia.de)

Registered new provider: XLhost (xlhost.de)

Registered new provider: Zoneedit (zoneedit.com)

Registered new provider: zzzz (zzzz.io)

Running on distribution: ipfire-2

Loading configuration file /var/ipfire/ddns/ddns.conf

Updating massaguana.nsupdate.info forced

Sending request (GET): http://checkip4.dns.lightningwirelabs.com

Request header:

Pragma: no-cache

User-agent: IPFireDDNSUpdater/011

Dynamic DNS update for massaguana.nsupdate.info (nsupdate.info) successful

Logging successful update for massaguana.nsupdate.info

Opening database /var/lib/ddns.db

roberto · 17 November 2019 09:22

@betatester

There’s no more?. How strange!!!.

The only thing that occurs to me is to look at the permissions of the folders involved, since they may not have access to them.

var:

lib:

And file:

I have looked in the ISO installation image and I have not found the file in question:

imagen

Perhaps it is damaged and for that reason I cannot access it? In that case, rename it as “ddns.db_old” and try launching the same command from SSH to see if it works.

Maybe someone else comes up with something else.

Regards.

betatester · 27 October 2020 17:58

Here an late update with core 151

I think it works… i just do nothing… just update to core 151

[root@ipfire ~]# ddns -d update-all --force
Debugging mode enabled
Registered new provider: All-inkl.com (all-inkl.com)
Registered new provider: ChangeIP.com (changeip.com)
Registered new provider: DDNSS (ddnss.de)
Registered new provider: desec.io (desec.io)
Registered new provider: DHS International (dhs.org)
Registered new provider: Lightning Wire Labs DNS Service (dns.lightningwirelabs.com)
Registered new provider: DNSmadeEasy.com (dnsmadeeasy.com)
Registered new provider: DNS Park (dnspark.com)
Registered new provider: Domain-Offensive (do.de)
Registered new provider: Google Domains (domains.google.com)
Registered new provider: domopoli.de (domopoli.de)
Registered new provider: DtDNS (dtdns.com)
Registered new provider: Duck DNS (duckdns.org)
Registered new provider: dy.fi (dy.fi)
Registered new provider: Dyn (dyndns.org)
Registered new provider: DyNS (dyns.net)
Registered new provider: Dynu (dynu.com)
Registered new provider: DynUp.DE (dynup.de)
Registered new provider: EasyDNS (easydns.com)
Registered new provider: eNom Inc. (enom.com)
Registered new provider: EntryDNS (entrydns.net)
Registered new provider: freedns.afraid.org (freedns.afraid.org)
Registered new provider: INWX (inwx.com)
Registered new provider: it's DNS (itsdns.de)
Registered new provider: Joker.com Dynamic DNS (joker.com)
Registered new provider: dynamicdns.key-systems.net (key-systems.net)
Registered new provider: Loopia AB (loopia.se)
Registered new provider: myonlineportal.net (myonlineportal.net)
Registered new provider: Namecheap (namecheap.com)
Registered new provider: NoIP (no-ip.com)
Registered new provider: NOW-DNS (now-dns.com)
Registered new provider: BIND nsupdate utility (nsupdate)
Registered new provider: nsupdate.info (nsupdate.info)
Registered new provider: OpenDNS (opendns.com)
Registered new provider: OVH (ovh.com)
Registered new provider: Regfish GmbH (regfish.com)
Registered new provider: Schokokeks (schokokeks.org)
Registered new provider: Selfhost.de (selfhost.de)
Registered new provider: servercow.de (servercow.de)
Registered new provider: SPDYN (spdns.org)
Registered new provider: Strato AG (strato.com)
Registered new provider: TwoDNS (twodns.de)
Registered new provider: Udmedia GmbH (udmedia.de)
Registered new provider: Variomedia (variomedia.de)
Registered new provider: XLhost (xlhost.de)
Registered new provider: Zoneedit (zoneedit.com)
Registered new provider: zzzz (zzzz.io)
Running on distribution: ipfire-2
Loading configuration file /var/ipfire/ddns/ddns.conf
Updating massaguana.nsupdate.info forced
Sending request (GET): https://checkip4.dns.lightningwirelabs.com
Request header:
  User-agent: IPFireDDNSUpdater/013
  Pragma: no-cache
Response header (Status Code 200):
  content-length: 36
  vary: Accept-Encoding
  etag: "######"
  date: Tue, 27 Oct 2020 17:55:44 GMT
  content-type: text/html; charset=UTF-8
  strict-transport-security: max-age=31536000; includeSubDomains; preload
  connection: close
Sending request (GET): https://nsupdate.info/nic/update?myip=###.###.###.###
Request header:
  Authorization: Basic ######
  User-agent: IPFireDDNSUpdater/013
  Pragma: no-cache
Response header (Status Code 200):
  Server: nginx
  Date: Tue, 27 Oct 2020 17:56:12 GMT
  Content-Type: text/plain
  Content-Length: 21
  Connection: close
  x-content-type-options: nosniff
  x-xss-protection: 1; mode=block
  X-Frame-Options: DENY
  Referrer-Policy: same-origin
  Vary: Accept-Language, Cookie
  Content-Language: en
  Strict-Transport-Security: max-age=31536000;
  Expect-CT: enforce, max-age=21600
Dynamic DNS update for #####.#####.##### (nsupdate.info) successful
Logging successful update for ######.#####.#####
Opening database /var/lib/ddns.db
[root@ipfire ~]#

jon · 9 August 2023 18:36

A post was split to a new topic: Get access from outside