I had my client migrate his domain from GoDaddy to Netlify by updating his DNS records. When I attempt to provision an HTTPS cert, I get "We could not provision a Let’s Encrypt certificate for your custom domain."
The domain is www.ifbidtransport.com
These are his DNS records in Godaddy currently:
(The type A record's name has been corrected to just "#")
What can I do to resolve this? I am happy to provide any info I missed; I'm a bit of a noob at server stuff.
Thank you!
Related
I have deployed an app on Heroku, and everything is going great when the app is being accessed from the herokuapp.com domain. I tried adding a custom domain and have followed the instructions from the documentation, but unfortunately, I encounter a DNS_PROBE_FINISHED_NXDOMAIN error when trying to access the app from my custom domain.
Some articles pointed out how Heroku requires the usage of ALIAS ANAME or FLATTENING records, which may not be available in DNS providers. I am using a local DNS provider where Name Server configuration is not directly accessible, and only the DNS provider admin can configure it on my request, so I am unable to check the CNAME Records and such (probably because I use .id domain, which I believe to have a somewhat specific configuration due to its affiliation with the country Indonesia, could be wrong though).
For my Name Server, because my DNS Provider requires at least two different name servers, I registered the domains for my Heroku app (from the Heroku settings dashboard > add domain and from the CLI) as follows:
my-domain.id
*.my-domain.id
www.my-domain.id
Is there anything I can do to fix this? Any help would be highly appreciated! Thank you!
EDIT:
I have just been informed by my DNS provider admin that the name servers I used, which I got from Heroku ([haiku].herokudns.com) does not have IP address. Is there anything I did wrong on the configuration?
As it turns out I managed to find my own mistake! It turns out that I provided the DNS Target as Name Server to my provider, which is totally not the same thing. What solved my problem was simply asking the provider to register a CNAME with the DNS target from Heroku as the value.
Be sure to provide the correct DNS Target for the domains as the DNS Target produced for registering root domains like your-domain.com will be different from the DNS Target produced for registering subdomains like www.your-domain.com or when using wildcard tag (*.your-domain.com). Also, note that Heroku doesn't recommend the usage of A Record for root domains, so be sure that your DNS Provider supports the record types needed as this Heroku article suggests.
Thank you #Ruurtjan Pul for getting in touch! Hope this helps!
we are using route53 to manage our domain, however our www.ourdomain.com is not resolving to https.
1) Currently, we have an AWS Classic Loadbalancer with an certificate installed so that we can serve the following domains:
admin.ourdomain.com
2) The certificate we created with AWS Certificate Manager, has registered www.ourdomain.com, and ourdomain.com, as well as admin.ourdomain.com. All have been set up successfully.
3) In Route53, our admin.ourdomain.com has an A record pointing to the ALIAS of our loadbalancer.
4) In Route53 www.ourdomain.com has an A record pointing to two external IP Addresses which are firebase servers hosting our mobile app.
www.ourdomain.com is NOT resolving to https. What must we do to have them resolve to hTTPS?
I figured out the problem. I actually had to wander over to Firebase, login, and click on hosting. I then pressed "Add a domain" and added www.ourdomain.com.
It then asked me to verify the domain with a TXT record, which I added to Route53.
It then verified after waiting a bit. After this, Route53 asked me to add two A records .. which I did... after about 1 hour, our domain resolved properly to https
Heroku DNS is causing troubles: cannot recieve any email at myuser#stickersgallito.pe that uses Google Suite as Mailbox.
My host provider is Punto.pe a peruvian company.
My projects is hosted in Heroku, in there I've 2 DNS:
1) www.stickersgallito.pe -> ancient-crab-bwwmzXXXXXXXXXXXX.herokudns.com
2) stickersgallito.pe -> functional-wallaby-XXXXXXXXXXXXXXXX.herokudns.com
I need that people can visit the site entering: www.stickersgallito.pe or just stickersgallito.pe.
So I've entered these 2 records as CNAMEs in my Host Provider Registry Panel.
Problem:
I've also set up other tools like MailGun and Google Suite (to have mailboxes like omar#stickersgallito.pe). MailGun functions correctly, I can visit the page either using: www.stickersgallito.pe or stickersgallito.pe.
But I cannot recieve emails at omar#stickersgallito.pe.
I've consulted my Host Provider and the say that the record for
stickersgallito.pe ->
functional-wallaby-XXXXXXXXXXXXXXXX.herokudns.com is the
problem. It's interfering with other records.
They don't offer any solution, but point to Heroku for a response.
Heroku point me to their documentation and if after following it's steps it doesn't work I should talk to my Host Provider.
My host provider says that if I can provide an IP Address from Heroku we could solve this. Heroku's doesn't offer an IP address as far as I know.
Google Documentation to Set Up MX Records:
https://support.google.com/a/answer/140034?hl=en
What can I do?
DNSs in Host Provider:
Registers:
UPDATE 1:
This is the kind of records my Host Provider allows me to enter: A, CNAME, TXT, MX.
When using heroku domains I get:
The CNAME record is forbidden for the root domain exactly for this reason, it doesn't allow any other records you have to work the way you want them to. In the heroku docs they say to use a CNAME like functionality for the root domain, which is ALIAS or ANAME record, but don't use CNAME, your provider should not even allow you to create it.
You can configure heroku to work for a subdomain (e.g. www) and then use a Web Forwarding/Redirecting for the root domain to the www subdomain, if your DNS host doesn't support ALIAS or ANAME record. Contact them for more information.
Here is more info about the root domain configuration: https://devcenter.heroku.com/articles/custom-domains#add-a-custom-root-domain
And here is for a subdomain: https://devcenter.heroku.com/articles/custom-domains#add-a-custom-domain-with-a-subdomain
I am hosting Tableau Server on Amazon Web Services (AWS) EC2. My domain name is ec2-xx-xx-xxx-xx.xx-xxxx-x.xxxxxxx.amazonaws.com. I would like to convert http to https, so I want to get a SSL certificate. When I asked a certificate authority (CA), they told me that my domain includes "amazonaws.com", so I couldn't get a SSL certificate. I then tried to get a SSL certificate from AWS, I received an error message.
Error message.png
This was due to the fact that I couldn't request a certificate for Amazon-owned domain name ending in "amazonaws.com".
Does anyone know how to deal with this issue?
Sincerely,
Kazumi
Looks like you need to understand the basics of the process of purchasing a domain name, assigning an IP address to the domain name, purchasing an SSL certificate etc.
Below steps are the easiest and the cheapest way to make your endpoint be served by SSL on AWS infrastructure:
Purchase a domain name eg. knozawa.com from AWS Route 53
Create a new SSL certificate free of cost using AWS
Certification Manager (ACM)
Add your EC2 instance which hosts the Tableau server behind an ELB. The ELB
should be configured to accept traffic over port 443 only. Select
the certificate created using ACM to serve for SSL traffic over port
443.
Go to Route 53, and created a hosted zone entry like
tableau.knozawa.com and add the ELB alias to the entry.
And you are done! You can now access your Tableau installation on your own domain name, serving traffic over SSL on the link https://tableau.knozawa.com
This will probably cost you and additional USD 12.00/year for the domain name, $10-$20 per month for ELB based on traffic.
We purchased and installed an SSL Certificate on our Heroku app, and install the SSL endpoint. The domain is using nameservers that point to a separate cPanel hosting account. I have tried to add a CNAME record in cPanel that points to our Heroku secure endpoint.
I setup the CNAME like this:
Name: *.domain.com.
Type: CNAME
Record: example-7245.herokussl.com
But is has been a whole day and the url still doesn't to heroku. Is this even possible to do this way? We need the email to run off the cpanel host so if we could just use a cname record for the domain server it was perfect.
Thanks for any help.
Not sure why but when I added the DNS add-on Zerigo DNS Zerigo Tier 1, it started to work.