I own the domain abc.com purchased through NameCheap. I have set up a custom DNS redirecting it to my digital ocean droplet as below.
NAMESERVERS:
ns1.digitalocean.com
ns2.digitalocean.com
ns3.digitalocean.com
This is working fine.
My email for #abc.com is provided by Google and this has been setup through corresponding A and MX records on Digital Ocean, and the email is working fine.
Now, I am attempting to authenticate this domain for both Mailchimp and firebase to send emails using my #abc.com email.
For Mailchimp, they need me to authenticate the domain using c-name records as below -
Mailchimp Instructions:
CNAME 1 : Name: k2._domainkey.abc.com, Value: dkim2.mcsv.net
CNAME 2: Name: k3._domainkey.abc.com, Value: dkim3.mcsv.net
On my digital ocean I set up the following CNAME records:
Type- Hostname - Value - TTL (seconds)
CNAME- k2._domainkey.abc.com - dkim3.mcsv.net - 43200
CNAME- k3._domainkey.abc.com - dkim2.mcsv.net - 43200
This is Not Working. I am getting the following message:
Uh oh, something went wrong.It looks like something didn't get copied and pasted correctly when you added the CNAME records to your domain. Delete or edit those records to try copying and pasting again.
I am having a similar problem with authenticating the domain for firebase to send emails from my #abc.com email, which leads me to believe that my setting up of CNAME record is incorrect.
Given my setup of the domain (Namecheap), custom DNS (digital ocean) and email (google) am I supposed to set up the c-name record differently? Please help me solve this problem.
The problem seemed to be occurring because of the custom DNS set-up on NameCheap redirecting it to digital ocean servers. I am given to understand from Mailchimp service provider that this means that some of the DNS records were not publicly visible. Hence the domain authentication failed.
I changed the set-up to a standard DNS set up on NameCheap, and created the CName records. The authentication then worked.
Related
I have a Next.js (deployed with Vercel) app and I am trying to implement SendGrid to create a contact form on my site.
I have followed this tutorial
when trying to submit the form I get the following error:
POST http://localhost:3000/api/send 400 (Bad Request)
I believe the issue is around sender authentication. (https://app.sendgrid.com/settings/sender_auth)
My domain provider is '123-reg'.
I have added the dns records from Sendergrid to the 123 dns section. However when I click on verify I get the following errors:
I can't seem to verify these records.
UPDATE
I have actually updated my Vercel dashboard domains section with the values provided from SendGrid but I still get the same errors:
It seems you are using Vercel (Zeit Now) for your DNS and you haven't configured the SendGrid DNS records that the service requires.
When adding CNAME to the Vercel DNS interface, try adding only the subdomain part. This means em8573 instead of em8573.alex-web.co.uk and so on.
You can find instructions on how to create CNAME here.
You can easily test your records using Dig web interface, an amazing web service.
if your domain doesn't match 'alex-web.co.uk' then it will not work. Ensure the CNAME has the correct domain. If it matches your domain name Vercel will auto remove the domain name from your CNAME.
I have a problem setting up GSuite gmail. I can send out emails to other accounts; however, I cannot receive any emails from outside. My admin page says
Setting up email is taking longer than expected
We were unable to set up email, or your domain host is taking longer than expected to update your information.
My domain is registered with Namecheap. But it is served from Amazon S3. And the "https" certificate is verified and served through CloudFront. When setting up "MX Records" for Gsuite gmail, I set up in Namecheap. But it has been more than 72 hours, and Gsuite is still not picking up. In my situation, do I have to set up "MX Records" through Route53 because it is being hosted in Amazon S3?
You can setup MX records however if your domain is still not verified with G Suite you will not be able to use emails or any other service. Make sure to:
Your domain has been verified Verify your domain for G Suite.
MX Records are setup properly G Suite MX record values
If you domain is verified make sure that all apps on Admin Console > Apps > G Suite are enabled.
Also as recommendation set up SPF, DKIM and DMARC to authenticate email.
If you are still not able to receive emails I would suggest to contact G Suite Support. Also make sure where your Domain NS servers are pointing to, there is where you have to update the DNS.
It's not really an issue with Google, every domain's MX records are public, you can easily inspect your domain and verify if the MX records are already setup to Google, check https://mxtoolbox.com/ and make sure that the MX records are already ASPMX.L.GOOGLE.COM, if it's not, then make sure that the MX is updated in your NameServers (not necesarily your domain provider), same online tools can easily tell you which is your active NameServers (Google NS lookup tools).
I followed Quickstart: Add a custom domain name to Azure Active Directory to verify my custom domain but still experiencing difficulties. I owe a domain (something like www.example.com with the only difference is mine is not 'example') purchased at GoDaddy.com.
If I try to verify that domain and specify its name (in AAD portal) as www.example.com then I can successfully complete the verification, but if I use the name example.com (without www) - I am seeing an error saying
Unable to verify domain name. Ensure you have added the record above
at the registrar 'MyDomainNameIsHere.COM', and try again in a little
while.
I employed nslookup to make sure the TXT record was added, I also followed the section Troubleshooting, non of those 3 cases apply to me:
waited for few hours
made sure with nslookup that the dns record is
correct and exists
there is no existing domain with that name
Why does it work if I prefix it with www and doesn't without it? Do I need to make some changes at GoDaddy?
I need that custom verified domain to add AAD users associated with their emails at my domain, for instance, User1#example.com; User2#example.com and so on. That doesn't work when I verify the www option complaining that example.com is not verified domain but doesn't complain if I try to create a user User1#www.example.com and I cannot do that because there is no corresponding email address.
I've a domain, let's say abcd.com, For this domain,
We have a wildcard A record pointing to an IP say, 12.34.56.78,
* => 12.34.56.78
So, all subdomains of abcd.com point to 12.34.56.78.
So, when I access small.abcd.com, it points to 12.34.56.78.
Then, we added a Cname record for Google domain verification of small.abcd.com,
eocjdrkdkoed.small => gv-f8ded7dfivfkdo.dv.googlehosted.com
For more information on this, go to https://support.google.com/a/answer/47283?hl=en
This caused a DNS error with small.abcd.com. That is, this url small.abcd.com is no longer accessible and it no longer points to 12.34.56.78.
On nslookup, it says, "Can't find small.abcd.com: No answer".
Can anyone help me with this ? Is it an issue with my DNS provider or is it how DNS records work ?
edit:
The domain not working - small57.realizegoal.com.
Before, it used to point to xxx.xx.68.191.
After adding DNS verification Cname record, it started failing.
A domain name that we have is using google mail as its backend, but its not hosted anywhere (no website). How can I, through the registrar interface (I'm using 1&1), redirect ppl who type in http://mail.example.com to http://mail.google.com/a/example.com ?
I can create a subdomain and set its DNS/CNAME, but what do I put where? Also, if I make this change will it affect the existing mail delivery (for which everything is running fine presently).
It turns out it wasn't that tough... and the instructions are part of Google itself:
Dashboard -> Service settings: Email -> General:Web address -> Change URL
https://www.google.com/a/cpanel/example.com/CustomUrl?s=mail
Changing CNAME record
To use the custom URL mail.example.com, you must change the CNAME record with your domain host.
Sign in to oneandone.
Navigate to your DNS Management page. The location and name
of this page will vary by host, but
can generally be found in Domain
Management or Advanced Settings.
Find the CNAME settings and enter the following as the CNAME value
or alias:
mail
Set the CNAME destination to the following address:
ghs.googlehosted.com
Save changes with your domain host and click "I've completed
these steps" below.
You cannot redirect to a path (such as /a/example.com) using only DNS. DNS CNAME records can make mail.example.com/foo effectively point to mail.google.com/foo, but something more sophisticated will require HTTP redirects. This means you need someone hosting your web page for this to work.
Sorry.
If your registrar offers an "HTTP Redirect" option, you can use that. Some registrars do. If you use this, they're effectively running a minimal web server for you. Note that this may break SSL when users access your page via https://example.com.
Mail delivery is via MX records, which won't be affected by changes to other types of record (so long as you don't interfere with the DNS records for the domain's mail servers).