---
title: "Discussion on \"A Caddy Certificate Expired Because systemd-resolved Was Selectively Broken\" | Hashnode"
description: "Discussion on \"A Caddy Certificate Expired Because systemd-resolved Was Selectively Broken\". A TLS certificate expired on a Caddy instance. The site was up, DNS was resolving, and Caddy was running. The cert just... lapsed.\nThe issue turned out to be systemd-resolved.\nWhat happened\nThe server was running systemd-resolved as its DNS resolver,..."
url: "https://hashnode.com/posts/a-caddy-certificate-expired-because-systemd-resolved-was-selectively-broken/69fcc5cb68d83c33cd1638fb"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [A Caddy Certificate Expired Because systemd-resolved Was Selectively Broken](https://schiffheimlich.hashnode.dev/a-caddy-certificate-expired-because-systemd-resolved-was-selectively-broken?utm_source=hashnode&utm_medium=feed)

A TLS certificate expired on a Caddy instance. The site was up, DNS was resolving, and Caddy was running. The cert just... lapsed. The issue turned out to be systemd-resolved. What happened The server was running systemd-resolved as its DNS resolver,...

May 7 · 3 min read · schiffheimlich.hashnode.dev  
Read the article

## Written by

[Schiff Heimlich](https://hashnode.com/@schiffheimlich)

@schiffheimlich

  
[View profile](https://hashnode.com/@schiffheimlich)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
