Just saw you did a lot of mistakes:
- you do have a seperate subdomain for Mail (
mail.vulcanwaterproofing.com) but you point your MX entrys to
vulcanwaterproofing.com instead of
vulcanwaterproofing.com is getting proxied. All domains/subdomains your MX entrys are pointing at are not allowed to be proxied! Also if you CNAME them to any other DNS entry.
Pls set it up like this:
vulcanwaterproofing.com () --> 220.127.116.11
CNAME webdisk () -->
CNAME webmail () -->
A mail () --> 18.104.22.168
Keep the rest. After this it will work, but if your Browser and the Servers have already cached the proxied result you may have to wait untill the TTL is reached and they resolves the Domain again.
Also I would recommend you never keep the Mail-Server and the Web-Server one the same physical machine! Thats bad practice and also exposes your origin Domain, even if CF gives your the chance to hide it. This will automatically be the case as you cant proxy Mail Requests and MX entrys
(…well you can but then it will not work anymore by definition!)
No… clear the DNS cache from your Server if he resolved your MX entrys while they have been proxied. CF Cache does not have to do anything with this problem right now.
this is the actual behaviour of your setup (at least of the one you provided with your screenshot) as you point your MX entry to your QDN (
vulcanwaterproofing.com) which actually gets proxied by CF, so your MX entry will resolve to CF which makes it unusable. You shall not proxy any MX entrys
Solution (as shown above):
- point your MX entry to (
mail.vulcanwaterproofing.com with an unproxied () A record to your plain IP on which your Mail Server is set up