{"id":2625,"date":"2019-10-22T17:31:42","date_gmt":"2019-10-22T09:31:42","guid":{"rendered":"https:\/\/www.mondoze.com\/guide\/?post_type=kb&p=2625"},"modified":"2022-10-05T08:02:37","modified_gmt":"2022-10-05T00:02:37","slug":"dns-troubleshooting-faq","status":"publish","type":"kb","link":"https:\/\/www.mondoze.com\/guide\/kb\/dns-troubleshooting-faq","title":{"rendered":"DNS for Troubleshooting FAQ"},"content":{"rendered":"\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t

DNS for Troubleshooting<\/h2>\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t
\n\t\t\t\t

Why do I have a dc-######### subdomain?<\/strong><\/h3>

The dc-##### subdomain is added to overcome a conflict created when your SRV or\u00a0MX record<\/em>\u00a0resolves to a domain configured to proxy to Cloudflare.<\/p>

Do not orange-cloud DNS records used to receive mail: Cloudflare does not proxy mail traffic by default.<\/p>

Therefore, Cloudflare will create a dc-##### DNS record that resolves to the origin IP address. The dc-##### record ensures that traffic for your MX or SRV record isn\u2019t proxied (it directly resolves to your origin IP) while the Cloudflare proxy works for all other traffic.<\/p>

For example, before using Cloudflare, suppose your DNS records for mail are as follows:<\/p>

example.com MX example.com\nexample.com A 192.0.2.1<\/pre>

After using Cloudflare and proxying the\u00a0A record<\/em>, CloudFlare will provide DNS responses with a Cloudflare IP (203.0.113.1 in the example below):<\/p>

example.com MX example.com\nexample.com A 203.0.113.1<\/pre>

Since proxying mail traffic to Cloudflare would break your mail services, Cloudflare detects this situation and creates a dc-##### record:<\/p>

example.com MX dc-1234abcd.example.com\ndc-1234abcd.example.com A 192.0.2.1 \nexample.com A 203.0.113.1<\/pre>

Removing the dc-###### record is only possible via one of these methods:<\/p>