dns – Do I need to change CNAME record for email redirecting?

You are both right and wrong.

For email delivery to work, DNS wise all that is required is a valid MX record (but an A record would work absent an mx record). That only covers the MTA though.

In order for imap/pop etc to work, the mail client needs to know the appropriate settings. An autodiscover record linked to an appropriately configured web server makes this a llot easier and would appear to be what is requested.

I note that “autodiscover” should be a subdomain (eg autodiscover.example.com) – so if it already exists the cname should be updated or replaced, and this should not affect anything else A cnsme for the domain name would be a very bad idea (ie you dont want a cname for example.com), and would likely break stuff. If you already have a cname for example.com you are likely doing it wrong, and autodiscover.example.com will be ignored.

Domain, DNS records and Cloudflare – An MX, A, AAAA or CNAME record was not found

I’m right now overwhelmed by the information out there. Hope some can point me in a direction.
I got a Dynadot domain (example.shop) that points to my hoster server IP where I also got a free domain (example24.de) which I deactivated. The hoster uses Plesk. WordPress Website and Email service works in that constellation (example.shop).

In Dynadot I pointed to the Server IP through the DNS setting:
Domain Record Type A = Server IP
Subdomain (www) Record Type A = Server IP

Now I wanted to connect it to Cloudflare which I’ve done in the past with an other page with success, but now I get error messages by Cloudflare saying:

An MX record was not found for your root domain. An MX record is required for mail to reach @example.shop addresses

An A, AAAA or CNAME record was not found for the www subdomain. The www.acido.shop subdomain will not resolve.

Do I need to go to Dynadot and set additionally A, AAAA or CNAME records for the “www” as subdomain?

I get mails in and out without errors now. I didn’t set any MX records in Dynadot DNS settings. With using Cloudflare do I need to have them set?

domains – point CNAME record to A record

On my domain example.com, I want to have a generic subdomain test.example.com that point to the folder test, and various cname (es. bar.example.com, foo.example.com) that all points to test.example.com.

I’m using Hetzner as provider, I created an A record (test.example.com) and a CNAME (bar.example.com) that point on the A record, and to make it works I had to add bar.example.com as an addon domain on Hetzner.

Any suggestion? Any possible solution that doesn’t involve adding cname to addon domain?

domain name system – CNAME and A record order in the ANSWER section

When resolving www.lowcarbmaven.com., if I get

lowcarbmaven.com.   13146   IN  A
www.lowcarbmaven.com.   300 IN  CNAME   lowcarbmaven.com.

my browser (Chrome in this case) is not able to understand the answer and show a 404. But if it gets:

www.lowcarbmaven.com.   300 IN  CNAME   lowcarbmaven.com.
lowcarbmaven.com.   13146   IN  A

It works. Is there a specification somewhere that clearly states the CNAME should be sent first?

exchange – Would adding CNAME records in DNS server for setting up DKIM cause email server issues?

I want to add two CNAME records to make my Microsoft exchange be DKIM compliant according to Microsoft.com’s instructions.

Is there any possibility adding the two CNAME records would cause disruptions to people sending emails in exchange?

CNAME record updates for DKIM is also really slow to be recognized by Microsoft so I might have to wait 72 hours until the CNAME is recognized by Microsoft for DKIM.

dns – Why is CNAME record being ignored – setting up Hostgator to use new Google Sites?

After posting here I got in touch with a colleague who was able to resolve the issue for me – although I confess I don’t fully understand why this works.

In a nutshell, when testing, I was keying in the domain name, without WWW, into the browser. In that scenario, the .htaccess file was being processed and my request was being forwarded with a temporary (302) redirect to the Google Sites URL.

What didn’t make sense to me was that the .htaccess file was being processed “before” the CNAME record – but there’s two points to note here: my request without WWW never engages that CNAME record, and secondly, you can use .htaccess to set up your web server so that regardless of whether end-users request using http or https, with or without the WWW subdomain, you can point all such requests to one “canonical” reference. The code I used is below, and all combinations of these requests will resolve to a request using https and the WWW subdomain. Of course, with the subdomain in the request, the CNAME record is then engaged and the site works as desired – displaying the Google Sites website while retaining my domain name (with https and WWW) in the address bar.

# Canonical https/www
<IfModule mod_rewrite.c>
    RewriteCond %{HTTPS} off (OR)
    RewriteCond %{HTTP_HOST} !^www. (NC)
    RewriteCond %{HTTP_HOST} ^(.*)$ (NC)
    RewriteRule (.*) https://www.%1/$1 (R=301,L)

And to Patrick, who downvoted the question because I didn’t give the domain name, that is how you answer a question which is posed generically. Cheers to my mate Dan.

Can differing A, CNAME, TXT, and NS records in multiple domains TLD’s cause email deliverability issues?

I’m troubleshooting an issue where, after switching TLD’s internal and ESP-based emails are getting blocked when going to external customers. Could different A, CNAME, TXT, and NS records cause email deliverability issues?
Short of posting actual differences, is there anything obvious before I look for other issues?

dns – CNAME works for nslookup but not curl

The greatest benefit I derive from StackExchange is that asking the question forces me to state the problem in detail.

In this case, I through in the parenthetical “(Cloudfront)” solely for completeness, but then I thought, “Hey…”

Yes, turns out, when I set up the distribution for www (weeks ago) I specified the “alternative CNAME”, as “*.mydomain.com” of course.

The two CNAMEs resolved to two different Cloudfront distributions, but then AWS read the HOST header in the HTTPS request, to choose which distribution to use. Correcting the two “alternative CNAME” settings on the distributions fixed the problem.

(I have added the amazon-cloudfront tag to the question to help anyone with the exact same problem to find it, but presumably other CDNs work the same way.

Do CNAME subdomains redirect to their target?

I’ve created the CNAME subdomain: tumblr.wp20201111.blog which maps to doigy.tumblr.com.

However, when I load tumblr.wp20201111.blog in the address bar, it doesn’t redirect to doigy.tumblr.com, it goes to https://www.tumblr.com/explore/trending

doigy.tumblr.com is a live URL.

Why doesn’t tumblr.wp20201111.blog redirect to doigy.tumblr.com ?

dns – Creating an A record and then a CNAME to point a subdomain to a different server gives an error message

A and CNAME both are types of DNS records, that can be applied to a domain name.

But they are mutually exclusive:(1)

  • A resolves a domain name query to an IP address,
  • CNAME resolves it to an other domain name.

So if you are ”trying to point a subdomain to a different server“ it depends on you hosting situation if it’s better to have DNS queries resolved directly to the new server’s IP by setting the subdomain’s A record to the new IP or “redirect” the DNS lookup by setting CNAME to point to a domain name of the new server (which gets DNS-resolved iteratively).(2)

(I certainly have no crystal ball, but person asking the question may confuse a CNAME record to be some kind of alias naming mechanism.)

  1. Actually, a domain name having a CNAME attached must not have any other resource record associated.
  2. NB: In the case of HTTP requests to the mentioned subdomain, the host: header will not change during a CNAME resolution.