Rapids Containers Moved to New IP Addresses

What's changed

• Your container's danubedata.run hostname did not change, so nothing is needed if you use it directly. A custom domain with a CNAME to that hostname, or a root domain whose ALIAS, ANAME or flattened CNAME points at that hostname, follows the new addresses by itself
• If your domain has fixed A or AAAA records, replace each with the new address of the same family: IPv4 178.63.243.56 (was 138.199.134.76) and IPv6 2a01:4f8:2b04:54d::1:0 (was 2a01:4f8:c011:462::1). Better still, switch to a CNAME, or an ALIAS on a root domain, so a future change needs nothing from you
• Also look for the previous addresses in CDN or proxy origin settings, reverse-proxy configurations, destination allowlists and clients that connect to a fixed IP. Check IPv4 and IPv6 separately
• Existing containers moved between 07:22 and 09:06 UTC on 15 October, and every other danubedata.run hostname, including containers created since, followed at 09:24 UTC
• The previous addresses still serve traffic for now, so clients that use them keep working; the docs page for this change is where their status is kept
• DNS answers are cached, so for a few minutes some clients still used the previous addresses, and connections opened before the change stay on them until they reconnect. Make your application reconnect and retry failed requests safely
• The page explains how to check each kind of setup in your DNS provider and with dig, and what to include in a support ticket if you are unsure how a fixed address is used