This issue is become a little complicated to me.
I´m using GoDaddy for my DNS Host and trying to configure my domain in IBM Cloud Application.
I followed the IBM Cloud documentation in Adding and using a custom domain.
My doubt is in how to configure the CNAME in GoDaddy to change my domain from myapp.us-south.cf.appdomain.cloud to www.mydomain.com
The redirection options is working fine for http request (https is not working) when i type www.mydomain.com and then redirect to myapp.us-south.cf.appdomain.cloud but just show my domain in url not.
Any idea to how fix it?
The configuration that I tried and it´s redirecting from www.mydomain.com to IBM Cloud App in GoDaddy is
Tipo Nome completo Valor TTL Ações
A # Parked 600 segundos Editar
CNAME <mydomain>.com <myapp>.us-south.cf.appdomain.cloud 1/2 hora Editar
CNAME www # 1 hora Editar
NS # ns09.domaincontrol.com 1 hora
NS # ns10.domaincontrol.com 1 hora
SOA # Servidor de nome principal: ns09.domaincontrol.com. 1 hora
In IBM Cloud I added my domain in Domains and also in routes I added [www].[mydomain.com]
The reason this is not working is because you need to set the CNAME record to the domain as instructed in the IBM Cloud docs which you linked to. It is misleading, but you have to follow the instructions literally.
Set your CNAME to custom-domain.us-south.cf.cloud.ibm.com. That is the IBM-internal resolver which would map the incoming request to your configured route.
I tried several options to configure CNAME in GoDaddy to IBM Cloud. My last configuration it was that:
In GoDaddy DNS Server:
Type Complete Name Value TTL
A # Parked 600 segundos Editar
CNAME mydomain.com custom-domain.us-south.cf.cloud.ibm.com 1 hora
CNAME www # 1 hora
NS # ns09.domaincontrol.com 1 hora
NS # ns10.domaincontrol.com 1 hora
SOA # Servidor de nome principal: ns09.domaincontrol.com. 1 hora
In IBM Cloud:
In Account, I included domain mydomain.com; and
In App Route, I include as ** .mydomain.com*, in order to associate to www according with the documentation.
What is wrong?
After several searchs in the internet and also in StackOverflow and the contribution of #data_henrik finally I found the right configuration for DNS between GoDaddy and IBM Cloud (Cloud Foundry Application).
As mentioned before, is necessary to follow the steps Adding and using a custom domain as bellow:
Adding a custom domain from the IBM Cloud console
Adding the route with the custom domain to an app - in my case I create the route as www + mydomain.com if you left the first field in blank, the URL will not be resolved by IBM Cloud Domain Service. Another important information is that IBM Cloud change the name of my original application route because in my case the name was the same of my domain (intersting).
In GoDaddy, the right configuration are bellow:
Type
Complete Name
Value
TTL
Note
A
#
169.62.254.80
600 sec
The # parameter must be pointed to the custom-domain server IP, in my case us-south server
CNAME
mydomain.com
custom-domain.us-south.cf.cloud.ibm.com
1 hour
As mentioned before by #data_henrik
CNAME
www
#
1 hour
Just redirect www to the current domain
NS
#
ns09.domaincontrol.com
1 hour
Default
NS
#
ns10.domaincontrol.com
1 hour
Default
SOA
#
Server main name: ns09.domaincontrol.com.
1 hour
Default
Related
I wanted to know if such a scenario is possible:
I have a domain hosted in GoDaddy - say example.com
I go to Cloudflare, create that domain, take the nameservers, and configure them in GoDaddy
I go to AWS Route53, create hosted zone, take 4x NS records that were generated and insert them in Cloudflare as NS records separately
So its: GoDaddy -> Cloudflare -> AWS Route53
And now - should I be able to manage my domains via AWS Route53?
I figured it out and it seems that doing what I described above is impossible for the root domain, like example.com.
Meaning that if in my domain registrar I point to different Nameservers for example.com only those are valid and I cannot configure NS records for example.com further. So:
I buy example.com at GoDaddy -> all good
I login to Cloudflare, add new domain, receive Nameservers: a.ns.cloudflare.com and b.ns.cloudflare.com -> all good
I go to GoDaddy and configure Nameservers to be those from point 2 -> all good
Now I login to AWS, go to AWS Route53 and generate HostedZone for example.com. I receive 4 Nameservers: a.aws.com, ... d.aws.com -> all good
Now I go to Cloudflare example.com domain records and try to configure the 4x NS records for those four I got from Route53 -> thats NOT good
In point 5 this is not going to work.
However!
It is possible with subdomains. So if in point 4. I would have created HostedZone for test.example.com I would have been able to go to Cloudflare and point test.example.com with NS records to those 4x Nameservers that I get from Route53 and manage test.example.com and *.test.example.com from Route53.
If I am wrong in anything please correct me!
Suppose I own example.com.
I delegate the subdomain www.example.com to a particular set of NS that is say a Route53 Hosted Zone. The rest of the example.com zone is not on R53 and contains important information for other subdomain/records. You can consider this Zone 1, and you can consider the new R53 Hosted Zone as Zone 2.
I want to have www.example.com CNAMEd to a particular endpoint, say a cloudfront distribution.
Since I can't CNAME the apex domain, instead hosted zone 2 is created in R53 with the original apex domain: example.com.
Then, inside that hosted zone, there is a record for the subdomain www.example.com with the CNAME to xxx.cloudfront.net.
I can't directly configure www.example.com with the CNAME in hosted zone 1 for various reasons, including that the CNAME is always changing and the person controlling the CNAME only has control over zone 2.
So the full chain looks like this:
User types in www.example.com, they get NS hosted 1 records. In that zone, the record for www.example.com points to Hosted zone 2 records. In this zone (which was created with apex example.com) the record for www.example.com is a CNAME to the proper endpoint.
My question: will any DNS resolvers mistakenly cache the NS from the second zone as apex domain records? Obviously, I want those NS accessed only for the www.example.com records. If example.com NS are mistakenly thought of as in hosted zone 2, there can be a lot of issues.
If this is the case, is there any way to make sure to dns resolvers that the apex domain nameservers are zone 1, and zone 2 records are ONLY for www.example.com, even though they were created with the example.com apex domain?
I understand that there are other ways to do this (CNAME to sep domain, etc) but for logistical purposes (for now) I am only interested in setting the NS directly for the www subdomain.
Thanks in advance.
I have domain on google domains and I want it to point to my Azure Web app.
I have followed the documentation of Microsoft and this topic and SO.
My actual configuration on Google Domains look like this:
Name server:
Use custom name servers
ns31.domaincontrol.com
ns32.domaincontrol.com
Registered hosts:
hostname: mywebsite.com
ipv4: 40.122.xxx.xxx
ipv6:
Custom ressource records:
# A 1h 40.122.xxx.xxx
# TXT 1h "mywebsite.azurewebsites.net"
awverify CNAME 1h awverify.mywebsite.azurewebsites.net.
www CNAME 1h mywebsite.azurewebsites.net.
Then I try to add a new custom Domain name on my web app but when I try to "mywebsite.com" or "www.mywebsite.com" Azure can't know if I own the domain ...
We have waited more than 48hours and checked all the typo but didn't see any mistake.
Do we need to something more on Azure ? Did I missed something ?
Thank you for your answer
EDIT:
My current ressource records now look like this:
# A 1h 40.122.xxx.xxx
# TXT 1h "mywebsite.azurewebsites.net"
www CNAME 1h mywebsite.azurewebsites.net.
In this case, the following records are not correct. It will be like this.
# TXT 1h mywebsite.azurewebsites.net
awverify.www TXT 1h mywebsite.azurewebsites.net
www CNAME 1h mywebsite.azurewebsites.net
The entry with the awverify subdomain is used to "prove" to Azure that you own that domain when you migrate a live site and its DNS domain name to App Service that DNS name is already serving live traffic. If your custom domain has not been used for live traffic yet. You do not need to add such awverify subdomains in the DNS zone, just remove it.
Moreover, the TXT record you need depends on the DNS record you want to migrate. For examples, see the following table (# typically represents the root domain):
You can use dig web interface to check the DNS records propagation. Once the DNS propagation is established, you do not need the awverify subdomains and remove them.
Get more details: Migrate an active DNS name to Azure App Service
We're trying to set up Cloudflare prior to our launch. We initially registered our domain with Route 53 and want to keep it there... For context, our servers are hosted by DigitalOcean
We set up Cloudflare and went through the flow about 24 hours ago. We changed the NS entries on Route 53 to Cloudflare.
However, when we go to sites like http://www.whoishostingthis.com/, it's still showing Digital Ocean.
We also have a subdomain - c.opencritic.com - for our image deploy pipeline. This is showing similar results.
Here are our current entries:
ON ROUTE 53
A - opencritic.com - IP of server
MX - opencritic.com - Gmail web servers
NS - opencritic.com -Cloudflare name servers
SOA - opencritic.com - long Amazon string during setup
CNAME - c.opencritic.com - Alias of opencritic.com
CNAME - www.opencritic.com - Alias of opencritic.com
ON CLOUDLFARE
A - opencritic.com - IP of server
CNAME - c.opencritic.com - Alias of opencritic.com
CNAME - www.opencritic.com - Alias of opencritic.com
What are we missing?? Why aren't we being routed through Cloudflare?
Cheers,
Matthew
Solved...
Route53 has two different places for DNS records: the actual name servers listed on the domain registration page, and the NS records.
We had editted the second, but not the first.
I've been working on trying to get my own domain, for example mydomain.com, hosted in Azure Websites.
I upgraded/scaled to change my setting to "Shared".
I added CNAME record from www.mydomain.com to mydomain.azurewebsites.net.
I added www.mydomain.com to my website in azure under "Manage Domains", and it allowed me to add it successfully.
I am able to browse successfully to the website with www.mydomain.com.
I changed the A record for mydomain.com to point to the IP address listed under the Manage Domains section of the Azure website.
The CNAME and A record have propagated based on testing on my machine and on centralops.net DNS lookup tools.
If I browse to mydomain.com I get a 404. www.mydomain.com works as expected.
Can anyone help?
Step by step. This is working for me.
1 - In your DNS registrar create a CNAME record like following.
Name = awverify.mydomain.com
Value = awverify.mydomain.azurewebsites.net
TTL = 86400
2 - In Azure panel, add mydomain.com to your custom domains. It should show green check.
3 - Go back to your DNS registrar's web site and add an A Record for your custom domain using to IP provided to you by Microsoft in Azure Portal.
Name = mydomain.com
Value = 64.49.121.33
TTL = 7200
More info here.
I can think two options:
a) The Azure web server needs to be configured to browse your site with both www.mydomain.com and mydomain.com. Maybe you have configured only one in "Manage Domains"
b) mydomain.azurewebsites.net. resolves to a different IP than mydomain.com (the A Record you added in mydomain.com is wrong)
you need to work with a DNS provider that allows you to forward the A record to a DNS (Go Daddy provides this option) - i.e. www.mydomain.com points to mydomain.azurewebsites.net and mydomain.com is forwarded to www.mydomain.com