Still searching a solution.
I am advised that I should either clear the HSTS settings or disable HSTS from my web browser.
What are the possible risks with this recommendation?.
Is there an altnative?
I have many website users that are experiencing this problem "Privacy error: Your connection is not private" It would be a massive task to clear the HSTS settings for all users.
Ideas welcome
Please advise
John Thorogood
Hi John,
Currently www.winslowbowlsclub.org is pointing at squarespace, and winslowbowlsclub.org (without the www) is pointing to Voice and squarespace. I dare say this is the cause of the browser confusion!
I suggest if you sort out the DNS entries to point only to the service that you want to use then it'll all work rather more smoothly :-)
I think the HSTS is a symptom rather than the cause of the problem, and that disabling it or clearing the browser cache won't do you any good.
Thanks
Joe
Thank you for the advice
I cannot see a difference between the domain names, whether with or without the www prefix to winslowbowlsclub.org, and therefore unsure what to change or where.
The domain name on the winslowbowlsclub admin page is winslowbowlsclub.org
The domain name on my squarespace account is also winslowbowlsclub.org
Please give further guidance.
The settings for your site domain on Voice are correct. The problem is with the DNS settings on the domain itself.
This is something that is managed at the registrar where you bought the domain. Looks like the domain is registered at squarespace so you'll need to use their DNS admin pages to set the appropriate A records. (and remove the inappropriate ones!)
Details of the records to set are in the custom domain instructions.
Thanks
Joe
I am advised by squarespace that I need to change the DNS record, and add a custom DNS record
Well if they're advising at as well as me then it must be true! :-)
If you want to use a CNAME then you can set it to e-voice.org.uk - since CNAME uses a domain name rather than IP address.
This will work fine with the www subdomain, however you shouldn't use a CNAME on the root domain (i.e., without www), so if you want this to work too then you'll have to use an A record.
For an A record the IP address is 83.136.248.56 - which is in the documentation page that I mentioned previously.
For consistency I'd use an A record for both www as well as the root domain, and then remove any other A records and CNAMEs in use.
Thanks
Joe
Thank you for your advice. I am a long way out of my comfort zone on this and appreciate your patience.
I have removed the sub domain, and focus on the root domain.
Therefore I will use the A record IP address in the domain IP address 83.136.248.56, and emove any other A records and CNAMEs in use.
Thank you for your support. I sincerely hope this will not cause additional problems but resolve the problem.
John Thorogood
Yes - that should do it. Though I would keep an A record with 83.136.248.56 for the www subdomain, as that's pretty much standard and what people will expect to see.
Thanks
Joe