Issue with Route53 wildcard record #513

New Issue

saavagebueno · 2025-11-20T04:24:40-05:00

saavagebueno commented

2025-11-20 04:24:40 -05:00

Originally created by @dsw-solutions on GitHub (Mar 31, 2025).

Issue with Route53 wildcard record

Is this urgent: No
DNS provider(s) you use: Route53
Program version: 2024-12-24T09:20:36.130Z (commit 78f3061)
What are you using to run the container: docker-compose (Dockge)
Extra information (optional): It changes the * to any and then creates an any record.

Logs:

2025-03-31T21:09:43Z INFO ipv4 address of any.domain.org is 192.168.1.41 and your ipv4 address is *.*.54.162
2025-03-31T21:09:43Z INFO ipv4 address of domain.org is 192.168.1.41 and your ipv4 address is *.*.54.162
2025-03-31T21:09:43Z INFO Updating record [domain: domain.org | owner: * | provider: route53 | ip: ipv4] to use *.*.54.162
2025-03-31T21:09:43Z INFO Updating record [domain: domain.org | owner: @ | provider: route53 | ip: ipv4] to use *.*.54.162

Configuration file (remove your credentials!):

    {
      "provider": "route53",
      "domain": "*.domain.org,domain.org",
      "ip_version": "ipv4",
      "access_key": "",
      "secret_key": "",
      "zone_id": "",
      "ttl": 300
    }

Host OS: debian

Originally created by @dsw-solutions on GitHub (Mar 31, 2025). *Issue with Route53 wildcard record* 1. Is this urgent: No 2. DNS provider(s) you use: Route53 3. Program version: 2024-12-24T09:20:36.130Z (commit 78f3061) 4. What are you using to run the container: docker-compose (Dockge) 5. Extra information (optional): It changes the * to any and then creates an any record. ![Image](https://github.com/user-attachments/assets/e3f222a1-05ff-46f2-8377-e065d4595edb) ![Image](https://github.com/user-attachments/assets/13d11b72-0d76-46a5-836a-752eb3dfb04e) Logs: ```log 2025-03-31T21:09:43Z INFO ipv4 address of any.domain.org is 192.168.1.41 and your ipv4 address is *.*.54.162 2025-03-31T21:09:43Z INFO ipv4 address of domain.org is 192.168.1.41 and your ipv4 address is *.*.54.162 2025-03-31T21:09:43Z INFO Updating record [domain: domain.org | owner: * | provider: route53 | ip: ipv4] to use *.*.54.162 2025-03-31T21:09:43Z INFO Updating record [domain: domain.org | owner: @ | provider: route53 | ip: ipv4] to use *.*.54.162 ``` Configuration file (**remove your credentials!**): ```json { "provider": "route53", "domain": "*.domain.org,domain.org", "ip_version": "ipv4", "access_key": "", "secret_key": "", "zone_id": "", "ttl": 300 } ``` Host OS: debian

saavagebueno closed this issue

2025-11-20 04:24:40 -05:00

saavagebueno commented

2025-11-20 04:24:40 -05:00

@rex commented on GitHub (Sep 22, 2025):

I am seeing identical behavior as well. Workaround is of course to create a whole bunch of subdomains manually and add them to DDNS config, but that is brutal and should be unnecessary.

@rex commented on GitHub (Sep 22, 2025): I am seeing identical behavior as well. Workaround is of course to create a whole bunch of subdomains manually and add them to DDNS config, but that is brutal and should be unnecessary.

saavagebueno referenced this issue

2025-11-20 04:25:50 -05:00

[PR #513] [MERGED] Fix IPs in some logging messages #720

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/ddns-updater#513