大网数据广告活动
网站运营与故障问答

Trouble activating free SSL from Domain.com when using Hostinger as a web host

· 52CE 我爱测

Recently, I transfered my domain from GoDaddy to Domain.com. My hosting is still provide by Hostinger.com. Domain.com have an option of Free SSL . You just enabled it to get SSL Certificate and you don't have pay for it. To enabl…

问题原文

原帖链接 · Ömürcan Cengiz · CC BY-SA 4.0

Recently, I transfered my domain from GoDaddy to Domain.com. My hosting is still provide by Hostinger.com. Domain.com have an option of Free SSL. You just enabled it to get SSL Certificate and you don't have pay for it. To enable it, my nameservers should point to ns1.domain.com and ns2.domain.com along with my A Record (which I don't know what that is).

On domain.com, my nameservers are like (I had ns1-2.hostinger.com but I deleted them)

ns1.domain.com
ns2.domain.com
ns3.hostinger.com
ns4.hostinger.com

and my DNS Record have @ and ftp A records along with hostinger IP's. But now, I can't reach out my site :D It says This site is under development on the title with blank page. I tried to change many nameserver and A record both on domain.com and hostinger.com.

Even if I can access to my website, I couldn't get SSL Certificate. How can I get that?

已采纳解答

原帖链接 · Stephen Ostermiller · CC BY-SA 4.0

You use NS records to connect your domain name registrar to your DNS host. You use A and CNAME records to at your DNS host to connect your domain name to the IP address of your web host.

You could have:

Domain.com -> NS ns1.hostinger.com -> A 1.1.1.1

Or you could have:

Domain.com -> NS ns1.domain.com -> A 1.1.1.1

In this case both your domain registrar and your web host offer DNS hosting services. You can choose to use either.

According to domain.com documentation their free security certificates are based on Let's Encrypt. Lets encrypt works like:

  1. You run the Lets Encrypt client to secure a domain name
  2. The client contacts Lets Encrypt servers and requests a security certificate
  3. The Lets Encrypt server asks for verification that you control the domain. It gives you a token to publish. There are variants for publishing it in a known location on your site, or in your DNS records.
  4. The Lets Encrypt client puts the token in place and lets the server know.
  5. The Lets Encrypt server verifies that the token has been publicly published and issues a security certificate for the domain
  6. The Lets Encrypt client installs the certificate in your web server.

Because domain.com is not your web host, that last step is not going to be automatic. That is a problem because the Lets Encrypt certificates expire every three months. Any process that requires manual steps is going to a burden and will likely get neglected at some point.

Hostinger will let you install a certificate from Lets Encrypt on their servers and you might even be able to automate the process, but it sounds like a bit of scripting to make it happen.

All this is to say that getting a security certificate for your domain is not as easy with your setup as you were hoping. It sounds like if you were hosting with domain.com, they could install and update the certificate for you. However, with third party hosting it is going to be much harder. It is certainly not going to work to just point DNS to domain.com.

Hostinger has a $12 "cheap lifetime SSL" option. My guess is that is just an up-front fee for having them set up LetsEncrypt for you and keep the certificate updated. Many web hosting companies will do the work of installing and updated LetsEncrypt certificates as part of your hosting plan. $12 isn't an unreasonable fee, but it something that is more usually included in hosting plans in my experience.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Webmasters Stack Exchange
适用范围
以原帖系统、软件版本与发布日期为准(2019-10-27)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 4.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。