Hey, this is actually a fix to domain redirection issue. I faced this problem, but managed to solve it with a simple trick. I thought maybe it can help many others who haven't received exact answer from Support team.
Solved! Go to Solution.
This is a common issue, though I'll note the third section of the article isn't actually needed. It creates yourdomain.com.yourdomain.com which I guess doesn't hurt anything, but it doesn't really help either.
If the host allows pointing to an IP address and handles the redirect on their end that would be the better option (which Google does in this situation, covered in the first 2 sections of the article). In other situations where the host does not provide an IP address you may need to use domain forwarding, instead of sub-domain forwarding.
I tried implementing Domain forwarding earlier, but I got following error on address resolve. Maybe I need to add SSL Certificate, again I'm in blogger and Google handles that, right?
PS: The page is loading fine with domain forwarding also.
@TwistBloggcomTo be clear you do not need forwarding at all if the host provides IP addresses to point the domain. That is an alternate method for working with a host that does not provide the IP address, both methods should not be used at once as the settings conflict.
When I do not use Domain Forwarding, there was an issue -- the naked domain with https (https://twistblogg.com) was showing Certificate error. It never happened with me before with other domains. Its not me alone, there are many bloggers out there facing it.
@TwistBloggcom Forwarding does not use SSL, so if someone tries to access a forwarded domain using https:// the browser would block it.
If you have multiple records for the same address one would be selected randomly each time, so some of your visitors would get one of the Google IP addresses and others would get the GoDaddy forwarding server. If you are getting a valid SSL it is likely using one of the Google IP addresses, there's about 1/5 chance of getting forwarding instead...
I will say it takes some time for these changes to take effect (usually an hour or two, but can take up to 48 hours). It's really not uncommon for someone to do all the steps right, get worried and try a bunch of random other stuff, then when the right settings kick in become convinced it was from one of the random other things.
OK ! I got the probability thing, but my domain was connected to Blogger a month ago and there was no fix till today (except forwarding option), so now my question is: what should I do? What is the fix to this issue? What steps should I follow?
I ran the domain thru an SSL checker that tests each IP address individually, the top one is the forwarding server.
So removing forwarding should solve the issue, as it does not use SSL.
It is possible there may have previously been some issue with the DNS records for Google, that could have been fixed when they were deleted and you added them again.
Thanks Nate. I removed Domain forwarding and still the page without www (https://twistblogg.com) is loading successfully. Maybe it was problem from server side (Google) and as you mentioned removing and adding A records might have fixed the error. Thanks a lot, I learnt a lot of new stuffs and thanks again for providing your time. Can you confirm once if everything is fine?
I'll update the article once confirmation is done !