Scaleway: [K8S] CoreDNS timeouts
Timeline of updates
- resolved
The DNS resolution failure has been resolved. To fix the issue, please proceed as follows: Replace or reboot your nodes to get the fix. Use a fqdn to resolve your addresses inside the Private Network. Meaning if you have a foo service in the mypn pn foo will not be resolved and you must use foo.mypn Important notes: Please avoid using an existing TLD (https://en.wikipedia.org/wiki/Top-level_domain (opens in new tab)) as PN name if you do so you can have some problem. For instance, if you name your pn fr you will not be able to resolve google.fr externally, meaning if you have not a service named google in your PN you won’t revsolv google.fr and if you have one, it will not be the good one. Please note that prod and dev are TLD (https://data.iana.org/TLD/tlds-alpha-by-domain.txt (opens in new tab))”
From Scaleway’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.scaleway.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Scaleway, started 2024-02-12 15:00 UTC, resolved after 8 d, 1 update(s).
- Title
- [K8S] CoreDNS timeouts
- Vendor
- Scaleway
- Date
- URL
- https://rewindex.com/company/scaleway/incidents/86k8rkrzh513
Scaleway profileRecent Scaleway incidentsAll outages on February 12, 2024Scaleway in February 2024MarkdownJSON