This weekend I plan to update the DNS records to make whimsy.apache.org point to whimsy-vm3 instead of resolving (through the proxy) to whimsy-vm2. Once those changes are live:

1) whimsy2.apache.org can be used to access whimsy-vm2. You will likely get a certificate error as the hostname will not match the certificate.

2) whimsy.apache.org can be used to access whimsy-vm3. Again there will likely be a certificate error initially until I go through and re-request a certificate from letsencrypt. Should I run into problems, I may need to back the DNS changes out until I resolve the problem.

3) whimsy3.apache.org will continue to be able to access whimsy-vm3.

- Sam Ruby

Reply via email to