On Fri, May 20, 2011 at 6:36 AM, Naveen Surisetty <naveenmai...@gmail.com>wrote:

> But when i upgraded to apache2.2
>
> there is no change in client. http://www.xyz.com in working fine but
> https://www.xyz.com (SSL) is not resolving the server IP.
>

That is not a DNS issue. There is no difference between resolving names for
HTTP and HTTPS.
You have a configuration problem.

Check the output of running `apache2ctl -S` on your server.
This command lists all virtual hosts that are configured in Apache.
You can post it here if you don't understand it.

- Yehuda

Reply via email to