Unable to validate the domain with GoDaddy after adding the CNAMEs from SendGrid
This was a simple fix. SendGrid asks you to add 3 CNAMES(5 CNAMES if branding needs to be enabled) for domain verification on your DNS Management Portal. Issue was that I was adding the entire CNAME which SendGrid was providing me, but GoDaddy just expects only the individual name, it appends the domain name to the CNAME during domain name resolution.
So for example, if SendGrid asks you to add something like below as a CNAME in GoDaddy,
ex0123.sub.domain.com, you should be adding only ex0123
for s1._domainkey.sub.domain.com you should be adding only s1._domainkey as the
For s2._domainkey.domain.com add only s2._domainkey
This fixed my issue, hope this helps you as well!
In my case, I struggled for a day and found this doc which says:-
Some DNS hosts will automatically add your top-level domain to the end of DNS records you create, which can turn a CNAME for “email.domain.com” into “email.domain.com.domain.com”. Be sure to follow the convention on existing records in your DNS panel when adding new ones, as sometimes you will only need to add what is to the left of the top-level domain.
For example, a CNAME for “email.” becomes “email.domain.com”
In Godaddy, you dont have to put domain name in CNAME records, just put the subdomain. Also, you need to put the entire VALUE string provided by Sendgrid in value field in Godaddy. as of Sep 2021.
The answer by Sreepriya Sreekumar worked perfectly but as of May 2021 in Godaddy I had to keep the full s2._domainkey.domain.com then it worked.
Steps 1 and 2 are exactly as written in that answer.
Related
Recently I have created a website for a client using Laravel/PHP. and then hosted on a cloud hosting provider vultr.com, the client didn't give me access to their domain (abc.com). they just pointed the domain to new hosting and the site is live.
The problem came when I wanted to configure email SMTP. I am using Mailgun for the emails. but for using service like mailgun you have to changes the nameservers in the domain setting. in my case, the client doesn't want to use the domain (abc.com) for emails because the domain is in their owner's name. so they are not changing the nameservers.
So my question is their anyways that I use some other domain or service for sending emails but
not the domain abc.com which is pointed to my hosting.
Also, they don't want to add the A record in the domain. the client just doesn't want to use the same domain for emails.
I hope I made my point clear.
Thanks
Case 1, You can create a subdomain and use dedicated for email like mail.domain.com, in subdomain update DNS recode and use for delivery its also not affect your main domain, in case you use sub email as abc#mail.domain.com for your emails.
Case 2, also an option to use the different domain name for emails and update DNS recode like PTR and DKIM, PTR, SPF
I have a domain (ex:- mydomain.com). I am using sendgrid mail service to send and receive mails. When I send any mail using sendgrid V3 API from address user#mydomain.com it is working fine. But I when try to use sub-domain user#username.mydomain.com sendgrid throwing 403 error (domain is not authenticated). Looks like it is accepting only root domain with out any subdomains. I would like to send emails from different custom subdomains.(like freshdesk and zendesk which allocates a different sub-domain for every user). Is there any way that I can overcome this probelm ?
Any little help would really be appreciated.
According to the info at SendGrid's Knowledge Center, you should be able to resolve your issue by properly setting up CNAME records for your sub-domains so that they point to sendgrid.net. See https://sendgrid.com/docs/glossary/cname/ for details.
Basically you need to 1) create a sub user 2) for the newly created sub user, go to Setting -> Sender Authentication to create your subdomain.
Then you need to go to Setting -> API Key to retrieve the access token for the new sub user. And use that access token when you send email and make sure to use the From address such as user#username.mydomain.com
You have to verify your subdomain also, similar as you verified your domain.
There will be 3 CNAME records given to you by Sendgrid which you can add into you DNS records in your domain.
(Only add first CNAME records Don't add last 2 records as it will be same as you already added for domain while domain(mydomain.com) verification
TYPE - CNAME
HOST - username.mydomain.com
VALUE - u2444223323.wl65.sendgrid.net
We have a domain using Gmail for business for emails, we are changing our domain , is it possible to route\forward all email to new domain (we are using same address for new emails, only the part after the # is changed)
Thank you
My organization recently added a second domain. This is done from your domain panel. See help. I would just recommend adding the the new domain as a alias of the old one, so that both email endings are recognized. See google warning about changing the primary domain
Don't forget to set up authentication on the new emails and update the authentication on your DNS providers site if you are rerouting to a new nameserver. Our emails were hitting spam filters for a week before we caught it.
I recently got an account with a custom after the # email address. I can send emails from this, but cannot receive them. I am currently hosting my website with GitHub Pages, and am wondering how the MX records work. Zoho's documentation is kinda confusing: I am wondering how to set this up.
Thanks!
Github Pages doesn't directly have anything to do with your particular question I don't think.
The MX records need to be set as part of your DNS settings (or ZONE file), and therefore are related to your domain name rather than necessarily your hosting provider.
Unless your hosting provider also manages your DNS settings (as in my case with DigitalOcean), these settings will typically be managed with your domain registrar (e.g. GoDaddy, 123-Reg.co.uk etc.).
The documentation you link to provides walkthrough tutorials for many domain providers (e.g. GoDaddy etc.), but from what I can remember, you basically have two steps in setting up Zoho (which I also use - and wholeheartedly recommend!):
Add a temporary CNAME record to the DNS settings for your domain (using the details provided by Zoho) so that Zoho can verify you have administrative access to the domain record.
Add the two MX records to your domain record, again using the details provided by Zoho.
Here is an example set of DNS records containing the two Zoho MX records and the verify CNAME record to help illustrate:
Hope this helps.
So before i can start sending emails with MailGun, i need to verify the domain with several DNS records, two TXT and one CNAME record. My problem is that am a bit confused to if these records should be added on the Domain provider or is the "Advanced DNS Zone Editor" in hosting's CPanel sufficient to make the DNS changes.
An additional question, can adding a CNAME record "email.domain.com" mess anything up for sending & receiving functionality?
I would be thankful if anyone could help me clear this up.
Thanks
Adding the described DNS records in the hosting account solved my problem.