<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>unbound on CoreDNS: DNS and Service Discovery</title>
    <link>https://coredns.io/tags/unbound/</link>
    <description>Recent content in unbound on CoreDNS: DNS and Service Discovery</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>CoreDNS - All Rights Reserved</copyright>
    <lastBuildDate>Thu, 25 Jan 2018 11:25:00 +0000</lastBuildDate><atom:link href="https://coredns.io/tags/unbound/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>unbound</title>
      <link>https://coredns.io/explugins/unbound/</link>
      <pubDate>Thu, 25 Jan 2018 11:25:00 +0000</pubDate>
      
      <guid>https://coredns.io/explugins/unbound/</guid>
      <description>Description Via unbound you can perform recursive queries. Unbound uses DNSSEC by default when resolving and it returns those records (DNSKEY, RRSIG, NSEC and NSEC3) back to the clients. The unbound plugin will remove those records when a client didn&amp;rsquo;t ask for it. The internal (RR) answer cache of Unbound is disabled, so you may want to use the cache plugin.
Libunbound can be configured via (a subset of) options, currently the following are set, by default:</description>
    </item>
    
  </channel>
</rss>
