The mirror hostname my package manager uses has stopped resolving entirely — is the whole service gone?

The fix is to stop asking for a dynamic list of mirrors and start pointing at a fixed archive location, because that is what still exists after end of life.

Projects generally keep an archive host carrying the final state of retired releases. The change in each repository file is to comment out the mirror-list line and add a base URL line pointing at that archive.

Two warnings that matter more than the mechanics:

• Those packages are frozen. You are restoring your ability to install software, not your ability to receive security updates. There will be no more of those, ever, for this release.
• Do it to all the repository files, including any third-party ones, and expect some third parties to have removed their old-release directories entirely.

It is a legitimate way to keep a machine functioning while you plan, and a bad place to stay.

The thing worth taking from this: end-of-life dates are published years in advance and are the most predictable outage you will ever have.

This one is preventable with a calendar entry. Every distribution publishes support windows; putting the date for every release you run into a shared calendar, with a reminder six months ahead, converts an emergency into a planned migration.

The same applies to the layer above — language runtimes, database majors, container base images. Almost every "it suddenly stopped working" incident of this shape was on somebody's public schedule long before it happened.

It is a bigger event, and the answer is almost certainly that the release reached end of life and the project retired the infrastructure that served it.

The mirror list service exists to hand your package manager a set of nearby mirrors that carry current packages for a supported release. Once a release is no longer supported, there are no current packages, mirrors stop carrying it, and the service that points at those mirrors has nothing to point at. Removing the DNS record is the last step of a decommissioning that happened on a published schedule.

So nothing broke on your side and nothing broke on theirs. Your server outlived the support window and found out via DNS, which is an abrupt way to be told.

One diagnostic tip for next time, since the symptom presented as a network problem: when a hostname stops resolving, check whether it resolves from anywhere before investigating your own DNS.

A public resolver, a phone on mobile data, or an online lookup tool answers in seconds. If the name is dead globally, you are looking at somebody else's decision rather than your own configuration, and that reframes the whole investigation immediately.