<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>sign on CoreDNS: DNS and Service Discovery</title>
    <link>https://coredns.io/tags/sign/</link>
    <description>Recent content in sign on CoreDNS: DNS and Service Discovery</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>CoreDNS - All Rights Reserved</copyright>
    <lastBuildDate>Mon, 15 Mar 2021 14:42:29 +0000</lastBuildDate><atom:link href="https://coredns.io/tags/sign/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>sign</title>
      <link>https://coredns.io/plugins/sign/</link>
      <pubDate>Mon, 15 Mar 2021 14:42:29 +0000</pubDate>
      
      <guid>https://coredns.io/plugins/sign/</guid>
      <description>Description The sign plugin is used to sign (see RFC 6781) zones. In this process DNSSEC resource records are added. The signatures that sign the resource records sets have an expiration date, this means the signing process must be repeated before this expiration data is reached. Otherwise the zone&amp;rsquo;s data will go BAD (RFC 4035, Section 5.5). The sign plugin takes care of this.
Only NSEC is supported, sign does not support NSEC3.</description>
    </item>
    
  </channel>
</rss>
