Feature request: check wildcard support for all providers #347

New Issue

saavagebueno · 2025-11-20T04:22:59-05:00

saavagebueno commented

2025-11-20 04:22:59 -05:00

Originally created by @qdm12 on GitHub (Jan 18, 2024).

Some providers do not support updating wildcards, and it should be investigated why and the code/docs updated if it's possible to do so.

AllInkl
DDNSS
DuckDNS: only supports host.duckdns.org, no wildcard
DynDNS: wildcard support added in 59d8791b8d it might just work
Dynu
Dynv6
Infomaniak
Inwx
namecheap
Netcup
NoIP
OpenDNS
OVH
Selfhost.de
Servercow
Spdyn
Strato
Variomedia

Originally created by @qdm12 on GitHub (Jan 18, 2024). Some providers do not support updating wildcards, and it should be investigated why and the code/docs updated if it's possible to do so. - [ ] AllInkl - [ ] DDNSS - [x] DuckDNS: only supports host.duckdns.org, no wildcard - [x] DynDNS: wildcard support added in 59d8791b8dfce9d839276704c17c88a82561ae8a it might just work - [ ] Dynu - [ ] Dynv6 - [ ] Infomaniak - [ ] Inwx - [x] namecheap - [x] Netcup - [ ] NoIP - [ ] OpenDNS - [ ] OVH - [ ] Selfhost.de - [ ] Servercow - [ ] Spdyn - [ ] Strato - [ ] Variomedia

saavagebueno added the Status: 🔒 After next release Category: Maintenance ⛓️Category: Provider update ♻️ labels 2025-11-20 04:22:59 -05:00

saavagebueno commented

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

@ciaranj commented on GitHub (Sep 14, 2024):

Don't know if it helps, but I just successfully setup a wildcard update using the namecheap provider. Although my required config differed slightly from the docs (the docs suggest to use *.foo.com as the domain, but in actuality I had to use foo.com as the domain and * as the host, otherwise there was an error with the domain name validation.

This worked for me.

{
  "settings": [
    {
      "provider": "namecheap",
      "domain": "foo.com",
      "password": "my_namecheap_password",
      "host":"*"
    }
  ]
}

This did not, but the docs suggest it should:
This worked for me.

{
  "settings": [
    {
      "provider": "namecheap",
      "domain": "*.foo.com",
      "password": "my_namecheap_password"
    }
  ]
}

@ciaranj commented on GitHub (Sep 14, 2024): Don't know if it helps, but I just successfully setup a wildcard update using the namecheap provider. Although my required config differed slightly from the docs (the docs suggest to use *.foo.com as the domain, but in actuality I had to use foo.com as the domain and * as the host, otherwise there was an error with the domain name validation. This worked for me. ``` { "settings": [ { "provider": "namecheap", "domain": "foo.com", "password": "my_namecheap_password", "host":"*" } ] } ``` This did not, but the docs suggest it should: This worked for me. ``` { "settings": [ { "provider": "namecheap", "domain": "*.foo.com", "password": "my_namecheap_password" } ] } ```

saavagebueno commented

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

@qdm12 commented on GitHub (Sep 15, 2024):

@ciaranj i think you are reading the wrong documentation, see the top of the readme for links to the right version of documentation. Marking this and your comment as off topic, but otherwise feel free to create a separate issue!

@qdm12 commented on GitHub (Sep 15, 2024): @ciaranj i think you are reading the wrong documentation, see the top of the readme for links to the right version of documentation. Marking this and your comment as off topic, but otherwise feel free to create a separate issue!

saavagebueno commented

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

@NotaInutilis commented on GitHub (Feb 28, 2025):

I have sent an e-mail to Infomaniak to know more about this DDNS wildcard support, and their answer is that they're not supporting it. Unfortunately got no information as to why.

@NotaInutilis commented on GitHub (Feb 28, 2025): I have sent an e-mail to Infomaniak to know more about this DDNS wildcard support, and their answer is that they're not supporting it. Unfortunately got no information as to why.

saavagebueno commented

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

@steiny2k commented on GitHub (Apr 2, 2025):

I can confirm INWX supports wildcard updates. And it's working with your updater. 👍

@steiny2k commented on GitHub (Apr 2, 2025): I can confirm INWX supports wildcard updates. And it's working with your updater. 👍

saavagebueno commented

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

@nirizr commented on GitHub (Aug 18, 2025):

OVH through API (not the default) works well with a wildcard subdomain,

@nirizr commented on GitHub (Aug 18, 2025): OVH through API (not the default) works well with a wildcard subdomain,

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/ddns-updater#347