Update ip4 (A) records via DyNDNS or api calls

IPv64.net - Services
1

From the start, my apologies if this questions has already been posted, due to my limited german I might have missed it.

I have a standard account with a hostname aaa.bbb.ipv64.net.
I’m trying to update the related api using curl. Based o the documentation found (IPv64.net • DynDNS2 & API Documentation - IPv4 & IPv6) I’ve tried the followings :

curl --request POST --location https://ipv64.net/update.php?key=xxxxxxxxxxxxxxxxxxxxxxxx\&hostname=aaa.bbb.ipv64.net\&ip4=111.122.133.144

curl --request POST --location https://ipv4.ipv64.net/api.php?apikey=xxxxxxxxxxxxxxxxxxxxxxxx\&host=aaa.bbb.ipv64.net\&ip=111.122.133.144

I’ve tried other minor variatons of the above commands by replacing „host“ with „hostname“ or „ip“ with „ip4“ and „ipv4“

For all my requests I get http200 back and {„status“:„success“}

The ip however dosn;t change :frowning:
What am I missing ? … or how should I do this froma the cli ?

2

Did you try this (as per the examples on the documentation page you posted):

curl --request POST --location https://ipv64.net/nic/update?key=xxxxxxxxxxxxxxxxxxxxxxxx&domain=aaa.bbb.ipv64.net&ip4=111.122.133.144
3

Just tried it. No luck.
I still get back „{„status“:„success“}“ but IP doesn’t change :frowning:
Any other ideas ? Isn’t this suppose to be the most basic functionality of a DynDNS server ?

4

Well, did you try the CURL example as stated on the documentation page:

CURL Example:

curl -sSL -H "Authorization: Basic $(echo -n none:xxxxxxxxxxxxxxxxxxxxxxxx | base64)" https://ipv64.net/nic/update?domain=YOURDOMAIN.IPV64.NET
5

Just did. Still the same… I get „{„status“:„success“}“ back but the ip doesn’t change.
This latest command it’s actually even crazier, 'cos it doesn’t even specify the IP ??? … so how would it know what’s the new value ???
Anyways, thx for the suggestions :slight_smile:

6

Paep, did you ever read my PM’s I send you here?
At Saturday i send you two PM’s here with hints how to solve the Problem.
Most likely you did not noticed them. So scroll down in the left part of the v64.tect start page until you see the Posteingang. There you will find them. Maybe it will help.

7

New user can’t read or send PM’s, rank is to low

8

Hi there, I just noticed you messages.
Yes, I’ve tried the rapspberrypi related commands but it didn’t work :frowning:

9

Dears,

just to preempt possible future discussion, I did notice that there is also a debian package that I could install (ipv64-ddns-update). The reason so far I did not try this is two fold :

  • I think is overkill to install the package to achieve the result that could reach with a simple curl command
  • If the package doesn’t work I have even less chance to sort it out

I do however accept the package as a last resort if I run out of ideas to get it done with curl.
So, for the time being, any additional curl related ideas are welcome :slight_smile:

10

I wrote you before in the PM here. Your example shown above (aaa.bbb.ipv64.net) is not an example of a standard DynDNS Domain of ipv64, but that of a Subdomain (Präfix) of it. Standard would be bbb.ipv64.net. the aaa in front of it in your example makes it to a subdomain of the DynDNS Domain.
So if you really need to update that you need to setup a Präfix and use the according Präfix-/Subdomain Update Token. Even in that case the aaa-Subdomain part is not part of the update String.