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:
The reverse of the address that the hostname resolves to must match the hostname. 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. Can I get around this issue if I have my own DNS server running on the same machine? On Thu, Jan 12, 2012 at 12:46 PM, Simo Sorce <[email protected]> wrote: > On Thu, 2012-01-12 at 10:28 -0600, Jeff White wrote: > > I'd like to use FreeIPA with Amazon's EC2 virtual machines. I'm > > seeing a number of barriers, mostly around DNS. An elastic IP address > > looks like it would solve the issues, but I'm not sure that will. And > > I'm wondering if there are any more barriers to making it work. > > Can you elaborate on the DNS issues ? > > Simo. > > -- > Simo Sorce * Red Hat, Inc * New York > > -- Jeff White Acesse.com Technical Operations Manager
_______________________________________________ Freeipa-users mailing list [email protected] https://www.redhat.com/mailman/listinfo/freeipa-users
