Hello Railway team,

Both custom domains for this service are still stuck on "Waiting for DNS update" after more than 72 hours:

• aventuraspixeladas.es
• www.aventuraspixeladas.es

The Railway-provided domain works normally, so the production service itself is healthy.

DNS has been checked against the authoritative DonDominio nameservers and multiple public resolvers:

• Authoritative NS: ns1.dondominio.com and ns2.dondominio.com
• Apex uses ANAME/flattening to the Railway target shown in the dashboard
• www uses the CNAME target shown in the dashboard
• Both Railway verification TXT records are present
• No conflicting AAAA, CAA, or DS/DNSSEC records remain

The nameserver change was submitted on 22 August 2026 at 10:58 CEST, so the documented 72-hour propagation window has passed.

HTTPS currently fails on both hostnames with a certificate hostname mismatch, while Railway still displays "Waiting for DNS update" for each custom domain.

Could you please re-run domain verification and certificate issuance for both domains, or advise what Railway-side state needs to be cleared? I would prefer not to delete and recreate the domains because the DNS values are already correct and the plan domain limit is reached.

Thank you.