Mailing-List: contact users-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cloudstack.apache.org
Received-SPF: pass (athena.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
MIME-Version: 1.0
Date: Wed, 21 May 2014 21:14:38 -0400
Message-ID: 
 <CAF1jPWc0ic2bU-ZbMrnjchTJc1Kxoh_Zdak37O0CuuzRRL2-kA@mail.gmail.com>
Subject: Proxy Console (RealhostIP Retired) Question
From: Mo <mo@daoenix.com>
To: users@cloudstack.apache.org, dev <dev@cloudstack.apache.org>
Content-Type: multipart/alternative; boundary=047d7bd6aea242cdcd04f9f2d62b

--047d7bd6aea242cdcd04f9f2d62b
Content-Type: text/plain; charset=UTF-8

Hello:

I am attempting to find more information (read: step by step) how to
correct the issue that came to be when realhostip was retired.

The links I saw suggested I setup the following for every IP address in my
DNS Zone:

192-168-1-1.cloud.domain.tld        IN    A    192.168.1.1

I have done that for ALL my IPs. Restarted my named/bind service. Not only
am I not obtaining an A record with this configuration, but I am also still
unable to proceed in getting console access as it states it's unable to
resolve the DNS.

All my other DNS resolves without issue, please note; 192.x is just an IP
address I tossed in this e-mail for general purposes, I am utilizing public
subnets.

I have also purchased an SSL certificate went through all of that too, if
someone could point me in the right direction or perhaps offer ideas
(alternates) that would be fantastic.

Thanks,
Mo

--047d7bd6aea242cdcd04f9f2d62b--