Bug: Porkbun new wildcard entry instead of updating existing one #406

New Issue

saavagebueno · 2025-11-20T04:23:47-05:00

saavagebueno commented

2025-11-20 04:23:47 -05:00

Originally created by @MalibThalion on GitHub (May 26, 2024).

New A wildcard entry on porkbun instead of updating the existing one

Is this urgent: No
DNS provider(s) you use: porkbun
Program version:

Running version latest built on 2024-05-23T13:33:03.304Z (commit 8e09cd6)

What are you using to run the container: unraid app (CA)
Extra information (optional)

Logs:

INFO reading JSON config from file /updater/data/config.json
INFO Found 3 settings to update records
INFO Reading history from database: domain domain.com host palworld ipv4
INFO Reading history from database: domain domain.com host @ ipv4
INFO Reading history from database: domain domain.com host * ipv4
INFO [healthcheck server] listening on 127.0.0.1:9999
INFO [backup] disabled
INFO [http server] listening on :8000
INFO obtaining ipv4 address succeeded after 1 failed try
INFO ipv4 address of any.domain.com is XXX.XXX.XXX.27 and your ipv4 address  is XXX.XXX.XXX.151
INFO Updating record [domain: domain.com| host: * | provider: porkbun | ip: ipv4] to use XXX.XXX.XXX.151
ERROR creating record: HTTP status is not valid: 400: Create error: We were unable to create the DNS record.

Configuration file (remove your credentials!):

  "settings": [
    {
      "provider": "porkbun",
      "domain": "domain.com
      "host": "palworld,@,*",
      "api_key": "KEY",
      "secret_api_key": "KEY",
      "ip_version": "ipv4",
      "ipv6_suffix": ""
    }
  ]
}

Host OS:
Unraid

Originally created by @MalibThalion on GitHub (May 26, 2024).  New A wildcard entry on porkbun instead of updating the existing one 1. Is this urgent: No 2. DNS provider(s) you use: porkbun 3. Program version: Running version latest built on 2024-05-23T13:33:03.304Z (commit 8e09cd6) 4. What are you using to run the container: unraid app (CA) 5. Extra information (optional) Logs: ``` INFO reading JSON config from file /updater/data/config.json INFO Found 3 settings to update records INFO Reading history from database: domain domain.com host palworld ipv4 INFO Reading history from database: domain domain.com host @ ipv4 INFO Reading history from database: domain domain.com host * ipv4 INFO [healthcheck server] listening on 127.0.0.1:9999 INFO [backup] disabled INFO [http server] listening on :8000 INFO obtaining ipv4 address succeeded after 1 failed try INFO ipv4 address of any.domain.com is XXX.XXX.XXX.27 and your ipv4 address is XXX.XXX.XXX.151 INFO Updating record [domain: domain.com| host: * | provider: porkbun | ip: ipv4] to use XXX.XXX.XXX.151 ERROR creating record: HTTP status is not valid: 400: Create error: We were unable to create the DNS record. ``` Configuration file (**remove your credentials!**): ```{ "settings": [ { "provider": "porkbun", "domain": "domain.com "host": "palworld,@,*", "api_key": "KEY", "secret_api_key": "KEY", "ip_version": "ipv4", "ipv6_suffix": "" } ] } ``` Host OS: Unraid

saavagebueno added the Status: 🗯️ Waiting for feedback Priority: 🚨 Urgent Category: Provider update ♻️Category: Wildcard 🃏 labels 2025-11-20 04:23:47 -05:00

saavagebueno closed this issue

2025-11-20 04:23:47 -05:00

saavagebueno commented

2025-11-20 04:23:48 -05:00

@TheGreatestJannet commented on GitHub (May 26, 2024):

Same issue here. I have had to manually remove all the wildcard entries or it seems stuck on 'We were unable to create the DNS record'.

@TheGreatestJannet commented on GitHub (May 26, 2024): Same issue here. I have had to manually remove all the wildcard entries or it seems stuck on 'We were unable to create the DNS record'.

saavagebueno commented

2025-11-20 04:23:48 -05:00

@MalibThalion commented on GitHub (May 26, 2024):

Exactly. I noticed an increase of loading times for my container until I found that I had 5 different dns entries for my wildcard. After removing them it went back to normal.

@MalibThalion commented on GitHub (May 26, 2024): Exactly. I noticed an increase of loading times for my container until I found that I had 5 different dns entries for my wildcard. After removing them it went back to normal.

saavagebueno commented

2025-11-20 04:23:48 -05:00

@jawaff commented on GitHub (May 31, 2024):

Same problem on my end as well. Everything still works, but it almost defeats the purpose of this project.

@jawaff commented on GitHub (May 31, 2024): Same problem on my end as well. Everything still works, but it almost defeats the purpose of this project.

saavagebueno commented

2025-11-20 04:23:48 -05:00

@videah commented on GitHub (Jun 13, 2024):

Running into this issue as well, seems to be an old one going by this issue.

@videah commented on GitHub (Jun 13, 2024): Running into this issue as well, seems to be an old one going by [this issue](https://github.com/qdm12/ddns-updater/issues/247).

saavagebueno commented

2025-11-20 04:23:49 -05:00

@qdm12 commented on GitHub (Jun 13, 2024):

Can you try pulling the image? I pushed 987138dfc1 which may fix this.
TLDR: before it was getting all records with https://porkbun.com/api/json/v3/dns/retrieveByNameType/domain.com/A/* but the * at the end is not really a valid URL character, so now it's removed (for both * and @, not just @). That could had explained it would re-create it because it wouldn't find it in the first place.

@qdm12 commented on GitHub (Jun 13, 2024): Can you try pulling the image? I pushed 987138dfc165f3b087d494cf4c3ed605bbeba529 which may fix this. TLDR: before it was getting all records with `https://porkbun.com/api/json/v3/dns/retrieveByNameType/domain.com/A/*` but the `*` at the end is not really a valid URL character, so now it's removed (for both `*` and `@`, not just `@`). That could had explained it would re-create it because it wouldn't find it in the first place.

saavagebueno commented

2025-11-20 04:23:49 -05:00

@MalibThalion commented on GitHub (Jun 14, 2024):

Seems okay now. Will test a few more days and report again.

@MalibThalion commented on GitHub (Jun 14, 2024): Seems okay now. Will test a few more days and report again.

saavagebueno commented

2025-11-20 04:23:49 -05:00

@qdm12 commented on GitHub (Jun 26, 2024):

Still good? About to make a v2.6.0 release. You can try by changing your A record to 127.0.0.1 on the porkbun webui and let ddns-updater detect the required update, to force a test.

@qdm12 commented on GitHub (Jun 26, 2024): Still good? About to make a v2.6.0 release. You can try by changing your A record to 127.0.0.1 on the porkbun webui and let ddns-updater detect the required update, to force a test.

saavagebueno commented

2025-11-20 04:23:49 -05:00

@MalibThalion commented on GitHub (Jun 28, 2024):

Thats what I did basically. It's working now. Thank you!

@MalibThalion commented on GitHub (Jun 28, 2024): Thats what I did basically. It's working now. Thank you!

saavagebueno commented

2025-11-20 04:23:49 -05:00

@qdm12 commented on GitHub (Jun 28, 2024):

Awesome, thanks for getting back. Closing this! 👍

@qdm12 commented on GitHub (Jun 28, 2024): Awesome, thanks for getting back. Closing this! 👍

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/ddns-updater#406