<div dir="ltr"><div>Thank you, Martin. '--allow-zone-overlap' may indeed fix one of the challenges. I will give it a try.<br><br></div>Another check that is not a blocker but undesirable is the reverse zone lookup. The installer does a check and some turkey upstream of my infrastructure has a zone for 192.168.101.0 in a public DNS hosts. Bizarre! Not exactly a blocker for I assume I can add it after the installation.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Sep 12, 2016 at 1:41 AM, Martin Basti <span dir="ltr"><<a href="mailto:mbasti@redhat.com" target="_blank">mbasti@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><span class="">
<p><br>
</p>
<br>
<div>On 11.09.2016 20:15, Richard Harmonson
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>Is there an option to disable the various DNS checks using
ipa-server-install with FreeIPA 4.3.2? Is there plans to do
provide the option in future releases? Reviewing the
ipa-server-install man page, I am not seeing it.<br>
<br>
I want to compliment the team for placing safeguards on the
installation of FreeIPA in respect to DNS best practices. I
get the need to help some of the installers that may not have
a strong grasp of DNS. However, there are scenarios where the
checks becomes installation blockers or result in undesirable
results. I am not trying to be mysterious, but I have no
desire to embarrass third parties on their DNS faux pas. Thank
you.<br>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
</blockquote>
<br></span>
Hello, which check exactly do you mean?<br>
<br>
For zone overlap there is --allow-zone-overlap option. This was
added in 4.3<span class="HOEnZb"><font color="#888888"><br>
<br>
Martin<br>
</font></span></div>
</blockquote></div><br></div>