Hello, I’ve configured my Nokia fiber router/firewall as follows.
But it doesn’t seem to update the A-record that corresponds with this domain.
I’ve set up the A-record with a temporary address.
What could be the issue? AFAIK I’ve configured the DNS and DDNS correctly.
The token keeps saying it has never been used. And it’s value should be correct as well.
I’ve also allready made sure my provider isn’t using CGNAT.
Thanks for any input you might have.
Try to use the domain you want to modify as both the “Username” and the “Domain Name”. See the API documentation for more information.
1 Like
Hello, funny thing is I found out more or less at the same time.
I’m now using the domain as both domain and username.
I now have an item in my token list as being used 10 minutes ago.
However, the A-record hasn’t been updated?
Additionally; the token used is not the same as the token that I created as an entry?
Hard to tell which one you actually used. The “Password” in that router form isn’t your account password. You should use the token that you created.
Hmm, yeah that’s what I understood regardless of which username I used before. It is the token in the password field…
What would your advice be moving forward, create a new token and try that one? Do you think my configuration of the domain is correct?
The address is obviously a non correct temporary one…
If you’re not sure you used the correct token, which can be difficult because they’re only shown once, simply create a new one and use that. Clean up unused tokens later.
Are you using your own domain with desec.io or a subdomain of dedyn.io? Assuming you’re using somename.dedyn.io, the address record you show would be for dyn.somename.dedyn.io, which would go in the router form. If you’re hosting yourdomain.abc at desec.io, that record is for dyn.yourdomain.abc, and then that needs to be put in the router form.
1 Like
Hi GenericUser, thanks for your quick responses!
I’m using a custom domain, let’s say test.com.
So in my router I have configured dyn.test.com as domain and user.
In my DNS I have an A-record defined as A dyn 100.100.100.100
My original token was issued related to dyn as you can see in the second screenshot. Or do I need to leave the field ‘name’ empty?
I will create a new token and test that.
The name is just so that you can tell the tokens apart in the user interface. It has no relevance to the token’s function. Tokens can be restricted to certain domains, even down to individual subnames and record types, but that isn’t exposed in the web interface. You’d need to use the API to create policy restrictions. All tokens you create in the web interface can from the get-go modify all domains and records in your account.
1 Like
So, I created a new token, added it to my router.
And again I see that an additional token line is added to the tokenlist.
Probably an update by my router.
But the new token I added myself doesn’t get the mention “last used”.
The token added by my router now has a mention “less than a minute ago”.
I also removed the existing A-record as the token should be able to create and delete domains.
It appears your router does some unnecessary elaborate dance there. Does it have a “custom” option where you can just enter an update URL? That may be easier to use.
Afraid not, it only has a preconfigured dropdownlist of DDNS-providers.
Hi Ronin,
welcome to deSEC! 
That is your log-in token which is used by the web interface. (Technically it just uses the API.)
That’s only the case if you turned on those permissions in the token configuration in the web interface. But, to create a record, it’s not necessary to have permission to create a domain.
If the domain already exists, a token with default settings will be able to create an A record inside it.
Stay secure,
Peter
3 Likes
Hello peter, thanks for your response! I was on my message limit so had to wait to be able to reply.
Ok so if I take your remarks into account; the router then never contacts desec.io… Because the configured token in the webinterface and in my router is never used… Regardless if I already have an A-record with a temp value or not…
Not sure how to continue from here :S
Ok, so I figured the Nokia is probably the problem.
I installed ddclient in a docker on a server and now the A-record is succesfully being updated using the token:
SUCCESS: [dyndns2][mydomain]> IPv4 address set to myip.myip.myip.myip
Thanks for helping out, just a shame Nokia didn’t implement DDNS very well apparently…!