[GH-ISSUE #165] Wrong Update-URL for FRITZ!Box 3170 (and maybe others)

kerem commented

2026-02-26 09:36:09 +03:00

Owner

Originally created by @1f5 on GitHub (Sep 13, 2014).
Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/165

After a long struggle i found out, that that Update-URL stated in the "AVM Fritz!Box"-Tab of the Configuration Menu does not work. Using "https://ipv4.nsupdate.info/nic/update" will lead to "Status: unkown" in the Fritz!Box web interface. Removing the "https://" from the text field and only leaving "ipv4.nsupdate.info/nic/update" at least sometimes works.

Since i do not own neither a Fritz!Box 6360 nor 7390 (the ones confirmed working on nsupdate.info), i could not test if the stated configuration might be wrong for these, too.

Firmware-Version is: 49.04.58

After rebooting the Fritz!Box the corrected update-url stopped working again. It now says "Status: Error".
I have no idea what this thing is trying to say me, but please fix this.

Originally created by @1f5 on GitHub (Sep 13, 2014). Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/165 After a long struggle i found out, that that Update-URL stated in the "AVM Fritz!Box"-Tab of the Configuration Menu does not work. Using "https://ipv4.nsupdate.info/nic/update" will lead to "Status: unkown" in the Fritz!Box web interface. Removing the "https://" from the text field and only leaving "ipv4.nsupdate.info/nic/update" at least sometimes works. Since i do not own neither a Fritz!Box 6360 nor 7390 (the ones confirmed working on nsupdate.info), i could not test if the stated configuration might be wrong for these, too. Firmware-Version is: 49.04.58 After rebooting the Fritz!Box the corrected update-url stopped working again. It now says "Status: Error". I have no idea what this thing is trying to say me, but please fix this.

kerem

2026-02-26 09:36:09 +03:00

closed this issue
added the
invalid
label

kerem commented

2026-02-26 09:36:09 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Sep 16, 2014):

the given configuration was practically tested on 6360 and 7390 (I have both, personally) and works.

it might be that AVM changed how they process the form fields.

what I am wondering: if you just enter the host name without protocol, does it do a http or https update then? do you see "TLS" for that host?

also, if it says "error", please log into the https://nsupdate.info/ site using a web browser and look at your record, a more precise reason of the error should be visible there, please post it here.

@ThomasWaldmann commented on GitHub (Sep 16, 2014): the given configuration was practically tested on 6360 and 7390 (I have both, personally) and works. it might be that AVM changed how they process the form fields. what I am wondering: if you just enter the host name without protocol, does it do a http or https update then? do you see "TLS" for that host? also, if it says "error", please log into the https://nsupdate.info/ site using a web browser and look at your record, a more precise reason of the error should be visible there, please post it here.

kerem commented

2026-02-26 09:36:10 +03:00

Author

Owner

@1f5 commented on GitHub (Sep 17, 2014):

Thanks for your reply!

I have no doubt, that it works with 6360 and 7390, but could you please check their firmware-version? Maybe the Firmware i have is just broken.

When i input the the Update-URL without protocol (ipv4.nsupdate.info/nic/update), an then activate it after logging into nsupdate.info, it works for once. nsupdate.info then states, that it updated the IP address without TLS. However, as soon as i try to test if it updates to a new IP by rebooting the fritzbox, it does not work any more and states "Status: Error". When i log into nsupdate.info then, it still has the old IP address and seems not to notice that there were any problems. When i then deactivate Dynamic DNS in the fritzbox and activate it again, nothing changes.

When i then change the Update-URL to "https://ipv4.nsupdate.info/nic/update", it say "Status: unknown" and at nsupdate.info nothing changes again.

So: TLS does not seem to work at all. Without TLS is works only sometimes. And nsupdate.info does not seem to be aware of any errors.

@1f5 commented on GitHub (Sep 17, 2014): Thanks for your reply! I have no doubt, that it works with 6360 and 7390, but could you please check their firmware-version? Maybe the Firmware i have is just broken. When i input the the Update-URL without protocol (ipv4.nsupdate.info/nic/update), an then activate it after logging into nsupdate.info, it works for once. nsupdate.info then states, that it updated the IP address without TLS. However, as soon as i try to test if it updates to a new IP by rebooting the fritzbox, it does not work any more and states "Status: Error". When i log into nsupdate.info then, it still has the old IP address and seems not to notice that there were any problems. When i then deactivate Dynamic DNS in the fritzbox and activate it again, nothing changes. When i then change the Update-URL to "https://ipv4.nsupdate.info/nic/update", it say "Status: unknown" and at nsupdate.info nothing changes again. So: TLS does not seem to work at all. Without TLS is works only sometimes. And nsupdate.info does not seem to be aware of any errors.

kerem commented

2026-02-26 09:36:10 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Sep 17, 2014):

I have no doubt, that it works with 6360 and 7390, but could you please
check their firmware-version? Maybe the Firmware i have is just broken.

It is the latest available.

But I remember 6.03 also worked for me.

When i input the the Update-URL without protocol
(ipv4.nsupdate.info/nic/update), an then activate it after logging into
nsupdate.info, it works for once. nsupdate.info then states, that it
updated the IP address without TLS.

OK, then it automatically prepends http:// in that case.

However, as soon as i try to test if
it updates to a new IP by rebooting the fritzbox, it does not work any
more and states "Status: Error". When i log into nsupdate.info then, it
still has the old IP address and seems not to notice that there were any
problems.

If there is an error, you should see it in the server message field near
the bottom of the host view page.

When i then deactivate Dynamic DNS in the fritzbox and
activate it again, nothing changes.

Sounds broken.

When i then change the Update-URL to
"https://ipv4.nsupdate.info/nic/update", it say "Status: unknown" and at
nsupdate.info nothing changes again.

So: TLS does not seem to work at all. Without TLS is works only
sometimes. And nsupdate.info does not seem to be aware of any errors.

If you like, you can give a precise hostname and UTC times (for such a
"first update" and "second update").

I could look it up in the logs then and show you what happened on the
server side.

@ThomasWaldmann commented on GitHub (Sep 17, 2014): > I have no doubt, that it works with 6360 and 7390, but could you please > check their firmware-version? Maybe the Firmware i have is just broken. It is the latest available. But I remember 6.03 also worked for me. > When i input the the Update-URL without protocol > (ipv4.nsupdate.info/nic/update), an then activate it after logging into > nsupdate.info, it works for once. nsupdate.info then states, that it > updated the IP address without TLS. OK, then it automatically prepends http:// in that case. > However, as soon as i try to test if > it updates to a new IP by rebooting the fritzbox, it does not work any > more and states "Status: Error". When i log into nsupdate.info then, it > still has the old IP address and seems not to notice that there were any > problems. If there is an error, you should see it in the server message field near the bottom of the host view page. > When i then deactivate Dynamic DNS in the fritzbox and > activate it again, nothing changes. Sounds broken. > When i then change the Update-URL to > "https://ipv4.nsupdate.info/nic/update", it say "Status: unknown" and at > nsupdate.info nothing changes again. > > So: TLS does not seem to work at all. Without TLS is works only > sometimes. And nsupdate.info does not seem to be aware of any errors. If you like, you can give a precise hostname and UTC times (for such a "first update" and "second update"). I could look it up in the logs then and show you what happened on the server side.

kerem commented

2026-02-26 09:36:10 +03:00

Author

Owner

@1f5 commented on GitHub (Sep 17, 2014):

Hostname is 1f5.nsupdate.info
Unfortunately, i do not have the exact UTC times, but i did all the things i said just a few minutes before i posted them here.

@1f5 commented on GitHub (Sep 17, 2014): Hostname is 1f5.nsupdate.info Unfortunately, i do not have the exact UTC times, but i did all the things i said just a few minutes before i posted them here.

kerem commented

2026-02-26 09:36:10 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Sep 18, 2014):

As far as my logs tell, that host NEVER received an update via /nic/update API url.

That it resolved to correct IP at first is because we add the current remote_addr into dns when you create the host on the web UI.

@ThomasWaldmann commented on GitHub (Sep 18, 2014): As far as my logs tell, that host NEVER received an update via /nic/update API url. That it resolved to correct IP at first is because we add the current remote_addr into dns when you create the host on the web UI.

kerem commented

2026-02-26 09:36:10 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Sep 18, 2014):

It seems to me that the ddns updater in the specific firmware you run does not work at all.

If there is a newer firmware available for that model, try updating the firmware (that might be also interesting due to the recent security issues discovered in some FB firmwares).

Maybe it would help if you open a ticket with AVM, so they fix their ddns updater. It might not be a big effort, considering they have a working one in more recent firmware releases. Of course it depends on whether they want to still support that specific model at all.

If you feel more adventurous, you could even try firmware not from AVM (not sure if they are better, though). There is some risk with doing this, though, read their docs first. http://freetz.org/

As also pointed out in our documentation, you could run an update client on some machine inside your network, it is not required to do this on the router. E.g. ddclient for Linux works quite stable and we support its configuration in the help assistent shown after adding a host, so you just need to copy&paste that into ddclient.conf. If that's not an option, there is lots of other dyndns2 compatible update software also.

If nothing else help, you could even run our browser-based updater (also shown in that assistant).

As this is not a problem located in nsupdate.info software or service, I am closing this now.

@ThomasWaldmann commented on GitHub (Sep 18, 2014): It seems to me that the ddns updater in the specific firmware you run does not work at all. If there is a newer firmware available for that model, try updating the firmware (that might be also interesting due to the recent security issues discovered in some FB firmwares). Maybe it would help if you open a ticket with AVM, so they fix their ddns updater. It might not be a big effort, considering they have a working one in more recent firmware releases. Of course it depends on whether they want to still support that specific model at all. If you feel more adventurous, you could even try firmware not from AVM (not sure if they are better, though). There is some risk with doing this, though, read their docs first. http://freetz.org/ As also pointed out in our documentation, you could run an update client on some machine inside your network, it is not required to do this on the router. E.g. ddclient for Linux works quite stable and we support its configuration in the help assistent shown after adding a host, so you just need to copy&paste that into ddclient.conf. If that's not an option, there is lots of other dyndns2 compatible update software also. If nothing else help, you could even run our browser-based updater (also shown in that assistant). As this is not a problem located in nsupdate.info software or service, I am closing this now.

Rows
Columns

[GH-ISSUE #165] Wrong Update-URL for FRITZ!Box 3170 (and maybe others) #156