ddns-scripts: update no-ip.com domain-name

[GrumpyMeow]

Maintainer: nobody?
Compile tested: x86-64
Run tested: x86-64

Description:
There are multiple issues about the ddns not working for no-ip.com. It might be actually because of still using the old domain-name..

Maybe related:

• DDNS. No-ip.com need to fix url. #25093
• ddns script for noip.com is not working,  #19389

[gadall]

The sole purpose of the dedicated no-ip.com script seems to be to first update the DNS record with 127.0.0.1 or ::1 and then with the real IP address.

The script contains the comment:

provider did not reactivate records, if no IP change was recognized
so we send a dummy (localhost) and a seconds later we send the correct IP addr

This goes back a very long time. The current policy for expiration is described here:

https://www.noip.com/support/faq/frequently-asked-questions#463

The user needs to click a confirmation link every 30 days. I can't find any references to records expiring when not updated, or updated but never changed. It looks like the no-ip.com script can just be deleted, the update URL should be updated in the json file and the generic code would work just fine.

Maybe try that?

As for the domain names:
dynupdate6.no-ip.com has no A or AAAA record.
dynupdate6.noip.com/nic/update does seem to accept requests, but it's not mentioned in https://www.noip.com/integrate/request
dynupdate6.noip.com has only an AAAA record, no A record. That looks like it's intended for requests lacking an myip= parameter. Since the request can only come via IPv6, the server will update the record with the client's IPv6 address.
Since OpenWRT will always use the myip= parameter, this isn't needed.

dynupdate.noip.com and dynupdate.no-ip.com resolve to the same IPv4 address, i.e. they are the same server. That would suggest they should behave the same way. But following the documentation is generally a good idea.