mspv.in
An A, AAAA, or CNAME record with that host already exists. For more details, refer to https://developers.cloudflare.com/dns/manage-dns-records/troubleshooting/records-with-same-name/.
Unable to add CNAME with auto-discover
01326404
I don’t know
An A, AAAA, or CNAME record with that host already exists
You already have the subdomain autodiscover.mspv.in (proxied) so you cannot add a new CNAME record for the same subdomain. This is a requirement of the DNS standard, and not something Cloudflare controls (and certainly not a problem to report to Cloudflare to fix).
Delete this record before you can add the new CNAME record for the same address (or simply edit the existing record). And be sure to set the “Proxy Status” as DNS Only 
and not Proxied 
.
Ditto for autoconfig.mspv.in (if needed).
Good luck!
@georgeAppiah, the other record is for Website so we cannot simply remove it. Last time, Cloudflare support team added the Autodiscover CNAME record by keeping the current one, When we experienced the same issue. Any how support can add this?
You can’t expect to eat your cake and still have it though.
But I’m curious, do you even know what the autodiscover record does? Perhaps this will bring you to speed: https://practical365.com/make-sure-your-implementation-of-autodiscover-avoids-common-pitfalls/
Your MX record implies you’re using a variation of Microsoft’s email services. That’s where the autodiscover.mspv.in record should point to and not anywhere else (much in the same as you had to change your MX record from your “website” to point to mspv-in.mail.protection.outlook.com.
And having a priced autodiscover does you no good. Perhaps you even have the correct record already, and you simply have to disable the proxy. I’ve no way of knowing those if you insist this is for your “website” and should not be touched.
No, I’m pretty sure they never did anything of the sort. And, again, this is a requirement of the DNS technology, and not something Cloudflare has control over (if they want to stay true to the standard and be compatible with the rest of the world anyways).
What’s more, I’m pretty certain Cloudflare support won’t even dig into customer accounts and make DNS changes for them. They have enough trouble keeping up their billing issues 
But, of course, you’re right in whatever you choose to believe.
Good luck!
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.