unbound needs to have cache-max-negative-ttl parameter for adjustment of the maximum TTL specifically for caching negative DNS responses

Solution Unverified - Updated -

Issue

  • unbound doesn't have cache-max-negative-ttl parameter, and the maximum TTL specifically for caching negative DNS responses can not be adjusted.
  • Previously, this limit was determined by the domain SOA record, or it was automatically the same as the maximum TTL limit for caching all DNS responses, if configured.

Environment

Red Hat Enterprise Linux 7

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content