{"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
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> 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> Since proxying mail traffic to Cloudflare would break your mail services, Cloudflare detects this situation and creates a dc-##### record:<\/p> Removing the dc-###### record is only possible via one of these methods:<\/p> If your mail server resides on the same IP as your web server, your\u00a0MX record<\/em>\u00a0will expose your origin IP address.<\/p> Third-party tools can sometimes fail to return correct DNS results if a recursive DNS cache fails to refresh. In this circumstance, purge your public DNS cache via these methods:<\/p> No A, AAAA or CNAME record found<\/em>\u00a0means the Cloudflare\u00a0DNS<\/strong>\u00a0app lacks proper records for DNS resolution.<\/p> Add the missing DNS records\u00a0to your domain.<\/p> Sites generally have at least an\u00a0A record<\/em>\u00a0that points to the origin server IP address, typically for the\u00a0www<\/em>\u00a0subdomain and the root domain.<\/p> For domains where Cloudflare hosts the DNS, Cloudflare continuously checks whether the domain uses Cloudflare\u2019s nameservers for DNS resolution. If Cloudflare’s nameservers are not used, the domain status is updated from\u00a0Active<\/em>\u00a0to\u00a0Moved<\/em>\u00a0in the Cloudflare\u00a0Overview<\/strong>\u00a0app and an email is sent to the customer.<\/p> Steps to resolve the issue require updating the DNS at your domain registrar to utilize the Cloudflare nameservers:<\/p> DNS for Troubleshooting Why do I have a dc-######### subdomain? The dc-##### subdomain is added to overcome a conflict created when your SRV or\u00a0MX record\u00a0resolves to a domain configured to proxy to Cloudflare. Do not orange-cloud DNS records used to receive mail: Cloudflare does not proxy mail traffic by default. Therefore, Cloudflare will create a …<\/p>\nexample.com MX example.com\nexample.com A 192.0.2.1<\/pre>
example.com MX example.com\nexample.com A 203.0.113.1<\/pre>
example.com MX dc-1234abcd.example.com\ndc-1234abcd.example.com A 192.0.2.1 \nexample.com A 203.0.113.1<\/pre>
example.com MX mail.example.com\nmail.example.com A 192.0.2.1\nexample.com A 203.0.113.1<\/pre>
Why are DNS queries returning incorrect results?<\/strong><\/h3>
No A, AAAA or CNAME record found?<\/strong><\/h3>
Why have I received an email:\u00a0Your Name Servers have Changed<\/em>?<\/strong><\/h3>