<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
On 16-Dec-20 11:37, Tim Daneliuk wrote:<br>
<blockquote type="cite"
cite="mid:%3Ceb1b313d-7344-07ed-62c0-2fb5bf5fbd2c@tundraware.com%3E">
<pre class="moz-quote-pre" wrap="">I ran into a situation yesterday which got me pondering something about bind.
In this case, a single line in a zone file was bad. The devops automation
had inserted a space in the hostname field of a PTR record.
What was interesting was that - at startup - bind absolutely refused
to load the zone file at all. I would have expected it to complain
about the bad record and ignore it, but load the rest of the
good records.
Can someone please explain the rationale or logic for this? Not complaining,
just trying to understand for future reference.
TIA,
Tim
</pre>
</blockquote>
<p>DNS is complicated. The scope of an error in a zonefile is hard
to determine.</p>
<p>To avoid this, your automation should use named-checkzone before
releasing a zone file.</p>
<p>This will perform all the checks that named will when it is
loaded.<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>
</body>
</html>