I am new to DNS management. I bought a domain from Godaddy. I've added some records like i've pointed domain to my cloudways server. Added TXT for google console verification. At the same time I added TXT Records to authenticate my domain to Email SMTP Service Provider (Sendinblue.com). Within 10 Minutes my records were propagated, google verification was sucessfull and my domain was pointed to my server. But TXT's for sendinblue.com were not being authorized. Now its been more then 2 days still didn't authorized. I dont know if there is something i did wrong in configuration. May be there are multiple TXT's of same type. As I mentioned above my domain is pointed to my server and google console is verified. If these 2 records were propagated then sendinblue should also be authorized at the same time. But still i waited for 2 days and no success. May be some issue in configuration.
Domain configurations screenshot( https://imgur.com/a/nbPmKf4 )
After a bit of research i found a fix from a community. https://pk.godaddy.com/community/Managing-Domains/DNS-TXT-record-not-propagating/m-p/139411#M26840
Related
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).
So my 'enabling' HTTPS stage for my CDN endpoint has been stuck for 3+ days at 'enabling cdn' with the usual message of: a verification request will be sent to the email listed in your domain’s registration record (WHOIS registrant).
Now, I have the CNAME set as you can't even add it if it's not set to the right CDN endpoint. I have cancelled the process and restarted it after 2 days and now at the 2'nd attempt it's been hanging for 3 days.
The issue is the email for verification via the WHOIS will always go to something like protected-by-gdpr#gdpr-protected.com -- some type of placeholder domain as due to GDPR in Europe WHOIS data is no longer available.
This is not like 'WHOIS GUARD' that still leaves a way of getting contact, nor it is changeable, it is by default enforced across all domains as far as I can tell.
Now my questions is, what do I do to enable HTTPS on my custom domain if it doesn't care/look at the CNAME records?
According to this doc, If the CNAME record entry for your endpoint no longer exists or it contains the cdnverify subdomain,
DigiCert also sends a verification email to additional email
addresses. If the WHOIS registrant information is private, verify that
you can approve directly from one of the following addresses:
admin#<your-domain-name.com>
administrator#<your-domain-name.com>
webmaster#<your-domain-name.com>
hostmaster#<your-domain-name.com>
postmaster#<your-domain-name.com>
You should receive an email in a few minutes, similar to the following
example, asking you to approve the request. If you are using a spam
filter, add admin#digicert.com to its whitelist. If you don't receive
an email within 24 hours, contact Microsoft support.
You also could verify the above addresses. As far as I know, some similar domain ownership verifying question such as could not get verified from WHOIS registrant or your domain owner information is not enough exposed publicly so that domain ownership verifying has a failure.
To get fix these issue quickly, you can directly contact Microsoft support. They will confirm the domain information for you. See another similar thread.
I needed to add digicert to my CAA authorities in my domains DNS setting, because I already had a value present, it wouldn't let me issue certificates unless I added that there.
I am having some difficulty setting up my SendGrid account to connect to my DNS on Cloudflare and enable custom domain whitelisting for two domains.
My plan is to deploy emails from my Clickfunnels' Actionetics account. Currently, my integration into Clickfunnels is a success and I was able to receive an automated test e-mail (from my custom domain) to my personal email address. I understand that I should be able to send emails from any e-mail address I need (support#domain.com, hamid#domain.com, info#domain.com) without needing to physically needing to go through any setup process to get these emails up and running. Initially when I went through the SendGrid setup, I needed to add 3 CNAMES to my Cloudflare DNS. Everything successfully installed without any issues from Cloudflare. After speaking with Support, I was told that I might need to retry the whitelabel wizard with automatic security off. Going through this wizard should give 2 txt's and one MX (mail exchanger) record instead of 3 CNAMES.
"Automating security allows the system to redirect ISPs to SendGrid to check DNS records that follow strict security protocols and are custom to your account. Due to a character limit on TXT records, we are only able to create a custom SPF (sender policy framework) record for users with up to 11 IP addresses. This will not affect deliverability. You would have to go through the whitelabel process again."
If you have experience in this type of issue, please let me know what you think.
This is one method the I recommended.
“white-label the domains again but this time completing it with automatic security turned off. Going through this wizard should give 2 txt's and one MX record instead of 3 CNAMES.”
"Automating security allows the system to redirect ISPs to SendGrid to check DNS records that follow strict security protocols and are custom to your account.
Due to a character limit on TXT records, we are only able to create a custom SPF record for users with up to 11 IP addresses. This will not affect deliverability. You would have to go through the white-label process again."
Thanks, I hope you can resolve this.
I can't understand your question.
SPF is kind of TXT record, it can help receiver know email comes from right ip address.
Whitelabeled Domains help receiver know email really comes from the right server.
Sendgrid need a subdomain and two well-know subdomain to verify your identity.
I'm using google apps for mail service. I have generated and submitted DKIM records for .co and .in domains successfully. But I'm not able to generate DKIM record for .net domain (say yourdomain.net). It shows an error we are unable to process your request at this time. Please try again later. (Error #1000). I have tried this for 2 .net domains. Both provide the same error. I have tried using in different browser and different machine, and the results are the same.
I am not sure if the issue is with the .net domain or if this is just a coincidence.
Had the same issue today (setup of DKIM on a new GSuite domain) and chatted with Google Support about it.
They pointed me to the following quote on the DKIM setup process.
Important: After you create your G Suite account and turn on Gmail, you must wait 24–72 hours before you can generate a DKIM domain key.
So you'll need to wait 24 - 72 hours after setup of the GSuite account before you can set up DKIM.
I also asked the support person whether I could get access to submit this as a product request (that the DKIM setup is prevented before this time) and he gave me access to the G Suite Feature Ideas (customers only) Cloud Connect Community. I've posted this as a feature suggestion there - upvote if you think this is needed! (needs login):
https://www.cloudconnectcommunity.com/ccc/ls/community/g-suite-chrome-feature-ideas/post/5075513382141952
Preview Screenshot:
I had a "Google Apps for Work" account and wanted to setup DKIM for Google Apps email and another provider and I couldn't do it. I contacted Google Apps support and they said it was a bug with no immediate plans to fix it.
I got the same useless error code you did. I'm disappointed in Google about this. They just leave the broken submit form up, leaving it to the user to contact support to find out it's broken with no plans to fix it.
I'm going to cancel my paying google apps account.
I experienced the same error message when I tried to set up DKIM immediately after signing up for GSuite. It worked when I re-tried about two days later.
I have registered a domain (though there is no hosting yet, just name registration) and I am trying to set up google apps so that I can have email, but I cannot figure it out. Is there something I am missing? I feel like it should be easier than it is right now.
You need to correctly set the MX records at your registrar.
Have you proved domain ownership including a CNAME record in your DNS server? Just follow the instructions.
If you don't have access to your DNS server for adding records, and don't have a webserver where you can put a verification file I think you wont be able do setup e-mail.
If you already have the domain, you just need to follow the registration process, you will be taken through all the steps. If you got to the Admin Console you should have a message bar Top of the page with Verify Domain.
the best way to do it is to try the new Learning Center, http://learn.googleapps.com/.