starred/ddns-updater
1
0
Fork 0
mirror of https://github.com/qdm12/ddns-updater.git synced 2026-08-02 18:48:49 -04:00
Code Issues 312 Packages Projects Releases 10 Wiki Activity

Bug: Wildcard on first subdomain level resolving not working #317

New Issue
Closed
opened 2025-11-20 04:22:40 -05:00 by saavagebueno · 6 comments
saavagebueno commented 2025-11-20 04:22:40 -05:00
Owner
Copy Link

Originally created by @LeoSum8 on GitHub (Oct 4, 2023).

TLDR: dns resolve of wildcard domain not working when on first subdomain level (.example.com) while update works*

  1. Is this urgent: No

  2. DNS provider(s) you use: INWX

  3. Program version:

    Running version latest built on 2023-09-13T19:49:02.170Z (commit 13ccb4f)

  4. What are you using to run the container: docker

  5. Extra information (optional)

Logs:

2023-10-04T10:11:50Z INFO reading JSON config from file /updater/data/config.json
2023-10-04T10:11:50Z INFO Found single setting to update record
2023-10-04T10:11:50Z INFO Reading history from database: domain *.example.com host @
2023-10-04T10:11:50Z INFO [backup] disabled
2023-10-04T10:11:50Z INFO [http server] listening on :8000
2023-10-04T10:11:50Z INFO [healthcheck server] listening on 127.0.0.1:9999
2023-10-04T10:11:50Z WARN cannot DNS resolve *.example.com after 5 tries: lookup *.example.com: no such host
2023-10-04T10:11:50Z INFO IPv6 address of *.example.com is invalid IP and your IPv6 address is 2ab2:6dd4:37c9:3101:3832:a80b:1234:1234
2023-10-04T10:11:50Z INFO Updating record [domain: *.example.com | host: @ | provider: inwx | ip: ipv6] to use 2ab2:6dd4:37c9:3101:3832:a80b:1234:1234

Configuration file (remove your credentials!):

{
  "settings": [
    {
      "provider": "inwx",
      "domain": "*.example.com",
      "host": "@",
      "username": "admin",
      "password": "admin",
      "ip_version": "ipv6"
    }
  ]
}

Host OS: Fedore Core OS (FCOS) runing in a bhyve vm on FreeBSD

Hi there,
I am running the above-mentioned setup.
While updating works, the lookup/resolving doesn't, which leads to the update unnecessarily happening every 5 minutes.
I noticed the issue #214 where something similar is adressed but for lower domain levels. Shouldn't my config also lead to doing the dns lookup for any.example.com?

Thanks for your docker image!
Leo

Originally created by @LeoSum8 on GitHub (Oct 4, 2023). <!-- YOU CAN CHAT THERE EVENTUALLY: https://github.com/qdm12/ddns-updater/discussions --> **TLDR**: *dns resolve of wildcard domain not working when on first subdomain level (*.example.com) while update works* 1. Is this urgent: No 2. DNS provider(s) you use: INWX 3. Program version: <!-- See the line at the top of your logs --> `Running version latest built on 2023-09-13T19:49:02.170Z (commit 13ccb4f)` 4. What are you using to run the container: docker 5. Extra information (optional) Logs: ``` 2023-10-04T10:11:50Z INFO reading JSON config from file /updater/data/config.json 2023-10-04T10:11:50Z INFO Found single setting to update record 2023-10-04T10:11:50Z INFO Reading history from database: domain *.example.com host @ 2023-10-04T10:11:50Z INFO [backup] disabled 2023-10-04T10:11:50Z INFO [http server] listening on :8000 2023-10-04T10:11:50Z INFO [healthcheck server] listening on 127.0.0.1:9999 2023-10-04T10:11:50Z WARN cannot DNS resolve *.example.com after 5 tries: lookup *.example.com: no such host 2023-10-04T10:11:50Z INFO IPv6 address of *.example.com is invalid IP and your IPv6 address is 2ab2:6dd4:37c9:3101:3832:a80b:1234:1234 2023-10-04T10:11:50Z INFO Updating record [domain: *.example.com | host: @ | provider: inwx | ip: ipv6] to use 2ab2:6dd4:37c9:3101:3832:a80b:1234:1234 ``` Configuration file (**remove your credentials!**): ```json { "settings": [ { "provider": "inwx", "domain": "*.example.com", "host": "@", "username": "admin", "password": "admin", "ip_version": "ipv6" } ] } ``` Host OS: Fedore Core OS (FCOS) runing in a bhyve vm on FreeBSD Hi there, I am running the above-mentioned setup. While updating works, the lookup/resolving doesn't, which leads to the update unnecessarily happening every 5 minutes. I noticed the issue #214 where something similar is adressed but for lower domain levels. Shouldn't my config also lead to doing the dns lookup for any.example.com? Thanks for your docker image! Leo
saavagebueno commented 2025-11-20 04:22:41 -05:00
Author
Owner
Copy Link

@LeVraiRoiDHyrule commented on GitHub (Jan 5, 2024):

Hi, I think I am having a similar problem and I can't find how to solve it. I want to update the root of my domain, "@", while having the web UI on a subdomain (ddns.mydomain.com). Apparently this makes the DNS lookup to fail.

@LeVraiRoiDHyrule commented on GitHub (Jan 5, 2024): Hi, I think I am having a similar problem and I can't find how to solve it. I want to update the root of my domain, "@", while having the web UI on a subdomain (ddns.mydomain.com). Apparently this makes the DNS lookup to fail.
saavagebueno commented 2025-11-20 04:22:41 -05:00
Author
Owner
Copy Link

@qdm12 commented on GitHub (Jan 18, 2024):

@LeoSum8 Hi there, sorry for the delay answering 😢!
It looks like you're using the @ host with *.example.com, why are you trying to do this 🤔? Sorry if I misunderstood or don't know something, but why not * host and example.com domain to update the wildcard *.example.com?
Note to myself: if you did have a misunderstanding, I'll add a check to error out if * is present in the domain field, for all providers.

@LeVraiRoiDHyrule I don't fully understand your issue, where you serve the web ui and what domains you update are independent, please create another issue with the requested information.

@qdm12 commented on GitHub (Jan 18, 2024): @LeoSum8 Hi there, sorry for the delay answering 😢! It looks like you're using the `@` host with `*.example.com`, why are you trying to do this 🤔? Sorry if I misunderstood or don't know something, but why not `*` host and `example.com` domain to update the wildcard `*.example.com`? Note to myself: if you did have a misunderstanding, I'll add a check to error out if `*` is present in the domain field, for all providers. @LeVraiRoiDHyrule I don't fully understand your issue, where you serve the web ui and what domains you update are independent, please create another issue with the requested information.
saavagebueno commented 2025-11-20 04:22:41 -05:00
Author
Owner
Copy Link

@LeoSum8 commented on GitHub (Feb 12, 2024):

Hi @qdm12 sorry myself for answering so late now.

I tried your suggestion. But when I put * for host, I get:

2024-02-12T14:07:59Z INFO reading JSON config from file /updater/data/config.json
2024-02-12T14:07:59Z ERROR validating provider settings: host cannot be a "*"
2024-02-12T14:07:59Z INFO Shutdown successful
@LeoSum8 commented on GitHub (Feb 12, 2024): Hi @qdm12 sorry myself for answering so late now. I tried your suggestion. But when I put * for host, I get: ``` 2024-02-12T14:07:59Z INFO reading JSON config from file /updater/data/config.json 2024-02-12T14:07:59Z ERROR validating provider settings: host cannot be a "*" 2024-02-12T14:07:59Z INFO Shutdown successful ```
saavagebueno commented 2025-11-20 04:22:41 -05:00
Author
Owner
Copy Link

@qdm12 commented on GitHub (Feb 12, 2024):

I removed the restriction in d009ef3d3e please try pulling the latest image and check if it works? I'm not too sure why the restriction was in place and if inwx supports dynamically updating a record with a wildcard owner (host), but let's find out!

(wait 5 minutes for the build to finish)

@qdm12 commented on GitHub (Feb 12, 2024): I removed the restriction in d009ef3d3e9de92752a29bb71706ff0c58bd2a2a please try pulling the latest image and check if it works? I'm not too sure why the restriction was in place and if inwx supports dynamically updating a record with a wildcard owner (host), but let's find out! (wait 5 minutes for the build to finish)
saavagebueno commented 2025-11-20 04:22:42 -05:00
Author
Owner
Copy Link

@LeoSum8 commented on GitHub (Feb 13, 2024):

Thank you, this seems to have done the trick!
Now everything looks normal.
Where is your tipjar? :)

To be clear: It worked before with the @-construction in terms of updating, but it just wouldn't be able to check the ip. Now the logs and the webinterface look normal and show everything is up to date.

@LeoSum8 commented on GitHub (Feb 13, 2024): Thank you, this seems to have done the trick! Now everything looks normal. Where is your tipjar? :) To be clear: It worked before with the @-construction in terms of updating, but it just wouldn't be able to check the ip. Now the logs and the webinterface look normal and show everything is up to date.
saavagebueno commented 2025-11-20 04:22:42 -05:00
Author
Owner
Copy Link

@qdm12 commented on GitHub (Feb 19, 2024):

Great 💯

Where is your tipjar? :)

Thanks, but don't worry that was a 10 seconds code change 😄
Buuut if you're still happy about the whole project (and me working part-time-no-pay on it), you can check out https://github.com/qdm12/ddns-updater?tab=readme-ov-file#support 🤑

@qdm12 commented on GitHub (Feb 19, 2024): Great 💯 > Where is your tipjar? :) Thanks, but don't worry that was a 10 seconds code change 😄 Buuut if you're still happy about the whole project (and me working part-time-no-pay on it), you can check out https://github.com/qdm12/ddns-updater?tab=readme-ov-file#support 🤑
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Category: Config problem 📝
Category: Database 🗃️
Category: Documentation ✒️
Category: Foolproof settings 👼
Category: Good idea 🎯
Category: Healthcheck 🩺
Category: IP fetching 📥
Category: Label missing ❗
Category: Maintenance ⛓️
Category: Motivated! 🙌
Category: New provider 🆕
Category: Provider update ♻️
Category: Shoutrrr 📢
Category: Web UI 🖱️
Category: Wildcard 🃏
Closed: ⚰️ Inactive
Closed: 👥 Duplicate
Closed: 🗑️ Bad issue
Complexity: ☣️ Hard to do
Complexity: 🟩 Easy to do
Priority: 💤 Low priority
Priority: 🚨 Urgent
pull-request
Mirrored from GitHub Pull Request
 Status: 🔒 After next release
Status: 🔴 Blocked
Status: 🗯️ Waiting for feedback
No Label Category: Config problem 📝 Closed: ⚰️ Inactive Status: 🗯️ Waiting for feedback
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ddns-updater#317
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?