Strato: banned #461

New Issue

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

saavagebueno commented

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

Originally created by @RalfPeter on GitHub (Nov 16, 2024).

Is this urgent: Yes, canot update any subdomain, getting abused
DNS provider(s) you use: Strato
Program version: latest built on 2024-11-12T13:25:56.063Z (commit 9a62043)
What are you using to run the container: docker-compose

Synology DS1621+ DSM 7.2.1-69057 Update 5. Here is my config.json (only part from beginning of file:

{
  "settings": [
    {
      "provider": "strato",
      "domain": "mydomain.eu",
      "password": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
      "ip_version": "ipv6"
    },
    {
      "provider": "strato",
      "domain": "files.mydomain.eu",
      "password": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
      "ip_version": "ipv6"
    },

i get the following error message:

2024-11-16T10:36:28Z INFO Updating record [domain: mydomain.eu | owner: files |  provider: strato 
| ip: ipv6] to use XXXX:XXXX:XXXX:XXXX:XXX:XXXX:XXXX:XXXX

and the update is abused for 1h (because owner ist NOT the subdomain name!).

Originally created by @RalfPeter on GitHub (Nov 16, 2024). 1. Is this urgent: Yes, canot update any subdomain, getting abused 2. DNS provider(s) you use: Strato 3. Program version: latest built on 2024-11-12T13:25:56.063Z (commit 9a62043) 4. What are you using to run the container: docker-compose Synology DS1621+ DSM 7.2.1-69057 Update 5. Here is my config.json (only part from beginning of file: ```json { "settings": [ { "provider": "strato", "domain": "mydomain.eu", "password": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx", "ip_version": "ipv6" }, { "provider": "strato", "domain": "files.mydomain.eu", "password": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx", "ip_version": "ipv6" }, ``` i get the following error message: ``` 2024-11-16T10:36:28Z INFO Updating record [domain: mydomain.eu | owner: files | provider: strato | ip: ipv6] to use XXXX:XXXX:XXXX:XXXX:XXX:XXXX:XXXX:XXXX ``` and the update is abused for 1h (because owner ist NOT the subdomain name!).

saavagebueno commented

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

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

because owner is NOT the subdomain name!

owner name (here owner) is for the subdomain part, and is also known as host.

From the DNS RFC:

NAME an owner name, i.e., the name of the node to which this resource record pertains.

So this is definitely not the cause of the ban.

and the update is abused for 1h

What error do you get in your logs? How do you know you're banned? What other logs do you have???

@qdm12 commented on GitHub (Nov 19, 2024): > because owner is NOT the subdomain name! `owner name` (here `owner`) is for the subdomain part, and is also known as `host`. From the [DNS RFC](https://datatracker.ietf.org/doc/html/rfc1035#section-3.2.1): > NAME an owner name, i.e., the name of the node to which this resource record pertains. So this is definitely not the cause of the ban. > and the update is abused for 1h What error do you get in your logs? How do you know you're banned? What other logs do you have???

saavagebueno commented

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

@RalfPeter commented on GitHub (Nov 20, 2024):

Perhaps the docu ist wrong? The docu for strato says:

  {
  "settings": [
    {
      "provider": "strato",
      "domain": "domain.com",
      "password": "password",
      "ip_version": "ipv4",
      "ipv6_suffix": ""
    }
  ]
}

So please what is the right config for a subdomain for strato:

  {
  "settings": [
    {
      "provider": "strato",
      "domain": "sub.domain.com",
      "owner": "domain.com",  ### or "host": "domain.com",  ### "host": "@" is not allowed any more
      "password": "password",
      "ip_version": "ipv4",
      "ipv6_suffix": ""
    }
  ]
}

In the log i found the error that i mentioned: i was abused for 1h because of authentication because the subdomain part was extracted from "domain" and added as "owner" part as you can see here (from log):

2024-11-16T10:36:28Z INFO Updating record [domain: mydomain.eu | owner: files | provider: strato | ip: ipv6] to use XXXX:XXXX:XXXX:XXXX:XXX:XXXX:XXXX:XXXX

@RalfPeter commented on GitHub (Nov 20, 2024): Perhaps the docu ist wrong? The docu for strato says: ``` { "settings": [ { "provider": "strato", "domain": "domain.com", "password": "password", "ip_version": "ipv4", "ipv6_suffix": "" } ] } ``` So please what is the right config for a subdomain for strato: ``` { "settings": [ { "provider": "strato", "domain": "sub.domain.com", "owner": "domain.com", ### or "host": "domain.com", ### "host": "@" is not allowed any more "password": "password", "ip_version": "ipv4", "ipv6_suffix": "" } ] } ``` In the log i found the error that i mentioned: i was abused for 1h because of authentication because the subdomain part was extracted from "domain" and added as "owner" part as you can see here (from log): `2024-11-16T10:36:28Z INFO Updating record [domain: mydomain.eu | owner: files | provider: strato | ip: ipv6] to use XXXX:XXXX:XXXX:XXXX:XXX:XXXX:XXXX:XXXX`

saavagebueno commented

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

@qdm12 commented on GitHub (Nov 20, 2024):

Just use sub.domain.com in the domain field. There is no need to define the owner field anymore in recent releases. The owner field should not be documented anymore, since it's now deprecated. How is the documentation confusing?

@qdm12 commented on GitHub (Nov 20, 2024): Just use `sub.domain.com` in the domain field. There is no need to define the owner field anymore in recent releases. The owner field should not be documented anymore, since it's now deprecated. How is the documentation confusing?

saavagebueno commented

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

@RalfPeter commented on GitHub (Nov 20, 2024):

You see the error message that i got from strato?

My subdomain files.mydomain.eu leads to an error:

2024-11-16T10:36:28Z INFO Updating record [domain: mydomain.eu | owner: files | provider: strato | ip: ipv6] to use XXXX:XXXX:XXXX:XXXX

It seems that owner is extracted from subdomain.

In my config i wrote:

{ "provider": "strato", "domain": "files.mydomain.eu", "password": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx", "ip_version": "ipv6" },

@RalfPeter commented on GitHub (Nov 20, 2024): You see the error message that i got from strato? My subdomain files.mydomain.eu leads to an error: ` 2024-11-16T10:36:28Z INFO Updating record [domain: mydomain.eu | owner: files | provider: strato | ip: ipv6] to use XXXX:XXXX:XXXX:XXXX ` It seems that owner is extracted from subdomain. In my config i wrote: ` { "provider": "strato", "domain": "files.mydomain.eu", "password": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx", "ip_version": "ipv6" }, `

saavagebueno commented

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

@qdm12 commented on GitHub (Nov 21, 2024):

My subdomain files.mydomain.eu leads to an error:
2024-11-16T10:36:28Z INFO Updating record [domain: mydomain.eu | owner: files | provider: strato | ip: ipv6] to use XXXX:XXXX:XXXX:XXXX

How is this an error? This is an info log, there is no error. If you get banned by strato, you must get an error message logged in your logs.

Again, in sub.domain.com the domain name is domain.com and the owner is sub. Technically it's actually sub.domain.com. (trailing dot added), where each part from start to end is:

sub: owner name of the resource record (i.e. A record, AAAA record etc.)
domain: domain name
com: top level domain
. root

@qdm12 commented on GitHub (Nov 21, 2024): > My subdomain files.mydomain.eu leads to an error: > 2024-11-16T10:36:28Z INFO Updating record [domain: mydomain.eu | owner: files | provider: strato | ip: ipv6] to use XXXX:XXXX:XXXX:XXXX How is this an error? This is an info log, there is no error. If you get banned by strato, you must get an error message logged in your logs. Again, in `sub.domain.com` the domain name is `domain.com` and the owner is `sub`. Technically it's actually `sub.domain.com.` (trailing dot added), where each part from start to end is: - `sub`: owner name of the resource record (i.e. A record, AAAA record etc.) - `domain`: domain name - `com`: top level domain - `.` root

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/ddns-updater#461