DNS record validation using sendgrid with Domain.com - validation

I have been unable to find any help of almost any kind for Domain.com.
I am trying to set up SendGrid domain authentication. All I get is errors.
SendGrid side:
Failed
Expected CNAME for "em.....[mywebsite].com" to match "..........sendgrid.net".
Expected CNAME for "s1._domainkey.[mywebsite].com" to match "s1.domainkey.........sendgrid.net".
Expected CNAME for "s2._domainkey.[mywebsite].com" to match "s2.domainkey...........sendgrid.net".
On the Domain.com side I set it up like this:
**Record** **Name** **Content**
CNAME em.... ..........sendgrid.net
CNAME s1._domainkey s1.domainkey...........sendgrid.net
CNAME s2._domainkey s2.domainkey...........sendgrid.net
Does anyone know what I am doing wrong?

Twilio SendGrid developer evangelist here.
If you lookup the DNS records for your domain you will see that there are no listed CNAME records. However, you will also see that your name servers are listed with Digital Ocean. So, making the changes in domain.com will not make a difference to your domain as they no longer control the name servers.
I recommend you log into Digital Ocean and set up the CNAME records for your domain there. Then you'll be well on your way to setting up your Domain Authentication with SendGrid.

Related

masking heroku app from godaddy using cloudflare

I am trying to set up my herokupapp with my custom domain name from Godaddy. I hav gone through the process of getting it wokring using a cname through cloudflare.
Everything is working. However, when I go to my site at example.com my browser changes the url to example.herokuapp.com.
Going to: http://www.example.com/ and www.example.com do work
I don't want this obviously, what am I doing wrong?
Don't use an A record for your root domain. Heroku doesn't provide static IP addresses, so whatever value you put there won't be valid for long.
Since you're using CloudFlare you should be able to set up a CNAME for your apex domain just like you did for your www subdomain. CloudFlare has a feature called CNAME flattening that should make a CNAME on your root domain work as expected.
Regarding your comment that the www subdomain started working, that's typical of DNS changes. They take time to propagate. Give it some time.

How to redirect my naked domain to https://www.mywebsite.com with Google Domains and Heroku?

I host my website on heroku and my domain is managed by google domains.
I have successfully linked my domain to my heroku app. However, to go to my website, people are forced to type the exact domain www.mywebsite.com . If someone just type mywebsite.com there is an http error.
I'm searching on both google & heroku docs but i don't find anything related to this . All info i found are about subdomains.
Any idea for redirecting all http/www typo to my www.mywebsite.com ?
At the core, keep in mind that example.com and www.example.com are 2 different hosts that can resolve to different IPs. Your DNS settings at Google Domains handles this. Either direct both of them to Heroku or simply direct "www" to Heroku via the CNAME record that they give you and then use Google Domains forwarding feature to forward all non-www traffic to www.example.com.
In the Synthetic records, choose Subdomain forward, fill # in Subdomain, then www.yourdomain.com in the Destination URL, also choose Forward path and then ADD

Trouble connecting domain name to Heroku app

I have bought a domain name with Porkbun.com, I have added that domain to my herokuapp domains and received a DNS target. I have added an ALIAS record with host: 'mywebsite.domain' and target as the DNS target I received from Heroku.
When trying to access the domain I get 'bad Request (400)' error. I have then tried these three separate steps:
As instructed by Porkbun I added another ALIAS record with host: www.mywebsite.domain and target: 'mywebsite.domain'.
I deleted all the ALIAS records I had and added a CNAME record with host: 'www.mywebsite.domain' and target: 'mywebsite.herokuapp.com'.
Changed CNAME target to be the DNS record I received from Heroku.
In the three cases I receive a Heroku page saying 'There is nothing here' and titled 'no such app'.
Similar problem occurred to me yesterday when i tried to deploy a ghost app to heroku pointing to a custom domain name purchased through porkbun. After googling i found out that the IT TAKES ALMOST A DAY TO RESOLVE THE DNS POINTING TO THE CUSTOM DOMAIN in porkbun.
Solution
I changed the CNAME RECORD pointing to the herokuapp url;-"yourappname.heruko.com"
Add the host as WWW
You can also use ALIAS-CNAME RECORDING to point to the heroku app url.
heroku domains:add example.com
heroku domains:add www.example.com
heroku domains:add *.example.com
This is to point your domain name from heroku side
Check out this video its about connecting your domain name to godaddy. I think its the same way with porkbun youtube.com/watch?v=kKGSGT7mSnQ&t=75s
Please let me know if this does work for you

use both www and naked domain to point my heroku app

I am having trouble to set both my www.domain.org and domain.org to point to Heroku rails app.
I did a CNAME from www to www.example.org.herokudns.com.
it works fine and my www.example.org point to my example.herokuapp.com
Concerning https://example.org
Should I do a
CNAME from # to example.herokudns.com ?
ALIAS is only accepted for IPs with my domain provider..
I having trouble finding an answer in stackoverflow.
Should I use http://wwwizer.com/naked-domain-redirect ?
Do I have a solution without using a third party free service ?
For naked domain example.com you can use the forwarding functionality. If you have purchased domain from GoDaddy you can follow this:
Go to manage DNS and scroll down to forwarding section where you will see something like this:
You can choose https and forward to www.example.com. (You can also make your naked domain point to some other subdomain)
heroku domains:add example.com
heroku domains:add www.example.com
heroku domains:add *.example.com
This is to point your domain name from heroku side
Here is a youtube video to make it easier https://www.youtube.com/watch?v=kKGSGT7mSnQ&t=29s
Please let me know if this does work

Is it possible to create a correct SPF and DMARC DNS record when you use a CNAME?

In my setup I have a website (example.app) hosted on Heroku.
Then, I use Sendgrid to send emails from the Heroku server to our users that forget their password. The email is registered using Google's Gsuite. So I also send emails from the Google servers.
The from email is: <Appname <noreply#example.app>
So I thought these should be my DNS records (note I don't have an A-record):
CNAMES:
example.app CNAME "example.app.herokudns.com"
www.example.app CNAME "www.example.app.herokudns.com"
SPF:
example.app TXT "v=spf1 a include:_spf.google.com include:sendgrid.net ~all"
Dmarc:
_dmarc TXT v=DMARC1; p=none; rua=mailto:dmarc#example.app; ruf=mailto:dmarc-forensic#example.app; fo=0; adkim=r; aspf=r; rf=afrf; pct=100; ri=86400; sp=none
However, the Dmarc record doesn't validate as mail is send from a different domain then the To address. I think the email is send from sendgrid.com and the to-address is example.app.
Hence, I think by adding the IP-addresses of my Heroku DNS into the SPF record it should work.
But how do I do this, when these IP-addresses are dynamic?
"No" by protocol - rfc1912#section-2.4 but "yes" if using CNAME flattening.
Also, you should configure your SPF and DMARC using your email servers, in your case, sendgrid not your#example.app
Check more about how Cloudflare deals with CNAME flattening here: https://blog.cloudflare.com/introducing-cname-flattening-rfc-compliant-cnames-at-a-domains-root/

Resources