Email service hijacking my MX domain

[j.mya.pitz]

So I recently decided to give the email service a try. While it seems nice for some use cases, it didn’t quite meet what I was looking for so I decided to disable it and start running my own mail server. After setting everything up and not having any issues with MX records for a week, I noticed that Cloudflare started automatically adding the MX record for their service, despite the service being disabled (and had been disabled for a good week). As a result, Cloudflare hijacks my MX domain from my managed email service.

Anyone else experience this?

[Cyb3r-Jak3]

What is your domain?

[j.mya.pitz]

pitz.tech

[fritex]

Currently, looks like none MX or A record found for it.
From DNS history, I could find some from Cloudflare and DigitalOcean.

May I ask have you tried looking into the Account → Audit Log for some details what event has happened and for some more additional information?

[j.mya.pitz]

@fritex

May I ask have you tried looking into the Account → Audit Log for some details what event has happened and for some more additional information?

I’m not sure what you’re looking at but there are definitely records there.

The 10. address is the one that’s being added by Cloudflare. The 174. address is the one from my cluster in digitalocean. I’ve tried deleting the 10. address, but it just keeps coming back.

[fritex]

Unfortunately, from the above screenshot you shared, those are the two A type records and not MX type records.

It’s a difference.
A mx.yourdomain.com is not the same as MX yourdomain.com.

You’d have to adjust your DNS records.
Firstly, remove both A mx.
Secondly, add new MX type record pitz.tech pointed to mail.pitz.tech.
Therefore, add new A type record mail pointed to the IP and (DNS-only).

Usually, the MX record should point to a hostname such as mail , and the A (or CNAME ) type record for that hostname should be set to (DNS Only).

May I suggest checking below article if your e-mail records (usually the A mail and the MX record) are configured properly while you are using Cloudflare for your domain name:

• Email undeliverable when using Cloudflare

Email Troubleshooting

This tutorial covers the steps you should take if, when you change your domain to point to Cloudflare, you no longer receive emails to your domain. If you follow this tutorial and still need further help, please let us know what you have tried and share your domain name and, if possible, a redacted screenshot of your DNS records in Cloudflare. [Cloudflare Community Tutorial - Troubleshooting Email Delivery Issues] 1. Do you have the correct MX records set for your domain? You will…

Helpful articles about managing DNS records at Cloudflare:

Adding DNS Records

This tutorial covers adding general DNS records and specifically A, AAAA, CNAME, MX and TXT records. Go to the DNS app of your Cloudflare dashboard. Enter your credentials and click ‘Log In’ Click the domain in question Click [image] [Please note, the content of the records below are solely for example purposes and should be replaced by valid records with content provided by your web host] Please select which record you need help adding:

A Record

<a class="lightbox" href=&quot…

Editing DNS Records

This tutorial covers editing DNS records. Go to the DNS app of your Cloudflare dashboard. Enter your credentials and click ‘Log In’ Click the domain in question On this page, you will see a list of the DNS records for your domain. This page is where you edit them. You will see the list of records like this: [DNS Page] You can click the edit button to the right of any record to change it, then click ‘save’ when you’re done. There is also a tutorial on Adding DNS Records Tutorial Refer…

[j.mya.pitz]

Ah! the 10. address isn’t being added by Cloudflare. It’s an internal IP thats leaking through. I think I know what’s going on.

Thanks!