It is with the hostname requirements. AWS EC2 normally gives you a dynamic IP address, which then you can update DNS records with. The reverse lookup on the IP is still the aws IP address in a text form, not the proper reverse. The documentation says:<div>
<br></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div><span style="font-family:'liberation sans','Myriad ','Bitstream Vera Sans','Lucida Grande','Luxi Sans','Trebuchet MS',helvetica,verdana,arial,sans-serif;font-size:12px;line-height:15px;background-color:rgb(255,255,255)">The reverse of the address that the hostname resolves to must match the hostname.</span> </div>
<div><br></div></blockquote>Now I can get a nailed up elastic IP address which does not change, and if I put in a request I can get the reverse IP to map. The problem with that is there is a finite number of elastic IP addresses you can request - 5 - without begging for more. I'd rather not use them up.<div>
<br></div><div>Can I get around this issue if I have my own DNS server running on the same machine?<br><div><br><div class="gmail_quote">On Thu, Jan 12, 2012 at 12:46 PM, Simo Sorce <span dir="ltr"><<a href="mailto:simo@redhat.com">simo@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 class="im">On Thu, 2012-01-12 at 10:28 -0600, Jeff White wrote:<br>
> I'd like to use FreeIPA with Amazon's EC2 virtual machines. I'm<br>
> seeing a number of barriers, mostly around DNS. An elastic IP address<br>
> looks like it would solve the issues, but I'm not sure that will. And<br>
> I'm wondering if there are any more barriers to making it work.<br>
<br>
</div>Can you elaborate on the DNS issues ?<br>
<span class="HOEnZb"><font color="#888888"><br>
Simo.<br>
<br>
--<br>
Simo Sorce * Red Hat, Inc * New York<br>
<br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br><div>Jeff White</div><div>Acesse.com Technical Operations Manager</div><div> </div><br>
</div></div>