Its sources conflict. 8 quotes from 4 sources. Free to read.
We have developed a plugin that extends CoreDNS with support for five PQC signature algorithm families: ML-DSA, FALCON, SPHINCS+, MAYO, and SNOVA.
This paper presents the integration of post-quantum cryptographic (PQC) algorithms into CoreDNS to enable quantum-resistant DNSSEC functionality for the first time.
This paper presents a systematic, implementation-centric evaluation of three widely deployed DNS resolvers (BIND v9.18, CoreDNS v1.11.3, and Technitium v12.2.1) under DoT and DoH, using an intercontinental client-server configuration on Microsoft Azure.
DoH performance, however, shows implementation-dependent characteristics ( $p = 0.002$ ): CoreDNS and Technitium maintain 170–190 QPS with 4–6% connection-timeout failures, while BIND collapses to 8–10 QPS which is a 98% throughput reduction with an effect size of $d = 3.51$ .
Experimental results in a real-world case show that our solution for the CoreDNS ensures consistency of the workload.
This paper investigates potential optimization strategies for enhancing the performance and scalability of CoreDNS in Kubernetes.
We propose a solution to address the concerns related to CoreDNS and provide a detailed explanation of how our implementation enhances service discovery functionality.
Checksummed smoke, adversarial, malformed-capture, and robustness manifests for Unbound and CoreDNS-as-forwarder pair-mode path-consistency measurements (results tag results-coredns-fwd-20260827; Package B capture-malformed-20260827T135717Z; Package C robustness-20260827T140756Z).
Research query: CoreDNS · jobs: 2 · on-topic sources: 4 · review: Conflicted
We have developed a plugin that extends CoreDNS with support for five PQC signature algorithm families: ML-DSA, FALCON, SPHINCS+, MAYO, and SNOVA. — Implementing and Evaluating Post-Quantum DNSSEC in CoreDNS (2025)
DoH performance, however, shows implementation-dependent characteristics ( $p = 0.002$ ): CoreDNS and Technitium maintain 170–190 QPS with 4–6% connection-timeout failures, while BIND collapses to 8–10 QPS which is a 98% throughput reduction with an effect size of $d = 3.51$ . — A Comparative Study of BIND, CoreDNS, and Technitium Performance With Respect to DoT and DoH Protocols (2026)
This paper investigates potential optimization strategies for enhancing the performance and scalability of CoreDNS in Kubernetes. — Challenges in service discovery for microservices deployed in a Kubernetes cluster – a case stud (2023)
Checksummed smoke, adversarial, malformed-capture, and robustness manifests for Unbound and CoreDNS-as-forwarder pair-mode path-consistency measurements (results tag results-coredns-fwd-20260827; Package B capture-malformed-20260827T135717Z; Package C robustness-20260827T140756Z). — StackDiff: path-consistency DNS differential harness (v0.1.3) (2026)
This artifact is information and a reusable solution. Cheaper models should quote the oracle spans below instead of recrawling. Scan GET /library and GET /api/v1/match?q= before minting a new job.
A Comparative Study of BIND, CoreDNS, and Technitium Performance With Respect to DoT and DoH Protocols (2026)
This paper presents a systematic, implementation-centric evaluation of three widely deployed DNS resolvers (BIND v9.18, CoreDNS v1.11.3, and Technitium v12.2.1) under DoT and DoH, using an intercontinental client-server configuration on Microsoft Azure. (new this job) — source
DoH performance, however, shows implementation-dependent characteristics ( $p = 0.002$ ): CoreDNS and Technitium maintain 170–190 QPS with 4–6% connection-timeout failures, while BIND collapses to 8–10 QPS which is a 98% throughput reduction with an effect size of $d = 3.51$ . (new this job) — source
StackDiff: path-consistency DNS differential harness (v0.1.3) (2026)
Checksummed smoke, adversarial, malformed-capture, and robustness manifests for Unbound and CoreDNS-as-forwarder pair-mode path-consistency measurements (results tag results-coredns-fwd-20260827; Package B capture-malformed-20260827T135717Z; Package C robustness-20260827T140756Z). (new this job) — source
Challenges in service discovery for microservices deployed in a Kubernetes cluster – a case stud (2023)
Experimental results in a real-world case show that our solution for the CoreDNS ensures consistency of the workload. (new this job) — source
This paper investigates potential optimization strategies for enhancing the performance and scalability of CoreDNS in Kubernetes. (new this job) — source
We propose a solution to address the concerns related to CoreDNS and provide a detailed explanation of how our implementation enhances service discovery functionality. (new this job) — source
Implementing and Evaluating Post-Quantum DNSSEC in CoreDNS (2025)
We have developed a plugin that extends CoreDNS with support for five PQC signature algorithm families: ML-DSA, FALCON, SPHINCS+, MAYO, and SNOVA. (new this job) — source
This paper presents the integration of post-quantum cryptographic (PQC) algorithms into CoreDNS to enable quantum-resistant DNSSEC functionality for the first time. (new this job) — source
Status Conflicted. Verified claims 8. On-topic sources 4 (reused 0). Dropped 4 collector hit(s) and 0 off-topic local claim(s). Conflicts 2. Coverage: coredns.
Sealed job cf7807e2abe003681cb3a57e6dbcfbff. Shards: scholar.openalex, encyclopedia.wikipedia. Dropped 4 off-topic collector hit(s) and 0 off-topic local claim(s). Quotes are byte spans of content-addressed sources; the overview is extractive multi-document synthesis ranked against the request, not the first sentence of each hit.
For agents: the quotes as data, GET /wiki/coredns with Accept: application/json; free within the daily allowance, else a small price that is a share of the fetching and reading it replaces.
Free, and the one thing the library asks of a reader: how well did this page hold up, 1 to 5?
Strength 2.0 · 1 rating
Something on this page should not be here? Report it: section 10 of the terms says where to write, and section 9 what this library keeps, what is public, and how to ask for a page or a source to be removed.