<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Named has options at the global, view and zone levels. The 9.11
ARM shows allow-update<br>
in the options and zone statements. If it's broken in 9.13 - note
that it is a "Developement Release".<br>
So bugs are expected, and you should raise an issue on bind9-bugs
or on gitlab<br>
(<a class="moz-txt-link-freetext" href="https://gitlab.isc.org/isc-projects/bind9/issues">https://gitlab.isc.org/isc-projects/bind9/issues</a>).<br>
</p>
<p>You can work around your issue by using 'include
"my-common-stuff.conf";'<br>
to simplify your configuration. This is a useful strategy for
things that don't fit<br>
the three-level model.<br>
</p>
<p>If you have large zones, you can speed up load time with
masterfile-format raw or map;<br>
see the "tuning" section of the ARM for more information. <br>
</p>
<p>Parsing configuration data is unlikely to be the dominant factor
in startup, but I'm<br>
sure that the developers would welcome a reproducible test case
that shows otherwise.</p>
<p>You should consider update-policy instead of allow-update; it
provides much better control<br>
and better security.</p>
<p>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">It is really very obvious that this is only done by
ideologists, not technical oriented people.</pre>
</blockquote>
Actually, I've found that the contributors to named are very
technical, practical people.<br>
Sometimes they introduce bugs, or ideas that work in one context
but not another.<br>
They're responsive to criticism & contributions. But
name-calling is generally not an<br>
effective way to get anyone to help you.<br>
</p>
<pre class="moz-signature" cols="72">Timothe Litt
ACM Distinguished Engineer
--------------------------
This communication may not represent the ACM or my employer's views,
if any, on the matters discussed.
</pre>
<div class="moz-cite-prefix">On 17-Mar-19 10:35, Stephan von
Krawczynski wrote:<br>
</div>
<blockquote type="cite"
cite="mid:%3C20190317153541.45073d33@ithnet.com%3E">
<pre class="moz-quote-pre" wrap="">On Sun, 17 Mar 2019 12:40:35 +0100
Reindl Harald <a class="moz-txt-link-rfc2396E" href="mailto:h.reindl@thelounge.net"><h.reindl@thelounge.net></a> wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Am 17.03.19 um 12:13 schrieb Stephan von Krawczynski:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">So why is it, that there is no global way of defining default zone
definitions which are only overriden by the actual zone definition?
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
maybe because it brings a ton of troubles and whoever deals with more
than 5 zones has automatic config management in place anyways?
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
If you don't want to follow the positive way (how about a nice additional
feature), then please accept the negative way: someone broke the config
semantics by implementing a zone based-only "allow update". This option worked
globally before (too), so we can assume it is in fact broken now.
Can someone please point me to the discussion about this incompatible change?
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Why is there no way to define a hosts-type-of-file with an URL-to-IP list?
Do you really want people to define 50.000 zones to perform adblocking?
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
no, just use the right tool for the task, this don't fit into the domain
concept of named and hence you have dnsmasq and rbldnsd to step into
that niche
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
In todays' internet this is no niche any more. And the right tool means mostly
"yet-another-host" because you then need at least a cascade of two, one for
dnsmasq and one for bind/named. A lot of overhead for quite a simple task...
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Configs have to be reloaded every now and then, is there really no idea
how to shorten things a bit?
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
??
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
Shorter config = shorter load time. The semantic change of "allow update" alone
leaves every setup with 1000 domains in a situation where 999 config statments
more have to be read, interpreted and configured - just to end up in the same
runtime setup. It is really very obvious that this is only done by
ideologists, not technical oriented people.
</pre>
</blockquote>
</body>
</html>