惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

H
Hackread – Cybersecurity News, Data Breaches, AI and More
U
Unit 42
Vercel News
Vercel News
Martin Fowler
Martin Fowler
云风的 BLOG
云风的 BLOG
爱范儿
爱范儿
MongoDB | Blog
MongoDB | Blog
J
Java Code Geeks
F
Fortinet All Blogs
MyScale Blog
MyScale Blog
C
Check Point Blog
N
Netflix TechBlog - Medium
Microsoft Azure Blog
Microsoft Azure Blog
aimingoo的专栏
aimingoo的专栏
博客园_首页
WordPress大学
WordPress大学
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
IT之家
IT之家
Last Week in AI
Last Week in AI
罗磊的独立博客
大猫的无限游戏
大猫的无限游戏
Jina AI
Jina AI
V
Visual Studio Blog
小众软件
小众软件

Release on CoreDNS: DNS and Service Discovery

CoreDNS-1.14.5 Release CoreDNS-1.14.6 Release CoreDNS-1.14.4 Release CoreDNS-1.14.2 Release CoreDNS-1.14.3 Release CoreDNS-1.14.1 Release CoreDNS-1.14.0 Release CoreDNS-1.13.2 Release CoreDNS-1.13.1 Release CoreDNS-1.13.0 Release CoreDNS-1.12.4 Release CoreDNS-1.12.3 Release CoreDNS-1.12.2 Release CoreDNS-1.12.1 Release CoreDNS-1.12.0 Release CoreDNS-1.11.4 Release CoreDNS-1.11.3 Release CoreDNS-1.11.2 Release CoreDNS-1.11.1 Release CoreDNS-1.11.0 Release CoreDNS-1.10.1 Release CoreDNS-1.10.0 Release CoreDNS-1.9.4 Release CoreDNS-1.9.3 Release CoreDNS-1.9.2 Release CoreDNS-1.9.1 Release CoreDNS-1.9.0 Release CoreDNS-1.8.7 Release CoreDNS-1.8.6 Release CoreDNS-1.8.5 Release
CoreDNS-1.1.1 Release
coredns · 2018-03-26 · via Release on CoreDNS: DNS and Service Discovery

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’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:

Chris O’Haver, Mario Kleinsasser, Miek Gieben, Yong Tang.

And of course the people in Cure53. Also special shout out to Mario Kleinsasser for helping to debug the scrubbing issue.

For documentation see our (in progress!) manual. For help and other resources, see our community page.