• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Question Name Servers and CloudFlare

WebHostingAce

Silver Pleskian
Hi,

I have this custom Name Server setup in Plesk.

ns1. clickrocket .com .au (Spaced out)

This domain and NS are using CloudFlare.

When I check externally Port 53 is closed on ns1. clickrocket .com .au but it still WORKS!

How could be that possible?

Thank you.
 
In short, the free cloudflare account does not support custom nameservers, that is, using subdomains as nameservers.

Sometimes it will work, other times it may cause problems.

I would recommend using a different domain to use as a nameserver.

Personally, I use DigitalOcean as a DNS server to point nameservers to clients, the service is free and redundant.

However, godaddy has problems when using DigitalOcean, it simply refuses these nameservers, and to solve it I also use noip for the nameserver server in another domain.

Summary, I use 2 domains as nameservers:
domain1.com - DigitalOcean (free)
domain2.com - NoIp (paid)

Also as far as I remember Cloudflare doesn't support the NS record type.
 
Back
Top