Hi all,
Frank van Beek wrote:
Hi all,
This morning we migrated 4 of our websites to a new server. Each of
these websites uses a certificate for https connections. We've got only
one Apache instance running with 4 virtual hosts on 4 different
IP-addresses.
Today we discovered the cause of our problems. Our new hosting provider
had invalid reverse DNS records:
---------
% dig -x xxx.xxx.198.61
<-- snip -->
;; ANSWER SECTION:
61.198.xxx.xxx.in-addr.arpa. 900 IN PTR .
<-- snip -->
---------
After they changed their DNS, all we had to do was restart Apache to
make it function correctly.
With many thanks to ssh on Mac OS X which reported: Nasty PTR record ""
is set up for xxx.xxx.198.61, ignoring.
That's what gave us a clue that it might be reverse DNS related.
Frank.
--
Frank van Beek
WAXTRAPP BV
van Diemenstraat 366
1013CR Amsterdam
The Netherlands
Phone: +31 (0)20 672 2308
Fax: +31 (0)20 672 2488
http://www.waxtrapp.com
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List modssl-users@modssl.org
Automated List Manager [EMAIL PROTECTED]
