Actually, the above is untrue: typing “https://lsst.org” gets me a warning about a bad certificate. http://lsst.org/ works, though.

Frossie Economou- I am assuming you are the keep of DNS records for vro.org. If you are, can you check there is an A record for vro.org pointing to the same IP as www.vro.org? I cannot resolve vro.org.

John Swinbank- want to give it a vro.org noting the DNS issue.

John Swinbank- I saw you checked the other ticket. This one OK for you as well?

Hi Ian — I can't resolve vro.org, so I can't tell if it redirects to anywhere interesting.

Right. I forgot about my request to Frossie Economou about a need for a record to resolve the address.

Frossie Economou Ranpal Gill- Unless I am missing an obvious apache rewrite solution, I cannot take any action to fulfill the original request to make https://vro.org nor its unsecured variant http://vro.org work.

I can make the necessary changes if I have access to the domain admin portal. Assigning to Frossie Economou

Frossie Economou Ranpal Gill- I am not sure who really owns this issue. IT cannot make any changes since this seems to be a DNS A Record entry request. Whomever has access to the registrar's account and/or the DNS records needs to make this change. Converting this to a COMM Ticket.

Jonathan Sick is also a ticket that you can help out with?

SQuaRE operates the DNS that vro.org is associated with. We're looking into it.

I've set up an A record (ALIAS) for vro.org whose alias target is www.vro.org. This works, from my testing.

It seems that the weakness of this approach is that there's a certificate mismatch when doing this type of DNS redirect. Current browsers tolerate it, though. I'll ask the SQuaRE team about best practices here.

mismatch issue is resolved. The base URL of the OS was using its own self-assigned.

I have closed the ticket w/o realizing.

Still seeing the mismatch issue here —

$ date && wget https://vro.org/

Mon Jun 22 11:14:02 PDT 2020

--2020-06-22 11:14:02--  https://vro.org/

Resolving vro.org (vro.org)... 140.252.201.22

Connecting to vro.org (vro.org)|140.252.201.22|:443... connected.

The certificate's owner does not match hostname ‘vro.org’

I had to revert since it broke something else. I hadn't gotten the comment in. Figuring out the proper setup.

I think I need to deploy an Nginx server to terminate TLS and do the redirect.

I haven't done this because it hasn't bubbled up in my priority list, but let me know if this is important.

Or should I reassign the ticket?