Summary: | nsupdate.info: ddns is sending updates even if IP address has not changed | ||
---|---|---|---|
Product: | DDNS Updater | Reporter: | Timmothy Wilson <itsuperhack> |
Component: | Providers | Assignee: | Stefan Schantl <stefan.schantl> |
Status: | CLOSED NOTABUG | QA Contact: | Michael Tremer <michael.tremer> |
Severity: | - Unknown - | ||
Priority: | - Unknown - | ||
Version: | unspecified | ||
Hardware: | unspecified | ||
OS: | Unspecified | ||
Attachments: |
screenshot of the ddns log section in the WebIF
pppoe log section in the WebIF |
Created attachment 441 [details]
pppoe log section in the WebIF
What is the hostname of this machine? (In reply to Michael Tremer from comment #2) > What is the hostname of this machine? trikolon-de204 Host is offline at the moment, and this seems to be a problem which is not hostname-related: https://forum.ipfire.org/viewtopic.php?f=27&t=16487 Sorry for asking the question wrong. I was rather asking if the hostname of the system matches the dynamic DNS name. In that case the local internal IP address will be resolved which causes a mismatch and might trigger a DNS update. Is there more logs? (In reply to Michael Tremer from comment #4) > Sorry for asking the question wrong. I was rather asking if the hostname of > the system matches the dynamic DNS name. In that case the local internal IP > address will be resolved which causes a mismatch and might trigger a DNS > update. No, the systems hostname is "firewall". > > Is there more logs? Not really, the ddns log of the last few days before I opened this showed the same as the attached screenshot of the "ddns log" does: Many successful updates for the nsupdate.info domain. Since I disabled the host momentarily, there are no logs anymore for nsupdate.info. Can you confirm that you get back the correct IP address if you manually resolve that hostname on the firewall? (In reply to Michael Tremer from comment #6) > Can you confirm that you get back the correct IP address if you manually > resolve that hostname on the firewall? I think so: [root@firewall ~]# date Sat May 7 15:41:03 CEST 2016 [root@firewall ~]# host trikolon-de204.nsupdate.info Host trikolon-de204.nsupdate.info not found: 3(NXDOMAIN) [root@firewall ~]# ddns update trikolon-de204.nsupdate.info --force Dynamic DNS update for trikolon-de204.nsupdate.info (nsupdate.info) successful [root@firewall ~]# date Sat May 7 15:41:36 CEST 2016 [root@firewall ~]# host trikolon-de204.nsupdate.info Host trikolon-de204.nsupdate.info not found: 3(NXDOMAIN) [root@firewall ~]# host trikolon-de204.nsupdate.info Host trikolon-de204.nsupdate.info not found: 3(NXDOMAIN) [root@firewall ~]# host trikolon-de204.nsupdate.info trikolon-de204.nsupdate.info has address 188.97.[REDACTED] [root@firewall ~]# date Sat May 7 15:42:21 CEST 2016 [root@firewall ~]# (In reply to Timmothy Wilson from comment #7) > (In reply to Michael Tremer from comment #6) > > Can you confirm that you get back the correct IP address if you manually > > resolve that hostname on the firewall? > > I think so: > > [root@firewall ~]# date > Sat May 7 15:41:03 CEST 2016 > [root@firewall ~]# host trikolon-de204.nsupdate.info > Host trikolon-de204.nsupdate.info not found: 3(NXDOMAIN) > [root@firewall ~]# ddns update trikolon-de204.nsupdate.info --force > Dynamic DNS update for trikolon-de204.nsupdate.info (nsupdate.info) > successful > [root@firewall ~]# date > Sat May 7 15:41:36 CEST 2016 > [root@firewall ~]# host trikolon-de204.nsupdate.info > Host trikolon-de204.nsupdate.info not found: 3(NXDOMAIN) > [root@firewall ~]# host trikolon-de204.nsupdate.info > Host trikolon-de204.nsupdate.info not found: 3(NXDOMAIN) > [root@firewall ~]# host trikolon-de204.nsupdate.info > trikolon-de204.nsupdate.info has address 188.97.[REDACTED] > [root@firewall ~]# date > Sat May 7 15:42:21 CEST 2016 > [root@firewall ~]# So this looks quite good so far. Do you have the log files from that day after 15:42 CEST? Would be interesting to know if ddns tried to update again. (In reply to Michael Tremer from comment #8) > (In reply to Timmothy Wilson from comment #7) > > (In reply to Michael Tremer from comment #6) > > > Can you confirm that you get back the correct IP address if you manually > > > resolve that hostname on the firewall? > > > > I think so: > > > > [root@firewall ~]# date > > Sat May 7 15:41:03 CEST 2016 > > [root@firewall ~]# host trikolon-de204.nsupdate.info > > Host trikolon-de204.nsupdate.info not found: 3(NXDOMAIN) > > [root@firewall ~]# ddns update trikolon-de204.nsupdate.info --force > > Dynamic DNS update for trikolon-de204.nsupdate.info (nsupdate.info) > > successful > > [root@firewall ~]# date > > Sat May 7 15:41:36 CEST 2016 > > [root@firewall ~]# host trikolon-de204.nsupdate.info > > Host trikolon-de204.nsupdate.info not found: 3(NXDOMAIN) > > [root@firewall ~]# host trikolon-de204.nsupdate.info > > Host trikolon-de204.nsupdate.info not found: 3(NXDOMAIN) > > [root@firewall ~]# host trikolon-de204.nsupdate.info > > trikolon-de204.nsupdate.info has address 188.97.[REDACTED] > > [root@firewall ~]# date > > Sat May 7 15:42:21 CEST 2016 > > [root@firewall ~]# > > So this looks quite good so far. Do you have the log files from that day > after 15:42 CEST? Would be interesting to know if ddns tried to update again. No, it didn't. Since 15:42 CEST, everything is running fine, there are no days with more than one update try for nsupdate.info. I thereof assume we can close this, since it was a bug at nsupdate.info. Arne guessed in the forum that they didn't pass the updated IP to the DNS; thats my opinion, too. What do you think about that? Everything is working fine here, no errors appeared since my last post. Closing this issue as "NOTABUG", since it was a problem at nsupdate.info (probably). Okay, thanks. Reopen if the problem comes back. |
Created attachment 440 [details] screenshot of the ddns log section in the WebIF Today, nsupdate.info flagged my host as abusive. As the logs for ddns and pppoe connection show, ddns is sending updates even if the public IP address of the IPFire system has not changed meanwhile. Since ddns seems to work with other providers, such as changeip, dynu.com, etc., this appears to be a bug. My system worked well with the nsupdate.info ddns service until a while ago, but there were power outages (and no such log entries appeared). This time it seems to be a bug in the ddns updater itself.