Domain Expiry Unsupported for .de

[Natgho]

📑 I have found these related issues/pull requests

• fix(domain_expiry): include static RDAP DNS data with auto-updates instead of dynamically requesting it #6769
• Deployment Fails After Upgrading to 2.1.0-beta.1 and Above due to domain expiry check #6768
• Domain Expiry Monitor #944

🛡️ Security Policy

• I have read and agree to Uptime Kuma's Security Policy.

📝 Description

Hi,

After upgrade from 2.0.0 to 2.1.0 my update docker-compose file, this error is started to raising;

Uptime is up and running but the error is printing repeatedly.

👟 Reproduction steps

Save the default docker-compose.yml;
https://uptimekuma.org/install-uptime-kuma-docker/
upgrade from 2.0.0 to 2.1.0

👀 Expected behavior

no error.

😓 Actual Behavior

showing error.

🐻 Uptime-Kuma Version

2.1.0

💻 Operating System and Arch

Ubuntu ( with Docker-compose)

🌐 Browser

Chrome

🖥️ Deployment Environment

Default

📝 Relevant log output

[CommanderStorm]

• It is not an error, it is a warning.
• Please consider contacting DENIC, since they could just tell IANA where their RDAP server is, but don't for some reason.
• We changed the default enabled state to be smarter in fix(domain-expiry): only enable domain expiry notification when TLD has RDAP support #6884 and have force-migrated everyone. If you want to upgrade, you can use our nightly until we release our next version.

@louislam a patch release to get these spam-issues of my back would be appreciated 😉

[Natgho]

Hi @CommanderStorm ,
Thank you for the detailed information. Yes, I realized that this is not an error. However, seeing this annoying output constantly in the logs gave me the impression that there was a problem with the flow, so I wanted to report it. I hope you will take it into consideration.

[HarisDotParis]

Monitoring domain expiry for .de domains won't work for the simple reason the registry behind .de (DENIC) doesn't publish expiry data at all. DENIC only has an RDAP API declared as test operation ("im Versuchsbetrieb"), and trying it myself tells me it doesn't publish any expiry data as well.

Issue #6620 has amended the log entry in this case to make it a bit clearer. However, maybe we should create an explicit negative list for all TLDs that not just aren't in IANA's RDAP list but don't publish expiry data at all. However, ideally this would come from a central source as with IANA's RDAP list, and I'm not aware there is such a list for this specific purpose.

[CommanderStorm]

maybe we should create an explicit negative list for all TLDs that not just aren't in IANA's RDAP list but don't publish expiry data at all

They are still not in the RDAP database, so people can reach out to DENIC and ask them (nicely!) to please please publish to IANA.
I won't maintain a separate list for capacity reasons.

[CommanderStorm]

-> current logging is correct. We don't know where their server is because they don't tell us.