Ok, there does seem to be a communications issue here.
We have dozens of sites - hosted on dedicated hardware servers,
all running Plesk on the hardware,
all hardware and web sites are connected to Cloudflare,
all sites are set at their registrar to use CloudFlare NS servers as their DNS servers
all are using CloudFlare as their Primary "DNS server" for the hardware server & its websites,
AND NONE of those dedicated servers themselves have ANY “Plesk DNS” active/enabled.
ALL are connected to and working with Cloudflare without issues.
Now, Our newest dedicated server and it’s sites DO have ‘Plesk DNS’ enabled - the Plesk install did that -
BUT was, as we normally do, setup (through registrar) to use CloudFlare NS servers AND use Cloudflare for DNS.
We do NOT know if that will be a CONFLICT/Issue with the ‘Plesk DNS’ enabled, but Cloudflare NS servers
and Cloudflare for DNS. We have NEVER run a box with ‘Plesk DNS’ enabled before (as explained above).
That is what I am seeking advice upon. The hardware hasn’t gone totally ‘live’ yet for users.
Maybe that is clearer? LOL