Home / server / Questions / 448419
Accepted
Onitlikesonic
Asked: 2012-11-14 16:31:56 +0800 CST

Using namecheap dns with cloudflare

  • 772

Since CloudFlare doesn't provide E-mail forwarding I need to leave my DNS management on Namecheap.

What DNS records (A,CNAME,...) would I need to point to CloudFlare (and to where) to be able to still use their functionality whilst leaving the rest up to namecheap?

cloudflare

6 Answers

  1. Best Answer

    I ended up using Mailgun to "solve this problem" which gives me free mail servers to do the forwarding as I needed, there doesn't seem to be any way of doing this just with namecheap and cloud flare as the problem I stated. Thanks everyone for the help.

    • 13

  2. "Cloudflare does not make it easy for you to use their service without giving them DNS access (I think it is only possible through their API)"

    You don't need to change to our DNS when activating through a CloudFlare hosting partner.

    We also do offer CNAME setup to some users that can't change to our nameservers.

    "Then add them to your Cloudflare zone file and this will point all mail back to your previous provider."

    Yes, people would most certainly want to have all of your mail and MX records in your DNS settings at CloudFlare (if someone signed up directly). Thanks for answering this:)

    • 4

  3. You can perfectly well manage your DNS within CloudFlare. Just use its DNS manager to set your MX records to whatever they need to be.

    • 1

  4. This is not easily possible. When you setup CloudFlare, it will transfer all your current records. It is usually an on or off kind of thing. You can exempt each A or CNAME record from Cloudflare by clicking the orange flag. With namecheap, they probably rarely change their MX records. I would switch, it should still work, just make sure all your records are identical (which CloudFlare should do for you anyway).

    • 1

  5. Cloudflare does not make it easy for you to use their service without giving them DNS access (I think it is only possible through their API). Regardless, the better solution here is to keep DNS with Cloudflare and simply point your mail (MX) records back to where they are now. You can source what your current MX records are by performing 'dig mx domain.com' in a unix terminal or some other service to find MX records. Then add them to your Cloudflare zone file and this will point all mail back to your previous provider.

    • 0

  6. OK, if you have a website (e.g. on GitHub pages) for a custom domain on a DNS provider (e.g. Namecheap) and you want to put the CloudFlare CDN / HTTPS proxy in front of it and have mail forwarding work, this is the order of tasks you need to perform:

    1. Set up Mailgun for your email forwarding – as Onitlikesonic wrote, this is a good starting tutorial
    2. After you have these new MX/TXT rules in your DNS provider then follow these instructions to set up CloudFlare and have it scan all the DNS rules
    3. You might have to add missing rules (the 2nd mail server, 2nd TXT rule), so be sure to check the Advanced DNS settings for your domain on Namecheap
    4. Switch Namecheap to a custom DNS (the "Domain" tab) and enter the name servers CloudFlare provides
    • 0