iwantmyname: new API

[Brekkjern]

Welcome

• Yes, I'm using a binary release within 2 latest releases.
• Yes, I've searched similar issues on GitHub and didn't find any.
• Yes, I've included all information below (version, config, etc).

What did you expect to see?

I believe the base address for iwantmyname is wrong.
The documentation specifies a URL like this:

https://dynamicdns.key-systems.net/update.php?hostname=hostname&password=password&ip=213.4.7.1&mx=213.4.7.1

While the address in the current code is https://iwantmyname.com/basicauth/ddns.

I believe that was correct previously, but it seems iwantmyname has changed it lately.

The relevant documentation from iwantmyname:
https://new.help.iwantmyname.com/hc/en-gb/articles/26622471185309-How-does-a-dynamic-DNS-record-work-and-how-can-I-update-it

The relevant line:

lego/providers/dns/iwantmyname/internal/client.go

Line 14 in 990f9ac

const defaultBaseURL = "https://iwantmyname.com/basicauth/ddns"

What did you see instead?

My traefik logs are showing 404 errors.

How do you use lego?

Through Traefik

Reproduction steps

Use dnsChallenge in Traefik with iwantmyname as provider.

[entryPoints.websecure.http.tls]
certResolver = "leresolver"

[certificatesResolvers.leresolver.acme]
email = "myemail@censored"
storage = "/acme/acme.json"

[certificatesResolvers.leresolver.acme.dnsChallenge]
provider = "iwantmyname"
delayBeforeCheck = "10"

Effective version of lego

I cannot get the Traefik container to output the lego version, but this is the output of traefik version inside the container:

/ # traefik version
Version:      3.4.3
Codename:     chaource
Go version:   go1.24.4
Built:        2025-06-26T13:25:29Z
OS/Arch:      linux/amd64

Logs

2025-07-05T19:15:47+02:00 ERR Error renewing certificate from LE: {CENSORED []} error="error: one or more domains had a problem:\n[CENSORED] [CENSORED] acme: error presenting token: iwantmyname: unexpected status code: [status code: 404] body: ....

The body is the full 404 website for iwantmyname.com

Go environment (if applicable)

No response

[ldez]

I think they changed their API, because the address was right when I created the implementation.

You can check that with the Wayback Machine.

https://web.archive.org/web/20250521235012/https://iwantmyname.com/developer/domain-dns-api

[ldez]

The documentation page, you are referring to, doesn't explain how to update TXT records.

We can only hope that the API hasn't changed despite the new endpoint.

[ldez]

🤔 Based on documentation, this is not the same API:

Before

curl -u "[USERNAME]:[PASSWORD]" "https://iwantmyname.com/basicauth/ddns?hostname=[HOSTNAME]&myip=[IP]"

curl -u "[USERNAME]:[PASSWORD]" "https://iwantmyname.com/basicauth/ddns?hostname=[HOSTNAME]&type=[RECORD_TYPE]&value=[RECORD_VALUE]"

After

curl "https://dynamicdns.key-systems.net/update.php?password=[PASSWORD]&hostname=[HOSTNAME]&ip=[IP]"

curl "https://dynamicdns.key-systems.net/update.php?password=[PASSWORD]&hostname=[HOSTNAME]&ip=[IP]&mx=[MX]"

---

1. The authentication was basic auth (Authorization Header); now it's query parameters (and only password?).
2. Before, there were type and value; now, there are unknown elements.
3. Before, there was a specific value to delete a TXT record; now we don't know.

So, @Brekkjern, I recommend contacting the iwantmyname support to get the right information.

[Brekkjern]

I think they changed their API, because the address was right when I created the implementation.

You can check that with the Wayback Machine.

https://web.archive.org/web/20250521235012/https://iwantmyname.com/developer/domain-dns-api

It definitely was correct, because it has worked before. I just noticed it stopped working and started investigating it.

1. The authentication was basic auth (Authorization Header); now it's query parameters (and only password?).
2. Before, there were type and value; now, there are undefined elements.
3. Before, there was a specific value to delete a TXT record; now we don't know.

So, @Brekkjern, I recommend contacting the iwantmyname support to get the right information.

I can have a crack at figuring it out and contacting them.

[ldez]

@Brekkjern any news?

[Brekkjern]

@ldez I am still waiting for a response from their support. I will update when I get any.

[silbinarywolf]

I'm looking into this for myself, looking like it's available here, when you click the "Value" box you end up with this modal.
Will update this post if I get further.

A dynamic DNS record is a method of keeping a domain name linked to an IP address that is subject to change, as not all computers use static IP addresses. In general, when a user connects to the Internet, the user's ISP assigns an unused IP address from a pool of IP addresses, and this address is used only for the duration of that specific connection. Our dynamic DNS service allows you to use a client that runs on your computer, automatically contacting us each time the IP address provided by your ISP changes and subsequently updating the DNS database to reflect the change in your IP address. In this way, even though a domain name's IP address will change often, other users do not have to know the changed IP address in order to connect with your computer and services you may provide.

To dynamically update the Dynamic DNS host you need to call the following HTTP APIs:

https://dynamicdns.key-systems.net/update.php?hostname=hostname&password=password&ip=auto

https://dynamicdns.key-systems.net/update.php?hostname=hostname&password=password&ip=213.4.7.1&mx=213.4.7.1

EDIT:

Alright, if in the above modal fields I provide:

• Name: subdomain
• Password: the_password

Then I visit:

• https://dynamicdns.key-systems.net/update.php?hostname=subdomain.mywebsite.com&password=the_password&ip=auto

It updates the dynamic DNS but that seems to be about it.

[ldez]

This is the same content as How-does-a-dynamic-DNS-record-work-and-how-can-I-update-it from the initial post.

This API seems to be only for creating and updating (but not deleting) A and MX records related to dynamic DNS, and not for creating or deleting TXT records.

[ldez]

I recommend contacting the support and asking them for an API to create and delete TXT records.
The more users request it, the more likely it is to have this API.

[silbinarywolf]

I've contacted support with the following, here's hoping it goes somewhere.

The current issue is that I cannot use Lego to automate renewing and setting up an SSL certificate anymore because the new Dynamic DNS API cannot add TXT records. Only A and MX records.

Old API Link:
https://iwantmyname.com/basicauth/ddns

Related Github issue comments related specifically to iwantmyname:
#2563 (comment)
#2563 (comment)