COREDNS-READY(7)

💖 COREDNS-READY(7) 💖

okay so bestie, welcome to the ready page of the CoreDNS manual — yes that's the plugin name and the manual name all at once, we love an economy 💅

✨ NAME ✨

ready — enables a readiness check HTTP endpoint. that's it, that's the whole vibe. she tells you when the server is ready to serve 🫶

🌸 DESCRIPTION 🌸

so by enabling ready, an HTTP endpoint on port 8181 will return 200 OK — but only when all plugins that are able to signal readiness have actually done so. like, everybody's here, everybody's seated, the show can start 👑

if some of them are not ready yet? the endpoint returns a 503 with a body containing the list of plugins that are not ready. snitch energy, honestly, but useful 💀

each Server Block that enables the ready plugin will have the plugins in that server block report readiness into the /ready endpoint that runs on the same port. and this also means that the same plugin with different configurations (in potentially different Server Blocks) will have their readiness reported as the union of their respective readinesses. like, collective main character energy — everyone's status gets pooled together 🌈

🎀 SYNTAX 🎀

ready [ADDRESS] {
    monitor until-ready|continuously
}

ready optionally takes an address; the default is :8181. the path is fixed to /ready — no, you can't change it, it's giving "the rules are the rules" 🙈

the readiness endpoint returns a 200 response code and the word "OK" when this server is ready. it returns a 503 otherwise, plus the list of plugins that are not ready. and by default, once a plugin has signaled it is ready it will not be queried again. one and done, periodt ✨

the ready directive can include an optional monitor parameter, defaulting to until-ready. the following values are supported:

• until-ready — once a plugin signals it is ready, it will not be checked again. this mode assumes stability after the initial readiness confirmation. like trusting your bestie to text back, we're not checking twice 🫶
• continuously — in this mode, plugins are continuously monitored for readiness. this means a plugin may transition between ready and not ready states, providing real-time status updates. highkey the anxious attachment option but honestly iconic for live status 🔥

🦋 PLUGINS 🦋

any plugin wanting to signal readiness will need to implement the ready.Readiness interface by implementing a method Ready() bool that returns true when the plugin is ready and false otherwise. that's the whole contract, no cap — true good, false not yet 💜

⭐ EXAMPLES ⭐

let ready report readiness for both the . and example.org servers (assuming the whois plugin also exports readiness):

. {
    ready
    erratic
}

example.org {
    ready
    whoami
}

and run ready on a different port:

. {
    ready localhost:8091
}

look at her go, custom port and everything 💅🌸

---

and that's the page bestie! brought to you by CoreDNS (the source), version March 2026 (the date) — go be ready, stay ready, slay 🎀💖✨