You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all: Thanks a lot for making this. I have been experiencing some DNS-related instabilities that I believe are related to my current DDNS-provider, and I hope that by updating directly at Domeneshop I will get a much smoother experience.
So I am trying to update *.mydomain.com using your docker-image from DockerHub, but struggling to make it work.
Putting DOMAINS: anything.mydomain.com
in docker-compose.yml works perfectly, but none of the following work: DOMAINS: *.mydomain.com DOMAINS: "*.mydomain.com" DOMAINS: \*.mydomain.com DOMAINS: "\*.mydomain.com"
If docker-compose doesn't complain about the syntax of the file, the container yields the following:
> [email protected] production /app
> node -r dotenv-safe/config ./dist/index.js
info: Started with IP x.x.x.x. Running once and then every 30 minutes {"timestamp":"2021-09-04 17:26:14"}
(node:20) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'id' of undefined
at _loop$ (/app/dist/checkDomainRecords.js:121:70)
at tryCatch (/app/node_modules/regenerator-runtime/runtime.js:63:40)
at Generator.invoke [as _invoke] (/app/node_modules/regenerator-runtime/runtime.js:293:22)
at Generator.next (/app/node_modules/regenerator-runtime/runtime.js:118:21)
at tryCatch (/app/node_modules/regenerator-runtime/runtime.js:63:40)
at maybeInvokeDelegate (/app/node_modules/regenerator-runtime/runtime.js:356:18)
at Generator.invoke [as _invoke] (/app/node_modules/regenerator-runtime/runtime.js:267:32)
at Generator.next (/app/node_modules/regenerator-runtime/runtime.js:118:21)
at asyncGeneratorStep (/app/node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:24)
at _next (/app/node_modules/@babel/runtime/helpers/asyncToGenerator.js:25:9)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:20) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:20) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
The API allows to update wildcards, as the following works just fine: curl https://{token}:{secret}@api.domeneshop.no/v0/dyndns/update\?hostname\=\*.mydomain.com\&myip\=1.2.3.4
Is there a trick to adding wildcards to the docker-compose file, or is this something you may be able to fix in the code?
The text was updated successfully, but these errors were encountered:
First of all: Thanks a lot for making this. I have been experiencing some DNS-related instabilities that I believe are related to my current DDNS-provider, and I hope that by updating directly at Domeneshop I will get a much smoother experience.
So I am trying to update *.mydomain.com using your docker-image from DockerHub, but struggling to make it work.
Putting
DOMAINS: anything.mydomain.com
in docker-compose.yml works perfectly, but none of the following work:
DOMAINS: *.mydomain.com
DOMAINS: "*.mydomain.com"
DOMAINS: \*.mydomain.com
DOMAINS: "\*.mydomain.com"
If docker-compose doesn't complain about the syntax of the file, the container yields the following:
The API allows to update wildcards, as the following works just fine:
curl https://{token}:{secret}@api.domeneshop.no/v0/dyndns/update\?hostname\=\*.mydomain.com\&myip\=1.2.3.4
Is there a trick to adding wildcards to the docker-compose file, or is this something you may be able to fix in the code?
The text was updated successfully, but these errors were encountered: