I have changed the primary domain on my account from madebypens.com to madebyvapes.com and I am now trying to forward madebypens to madebyvapes via the interface in godaddy. The issue I am having is that the browser appears to be blocking requests to madebypens from forwarding to madebyvapes due to an ssl issue. I am guessing the old ssl cert is still active on madebypens but with the DNS info being different, it is now being blocked. In the short term I have added madebypens back to Netlify as an alias but this isn’t ideal as it’s not the forwarding behaviour that is desired.
who is the DNS for both sites, is it netlify or is it godaddy?
The DNS is managed via godaddy but the “A” records point to the IP provided by netlify in the domain settings. Ideally I would park the madebypens domain at godaddy and forward it via the godaddy ui but that was how I had it when I was getting the ssl issue.
I do see, though, that www.madebypens.com is not included in the SSL certificate. Have you tried adding www.madebypens.com as a domain alias here: https://app.netlify.com/sites/madebypens/settings/domain#custom-domains? You will also need to make a DNS record on the GoDaddy side pointing that subdomain to your Netlify URL: madebypens.netlify.app.
Note that for the best site performance, we recommend that the www. address is your primary domain, with the apex automatically redirecting to that. Here’s an article about why:
So our recommendation for the setup here would be:
- A record from madebyvapes.com to 184.108.40.206
- CNAME record from www.madebyvapes.com to madebypens.netlify.app
- A record from madebypens.com to 220.127.116.11
- CNAME record from www.madebypens.com to madebypens.netlify.app
- www.madebyvapes.com is primary
- madebyvapes.com automatically redirects to www.
- www.madebypens.com and madebypens.com are domain aliases
Let us know if that helps or if you have additional questions!