Maintained by: NLnet Labs

New forward zone records only on restart

John (Scott) Crooks
Thu Apr 7 04:53:59 CEST 2016


I don't have it explicitly defined, so it's the default at `neg-cache-size:
1m`. You recommend to set it to `0` and not cache any of the failed queries?

On Wed, Apr 6, 2016 at 2:00 PM, Eduardo Schoedler <listas at esds.com.br>
wrote:

> negative-cache perhaps?
>
> --
> Eduardo Schoedler
>
> 2016-04-06 16:31 GMT-03:00 John (Scott) Crooks via Unbound-users
> <unbound-users at unbound.net>:
> > Greetings,
> >
> > I'm using Unbound as a recursing DNS server in our company office
> > infrastructure. Here is the link to my `unbound.conf` file:
> > https://gist.github.com/sc250024/5874948dceac674df53579c2a13d051d
> >
> > The `forward-zone` entries point to two PowerDNS servers that are
> > authoritative for those domains listed in the configuration. Both
> PowerDNS
> > servers are using a typical MySQL backend, and they are in a Master-Slave
> > configuration.
> >
> > I notice that when I add new records to the authoritative servers,
> Unbound
> > does not successfully resolve these records UNTIL I restart the Unbound
> > daemon. In other words:
> >
> > `dig @10.0.32.6 somenewrecord.infra.company.com` <<-- Works since I'm
> > querying the authoritative server directly
> > `dig somenewrecord.infra.company.com` <<-- Returns a SERVFAIL until I
> > restart the Unbound daemon
> >
> > Is this typical behavior? What am I doing wrong?
> >
> > --
> > Scott Crooks
>



-- 

Scott Crooks | DevOps Engineer

971.266.9761 |

scott.crooks at vacasa.com

vacasa.com

Vacation rentals made easy®
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://unbound.nlnetlabs.nl/pipermail/unbound-users/attachments/20160406/1201232b/attachment.html>