I've gotten ddns to work with a single domain, with settings below.
However I can't seem to be able to get multiple ones updated. I've tried adding domain1.com -a domain2.com but then it thinks -a is an invalid host. If I just use a space between the domains, it does nothing at all...
Code:
In-a-dyn version 2.10.0 -- Dynamic DNS update client.
Startup delay: 30 sec ...
Failed resolving hostname -a: Name does not resolve
Update forced for alias -a, new IP# 1.2.3.4
HTTP 400: Cloudflare says our request was invalid. Possibly a malformed API token.
Fatal error in DDNS server response:
[400 Bad Request] {"result":null,"success":false,"errors":[{"code":1004,"message":"DNS Validation Error","error_chain":[{"code":9000,"message":"DNS name is invalid."
I know there are other ways to do this, but it would be nice to keep all the work "inhouse".
Joined: 08 May 2018 Posts: 14249 Location: Texas, USA
Posted: Fri Sep 01, 2023 2:31 Post subject:
The latest commit on the source code for inadynv2 is 52714, the latest commit to DDNS.asp is 53045, and that is about as far as I'm going to dig to suggest updating to the current release and testing it, but also, that wiki is old and unmaintained:
Using DNS to handle this would be an option, but seems like a bit of a hack. Considering the functionality is there...
I seem to have managed to get two hosts updated by just putting them next to each other, no commas, no -a. sub1.domain.com sub2.domain.com
It didn't seem to be working as the Service Status never updated after saving and applying settings, but if I reboot the router, it does run correctly. We'll see if it updates later today.
In the /tmp/ddns/inadyn.conf file the hostname shows as {"sub1.domain.com", "sub2.domain.com"} so that seems correct per the inadyn docs.
Only issue I'm seeing now is that the proxied option is not available, so the Cloudflare orange cloud is not set.
So for the time being I am able to get this to work and set the Orange Cloud (proxi) through the Administration -> Commands setting. Kill the inadyn process and then run again with custom inadyn.conf file.
It's essentially the same file as the /tmp/ddns/inadyn/inadyn.com that can be setup through the GUI, but since we can't add multiple hostnames or enable the proxi setting we can use this in the conf file instead:
