Query about new bind install and it's chatty log

[Ted Mittelstaedt]

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20260324/4a3f3745/attachment-0001.htm>