Required data blank when connecting domain

Site URL: https://milesingram.co.uk

I am trying to connect a domain, I own with 123-reg.co.uk, to a site I am creating. I have connected all the DNS entries except the last one as the required data section is blank, as shown in the screenshot. What do I do? Many thanks 

On 2/7/2022 at 10:17 PM, Ming997 said:

I am trying to connect a domain, I own with 123-reg.co.uk

In your 123-reg DNS panel, delete the 'A' record for "35.227.197.36". 

Thank you very much Paul2009 that seems to have worked.

Additionally when I connect to my site it says it is insecure the SSL certificate status is still processing do you know if there is anything I can do to ensure it will work so people can access the site?

kind regards and many thanks,

Miles 

The site appears to be protected by a public password at the moment, but if visitors go to http://milesingram.co.uk (without the 's' in the prefix) they should connect without an error.

Once the certificate has finished processing, the https version should work too. There's nothing you can do to speed this up.

Okay, thank you again

Hello I have the same problem, however, I cannot delete the A record that is being shown because I actually don't have that specific record. What should I do? Im trying to connect with namecheap

1 hour ago, PoeticDesigners said:

I cannot delete the A record that is being shown because I actually don't have that specific record.

I recommend you take another look at your Namecheap DNS records because I can still see the A record 162.255.119.187.

Hi Paul, 

Here is a screenshot of my Namecheap DNS records and I don't see the A record 162.255.119.187.

What should I do if I don't see it on NameCheap?

Can you explain why you have the unmasked redirect? I wouldn't expect to see that.

On 7/15/2022 at 12:43 PM, paul2009 said:

Can you explain why you have the unmasked redirect? I wouldn't expect to see that.

I noticed those but they were always there so I just left them. I just deleted them and it worked! Thanks for your help! 

Hi Paul

I'm having the same problem as Ming 

I've deleted the record in 123 reg DNS management  but it still shows up on the SS  end. I appreciate I have to wait 72 hours for the transfer but dont want to wait only to find out that I missed something and have to correct it and wait again. Its also saying its not a secure connection even when I remove the https - any ideas?

 ERR_SSL_VERSION_OR_CIPHER_MISMATCH

Or do I just wait and see?

My URL is https://www.lasting-legacy.co.uk/

Many thanks in advance

Matt

49 minutes ago, LL_Matt said:

I've deleted the record in 123 reg DNS management  but it still shows up on the SS  end...do I just wait and see?

You can ignore the red A record as I can see it was deleted. Propagation can just take a little while but it should resolve itself soon. If everything isn't correct after 72 hours, that's the time to reach out to support.

Hi Paul,

Identical error. I did what you suggested above and deleted that row on domain.com. So far, it's been an hour and on refreshing on squarespace, it shows the same red numbers. See screenshot.

2 hours ago, Rah2023 said:

Hi Paul,

Identical error.

You forgot to tell me your domain name 🙂

Blpctherapy.com

square space now shows all green - connected apparently

I made the site public and clicked on it and it worked! Now just waiting for SSL certificate and then will make it go public

Hi Paul, I have an identical error on my client's website nhlifesciences.org. Two random A entries in red on Squarespace's end, but I don't see the entries in GoDaddy. However, I do see a lot of other entries that I am unsure of. 

3 minutes ago, k10designer said:

I have an identical error on my client's website nhlifesciences.org.

See this thread - same issue 🙂

Thank you so much! I still see the 2 entries in there but I assume it will take time to adjust on the back end.

25 minutes ago, k10designer said:

I assume it will take time to adjust on the back end.

Yes. It will take time for the updates to DNS records to take effect across all servers on the internet. Changes don’t take effect instantaneously because nameservers store domain record information in their cache for a certain amount of time before refreshing. There’s no set amount of time for propagation, but it typically take a few hours (up to 72 hours on occasion).