Why do I have a dc-######### subdomain?

The reason the dc-##### subdomain is added is because we need to
overcome a potential conflict created with your MX record. Take the
following example:

example.com   A   1.1.1.1
example.com  MX  example.com

The "A" record can be "CloudFlare Enabled." When that happens, CloudFlare
will announce DNS that looks like:

example.com  A  9.9.9.9

Where 9.9.9.9 is a CloudFlare proxy IP address. The problem is, the MX
record is still:

example.com  MX  example.com

Since the A record now has example.com pointing to 9.9.9.9, and since
CloudFlare does not proxy mail, we need to create a "shadow" record to
ensure mail is still delivered properly. So your DNS effectively becomes:

example.com  A  9.9.9.9
dc-1234abcd.example.com  A  1.1.1.1
example.com  MX  dc-1234abcd.example.com

The solution to get rid of the dc-###### record is to change your DNS
configuration to eliminate the conflict caused by your MX record. You could
do one of two things:

1. If you're not receiving mail on the domain, simply delete the MX record;
or
2. If you are receiving mail on the domain, dereference the MX record
explicitly with a setup like:

mail.example.com  A  1.1.1.1   [cloudflare disabled]
example.com  MX  mail.example.com

Note, however, that if you're running your mail server on the same IP as
your web server, your MX record will always expose the IP address of your
origin.

The dc-###### records was previously called direct-connect.

Still not finding what you need?

The Cloudflare team is here to help. 95% of questions can be answered using the search tool, but if you can’t find what you need, submit a support request.

Powered by Zendesk