DNSSEC DNS Records

I own a domain on hostinger but am wanting to use Cloudflare DNSSEC, I have changed the nameservers on hostinger to be my Cloudflare namservers but now can not update the DNS Records. When I try to do this it tells me to change the NS back. I can update the DNS on Cloudflare but I cant add the DS record as cloudflare wants me to do it on the registrars end.

The DS entry needs to be configured with the registrar. You need to clarify this with your registrar and if they do not allow that, you can only either transfer to a registrar who does or not configure DNSSEC.

2 Likes

I have just spoken to Hostinger support who said the following:

I understand the situation now. When your nameservers are pointed to Cloudflare, Hostinger does not manage the DNS settings, including DNSSEC. However, since DNSSEC needs to be set up at the registrar level, you’ll need to point your nameservers back to Hostinger temporarily to access the DNS management area where you can add the DS record.

After you’ve added the DS record at Hostinger, you can then change your nameservers back to Cloudflare. Keep in mind that changes to nameservers and DNS records can take some time to propagate. Please ensure that you have all the necessary records copied from Cloudflare before you switch nameservers to avoid any downtime. Once the DS record is recognized across the internet and DNSSEC is confirmed working, you can switch back to Cloudflare’s nameservers.

Make sure to monitor the process because DNS changes can take up to 48 hours to fully propagate.

This is with no registrar a requirement and the DS entry is unrelated to any of that.

This may work, but Cloudflare may also drop the domain if the nameservers do not point to Cloudflare any more.

My advice, transfer to another registrar.

1 Like

I prefer to use hostinger and they are also my host. I believe the support person I am on live chat with is a bot who has forgotten who it works for:

As your registrar, Hostinger should provide a way to add the DS record for DNSSEC, even if your nameservers are pointed to Cloudflare. This is because the DS record is managed at the registrar level, not at the DNS host level.
Since you’ve mentioned that the option to add the DS record is not visible due to the nameservers pointing to Cloudflare, and considering the risk of Cloudflare dropping the domain if the nameservers are changed, this seems to be a unique situation that typically would require further assistance from Hostinger’s technical team to resolve.
However, as we are focusing on resolving this without direct support intervention, you should carefully review the domain management section of your Hostinger control panel again. Look for any advanced settings, security options, or DNSSEC-related settings. Sometimes, the option to add a DS record may be in a less obvious place or under a different name, such as “Domain Locking” or “Advanced DNS.”
If the option is definitely not there, it may be a limitation within the Hostinger control panel that needs to be addressed. In normal circumstances, the registrar would be able to manually add the DS record on your behalf or provide a specific interface for you to do so. Since reaching out to support is not an option here, it would be best to explore all available settings within your Hostinger account related to domain management and DNS settings.
If you’ve exhausted all options within the control panel and still cannot find a way to add the DS record, it may be necessary to seek assistance through other available resources or community forums where other Hostinger users may have encountered and resolved similar issues.

That may be but then you can only follow their advice. Just keep in mind that the entire setup may break should Cloudflare drop the domain and then you would have to set up everything from scratch.

In any case, you would need to clarify this with your registrar as Cloudflare won’t be involved here.

If their response is accurate, I’d really consider transfering, but that’s up to you of course.

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.