mirror of
https://github.com/qdm12/ddns-updater.git
synced 2026-07-30 01:22:38 -04:00
Bug: Error while using Linode DNS Update #198
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @DevSkoll on GitHub (Jun 30, 2022).
Originally assigned to: @qdm12 on GitHub.
TLDR: Failure (cannot create record: bad HTTP status: 400: {[{name Name contains invalid characters} {name Invalid hostname}]}),
Logs:
Configuration file (remove your credentials!):
Host OS: unRAID
@DevSkoll commented on GitHub (Jun 30, 2022):
Update: This is just an issue when I use the @ record. Might need to find a way to target it without it throwing an error. It worked just fine with a host that had a time.
@DevSkoll commented on GitHub (Jul 1, 2022):
Fixed by resetting the updates.json file. Will throw an error on launch if there are hostnames without input.
@qdm12 commented on GitHub (Jul 2, 2022):
Sorry I didn't get how you fixed it. Can you clarify what was wrong with updates.json so i can fix it for good? Thanks!
@DevSkoll commented on GitHub (Jul 2, 2022):
Haha, my bad.
So my configuration is as follows (Modified with domain.com):
If I stop the service and then start it again with the object as
"host": "", it creates an error in the console where it won't start.The fix I found that works are to delete the data in updates.json every time before I launch the service again. Where it can regenerate it with current info. It will create these entries, but it will not restart and run if that info is already there.
Sorry if this is a bad explanation.
@qdm12 commented on GitHub (Sep 3, 2022):
I changed it in
f09ca2dd0ato set thenamefield to the actual full domain name instead of just the host. So now instead of@it would bedomain.com. As documented https://www.linode.com/docs/api/domains/#domain-record-createClosing this assuming this would fix, but let me know if the problem is still there 😉