• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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