<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Blogs on CoreDNS: DNS and Service Discovery</title>
    <link>https://coredns.io/blog/</link>
    <description>Recent content in Blogs on CoreDNS: DNS and Service Discovery</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>CoreDNS - All Rights Reserved</copyright>
    <lastBuildDate>Fri, 06 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://coredns.io/blog/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CoreDNS-1.14.2 Release</title>
      <link>https://coredns.io/2026/03/06/coredns-1.14.2-release/</link>
      <pubDate>Fri, 06 Mar 2026 00:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2026/03/06/coredns-1.14.2-release/</guid>
      <description>This release adds the new proxyproto plugin to support Proxy Protocol and preserve client IPs behind load balancers. It also includes enhancements such as improved DNS logging metadata and stronger randomness for loop detection (CVE-2026-26018), along with several bug fixes including TLS+IPv6 forwarding, improved CNAME handling and rewriting, allowing jitter disabling, prevention of an ACL bypass (CVE-2026-26017), and a Kubernetes plugin crash fix. In addition, the release updates the build to Go 1.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.14.1 Release</title>
      <link>https://coredns.io/2026/01/15/coredns-1.14.1-release/</link>
      <pubDate>Thu, 15 Jan 2026 00:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2026/01/15/coredns-1.14.1-release/</guid>
      <description>This release primarily addresses security vulnerabilities affecting Go versions prior to Go 1.25.6 and Go 1.24.12 (CVE-2025-61728, CVE-2025-61726, CVE-2025-68121, CVE-2025-61731, CVE-2025-68119). It also includes performance improvements to the proxy plugin via multiplexed connections, along with various documentation updates.
Brought to You By Alex Massy Shiv Tyagi Ville Vesilehto Yong Tang
Noteworthy Changes plugin/proxy: Use mutex-based connection pool (https://github.com/coredns/coredns/pull/7790) </description>
    </item>
    
    <item>
      <title>CoreDNS-1.14.0 Release</title>
      <link>https://coredns.io/2026/01/10/coredns-1.14.0-release/</link>
      <pubDate>Sat, 10 Jan 2026 00:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2026/01/10/coredns-1.14.0-release/</guid>
      <description>This release focuses on security hardening and operational reliability. Core updates introduce a regex length limit to reduce resource-exhaustion risk. Plugin updates improve error consolidation (show_first), reduce misleading SOA warnings, add Kubernetes API rate limiting, enhance metrics with plugin chain tracking, and fix issues in azure and sign. This release also includes additional security fixes; see the security advisory for details.
Brought to You By cangming pasteley Raisa Kabir Ross Golder rusttech Syed Azeez Ville Vesilehto Yong Tang</description>
    </item>
    
    <item>
      <title>CoreDNS-1.13.2 Release</title>
      <link>https://coredns.io/2025/12/08/coredns-1.13.2-release/</link>
      <pubDate>Mon, 08 Dec 2025 00:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2025/12/08/coredns-1.13.2-release/</guid>
      <description>This release adds initial support for DoH3 and includes several core performance and stability fixes, including reduced allocations, a resolved data race in uniq, and safer QUIC listener initialization. Plugin updates improve forwarder reliability, extend GeoIP schema support, and fix issues in secondary, nomad, and kubernetes. Cache and file plugins also receive targeted performance tuning.
Deprecations: The GeoIP plugin currently returns 0 for missing latitude/longitude, even though 0,0 is a real location.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.13.1 Release</title>
      <link>https://coredns.io/2025/10/08/coredns-1.13.1-release/</link>
      <pubDate>Wed, 08 Oct 2025 00:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2025/10/08/coredns-1.13.1-release/</guid>
      <description>This release updates CoreDNS to Go 1.25.2 and golang.org/x/net v0.45.0 to address multiple high-severity CVEs. It also improves core performance by avoiding string concatenation in loops, and hardens the sign plugin by rejecting invalid UTF-8 tokens in dbfile.
Brought to You By Catena cyber Ville Vesilehto Yong Tang
Noteworthy Changes core: Avoid string concatenation in loops (https://github.com/coredns/coredns/pull/7572) core: Update golang to 1.25.2 and golang.org/x/net to v0.45.0 on CVE fixes (https://github.com/coredns/coredns/pull/7598) plugin/sign: Reject invalid UTF‑8 dbfile token (https://github.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.13.0 Release</title>
      <link>https://coredns.io/2025/10/05/coredns-1.13.0-release/</link>
      <pubDate>Sun, 05 Oct 2025 00:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2025/10/05/coredns-1.13.0-release/</guid>
      <description>This release introduces a new Nomad plugin for integrating CoreDNS with HashiCorp Nomad. It also fixes major Corefile issues on infinite loops and import cycles, improves shutdown handling, normalizes core panics, addresses data races in the file plugin, enforces gRPC size limits, adjusts forward failover behavior, as well as prevents reload deadlocks.
Brought to You By Fitz_dev Ilya Kulakov Olli Janatuinen Ville Vesilehto Yong Tang
Noteworthy Changes core: Export timeout values in dnsserver.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.12.4 Release</title>
      <link>https://coredns.io/2025/09/08/coredns-1.12.4-release/</link>
      <pubDate>Mon, 08 Sep 2025 00:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2025/09/08/coredns-1.12.4-release/</guid>
      <description>This release improves stability and security, fixing context propagation in DoH, label offset handling in the file plugin, and connection leaks in gRPC and transfer. It also adds support for the prefer option in loadbalance, introduces timeouts to the metrics server, and fixes several security vulnerabilities (see details in related security advisories).
Brought to You By Archy Ilya Kulakov Olli Janatuinen Qasim Sarfraz Syed Azeez Ville Vesilehto wencyu Yong Tang</description>
    </item>
    
    <item>
      <title>CoreDNS-1.12.3 Release</title>
      <link>https://coredns.io/2025/08/05/coredns-1.12.3-release/</link>
      <pubDate>Tue, 05 Aug 2025 00:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2025/08/05/coredns-1.12.3-release/</guid>
      <description>This release improves plugin reliability and standards compliance, adding startup timeout to the Kubernetes plugin, fallthrough to gRPC, and EDNS0 unset to rewrite. The file plugin now preserves SRV record case per RFC 6763, route53 is updated to AWS SDK v2, and multiple race conditions in cache and connection handling in forward are fixed.
Brought to You By blakebarnett Brennan Kinney Cameron Steel Dave Brown Dennis Simmons Guillaume Jacquet harshith-2411-2002 houpo-bob Oleg Guba Sebastian Mayr Stephen Kitt Syed Azeez Ville Vesilehto Yong Tang Yoofi Quansah</description>
    </item>
    
    <item>
      <title>CoreDNS-1.12.2 Release</title>
      <link>https://coredns.io/2025/06/06/coredns-1.12.2-release/</link>
      <pubDate>Fri, 06 Jun 2025 00:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2025/06/06/coredns-1.12.2-release/</guid>
      <description>This release introduces significant improvements to plugin stability and extensibility. It adds multicluster support to the Kubernetes plugin, fallthrough support in the file plugin, and a new SetProxyOptions function for the forward plugin. Notably, the QUIC (DoQ) plugin now limits concurrent streams, improving performance under load. Several bug fixes and optimizations improve reliability across plugins, including rewrite, proxy, and metrics.
Brought to You By Ambrose Chua, Arthur Outhenin-Chalandre, Ben Kochie, Colden Cullen, Gleb Kogtev, Hirotaka Tagawa, Kevin Lyda, Manuel Rüger, Mark Mickan, Parfenov Ivan, skipper, vdbe, Viktor Oreshkin, Ville Vesilehto, Yannick Epstein, Yong Tang</description>
    </item>
    
    <item>
      <title>CoreDNS-1.12.1 Release</title>
      <link>https://coredns.io/2025/03/24/coredns-1.12.1-release/</link>
      <pubDate>Mon, 24 Mar 2025 00:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2025/03/24/coredns-1.12.1-release/</guid>
      <description>In this release:
kubernetes: Revert recent change to only create PTR records for endpoints with hostname defined. forward: added option to return SERVFAIL immediately if all upstreams are unhealthy. Brought to You By Adrian Moisey, Arthur Outhenin-Chalandre, Bartosz Borkowski, Ben Kochie, Chris O&amp;rsquo;Haver, Min Woo Kim, Puneet Loya, Rich, Viktor, momantech
Noteworthy Changes core: Increase CNAME lookup limit from 7 to 10 (https://github.com/coredns/coredns/pull/7153) plugin/kubernetes: Fix handling of pods having DeletionTimestamp set (https://github.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.12.0 Release</title>
      <link>https://coredns.io/2024/11/21/coredns-1.12.0-release/</link>
      <pubDate>Thu, 21 Nov 2024 00:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2024/11/21/coredns-1.12.0-release/</guid>
      <description>This release adds a new feature:
New multisocket plugin - allows CoreDNS to listen on multiple sockets Brought to You By Ben Kochie, Chris O&amp;rsquo;Haver, Emmanuel Ferdman, Viktor
Noteworthy Changes plugin/multisocket (https://github.com/coredns/coredns/pull/6882) </description>
    </item>
    
    <item>
      <title>CoreDNS-1.11.4 Release</title>
      <link>https://coredns.io/2024/11/13/coredns-1.11.4-release/</link>
      <pubDate>Wed, 13 Nov 2024 00:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2024/11/13/coredns-1.11.4-release/</guid>
      <description>This release adds some new features and fixes some bugs. New features of note:
forward plugin: new option next, to try alternate upstreams when receiving specified response codes upstreams on (functions like the external plugin alternate) dnssec plugin: new option to load keys from AWS Secrets Manager rewrite plugin: new option to revert EDNS0 option rewrites in responses Brought to You By AdamKorcz, Anifalak, Ben Kochie, Chris O&amp;rsquo;Haver, Frederic Hemery, Grant Spence, Harshita Sao, Jason Joo, Jasper Bernhardt, Johnny Bergström, Keith Coleman, Kevin Lyda, Lan, Lin-1997, Manuel Rüger, Nathan Currier, Nicolai Søborg, Nikita Usatov, Paco Xu, Reinhard Nägele, Robbie Ostrow, TAKAHASHI Shuuji, Till Riedel, Tobias Klauser, YASH JAIN, cedar-gao, chenylh, wmkuipers, xinbenlv, zhangguanzhang</description>
    </item>
    
    <item>
      <title>CoreDNS-1.11.3 Release</title>
      <link>https://coredns.io/2024/04/24/coredns-1.11.3-release/</link>
      <pubDate>Wed, 24 Apr 2024 16:57:00 -0400</pubDate>
      
      <guid>https://coredns.io/2024/04/24/coredns-1.11.3-release/</guid>
      <description>This release contains some new features, bug fixes, and package updates. Because of the deployment issues with the previous release, all changed features from 1.11.2 have been included in this release. New features include:
When the forward plugin receives a malformed upstream response that overflows, it will now send an empty response to the client with the truncated (TC) bit set to prompt the client to retry over TCP. The rewrite plugin can now rewrite response codes.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.11.2 Release</title>
      <link>https://coredns.io/2024/01/26/coredns-1.11.2-release/</link>
      <pubDate>Fri, 26 Jan 2024 00:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2024/01/26/coredns-1.11.2-release/</guid>
      <description>This release contains some new features, bug fixes, and package updates. New features include:
When the forward plugin receives a malformed upstream response that overflows, it will now send an empty response to the client with the truncated (TC) bit set to prompt the client to retry over TCP. The rewrite plugin can now rewrite response codes. The dnstap plugin now supports adding metadata to the dnstap extra field. Brought to You By Amila Senadheera, Ben Kochie, Benjamin, Chris O&amp;rsquo;Haver, Grant Spence, John Belamaric, Keita Kitamura, Marius Kimmina, Michael Grosser, Ondřej Benkovský, P.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.11.1 Release</title>
      <link>https://coredns.io/2023/08/15/coredns-1.11.1-release/</link>
      <pubDate>Tue, 15 Aug 2023 00:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2023/08/15/coredns-1.11.1-release/</guid>
      <description>This release fixes a major performance regression introduced in 1.11.0 that affected DoT (TLS) forwarded connections. It also adds a new option to dnstap to add metadata to the dnstap extra field, and fixes a config parsing bug in cache.
Brought to You By Chris O&amp;rsquo;Haver, P. Radha Krishna, Yong Tang, Yuheng, Zhizhen He
Noteworthy Changes Revert &amp;ldquo;plugin/forward: Continue waiting after receiving malformed responses (https://github.com/coredns/coredns/pull/6014)&amp;quot; (#6270) plugin/dnstap: add support for &amp;ldquo;extra&amp;rdquo; field in payload (https://github.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.11.0 Release</title>
      <link>https://coredns.io/2023/07/25/coredns-1.11.0-release/</link>
      <pubDate>Tue, 25 Jul 2023 00:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2023/07/25/coredns-1.11.0-release/</guid>
      <description>Release Highlights Adds support for accepting DNS connections over QUIC (doq). Adds CNAME target rewrites to the rewrite plugin. Plus many bug fixes, and some security improvements. This release introduces the following backward incompatible changes:
In the kubernetes plugin, we have dropped support for watching Endpoint and Endpointslice v1beta, since all supported K8s versions now use Endpointslice. The bufsize plugin changed its default size limit value to 1232 Some changes to forward plugin metrics.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.10.1 Release</title>
      <link>https://coredns.io/2023/01/20/coredns-1.10.1-release/</link>
      <pubDate>Fri, 20 Jan 2023 00:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2023/01/20/coredns-1.10.1-release/</guid>
      <description>This release fixes some bugs, and adds some new features including:
Corrected architecture labels in multi-arch image manifest A new plugin timeouts that allows configuration of server listener timeout durations acl can drop queries as an action template supports creating responses with extended DNS errors New weighted policy in loadbalance Option to serve original record TTLs from cache Brought to You By Arthur Outhenin-Chalandre, Ben Kaplan, Chris O&amp;rsquo;Haver, Gabor Dozsa, Grant Spence, Kumiko as a Service, LAMRobinson, Miciah Dashiel Butler Masters, Ondřej Benkovský, Rich, Stephen Kitt, Yash Singh, Yong Tang, rsclarke, sanyo0714</description>
    </item>
    
    <item>
      <title>CoreDNS-1.10.0 Release</title>
      <link>https://coredns.io/2022/09/16/coredns-1.10.0-release/</link>
      <pubDate>Fri, 16 Sep 2022 00:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2022/09/16/coredns-1.10.0-release/</guid>
      <description>This release adds the new view plugin, enabling advanced server-block routing configurations such as split-DNS.
Brought to You By Ben Kochie Chris O&amp;rsquo;Haver Erik Johansson John Belamaric Marius Kimmina Ondřej Benkovský
Noteworthy Changes plugin/view: Advanced routing interface and new &amp;lsquo;view&amp;rsquo; plugin (https://github.com/coredns/coredns/pull/5538) plugin/template: Add parseInt template function (https://github.com/coredns/coredns/pull/5609) </description>
    </item>
    
    <item>
      <title>CoreDNS-1.9.4 Release</title>
      <link>https://coredns.io/2022/09/07/coredns-1.9.4-release/</link>
      <pubDate>Wed, 07 Sep 2022 00:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2022/09/07/coredns-1.9.4-release/</guid>
      <description>This is a release with many new features. The most notable addition is a new plugin tsig for validating TSIG requests and signing responses. In header plugin a selector of query or response (default) is added for applying the actions. This release also adds lots of enhancements and bug fixes.
Brought to You By Abirdcfly Alex AndreasHuber-CH Andy Lindeman Chris Narkiewicz Chris O&amp;rsquo;Haver Christoph Heer Daniel Jolly Konstantin Demin Marius Kimmina Md Sahil Ondřej Benkovský Shane Xie TomasKohout Vancl Yong Tang</description>
    </item>
    
    <item>
      <title>CoreDNS-1.9.3 Release</title>
      <link>https://coredns.io/2022/05/27/coredns-1.9.3-release/</link>
      <pubDate>Fri, 27 May 2022 00:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2022/05/27/coredns-1.9.3-release/</guid>
      <description>This is a release with a focus on security (CVE-2022-27191 and CVE-2022-28948) fixes. Additionally, several feature enhancements and bug fixes have been added.
Brought to You By Chris O&amp;rsquo;Haver, lobshunter, Naveen, Radim Hatlapatka, RetoHaslerMGB, Tintin, Yong Tang
Noteworthy Changes core: update gopkg.in/yaml.v3 to fix CVE-2022-28948 (https://github.com/coredns/coredns/pull/5408) core: update golang.org/x/crypto to fix CVE-2022-27191 (https://github.com/coredns/coredns/pull/5407) plugin/acl: adding a check to parse out zone info (https://github.com/coredns/coredns/pull/5387) plugin/dnstap: support FQDN TCP endpoint (https://github.com/coredns/coredns/pull/5377) plugin/errors: add stacktrace option to log a stacktrace during panic recovery (https://github.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.9.2 Release</title>
      <link>https://coredns.io/2022/05/13/coredns-1.9.2-release/</link>
      <pubDate>Fri, 13 May 2022 00:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2022/05/13/coredns-1.9.2-release/</guid>
      <description>This is a release with many added features and security and bug fixes. The most notable one is the release of 3rd party security audit from Trail of Bits. Security issues discovered by this audit have all been fixed or covered.
Brought to You By Antoine Tollenaere, Balazs Nagy, Chris O&amp;rsquo;Haver, dilyevsky, hansedong, Lorenz Brun, Marius Kimmina, nathannaveen, Ondřej Benkovský, Patrick W. Healy, Qasim Sarfraz, xuweiwei, Yong Tang
Noteworthy Changes core: add Trail of Bits to list of 3rd party security auditors (https://github.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.9.1 Release</title>
      <link>https://coredns.io/2022/03/09/coredns-1.9.1-release/</link>
      <pubDate>Wed, 09 Mar 2022 00:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2022/03/09/coredns-1.9.1-release/</guid>
      <description>This is a release with security and bug fixes and some new features added. 1.9.1 is also built with golang 1.17.8 that addressed several golang 1.17.6 vulnerabilities (CVE-2022-23772, CVE-2022-23773, CVE-2022-23806). Note golang 1.17.6 was used to built coredns 1.9.0.
Brought to You By Chris O&amp;rsquo;Haver, Elijah Andrews, Rudolf Schönecker, Yong Tang, nathannaveen, xuweiwei
Noteworthy Changes plugin/autopath: Don&amp;rsquo;t panic on empty token (https://github.com/coredns/coredns/pull/5169) plugin/cache: Add zones label to cache metrics (https://github.com/coredns/coredns/pull/5124) plugin/file: Add TXT test case (https://github.</description>
    </item>
    
    <item>
      <title>CoreDNS and Apache APISIX open new doors for Service Discovery?</title>
      <link>https://coredns.io/2022/03/03/coredns-and-apache-apisix-open-new-doors-for-service-discovery/</link>
      <pubDate>Thu, 03 Mar 2022 08:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2022/03/03/coredns-and-apache-apisix-open-new-doors-for-service-discovery/</guid>
      <description>Background information In traditional physical machine and virtual machine deployment, calls between various services can
be made through fixed IP + port. With the advent of the cloud-native era, enterprise
business deployment is more inclined to cloud-native containerization. However, in a containerized
environment, the startup and destruction of service instances are very frequent. Manual maintenance
by operation and maintenance personnel will not only be a heavy workload, but also ineffective.</description>
    </item>
    
    <item>
      <title>Trail Of Bits Security Review</title>
      <link>https://coredns.io/2022/02/24/trail-of-bits-security-review/</link>
      <pubDate>Thu, 24 Feb 2022 00:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2022/02/24/trail-of-bits-security-review/</guid>
      <description>Trail of Bits (https://trailofbits.com) conducted a security review and threat model of CoreDNS.
Quoting from the security review summary:
&amp;ldquo;The audit uncovered one high-severity issue (TOB-CDNS-8) concerning a bug that could lead to cache poisoning attacks. The majority of the other issues are of informational or low severity; these include several resulting from insufficient data validation, specifically from assumptions about the data processed by various functions, which we discovered by running fuzzing harnesses.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.9.0 Release</title>
      <link>https://coredns.io/2022/02/01/coredns-1.9.0-release/</link>
      <pubDate>Tue, 01 Feb 2022 00:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2022/02/01/coredns-1.9.0-release/</guid>
      <description>This is a release with bug fixes and some new features added. Starting with 1.9.0 the minimal required go version will be 1.17. Wildcard queries are no longer supported by the kubernetes plugin.
Brought to You By Chris O&amp;rsquo;Haver, Ondřej Benkovský, Tomas Hulata, Yong Tang, xuweiwei
Noteworthy Changes plugin/kubernetes: remove wildcard query functionality (https://github.com/coredns/coredns/pull/5019) Health-checks should respect force_tcp (https://github.com/coredns/coredns/pull/5109) plugin/prometheus: Write rcode properly to the metrics (https://github.com/coredns/coredns/pull/5126) plugin/template: Persist truncated state to client if CNAME lookup response is truncated (https://github.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.8.7 Release</title>
      <link>https://coredns.io/2021/12/09/coredns-1.8.7-release/</link>
      <pubDate>Thu, 09 Dec 2021 00:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2021/12/09/coredns-1.8.7-release/</guid>
      <description>This is a release with bug fixes and some new features added. We now enable HTTP/2 in gRPC service (https://github.com/coredns/coredns/pull/4842). The shuffling algorithm in loadbalance plugin has also been improved to have a more consistent behavior (https://github.com/coredns/coredns/pull/4961). This release will also log deprecation warnings when wildcard queries are received by kubernetes. The wildcard functionality will be completely removed from kubernetes plugin in future releases.
Brought to You By Chris O&amp;rsquo;Haver, Christian Ang, Cyb3r Jak3, Denis Tingaikin, gomakesix, Hu Shuai, Humberto Leal, jayonlau, Johnny Bergström, LiuCongran, Matt Palmer, Miek Gieben, OctoHuman, Ondřej Benkovský, Pavol Lieskovský, Vector, Wu Shuang, xuweiwei, xww, Yong Tang, ZhangJian He, Zou Nengren</description>
    </item>
    
    <item>
      <title>CoreDNS-1.8.6 Release</title>
      <link>https://coredns.io/2021/10/07/coredns-1.8.6-release/</link>
      <pubDate>Thu, 07 Oct 2021 00:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2021/10/07/coredns-1.8.6-release/</guid>
      <description>This is a small bug fix release.
Brought to You By Chris O&amp;rsquo;Haver, Miek Gieben.
Noteworthy Changes plugin/kubernetes: fix reload panic (https://github.com/coredns/coredns/pull/4881) plugin/kubernetes: Don&amp;rsquo;t use pod names longer than 63 characters as dns labels (https://github.com/coredns/coredns/pull/4908) </description>
    </item>
    
    <item>
      <title>CoreDNS-1.8.5 Release</title>
      <link>https://coredns.io/2021/09/10/coredns-1.8.5-release/</link>
      <pubDate>Fri, 10 Sep 2021 07:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2021/09/10/coredns-1.8.5-release/</guid>
      <description>This is a rather big release, we now share plugins among zones in the same server block, which should save memory. Various bug fixes in a bunch of plugins and not one, but two new plugins. A geoip plugin that can report where the query came from and a header plugin that allows you to fiddle with (some of) the header bits in a DNS message.
With this release, the coredns_cache_misses_total metric is deprecated.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.8.4 Release</title>
      <link>https://coredns.io/2021/05/28/coredns-1.8.4-release/</link>
      <pubDate>Fri, 28 May 2021 07:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2021/05/28/coredns-1.8.4-release/</guid>
      <description>The CoreDNS team has released CoreDNS-1.8.4. This release includes a bunch of bugfixes and a few enhancements mostly in the dnssec and kubernetes plugins, and a new (small) plugin called minimal.
It also include a fix when using the &amp;ldquo;reverse zone cidr syntax&amp;rdquo;, e.g. 10.0.0.0/15, now return the proper set of reverse zones.
Brought to You By Chris O&amp;rsquo;Haver, cuirunxing-hub, Frank Riley, Keith Coleman, Miek Gieben, milgradesec, Mohammad Yosefpor, ntoofu, Paco Xu, Soumya Ghosh Dastidar, Steve Greene, Théotime Lévêque, Uwe Krueger, wangchenglong01, Yong Tang, Yury Tsarev.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.8.3 Release</title>
      <link>https://coredns.io/2021/02/24/coredns-1.8.3-release/</link>
      <pubDate>Wed, 24 Feb 2021 07:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2021/02/24/coredns-1.8.3-release/</guid>
      <description>The CoreDNS team has released CoreDNS-1.8.3. This release includes a bunch of bugfixes and a few enhancements, see below.
In case you&amp;rsquo;re wondering, 1.8.2 didn&amp;rsquo;t properly upload and tag the docker images, hence a quick followup release with that fixed.
Brought to You By Bob, chantra, Chris O&amp;rsquo;Haver, Frank Riley, George Shammas, Johnny Bergström, Jun Chen, Lars Ekman, Manuel Rüger, Maxime Ginters, Miek Gieben, slick-nic, TimYin.
Noteworthy Changes core: Also clear do and size (https://github.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.8.2 Release</title>
      <link>https://coredns.io/2021/02/23/coredns-1.8.2-release/</link>
      <pubDate>Tue, 23 Feb 2021 07:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2021/02/23/coredns-1.8.2-release/</guid>
      <description>The CoreDNS team has released CoreDNS-1.8.2. This release includes a bunch of bugfixes and a few enhancements, see below.
Brought to You By Bob, chantra, Chris O&amp;rsquo;Haver, Frank Riley, George Shammas, Johnny Bergström, Jun Chen, Lars Ekman, Manuel Rüger, Maxime Ginters, Miek Gieben, slick-nic, TimYin.
Noteworthy Changes core: Also clear do and size (https://github.com/coredns/coredns/pull/4465) core: Flag blacklisting not needed anymore (https://github.com/coredns/coredns/pull/4420) core: Set http request in writer (https://github.com/coredns/coredns/pull/4445) Makefile.release: Replace manifest-tool with docker manifest (https://github.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.8.1 Release</title>
      <link>https://coredns.io/2021/01/20/coredns-1.8.1-release/</link>
      <pubDate>Wed, 20 Jan 2021 07:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2021/01/20/coredns-1.8.1-release/</guid>
      <description>The CoreDNS team has released CoreDNS-1.8.1.
This release fixes a bunch of bugs, and adds a (very) simple new plugin called local to answer &amp;ldquo;local&amp;rdquo; queries. Bunch of work in the kubernetes plugin to add support for new upstream features.
If using the kubernetes plugin for a Kubernetes cluster &amp;gt;= 1.19, CoreDNS must be granted list and watch access to endpointslices.
Brought to You By Blake Ryan, Bob, Chotiwat Chawannakul, Chris O&amp;rsquo;Haver, Guangwen Feng, Gunadhya, Jiang Biao, Johnny Bergström, luanphantiki, Matt Kulka, mgugger, Miek Gieben, Serge, sschepens, Yong Tang, ZouYu.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.8.0 Release</title>
      <link>https://coredns.io/2020/10/22/coredns-1.8.0-release/</link>
      <pubDate>Thu, 22 Oct 2020 08:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2020/10/22/coredns-1.8.0-release/</guid>
      <description>The CoreDNS team has released CoreDNS-1.8.0.
If you are running 1.7.1 you want to upgrade for the cache plugin fixes.
This release also adds three backwards incompatible changes. This will only affect you if you have an external plugin or use outgoing zone transfers. If you&amp;rsquo;re using dnstap in your plugin, you&amp;rsquo;ll need to upgrade to the new API as detailed in it&amp;rsquo;s documentation.
Two, because Caddy is now developing a version 2 and we are using version 1, we&amp;rsquo;ve internalized Caddy into https://github.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.7.1 Release</title>
      <link>https://coredns.io/2020/09/21/coredns-1.7.1-release/</link>
      <pubDate>Mon, 21 Sep 2020 10:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2020/09/21/coredns-1.7.1-release/</guid>
      <description>The CoreDNS team has released CoreDNS-1.7.1.
This is a small, incremental release that adds some polish and fixes a bunch of bugs.
Brought to You By Ben Kochie, Ben Ye, Chris O&amp;rsquo;Haver, Cricket Liu, Grant Garrett-Grossman, Hu Shuai, Li Zhijian, Maxime Guyot, Miek Gieben, milgradesec, Oleg Atamanenko, Olivier Lemasle, Ricardo Katz, Ruslan Drozhdzh, Yong Tang, Zhou Hao, Zou Nengren.
Noteworthy Changes backend: fix root zone usage (https://github.com/coredns/coredns/pull/4039) core: Add timeouts for http server (https://github.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.7.0 Release</title>
      <link>https://coredns.io/2020/06/15/coredns-1.7.0-release/</link>
      <pubDate>Mon, 15 Jun 2020 10:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2020/06/15/coredns-1.7.0-release/</guid>
      <description>The CoreDNS team has released CoreDNS-1.7.0.
This is a backwards-incompatible release. Major changes include:
Better metrics names. The federation plugin (which allows for v1 Kubernetes federation) has been removed. We&amp;rsquo;ve also removed some supporting code from the kubernetes plugin, so it will not build as an external plugin (with this version of CoreDNS). As this was already backwards-incompatible release, we took the liberty of stuffing as much in one release as possible to minimize the disruption going forward.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.6.8 Release</title>
      <link>https://coredns.io/2020/03/24/coredns-1.6.8-release/</link>
      <pubDate>Tue, 24 Mar 2020 10:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2020/03/24/coredns-1.6.8-release/</guid>
      <description>The CoreDNS team has released CoreDNS-1.6.8.
Again a small release with some nice improvements in the forward plugin, and overall polish. See &amp;ldquo;Noteworthy Changes&amp;rdquo; for more detail.
Note that 1.7.0 will contain a bunch of backward incompatible changes: the federation plugin will be full removed and the metrics name will be changed to inline with the naming recommendation from the Prometheus project.
Brought to You By Andy Bursavich, Chris O&amp;rsquo;Haver, Christian Tryti, Darshan Chaudhary, Kohei Yoshida, LongKB, Miek Gieben, Ricky S, Sylvain Rabot, Zou Nengren.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.6.9 Release</title>
      <link>https://coredns.io/2020/03/24/coredns-1.6.9-release/</link>
      <pubDate>Tue, 24 Mar 2020 10:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2020/03/24/coredns-1.6.9-release/</guid>
      <description>The CoreDNS team has released CoreDNS-1.6.9. This release is identical to 1.6.8.
(Yes there was a CoreDNS-1.6.8, but our automation broke after tagging it in Git - hence another bump in the minor version)
Again a small release with some nice improvements in the forward plugin, and overall polish. See &amp;ldquo;Noteworthy Changes&amp;rdquo; for more detail.
Note that 1.7.0 will contain a bunch of backward incompatible changes: the federation plugin will be full removed and the metrics name will be changed to inline with the naming recommendation from the Prometheus project.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.6.7 Release</title>
      <link>https://coredns.io/2020/01/28/coredns-1.6.7-release/</link>
      <pubDate>Tue, 28 Jan 2020 10:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2020/01/28/coredns-1.6.7-release/</guid>
      <description>The CoreDNS team has released CoreDNS-1.6.7.
This is a fairly small release that resolves some nits and it adds mips64le to the set of architectures that we create binaries for. See &amp;ldquo;Noteworthy Changes&amp;rdquo; for more detail.
Brought to You By Antonio Ojea, Brad P. Crochet, Dominic Yin, DrmagicE, Erfan Besharat, Jonathan Nagy, Kohei Yoshida, Miek Gieben, Yong Tang, Zheng Xie, Zou Nengren.
Noteworthy Changes Add mips64le to released architectures (https://github.com/coredns/coredns/pull/3589) Fix HostPortOrFile to support IPv6 addresses with zone (https://github.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.6.6 Release</title>
      <link>https://coredns.io/2019/12/11/coredns-1.6.6-release/</link>
      <pubDate>Wed, 11 Dec 2019 10:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2019/12/11/coredns-1.6.6-release/</guid>
      <description>The CoreDNS team has released CoreDNS-1.6.6.
A fairly small release that polishes various plugins and fixes a bunch of bugs.
Security The github.com/miekg/dns dependency has been updated to v1.1.25 to fix a DNS related security vulnerability (https://github.com/miekg/dns/issues/1043).
Plugins A new plugin bufsize has been added that prevents IP fragmentation for the DNS Flag Day 2020 and to deal with DNS vulnerabilities.
cache added a serve_stale option similar to unbound&amp;rsquo;s serve_expired. sign fix signing of authoritative data that we are not authoritative for.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.6.5 Release</title>
      <link>https://coredns.io/2019/11/06/coredns-1.6.5-release/</link>
      <pubDate>Wed, 06 Nov 2019 10:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2019/11/06/coredns-1.6.5-release/</guid>
      <description>The CoreDNS team has released CoreDNS-1.6.5.
A fairly small release that polishes various plugins and fixes a bunch of bugs.
Plugins A new plugin transfer that encapsulates the zone transfer knowledge and code in one place. This makes it easier to add this functionality to new plugins. Plugins that already implement zone transfers are expected to move to it in the 1.7.0 release.
forward don&amp;rsquo;t block on returning sockets; instead timeout and drop the socket on the floor, this makes each go-routine guarantee to exit.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.6.4 Release</title>
      <link>https://coredns.io/2019/09/27/coredns-1.6.4-release/</link>
      <pubDate>Fri, 27 Sep 2019 10:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2019/09/27/coredns-1.6.4-release/</guid>
      <description>The CoreDNS team has released CoreDNS-1.6.4.
Various code cleanups and documentation improvements. We&amp;rsquo;ve added one new plugin: acl, that allows blocking requests.
Plugins acl block request from IPs or IP ranges. kubernetes received some bug fixes, see below for specific PRs. hosts exports metrics on the number of entries and last reload time. Brought to You By An Xiao, Chris O&amp;rsquo;Haver, Cricket Liu, Guangming Wang, Kasisnu, li mengyang, Miek Gieben, orangelynx, xieyanker, yeya24, Yong Tang.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.6.3 Release</title>
      <link>https://coredns.io/2019/08/31/coredns-1.6.3-release/</link>
      <pubDate>Sat, 31 Aug 2019 07:30:47 +0000</pubDate>
      
      <guid>https://coredns.io/2019/08/31/coredns-1.6.3-release/</guid>
      <description>The CoreDNS team has released CoreDNS-1.6.3.
In this release we have moved the federation plugin to github.com/coredns/federation, but it is still fully functional in this version. In version 1.7.0 we expect to deprecate it.
Further more a slew a spelling corrections, and other minor improvements and polish. And two new plugins: clouddns and sign.
Plugins clouddns to enable serving zone data from GCP Cloud DNS. sign that (DNSSEC) signs your zonefiles (in its most basic form).</description>
    </item>
    
    <item>
      <title>CoreDNS-1.6.2 Release</title>
      <link>https://coredns.io/2019/08/13/coredns-1.6.2-release/</link>
      <pubDate>Tue, 13 Aug 2019 14:35:47 +0100</pubDate>
      
      <guid>https://coredns.io/2019/08/13/coredns-1.6.2-release/</guid>
      <description>The CoreDNS team has released CoreDNS-1.6.2.
This is a bug fix release, but it also features a new plugin called azure.
It&amp;rsquo;s compiled with Go 1.12.8 that incorporates fixes for HTTP/2 that may impact you if you use DoH.
Plugins Add azure to facilitate serving records from Microsoft Azure. Make the refresh frequency adjustable in the route53 plugin. Fix the handling of truncated responses in forward. Brought to You By Andrey Meshkov, Chris O&amp;rsquo;Haver, Darshan Chaudhary, ethan, Matt Kulka and Miek Gieben.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.6.1 Release</title>
      <link>https://coredns.io/2019/08/02/coredns-1.6.1-release/</link>
      <pubDate>Fri, 02 Aug 2019 14:35:47 +0100</pubDate>
      
      <guid>https://coredns.io/2019/08/02/coredns-1.6.1-release/</guid>
      <description>The CoreDNS team has released CoreDNS-1.6.1.
This is a small (bug fix) release.
Plugins Fix a panic in the hosts plugin. The reload now detects changes in files imported from the main Corefile. route53 increases the paging size when talking to the AWS API, this decreases the chances of getting throttled. Brought to You By Alan, AllenZMC, dzzg, Erik Wilson, Matt Kulka, Miek Gieben, Yong Tang.
Noteworthy Changes core: log panics (https://github.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.6.0 Release</title>
      <link>https://coredns.io/2019/07/28/coredns-1.6.0-release/</link>
      <pubDate>Sun, 28 Jul 2019 14:35:47 +0100</pubDate>
      
      <guid>https://coredns.io/2019/07/28/coredns-1.6.0-release/</guid>
      <description>The CoreDNS team has released CoreDNS-1.6.0.
The -cpu flag is removed from this version.
This release sports changes in the file plugin. A speed up in the log plugin and fixes in the cache and hosts plugins.
Upcoming deprecation: the kubernetes federation plugin will be moved to github.com/coredns/federation. This is likely to happen in CoreDNS 1.7.0.
Plugins The file got lot of bug fixes and it now loads zones lazily on start, i.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.5.2 Release</title>
      <link>https://coredns.io/2019/07/03/coredns-1.5.2-release/</link>
      <pubDate>Wed, 03 Jul 2019 07:35:47 +0100</pubDate>
      
      <guid>https://coredns.io/2019/07/03/coredns-1.5.2-release/</guid>
      <description>The CoreDNS team has released CoreDNS-1.5.2.
Small bugfixes and a change to Caddy&amp;rsquo;s import path (mholt/caddy -&amp;gt; caddyserver/caddy). Doing a release helps plugins deal with the change better.
Plugins For all plugins that use the upstream directive it use removed from the documentation; it&amp;rsquo;s still accepted but is a noop. Currently these plugins use CoreDNS to resolve external queries. The template plugin now supports meta data. The file plugin closes the connection after an AXFR.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.5.1 Release</title>
      <link>https://coredns.io/2019/06/26/coredns-1.5.1-release/</link>
      <pubDate>Wed, 26 Jun 2019 13:54:47 +0100</pubDate>
      
      <guid>https://coredns.io/2019/06/26/coredns-1.5.1-release/</guid>
      <description>The CoreDNS team has released CoreDNS-1.5.1.
Various bugfixes, better documentation and cleanups.
The -cpu flag is somewhat redundant (cgroups/systemd/GOMAXPROCS are better ways to deal with this) and we want to remove it; if you depend on it in some way please voice that in this PR otherwise we&amp;rsquo;ll remove it in the next release.
Plugins A new plugin any that block ANY queries according to RFC 8482 was added.
Failed reload fixes for: ready, health and prometheus - when CoreDNS reloads and the Corefile is invalid these plugins now keep on working.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.5.0 Release</title>
      <link>https://coredns.io/2019/04/06/coredns-1.5.0-release/</link>
      <pubDate>Sat, 06 Apr 2019 08:24:07 +0000</pubDate>
      
      <guid>https://coredns.io/2019/04/06/coredns-1.5.0-release/</guid>
      <description>A new release: CoreDNS-1.5.0.
Two new plugins in this release: grpc, and ready. And some polish and simplifications in the core server code.
The use of TIMEOUT and no_reload in file and auto have been fully deprecated. As is the proxy plugin.
And a update on two important and active bugs:
2593 seems to hone in on Docker and/or the container environment being a contributing factor.
2624 is because of TLS session negotiating in the forward plugin.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.4.0 Release</title>
      <link>https://coredns.io/2019/03/03/coredns-1.4.0-release/</link>
      <pubDate>Sun, 03 Mar 2019 09:04:07 +0000</pubDate>
      
      <guid>https://coredns.io/2019/03/03/coredns-1.4.0-release/</guid>
      <description>We are pleased to announce the release of CoreDNS-1.4.0! Our first release after we became a graduated project in CNCF.
Deprecation notice for the next release:
auto will deprecate TIMEOUT and recommends the use of RELOAD (2516). auto and file will deprecate NO_RELOAD and recommends the use of RELOAD set to 0 (2536). health will revert back to report process level health without plugin status. A new ready plugin will make sure plugins have at least completed their startup sequence.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.3.1 Release</title>
      <link>https://coredns.io/2019/01/13/coredns-1.3.1-release/</link>
      <pubDate>Sun, 13 Jan 2019 15:00:29 +0000</pubDate>
      
      <guid>https://coredns.io/2019/01/13/coredns-1.3.1-release/</guid>
      <description>We are pleased to announce the release of CoreDNS-1.3.1! This is a fairly small release that allows us to announce some backwards incompatible changes in the next (1.4.0) release:
The upstream directive used in various plugin will start to default to the coredns process itself. This allow those resolutions to take advantage of other plugins (i.e. caching). The etcd&amp;rsquo;s plugin StubDomain subsystem relied heavily on this functionality and as such will be removed from that plugin.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.3.0 Release</title>
      <link>https://coredns.io/2018/12/15/coredns-1.3.0-release/</link>
      <pubDate>Sat, 15 Dec 2018 16:14:29 +0000</pubDate>
      
      <guid>https://coredns.io/2018/12/15/coredns-1.3.0-release/</guid>
      <description>We are pleased to announce the release of CoreDNS-1.3.0!
Core In this release we do the EDNS0 handling in the server and make it compliant with https://dnsflagday.net/. This fits a theme where we move more and more protocol details into the server to make life easier for plugin authors.
Plugins k8s_external a new plugin that allows external zones to point to Kubernetes in-cluster services.
rewrite fixes a bug where a rule would eat the first character of a name</description>
    </item>
    
    <item>
      <title>Cluster DNS: CoreDNS vs Kube-DNS</title>
      <link>https://coredns.io/2018/11/27/cluster-dns-coredns-vs-kube-dns/</link>
      <pubDate>Tue, 27 Nov 2018 00:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2018/11/27/cluster-dns-coredns-vs-kube-dns/</guid>
      <description>When compiling data for a resource deployment guide for CoreDNS a few weeks ago, I also collected the same data for kube-dns using the same test environments. Although CoreDNS and Kube-dns ultimately perform the same task, there are some key differences in implementation that affect resource consumption and performance. At a high level, some of these differences are:
CoreDNS is a single container per instance, vs kube-dns which uses three. Kube-dns uses dnsmasq for caching, which is single threaded C.</description>
    </item>
    
    <item>
      <title>Scaling CoreDNS in Kubernetes Clusters</title>
      <link>https://coredns.io/2018/11/15/scaling-coredns-in-kubernetes-clusters/</link>
      <pubDate>Thu, 15 Nov 2018 00:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2018/11/15/scaling-coredns-in-kubernetes-clusters/</guid>
      <description>I&amp;rsquo;m sharing the results of some tests I ran with CoreDNS (1.2.5) in Kubernetes (1.12) to provide some reference points for tuning CoreDNS to your cluster. In addition to testing CoreDNS in its default configuration, I tested CoreDNS with the optional autopath plugin enabled. The autopath plugin is an optimization that helps transparently mitigate the DNS performance penalties Pods incur due to Kubernetes&amp;rsquo; infamous ndots:5 issue. These tests quantify the memory/performance trade when enabling autopath.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.2.6 Release</title>
      <link>https://coredns.io/2018/11/05/coredns-1.2.6-release/</link>
      <pubDate>Mon, 05 Nov 2018 20:40:29 +0100</pubDate>
      
      <guid>https://coredns.io/2018/11/05/coredns-1.2.6-release/</guid>
      <description>We are pleased to announce the release of CoreDNS-1.2.6!
Core Ignore the error when setting SO_REUSEPORT on a socket fails; this makes CoreDNS work on older kernels.
Plugins etcd has seen minor bugfixes.
loop fixes a bug when dealing with a failing upstream.
log unifies all logging (done by this plugin and normal logs) and always use RFC3339 timestamps (with millisecond accuracy). The {when} verb has been made a noop, it will be removed in the next release.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.2.5 Release</title>
      <link>https://coredns.io/2018/10/24/coredns-1.2.5-release/</link>
      <pubDate>Wed, 24 Oct 2018 20:40:29 +0100</pubDate>
      
      <guid>https://coredns.io/2018/10/24/coredns-1.2.5-release/</guid>
      <description>We are pleased to announce the release of CoreDNS-1.2.5!
Core Correctly make a reply fit in the client&amp;rsquo;s buffer, especially when EDNS0 is not used. This used to be the responsibility of a plugin, now the server will handle it.
Plugins Documentation and smaller updates for various plugins, as well as:
cache - resets min TTL default back to 5 second (instead of 0). dnssec - now allows aZSK/KSK split as well as a CSK setup.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.2.4 Release</title>
      <link>https://coredns.io/2018/10/17/coredns-1.2.4-release/</link>
      <pubDate>Wed, 17 Oct 2018 20:01:29 +0100</pubDate>
      
      <guid>https://coredns.io/2018/10/17/coredns-1.2.4-release/</guid>
      <description>We are pleased to announce the release of CoreDNS-1.2.4!
Remember we said the 1.2.3 release was a big release and took quite a while? Well, we&amp;rsquo;ve fixed that glitch; as 1.2.4 is here now.
CoreDNS v1.2.3&amp;rsquo;s kubernetes plugin DOES NOT WORK IN KUBERNETES and our testing that didn&amp;rsquo;t catch that regression, nor the Kubernetes scale testing which doesn&amp;rsquo;t really exercise the whole API.
Plugins cache use zero of the minimal negative TTL (if no suitable TTL was found in the packet).</description>
    </item>
    
    <item>
      <title>CoreDNS-1.2.3 Release</title>
      <link>https://coredns.io/2018/10/16/coredns-1.2.3-release/</link>
      <pubDate>Tue, 16 Oct 2018 11:37:29 +0100</pubDate>
      
      <guid>https://coredns.io/2018/10/16/coredns-1.2.3-release/</guid>
      <description>We are pleased to announce the release of CoreDNS-1.2.3!
Core This is a big release that spans almost 6 weeks of development, slightly longer than normal. You may also have noticed that CoreDNS wasn&amp;rsquo;t made the default in Kubernetes 1.12 due to increased memory used compared to kube-dns. This release contains a fix for that.
The underlying DNS library has seen multiple updates to improve throughput and memory and we have enabled REUSE_PORT on the ports CoreDNS opens on *nix.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.2.2 Release</title>
      <link>https://coredns.io/2018/08/29/coredns-1.2.2-release/</link>
      <pubDate>Wed, 29 Aug 2018 07:10:29 +0100</pubDate>
      
      <guid>https://coredns.io/2018/08/29/coredns-1.2.2-release/</guid>
      <description>We are pleased to announce the release of CoreDNS-1.2.2!
This is a (small) release that helps out our friends at kops: make the default cache size smaller.
Contributors The following people helped with getting this release done:
Chris O&amp;rsquo;Haver, Miek Gieben.
For documentation see our (in progress!) manual. For help and other resources, see our community page.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.2.1 Release</title>
      <link>https://coredns.io/2018/08/28/coredns-1.2.1-release/</link>
      <pubDate>Tue, 28 Aug 2018 07:10:29 +0100</pubDate>
      
      <guid>https://coredns.io/2018/08/28/coredns-1.2.1-release/</guid>
      <description>We are pleased to announce the release of CoreDNS-1.2.1!
This release features bugfixes (mostly in the kubernetes plugin), documentation improvements and one new plugin: loop.
Plugins A new plugin called loop was added. When starting up it detects resolver loops and stops the process if one is detected. Contributors The following people helped with getting this release done. Good to see a whole bunch of new names, as well as the usual suspects:</description>
    </item>
    
    <item>
      <title>CoreDNS-1.2.0 Release</title>
      <link>https://coredns.io/2018/07/11/coredns-1.2.0-release/</link>
      <pubDate>Wed, 11 Jul 2018 11:13:29 +0100</pubDate>
      
      <guid>https://coredns.io/2018/07/11/coredns-1.2.0-release/</guid>
      <description>We are pleased to announce the release of CoreDNS-1.2.0!
In this release we have a new plugin, bump etcd to version 3 and bugfixes.
Core Enable watch functionality when CoreDNS is used as a gRPC server (documented in the code - for now).
Plugins A new plugin called metadata was added. It adds metadata to a query, via the context. The etcd plugin now supports etcd version 3 (only!). It was impossible to support v2 and v3 at the same time (even as separate plugins); so we decided to drop v2 support.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.1.4 Release</title>
      <link>https://coredns.io/2018/06/19/coredns-1.1.4-release/</link>
      <pubDate>Tue, 19 Jun 2018 09:39:29 +0100</pubDate>
      
      <guid>https://coredns.io/2018/06/19/coredns-1.1.4-release/</guid>
      <description>We are pleased to announce the release of CoreDNS-1.1.4!
This release has a few enhancements in the plugins, and a few (Docker) improvements.
Core As said in the 1.1.3 Release Notes, we are making the -log command line flag a noop.
This is also a heads up that in the next release - 1.2.0 - the current etcd plugin will be replaced by a new plugin that supports etcd3, see this pull request.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.1.3 Release</title>
      <link>https://coredns.io/2018/05/24/coredns-1.1.3-release/</link>
      <pubDate>Thu, 24 May 2018 09:43:29 +0100</pubDate>
      
      <guid>https://coredns.io/2018/05/24/coredns-1.1.3-release/</guid>
      <description>We are pleased to announce the release of CoreDNS-1.1.3!
This release has fixes in the plugins, small core updates and experimental DNS over HTTPs support. We also announce the deprecation of a few things.
Core Experimental DNS-over-HTTPS support was added in the server. Use https:// as the server&amp;rsquo;s scheme in the configuration.
The -log flag actually doesn&amp;rsquo;t do anything, so this is a deprecation notice that this flag will be removed in the next release.</description>
    </item>
    
    <item>
      <title>Migration from kube-dns to CoreDNS</title>
      <link>https://coredns.io/2018/05/21/migration-from-kube-dns-to-coredns/</link>
      <pubDate>Mon, 21 May 2018 20:23:43 +0000</pubDate>
      
      <guid>https://coredns.io/2018/05/21/migration-from-kube-dns-to-coredns/</guid>
      <description>CoreDNS is currently a Beta feature in Kubernetes and on course to being graduated to General Availability (GA) for Kubernetes 1.11. This means that CoreDNS will be available as a standard in Kubernetes via the installation toolkits such as kubeadm, kube-up, minikube and kops.
This document will guide you to migrating the DNS service from CoreDNS to kube-dns when using the various tools available to spin up a Kubernetes cluster.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.1.2 Release</title>
      <link>https://coredns.io/2018/04/23/coredns-1.1.2-release/</link>
      <pubDate>Mon, 23 Apr 2018 09:21:29 +0100</pubDate>
      
      <guid>https://coredns.io/2018/04/23/coredns-1.1.2-release/</guid>
      <description>We are pleased to announce the release of CoreDNS-1.1.2!
This release has some fixes in the plugins and no core updates.
Plugins forward has received a large pile of fixes and improvements. reload: the metrics and health plugin saw fixes for this reload issue, still not 100% perfect, but a whole lot better than it was. log now allows ORing of log classes. metrics: add a server label to make each metric unique to the server handling it.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.1.1 Release</title>
      <link>https://coredns.io/2018/03/25/coredns-1.1.1-release/</link>
      <pubDate>Sun, 25 Mar 2018 18:04:29 +0100</pubDate>
      
      <guid>https://coredns.io/2018/03/25/coredns-1.1.1-release/</guid>
      <description>We are pleased to announce the release of CoreDNS-1.1.1!
This release fixes a critical bug in the cache plugin found by Cure53.
All users are encouraged to upgrade.
Core Fix a bug when scrubbing the reply to fit the request&amp;rsquo;s buffer consumes 100% CPU and does not return the reply.
Plugins cache fixes the critical spoof vulnerability. route53 adds support for PTR records. Contributors The following people helped with getting this release done:</description>
    </item>
    
    <item>
      <title>Cure53 Security Assessment</title>
      <link>https://coredns.io/2018/03/15/cure53-security-assessment/</link>
      <pubDate>Thu, 15 Mar 2018 09:34:29 +0000</pubDate>
      
      <guid>https://coredns.io/2018/03/15/cure53-security-assessment/</guid>
      <description>Being an incubating CNCF project makes us eligible for nice things like a security assessment (cue ominous music).
The CNCF asked Cure53 to perform such an assessment.
TL;DR: CoreDNS is in good shape, but Cure53 did find one critical issue (which we&amp;rsquo;ve fixed with the CoreDNS 1.1.1 release):
DNS-01-003 Cache: DNS Cache poisoning via malicious Response (Critical) The CoreDNS application allows to configure the caching of the DNS responses via the cache plugin.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.1.0 Release</title>
      <link>https://coredns.io/2018/03/12/coredns-1.1.0-release/</link>
      <pubDate>Mon, 12 Mar 2018 09:33:29 +0000</pubDate>
      
      <guid>https://coredns.io/2018/03/12/coredns-1.1.0-release/</guid>
      <description>We are pleased to announce the release of CoreDNS-1.1.0!
CoreDNS has been promoted to the incubating level in the CNCF! This has been made possible by the work done by contributors, users and adopters.
Thank you all!
Core Bump the version to 1.1.0, as we deprecate two plugins (shutdown and startup).
In CoreDNS 1.0.6 the bind plugin was extended to allow binding to multiple interfaces. This release adds the ability serve the same zone on different interfaces (we used to block this for no good reason).</description>
    </item>
    
    <item>
      <title>CoreDNS-1.0.6 Release</title>
      <link>https://coredns.io/2018/02/21/coredns-1.0.6-release/</link>
      <pubDate>Wed, 21 Feb 2018 11:10:29 +0000</pubDate>
      
      <guid>https://coredns.io/2018/02/21/coredns-1.0.6-release/</guid>
      <description>We are pleased to announce the release of CoreDNS-1.0.6! This release has bug fixes, documentation fixes, polish and new plugins.
Core We&amp;rsquo;ve moved to a OWNERS model, where each plugin (and CoreDNS itself) now has an OWNERS file listing people involved with this code.
Plugins The startup and shutdown plugin are deprecated (but working and included) in this release in favor of the on plugin. If you use them, this is the moment to move to on.</description>
    </item>
    
    <item>
      <title>Deploying Kubernetes with CoreDNS using kubeadm</title>
      <link>https://coredns.io/2018/01/29/deploying-kubernetes-with-coredns-using-kubeadm/</link>
      <pubDate>Mon, 29 Jan 2018 10:12:43 +0000</pubDate>
      
      <guid>https://coredns.io/2018/01/29/deploying-kubernetes-with-coredns-using-kubeadm/</guid>
      <description>Kubernetes 1.9 has recently been launched and it ships with CoreDNS being a part of it. We can now install CoreDNS as the default service discovery via Kubeadm, which is the toolkit to install Kubernetes easily in a single step.
Currently, CoreDNS is Alpha in Kubernetes 1.9. We have a roadmap which will make CoreDNS Beta in version 1.10 and eventually be the default DNS, replacing kube-dns.
It is important to note that currently when switching from kube-dns to CoreDNS, the configurations that come with kube-dns (stubzones, federations&amp;hellip;) will no longer exist and will switch to a default configuration in CoreDNS.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.0.5 Release</title>
      <link>https://coredns.io/2018/01/25/coredns-1.0.5-release/</link>
      <pubDate>Thu, 25 Jan 2018 11:10:29 +0000</pubDate>
      
      <guid>https://coredns.io/2018/01/25/coredns-1.0.5-release/</guid>
      <description>We are pleased to announce the release of CoreDNS-1.0.5! This release has bug fixes, documentation fixes, polish and new plugins.
Core Add ability to really compile out the default plugins.
Plugins A new plugin route53 was added that enables serving zone data from AWS route53, see the documentation.
A new plugin on was added. This is an external Caddy plugin, that is now also available (by default) for CoreDNS; it allows you to run commands when an event is generated.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.0.4 Release</title>
      <link>https://coredns.io/2018/01/18/coredns-1.0.4-release/</link>
      <pubDate>Thu, 18 Jan 2018 15:54:29 +0000</pubDate>
      
      <guid>https://coredns.io/2018/01/18/coredns-1.0.4-release/</guid>
      <description>We are announcing the release of CoreDNS-1.0.4!
This is a release that fixes a vulnerability in the underlying DNS library. See https://github.com/miekg/dns/issues/627 and the (still embargoed) CVE-2017-15133. Thanks to Tom Thorogood for bringing this issue to our attention.
CoreDNS-1.0.4 is CoreDNS-1.0.3 recompiled with a patched DNS library.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.0.3 Release</title>
      <link>https://coredns.io/2018/01/10/coredns-1.0.3-release/</link>
      <pubDate>Wed, 10 Jan 2018 19:38:29 +0000</pubDate>
      
      <guid>https://coredns.io/2018/01/10/coredns-1.0.3-release/</guid>
      <description>We are pleased to announce the release of CoreDNS-1.0.3! This is a small bugfix release, but we also have a new plugin: template.
Core Manual pages are now generated from the READMEs, you can find them in the man/ directory. A coredns(1) and corefile(5) one where also added.
Plugins The fallthrough directive was overhauled and now allows a list of zones to be specified. It will then only fallthrough for those zones, see plugin/plugin.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.0.2 Release</title>
      <link>https://coredns.io/2017/12/31/coredns-1.0.2-release/</link>
      <pubDate>Sun, 31 Dec 2017 09:06:29 +0000</pubDate>
      
      <guid>https://coredns.io/2017/12/31/coredns-1.0.2-release/</guid>
      <description>We are pleased to announce the release of CoreDNS-1.0.2! This release can be summarized as &amp;ldquo;help external plugin developers&amp;rdquo; as most changes are geared towards exposing CoreDNS functionality to make this as easy as possible. Is also a fairly small release.
Core Expose the directives list, so that external plugins can be easily added without mucking with CoreDNS code, see the pull request for details.
Fix crash when there are no handlers that can actually serve queries, i.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.0.1 Release</title>
      <link>https://coredns.io/2017/12/11/coredns-1.0.1-release/</link>
      <pubDate>Mon, 11 Dec 2017 14:43:43 +0000</pubDate>
      
      <guid>https://coredns.io/2017/12/11/coredns-1.0.1-release/</guid>
      <description>We are pleased to announce the release of CoreDNS-1.0.1!
This release fixes a crash in the file plugin and has some minor bug fixes for other plugins. One new plugin was added: nsid, that implements RFC 5001.
Plugins file fixes a crash when an request with a DO bit (pretty much the default) hits an unsigned zone. The default configuration should recover the go-routine, but this is nonetheless serious. file received some other fixes when returning (secure) delegations.</description>
    </item>
    
    <item>
      <title>CoreDNS-1.0.0 Release</title>
      <link>https://coredns.io/2017/12/01/coredns-1.0.0-release/</link>
      <pubDate>Fri, 01 Dec 2017 22:43:43 +0000</pubDate>
      
      <guid>https://coredns.io/2017/12/01/coredns-1.0.0-release/</guid>
      <description>We are pleased to announce the release of CoreDNS-1.0.0!
Release 1.0.0 and other recent releases have focused on improving the performance and functionality of the kubernetes plugin, since CoreDNS is now on track to eventually replace kube-dns as the default cluster DNS in Kubernetes.
As part of the Kubernetes proposal, we have shown that CoreDNS not only provides more functionality than kube-dns, but performs much better while using less memory. In our tests, CoreDNS running against a cluster with 5000 services was able to process 18,000 queries per second using 73MB of RAM, while kube-dns achieved 7,000qps using 97MB of RAM.</description>
    </item>
    
    <item>
      <title>CoreDNS-0.9.10 Release</title>
      <link>https://coredns.io/2017/11/03/coredns-0.9.10-release/</link>
      <pubDate>Fri, 03 Nov 2017 20:45:43 +0000</pubDate>
      
      <guid>https://coredns.io/2017/11/03/coredns-0.9.10-release/</guid>
      <description>CoreDNS-0.9.10 has been released!
CoreDNS is a DNS server that chains plugins, where each plugin implements a DNS feature.
Release 0.9.10 is a minor release, with some fixes.
Core The reverse zone syntax was extended to allow non-octet boundaries:
192.168.1.0/17 { ... } Will behave correctly.
Lots of documentation clean ups.
More platforms have binaries for each release.
Plugins dnssec will now insert DS records (and sign them) when it signs a delegation response.</description>
    </item>
    
    <item>
      <title>Setting up CoreDNS (on AWS)</title>
      <link>https://coredns.io/2017/11/03/setting-up-coredns-on-aws/</link>
      <pubDate>Fri, 03 Nov 2017 07:40:37 +0000</pubDate>
      
      <guid>https://coredns.io/2017/11/03/setting-up-coredns-on-aws/</guid>
      <description>At step by step walkthrough on setting up CoreDNS in Kubernetes (on AWS). Published by Arun Gupta.
Also see this twitter thread.</description>
    </item>
    
    <item>
      <title>CoreDNS-0.9.9 Release</title>
      <link>https://coredns.io/2017/10/18/coredns-0.9.9-release/</link>
      <pubDate>Wed, 18 Oct 2017 11:37:43 -0400</pubDate>
      
      <guid>https://coredns.io/2017/10/18/coredns-0.9.9-release/</guid>
      <description>CoreDNS-0.9.9 has been released! (yes, we&amp;rsquo;ve moved to semver)
CoreDNS is a DNS server that chains plugins, where each plugin implements a DNS feature.
Release 0.9.9 is a major release, with lots of fixes.
Core We&amp;rsquo;ve renamed middleware.Middleware to plugin.Plugin. This is backwards incompatible for external middleware plugins, but you can update your plugin by just replacing [Mm]iddleware with [Pp]lugin: sed &amp;#39;s/Middleware/Plugin/&amp;#39;g -i *.go sed &amp;#39;s/middleware/plugin/&amp;#39;g -i *.go From now on we&amp;rsquo;ll use the term plugin in our documentation and code.</description>
    </item>
    
    <item>
      <title>Semantic Versioning</title>
      <link>https://coredns.io/2017/09/16/semantic-versioning/</link>
      <pubDate>Sat, 16 Sep 2017 07:28:00 +0000</pubDate>
      
      <guid>https://coredns.io/2017/09/16/semantic-versioning/</guid>
      <description>CoreDNS&amp;rsquo; next release is around the corner and it is going to be 1.0.0. With this release to move to semantic versioning. This will allow us to make changes, some of which may be backwards incompatible, in a sane manor:
Given a version number MAJOR.MINOR.PATCH, increment the:
MAJOR version when you make incompatible API changes, MINOR version when you add functionality in a backwards-compatible manner, and PATCH version when you make backwards-compatible bug fixes.</description>
    </item>
    
    <item>
      <title>CoreDNS-011 Release</title>
      <link>https://coredns.io/2017/09/10/coredns-011-release/</link>
      <pubDate>Sun, 10 Sep 2017 20:24:43 -0400</pubDate>
      
      <guid>https://coredns.io/2017/09/10/coredns-011-release/</guid>
      <description>CoreDNS-011 has been released!
CoreDNS is a DNS server that chains plugins, where each plugin implements a DNS feature.
Release v011 is a major release, with backwards incompatible changes in the kubernetes plugin.
Core This release has backwards incompatible changes for the kubernetes plugin.
Stop vendoring github.com/miekg/dns and golang.org/x/net/context. This enables external plugin to compile without tripping over vendored types that mismatch. Allow an easy way to specify reverse zones in the Corefile, just use (e.</description>
    </item>
    
    <item>
      <title>A first look at CoreDNS</title>
      <link>https://coredns.io/2017/09/09/a-first-look-at-coredns/</link>
      <pubDate>Sat, 09 Sep 2017 15:05:37 +0100</pubDate>
      
      <guid>https://coredns.io/2017/09/09/a-first-look-at-coredns/</guid>
      <description>JP Mens (author of Alternative DNS servers, takes a first look at CoreDNS on his blog: https://jpmens.net/2017/09/09/coredns/</description>
    </item>
    
    <item>
      <title>CoreDNS Performance Testing</title>
      <link>https://coredns.io/2017/08/08/coredns-performance-testing/</link>
      <pubDate>Tue, 08 Aug 2017 22:50:37 +0100</pubDate>
      
      <guid>https://coredns.io/2017/08/08/coredns-performance-testing/</guid>
      <description>As CoreDNS is an inception level project under the CNCF which means we have access to the physical cloud infrastructure of Packet, a bare metal(!) cloud provider. Physical machines imply performance and also because you get an entire machine you can use them for performance metrics.
For CoreDNS we have a few Benchmark tests (from the Go standard library) that haven&amp;rsquo;t seen much use. Typically you run these before your change and then after your and then use a tool like benchcmp to compare the results and impress your PR&amp;rsquo;s reviewers.</description>
    </item>
    
    <item>
      <title>Logging with dnstap</title>
      <link>https://coredns.io/2017/08/03/logging-with-dnstap/</link>
      <pubDate>Thu, 03 Aug 2017 10:25:28 +0200</pubDate>
      
      <guid>https://coredns.io/2017/08/03/logging-with-dnstap/</guid>
      <description>dnstap is a flexible, structured binary log format for DNS software1. It uses Protocol Buffers to encode events that occur inside DNS software in an implementation-neutral format.
dnstap can encode any DNS message exchanged by the server, along with information about the remote computer (IP address, port) and time. It includes client queries and responses, but also proxied requests or other information requested from other name servers.
This example shows output from the dnstap command-line tool to get an idea of the kind of information that dnstap can provide:</description>
    </item>
    
    <item>
      <title>Intro to CoreDNS webinar by John Belamaric</title>
      <link>https://coredns.io/2017/08/01/intro-to-coredns-webinar-by-john-belamaric/</link>
      <pubDate>Tue, 01 Aug 2017 18:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2017/08/01/intro-to-coredns-webinar-by-john-belamaric/</guid>
      <description>The recording of the webinar (&amp;ldquo;Intro to CoreDNS&amp;rdquo;) that John Belamaric gave is now available:</description>
    </item>
    
    <item>
      <title>CoreDNS-010 Release</title>
      <link>https://coredns.io/2017/07/25/coredns-010-release/</link>
      <pubDate>Tue, 25 Jul 2017 11:24:43 -0400</pubDate>
      
      <guid>https://coredns.io/2017/07/25/coredns-010-release/</guid>
      <description>CoreDNS-010 has been released!
CoreDNS is a DNS server that chains plugins, where each plugin implements a DNS feature.
Release v010 is mostly a bugfix release, with one new plugin - dnstap.
Core No changes.
Plugins New dnstap is a new plugin that allows you to get dnstap information from CoreDNS. Updates file now handles multiple wildcard below each other correctly, and handles wildcards at the apex. hosts, and kubernetes have been fixed to return success with no data in cases where records exist but not of the requested type.</description>
    </item>
    
    <item>
      <title>Compile Time Enabling or Disabling Plugins</title>
      <link>https://coredns.io/2017/07/25/compile-time-enabling-or-disabling-plugins/</link>
      <pubDate>Tue, 25 Jul 2017 16:07:39 +0100</pubDate>
      
      <guid>https://coredns.io/2017/07/25/compile-time-enabling-or-disabling-plugins/</guid>
      <description>CoreDNS&amp;rsquo; plugins (or external plugins) can be enabled or disabled on the fly by specifying (or not specifying) it in the Corefile. But you can also compile CoreDNS with only the plugins you need and leave the rest completely out.
There are two ways to achieve that. It could be done via compile-time configuration file with CoreDNS code base update. It also could be achieved without modifying CoreDNS code.
Build with compile-time configuration file The with compile-time configuration file, plugin.</description>
    </item>
    
    <item>
      <title>Quick Start</title>
      <link>https://coredns.io/2017/07/24/quick-start/</link>
      <pubDate>Mon, 24 Jul 2017 07:37:13 +0000</pubDate>
      
      <guid>https://coredns.io/2017/07/24/quick-start/</guid>
      <description>First get CoreDNS, either
Download the latest release from GitHub, unpack it. You should now have a &amp;ldquo;coredns&amp;rdquo; executable.
Compile from git by getting the source code from GitHub. Change directory to coredns and:
go get - to get a few dependencies, the other ones are vendored go build You should now have a &amp;ldquo;coredns&amp;rdquo; executable.
Get the Docker image from docker hub.
If you want to use CoreDNS in Kubernetes, please check this post about SD with the kuberneters plugin.</description>
    </item>
    
    <item>
      <title>When Should Plugins be External?</title>
      <link>https://coredns.io/2017/07/23/when-should-plugins-be-external/</link>
      <pubDate>Sun, 23 Jul 2017 22:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2017/07/23/when-should-plugins-be-external/</guid>
      <description>The plugin.md in the CoreDNS source tree has some pointers on what a plugin for CoreDNS should have as minimum requirements. It basically boils down to: &amp;ldquo;it should add something unique and useful to CoreDNS&amp;rdquo;. Further more documentation, tests and functionality should all be excellent.
It is easier to list when a plugin can be included in CoreDNS than to say it should stay external, so we will do that:</description>
    </item>
    
    <item>
      <title>Add External Plugins</title>
      <link>https://coredns.io/2017/07/23/add-external-plugins/</link>
      <pubDate>Sun, 23 Jul 2017 21:28:13 +0000</pubDate>
      
      <guid>https://coredns.io/2017/07/23/add-external-plugins/</guid>
      <description>If you want to have your external plugin listed create a pull request.
In that pull request you&amp;rsquo;ll need to add a file to content/explugins/ that looks like this:
+++ title = &amp;#34;&amp;lt;plugin name&amp;gt;&amp;#34; description = &amp;#34;*&amp;lt;plugin name&amp;gt;* is a ...&amp;#34; weight = 10 tags = [ &amp;#34;plugin&amp;#34; , &amp;#34;&amp;lt;plugin name&amp;gt;&amp;#34; ] categories = [ &amp;#34;plugin&amp;#34;, &amp;#34;external&amp;#34; ] date = &amp;#34;2017-07-22T12:37:19+01:00&amp;#34; repo = &amp;#34;https://link-to-your-plugin-repo&amp;#34; home = &amp;#34;https://link-to-your-homepage-or-readme&amp;#34; +++ ## Description The *&amp;lt;plugin name&amp;gt;* plugin is a .</description>
    </item>
    
    <item>
      <title>Corefile Explained</title>
      <link>https://coredns.io/2017/07/23/corefile-explained/</link>
      <pubDate>Sun, 23 Jul 2017 21:28:13 +0000</pubDate>
      
      <guid>https://coredns.io/2017/07/23/corefile-explained/</guid>
      <description>The Corefile is CoreDNS&amp;rsquo;s configuration file. It defines:
What servers listen on what ports and which protocol. For which zone each server is authoritative. Which plugins are loaded in a server. To explain more, let take a look at this &amp;ldquo;Corefile&amp;rdquo;:
ZONE:[PORT] { [PLUGIN]... } ZONE defines the zone this server. The optional PORT defaults to 53, or the value of the -dns.port flag. PLUGIN defines the plugin(s) we want to load.</description>
    </item>
    
    <item>
      <title>CoreDNS-009 Release</title>
      <link>https://coredns.io/2017/07/13/coredns-009-release/</link>
      <pubDate>Thu, 13 Jul 2017 22:52:11 +0000</pubDate>
      
      <guid>https://coredns.io/2017/07/13/coredns-009-release/</guid>
      <description>CoreDNS-009 has been released!
CoreDNS is a DNS server that chains plugins, where each plugin implements a DNS feature.
Release v009 is mostly a bugfix release, with a few new features in the plugin.
Core No changes.
Plugins secondary: fix functionality and improve matching of notify queries. cache: fix data race. proxy: async healthchecks. reverse: new option wildcard that also catches all subdomains of a template. kubernetes: experimental new option autopath that optimizes the search path and ndots combinatorial explosion, so clients with a large search path and high ndots will get a reply on the first query.</description>
    </item>
    
    <item>
      <title>CoreDNS-008 Release</title>
      <link>https://coredns.io/2017/06/14/coredns-008-release/</link>
      <pubDate>Wed, 14 Jun 2017 22:52:11 +0000</pubDate>
      
      <guid>https://coredns.io/2017/06/14/coredns-008-release/</guid>
      <description>CoreDNS-008 has been released!
CoreDNS is a DNS server that chains plugins, where each plugin implements a DNS feature.
Release v008 has a lot of content, with new plugin and major features added to existing plugin.
Please note there is an incompatible change to the log directive - it now only logs to stdout and so only allows stdout as the file name (which of course may be omitted).
Core -log flag was changed into a boolean as all logging will be written to standard output.</description>
    </item>
    
    <item>
      <title>How Queries Are Processed in CoreDNS</title>
      <link>https://coredns.io/2017/06/08/how-queries-are-processed-in-coredns/</link>
      <pubDate>Thu, 08 Jun 2017 20:01:00 +0000</pubDate>
      
      <guid>https://coredns.io/2017/06/08/how-queries-are-processed-in-coredns/</guid>
      <description>In the last post, we described three different use cases for custom DNS entries in Kubernetes:
Making an alias for an external name Dynamically adding services to another domain, without running another server Adding an arbitrary entry inside the cluster domain In that post we covered the first two. In this post, we&amp;rsquo;ll show you how to use the fallthrough option of the kubernetes plugin to satisfy the third case.</description>
    </item>
    
    <item>
      <title>Custom DNS Entries For Kubernetes</title>
      <link>https://coredns.io/2017/05/08/custom-dns-entries-for-kubernetes/</link>
      <pubDate>Mon, 08 May 2017 20:01:00 +0000</pubDate>
      
      <guid>https://coredns.io/2017/05/08/custom-dns-entries-for-kubernetes/</guid>
      <description>As described in our previous post, CoreDNS can be used in place of Kube-DNS for service discovery in Kubernetes clusters. Because of the flexible architecture of CoreDNS, this can enable some interesting use cases. In this blog, we&amp;rsquo;ll show how to solve a common problem - creating custom DNS entries for your services.
There are a couple of different possiblities here:
Making an alias for an external name Dynamically adding services to another domain, without running another server Adding an arbitrary entry inside the cluster domain CoreDNS can solve all of these use cases.</description>
    </item>
    
    <item>
      <title>CoreDNS-007 Release</title>
      <link>https://coredns.io/2017/05/03/coredns-007-release/</link>
      <pubDate>Wed, 03 May 2017 19:26:11 +0000</pubDate>
      
      <guid>https://coredns.io/2017/05/03/coredns-007-release/</guid>
      <description>CoreDNS-007 has been released!
CoreDNS is a DNS server that chains plugins, where each plugin implements a DNS feature.
News CoreDNS is accepted as an inception project by the CNCF! Which means a lot to us. See this blog post on why we wanted/did this.
Because of this we moved repos: https://github.com/coredns is the main overarching repo. There is an automatic redirect in place from the old repo.
And&amp;hellip; We have a new logo!</description>
    </item>
    
    <item>
      <title>CoreDNS for Minikube</title>
      <link>https://coredns.io/2017/04/28/coredns-for-minikube/</link>
      <pubDate>Fri, 28 Apr 2017 12:30:00 +0000</pubDate>
      
      <guid>https://coredns.io/2017/04/28/coredns-for-minikube/</guid>
      <description>In our previous post, we showed how CoreDNS can be used in place of Kube-DNS for service discovery in Kubernetes clusters. In that blog, there is a footnote about issues trying to replace Kube-DNS when using Google Container Engine (GKE). As it so happens, there is a similar issue with minikube, which is a local Kubernetes environment that is very useful for developers.
When you try to replace Kube-DNS, you will find that shortly after you modify its service to point to CoreDNS, your changes will be reverted.</description>
    </item>
    
    <item>
      <title>Why CNCF for CoreDNS?</title>
      <link>https://coredns.io/2017/03/02/why-cncf-for-coredns/</link>
      <pubDate>Thu, 02 Mar 2017 18:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2017/03/02/why-cncf-for-coredns/</guid>
      <description>CoreDNS has been accepted into the Cloud Native Computing Foundation as an inception project! We figure some of you may be wondering why we proposed CoreDNS as a CNCF project, so we wrote this blog entry.
Our goal is to make CoreDNS the cloud-native DNS server and service discovery solution. The CNCF as an organization is focused on the advancement of cloud-native architectures. So, to us, this is an excellent match.</description>
    </item>
    
    <item>
      <title>CoreDNS for Kubernetes Service Discovery, Take 2</title>
      <link>https://coredns.io/2017/03/01/coredns-for-kubernetes-service-discovery-take-2/</link>
      <pubDate>Wed, 01 Mar 2017 20:33:08 +0000</pubDate>
      
      <guid>https://coredns.io/2017/03/01/coredns-for-kubernetes-service-discovery-take-2/</guid>
      <description>A couple months ago we published a blog post on how to use CoreDNS instead of kube-dns in Kubernetes. Since then, we have made a lot of progress. We worked with the community to define a specification for [Kubernetes DNS-Based Service Discovery] (https://github.com/kubernetes/dns/blob/master/docs/specification.md), enabling us to ensure compatibility across the existing Kube-DNS implementation and our new one in CoreDNS. Version 1.0.0 of this specification mostly follows the current behavior of Kube-DNS.</description>
    </item>
    
    <item>
      <title>How to Add Plugins to CoreDNS</title>
      <link>https://coredns.io/2017/03/01/how-to-add-plugins-to-coredns/</link>
      <pubDate>Wed, 01 Mar 2017 20:23:48 +0000</pubDate>
      
      <guid>https://coredns.io/2017/03/01/how-to-add-plugins-to-coredns/</guid>
      <description>CoreDNS is a DNS server that chains plugins. A plugin is defined as a method: ServeDNS() that gets a request and either responds to the client or passes it on to the next plugin. If none of the plugins handle the request a default response of SERVFAIL is returned.
This blog post details how to add a plugin to CoreDNS. We&amp;rsquo;re using the example of the whoami plugin which is a CoreDNS plugin and loaded by default if no Corefile is specified.</description>
    </item>
    
    <item>
      <title>History of CoreDNS in four posts.</title>
      <link>https://coredns.io/2017/02/23/history-of-coredns-in-four-posts./</link>
      <pubDate>Thu, 23 Feb 2017 18:12:12 +0000</pubDate>
      
      <guid>https://coredns.io/2017/02/23/history-of-coredns-in-four-posts./</guid>
      <description>Yes, at some point CoreDNS was actually a forked webserver doing DNS.
This blog posts detail some of the early history of CoreDNS.
Pondering if I should create someting ala Caddy, but then for DNS. I didn&amp;rsquo;t have a name, so it was &amp;ldquo;Caddy DNS&amp;rdquo; (or Daddy as some point): https://miek.nl/2016/march/10/caddy-dns/.
This idea was good enough that I actually tried it out, resulting in the first queries answered by &amp;ldquo;Caddy DNS&amp;rdquo;: https://miek.</description>
    </item>
    
    <item>
      <title>CoreDNS-006 Release</title>
      <link>https://coredns.io/2017/02/22/coredns-006-release/</link>
      <pubDate>Wed, 22 Feb 2017 21:26:11 +0000</pubDate>
      
      <guid>https://coredns.io/2017/02/22/coredns-006-release/</guid>
      <description>CoreDNS-006 has been released!
CoreDNS is a DNS server that chains plugins, where each plugin implements a DNS feature.
What is New Core Move CoreDNS to https://github.com/coredns/coredns together with several other repos. This will be the new home for CoreDNS development.
Fixed:
Fix hot-reloading. This would fail with [ERROR] SIGUSR1: listen tcp :53: bind: address already in use. Allow removal of core plugin, see comments in plugin.cfg. Plugin improvements New reverse plugin: allows CoreDNS to respond dynamically to an PTR request and the related A/AAAA request.</description>
    </item>
    
    <item>
      <title>CoreDNS-005 Release</title>
      <link>https://coredns.io/2017/02/09/coredns-005-release/</link>
      <pubDate>Thu, 09 Feb 2017 18:50:31 +0000</pubDate>
      
      <guid>https://coredns.io/2017/02/09/coredns-005-release/</guid>
      <description>CoreDNS-005 has been released!
CoreDNS is a DNS server that chains plugins, where each plugin implements a DNS feature.
What is New Core A way to configure (external) plugin was added. Edit plugin.cfg and do a go generate &amp;amp;&amp;amp; go build and your plugin has been added. This allows for out-of-tree plugin to be easily added. Documentation can be found in plugin.cfg.
Plugin improvements New erratic: a new plugin that can drop queries, limited in the current functionality, but useful for testing.</description>
    </item>
    
    <item>
      <title>CoreDNS-004 Release</title>
      <link>https://coredns.io/2017/01/01/coredns-004-release/</link>
      <pubDate>Sun, 01 Jan 2017 10:30:31 +0000</pubDate>
      
      <guid>https://coredns.io/2017/01/01/coredns-004-release/</guid>
      <description>CoreDNS-004 has been released!
CoreDNS is a DNS server that chains plugins, where each plugin implements a DNS feature.
What is New Core We are now also releasing an ARM build that can run on Raspberry Pi.
Plugin improvements file|auto: resolve external CNAME when an upstream (new option) is specified. file|auto: allow port numbers for transfer from/to to be specified. file|auto: include zone&amp;rsquo;s NSset in positive responses. auto: close files and don&amp;rsquo;t leak file descriptors.</description>
    </item>
    
    <item>
      <title>Writing Plugins for CoreDNS</title>
      <link>https://coredns.io/2016/12/19/writing-plugins-for-coredns/</link>
      <pubDate>Mon, 19 Dec 2016 08:00:24 +0000</pubDate>
      
      <guid>https://coredns.io/2016/12/19/writing-plugins-for-coredns/</guid>
      <description>A plugin adds functionality to CoreDNS, i.e. caching, metrics and basic zone file serving are all plugins.
If you want to write a new plugin and want it to be included by default, i.e. merged in the code base please open an issue first to discuss initial design and other things that may come up. Starting with a README file to explain how things work from a user perspective is usually a good idea.</description>
    </item>
    
    <item>
      <title>DNS over HTTPS</title>
      <link>https://coredns.io/2016/11/26/dns-over-https/</link>
      <pubDate>Sat, 26 Nov 2016 17:22:44 +0000</pubDate>
      
      <guid>https://coredns.io/2016/11/26/dns-over-https/</guid>
      <description>Note this requires the proxy plugin which has been deprecated.
Since almost a year Google has a DNS service that can be queried over HTTPS: https://dns.google.com. This means your queries are encrypted and can only be seen by you (and Google(!)). Seeing all the press about the UK&amp;rsquo;s snooper&amp;rsquo;s charter I though I should implement this as a plugin in CoreDNS.
I&amp;rsquo;m (obviously) going to use this myself; which is perfect as it protects me and it allows me to dog food CoreDNS as a DNS proxy in my home network.</description>
    </item>
    
    <item>
      <title>CoreDNS-003 Release</title>
      <link>https://coredns.io/2016/11/11/coredns-003-release/</link>
      <pubDate>Fri, 11 Nov 2016 16:38:32 +0000</pubDate>
      
      <guid>https://coredns.io/2016/11/11/coredns-003-release/</guid>
      <description>CoreDNS-003 has been released!
CoreDNS is a DNS server that chains plugins, where each plugin implements a DNS feature.
What is New Core Refused queries are properly logged and exported if metrics are enabled.
Plugin improvements proxy: allow /etc/resolv.conf to be used in the configuration. metrics: add tests and normalize some of the metrics. Removed the AXFR size metrics. cache: Added size and capacity of the cache (for both denial and success cache types).</description>
    </item>
    
    <item>
      <title>CoreDNS for Kubernetes Service Discovery</title>
      <link>https://coredns.io/2016/11/08/coredns-for-kubernetes-service-discovery/</link>
      <pubDate>Tue, 08 Nov 2016 07:33:08 +0000</pubDate>
      
      <guid>https://coredns.io/2016/11/08/coredns-for-kubernetes-service-discovery/</guid>
      <description>Infoblox&amp;rsquo;s John Belamaric has published a blog post on how to use CoreDNS instead of kube-dns in Kubernetes.
A little excerpt:
Kubernetes includes a DNS server, Kube-DNS, for use in service discovery. This DNS server utilizes the libraries from SkyDNS to serve DNS requests for Kubernetes pods and services. The author of SkyDNS2, Miek Gieben, has a new DNS server, CoreDNS, that is built with a more modular, extensible framework. Infoblox has been working with Miek to adapt this DNS server as an alternative to Kube-DNS.</description>
    </item>
    
    <item>
      <title>Quick Start for Windows</title>
      <link>https://coredns.io/2016/10/30/quick-start-for-windows/</link>
      <pubDate>Sun, 30 Oct 2016 00:00:00 +0000</pubDate>
      
      <guid>https://coredns.io/2016/10/30/quick-start-for-windows/</guid>
      <description>This is a development quick start guide when you are using Windows.
Make sure that you have your GOPATH set up
Clone coredns and all dependencies: go get github.com/coredns/coredns
Navigate to the source: cd $ENV:GOPATH\src\github.com\coredns\coredns
Fork (but not clone) coredns
Update the origin to point at your repository: git remote set-url origin https://github.com/USERNAME/coredns.git
Open your editor: code .
Create a new file named Corefile and populate it:
# Only port 53 is supported as NSLOOKUP no longer supports non-standard ports .</description>
    </item>
    
    <item>
      <title>CoreDNS-002 Release</title>
      <link>https://coredns.io/2016/10/19/coredns-002-release/</link>
      <pubDate>Wed, 19 Oct 2016 19:09:32 +0000</pubDate>
      
      <guid>https://coredns.io/2016/10/19/coredns-002-release/</guid>
      <description>CoreDNS-002 has been released!
CoreDNS is a DNS server that chains plugins, where each plugin implements a DNS feature.
What is New -port was renamed to -dns.port to avoid clashing with Caddy&amp;rsquo;s -port (which was renamed to http.port). Lumberjack logger was removed, this means no built in log rotation; use an external tool for that. Brushed up GoDoc for all packages. Brushed up all READMEs to be more standard and look like manual page.</description>
    </item>
    
    <item>
      <title>Query Routing</title>
      <link>https://coredns.io/2016/10/13/query-routing/</link>
      <pubDate>Thu, 13 Oct 2016 08:50:13 +0000</pubDate>
      
      <guid>https://coredns.io/2016/10/13/query-routing/</guid>
      <description>Quiz time, in the following Corefile:
. { proxy . 8.8.8.8:53 file db.example.com } Will a query for www.google.com be handled by the proxy or the file plugin? Answer below.
What does this Corefile actually say? It specifies that queries for root (.) and everything below it (so for all domain names) we should enter this stanza.
Next all queries should be forwarded to 8.8.8.8:53.
Then because the file plugin does not specify what zones should be answered from the db.</description>
    </item>
    
    <item>
      <title>CoreDNS and Caddy</title>
      <link>https://coredns.io/2016/09/29/coredns-and-caddy/</link>
      <pubDate>Thu, 29 Sep 2016 06:18:40 +0000</pubDate>
      
      <guid>https://coredns.io/2016/09/29/coredns-and-caddy/</guid>
      <description>Caddy 0.9.3 is released. On it&amp;rsquo;s download page you can now select the &amp;ldquo;DNS plugin&amp;rdquo; to be added to Caddy! This is really nice and a culmination of all the work that has been put in to make this happen.
Note that if you select this option you get a binary that is both a DNS and webserver, during startup you can select between the two with -type=dns|http flag.
The CoreDNS developers will still provide their own (DNS only) binaries over at GitHub.</description>
    </item>
    
    <item>
      <title>CoreDNS-001 Release</title>
      <link>https://coredns.io/2016/09/18/coredns-001-release/</link>
      <pubDate>Sun, 18 Sep 2016 11:40:37 +0100</pubDate>
      
      <guid>https://coredns.io/2016/09/18/coredns-001-release/</guid>
      <description>CoreDNS-001 has been released. This is the first release! It provides a complete DNS server, that also does DNSSEC and is useful for service discovery in cloud setups.
What is CoreDNS? CoreDNS is a DNS server that started its life as a fork of the Caddy web(!)server.
It chains plugin, where each plugin implements some DNS feature. CoreDNS is a complete replacement (with more features, and maybe less bugs) for SkyDNS.</description>
    </item>
    
  </channel>
</rss>
