Hi, I have a domain achimo.in on godaddy . It is forwarded (with masking) to https://achimo.mybluemix.net. However, https://achimo.in is showing insecure even after buying and installing a certificate from GoDaddy. I read several past answers and also tried to check with the tools mentioned- but am lost here.
Further, forwarding on http://achimo.in is not honoring the 'forwarding with masking' directive.
Any insights into how to make it work shall be appreciated.
Solved! Go to Solution.
Don't use masking. Check with your website provider if they allow you to point your domain, generally with an IP address (manage DNS at GoDaddy) or namservers (the other provider manages DNS).
Thanks for your response. Need a bit more clarification.
If we don't use forwarding with masking, the original custom URL gets mapped to hosting provider's URL which is not desirable.
Could you please elaborate on the solution you shared. I could not understand it well. Specifically, could not understand the split between managing DNS at GoDaddy and nameserver at what ?
Pls elaborate. Thanks !
Ideally you do want your domain mapped to where the website resides (or in other words the website is actually on your domain). Right now your website is on a different domain and your own domain is redirecting to it. Masking is an outdated browser trick which just gives the illusion, but it relies on obsolete code to work and should be avoided.
The DNS holds the settings on where to direct web traffic, email, etc. With the default nameservers the DNS is managed at GoDaddy or if you use the nameservers of another provider the DNS would be managed with them.
Here is a video on working with domains at IBM Bluemix.
It seems they want you to use a CNAME, which gives the benefit that they can manage the routing on their end but the drawback that it applies to a sub-domain. As a workaround you could use www as the sub-domain, then forward yourdomain.com to www.yourdomain.com (301 redirect, no masking).