<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>I should have said, I changed the following parameter to resolve
the issue:<br>
</p>
<p>max-records-per-type 1000;<br>
<br>
--James<br>
</p>
<p><img src="cid:part1.2tr3MMF2.6IM7ylYJ@stegemeyer.net" alt=""></p>
<div class="moz-cite-prefix">On 7/24/24 07:18, James Stegemeyer
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:f87aa2d9-b236-41ce-ac08-e44becaa46b2@stegemeyer.net">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<p>Thanks for the new release, and the hard work you do.<br>
<br>
I recently upgraded from 9.18.24 to 9.18.28 per prompting by
Ubuntu USN-6909-1 to preform a security update. I deployed this
into production after passing some tests when installed in a
lab. After the upgrade, Internal Zones that were hosted by
Windows Active Directory were rejected and caused a production
impact. Under Windows Active Directory, the DC's create a round
robin DNS record at the apex of the zone and the number of
entries approximately match the number of DC's in the domain.
It is not uncommon to have hundreds of DC's in a domain, so
setting a limit of 100 will likely cause a series of unexpected
outages for IT administrators. Because this change restricts
existing functionality, This is a breaking change and as such
should be reserved to a minor release. If this feature was
critical to resolve an issue a provider was having, it should be
shipped with default values of 0 causing it to be effectively
disabled allowing the provider to opt in.</p>
<p><img src="cid:part2.XYTph18C.gmZjmfng@stegemeyer.net" alt=""
class=""></p>
<p>I was able to resolve this issue by adding the following
directive to the affected views:<br>
max-types-per-name 1000;<br>
<br>
--James<br>
</p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
</blockquote>
</body>
</html>