Re: Query about new bind install and it's chatty log
Ted Mittelstaedt <[email protected]> Tue, 24 Mar 2026 02:06:53 -0700
| Newsgroups | gmane.network.dns.bind9.user |
|---|---|
| Message-ID | <80f52747-4781-47a9-bba5-743db5a7b5f3__17897.4075404525$1774343236$gmane$org@ipinc.net> |
On 3/21/26 2:49 PM, Nick Tait via bind-users wrote: > > Your theory sounds entirely plausible. Are you aware of the "forward" > option > (https://bind9.readthedocs.io/en/latest/reference.html#namedconf-statement-forward)?: > > *Grammar: *|forward ( first | only );| > > *Blocks: *options, template, view, zone (forward, primary, > secondary, static-stub, stub) > > *Tags: *query > > Allows or disallows fallback to recursion if forwarding has > failed; it is always used in conjunction with the |forwarders| > <https://bind9.readthedocs.io/en/latest/reference.html#namedconf-statement-forwarders> > statement. > > This option is only meaningful if the |forwarders| > <https://bind9.readthedocs.io/en/latest/reference.html#namedconf-statement-forwarders> > list is not empty. A value of |first| is the default and causes > the server to query the forwarders first; if that does not answer > the question, the server then looks for the answer itself. If > |only| is specified, the server only queries the forwarders. > > i.e. If you wanted to stop BIND from making the 'last ditch effort', > you could try setting the forward option to "only". > > Thanks, I tried that and it seems to have quieted down the log spamming. The real fix is to get this DNS interference turned off, of course. Ted -- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list.