In OpenShift both mydomain.com and www.mydomain.com are configured as aliasses of myapp-rhcloud.com. Same for cloudflare.
I tried with the following coment: DNS settings openshift cloudflare
'www.mydomain.com' work fine, but the naked domain 'mydomain.com' redirects me to an error page that says: "The connection is not private. It is possible that unauthorized users are trying to steal your information" the Link change from example.com to https:// example.com/app with the 'https' denied.
Also an icon appears next to the CNAME in CloudFlare:
"Flattening CNAME will be applied to this record since root (ie apex) CNAME records are limited by the DNS specification." I dont understand that.
I modified the rules in cloudflare like this:
redirects "http:// example.com/*" to "http:// www.example.com/$1"
with '301' for the redirect type
I'm missing something?
After a few days my page example.com it worked. The link in my question works right, the problem was that CloudFlare took 4 days to establish the rules associated in the CNAME.
In conclusion... just wait.
Related
How can I configure DNS CNAME or another record which do the following requirement?
existing domain with its URL: example.com/brand/main/top
another domain: newdomain.com
My need is when I hit newdomain.com, it opens the existing domain URL (example.com/brand/main/top) with newdomain.com.
In CNAME,
you can only point one domain to another domain.
path or url can't be mentioned in dns records.
to reach the url, you can configure htaccess to redirect incoming request of
newdomain.com to example.com/brand/main/top
I have a website on an Azure app service and we are going to go live soon.
I've followed what has been suggested so I've created a CName to my Azure sub-domain. How can I make sure that google will not index my site as xxx.azurewebsites.net instead of xxx.com ?
Right now I have IP restrictions available, so google cannot see my website and index it, but when we go live both xxx.com and xxx.azurewebsites.net will be open to public. Right?
Add permanent redirects (301) in the app.
So if someone accesses a page e.g. aaa.azurewebsites.net/Something, redirect them to aaa.com/Something with a 301 redirect.
It was the first that came to my mind, but Google has more guidance on canonical URLs here: https://support.google.com/webmasters/answer/139066?hl=en
Best you can do is add a robot.txt file for google and other robots that try to index your site.
Robots_exclusion_standard
The host directive can have the preferred domainname:
Host: example.com
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.
I have an Azure Websites URL at http://mysite.azurewebsites.net. Attempting to browse to http://www.[mysite].azurewebsites.net/ results in a DNS lookup failure, with the error code in Chrome of "ERR_NAME_NOT_RESOLVED"
I've attempted to add www.[mysite].azurewebsites.net in "Manage custom domains", but receive the message "The host name www.[mysite].azurewebsites.net is invalid."
Note that I don't have a custom domain and I'm happy to use the .azurewebsites.net URL, I simply would like the users who add "www." to the URL they've been given to resolve to the correct URL.
Is this possible with Azure Websites without requiring a custom domain?
The menu from your screenshot can be used to configure any domain, you own, to point to your azurewebsite, this is not what you want.
Your "website" is a subdomain (level 3) of domain azurewebsites.net, where "azurewebsites" is a level 2 domain and "net" is the TLD. "www" is a subdoamin and normally used as (level 3) subdomain in ealier days to point out, that you are using the World Wide Web. This is not necessary and it does not make sense to create a level 4 subdomain "www". I don't even think, level 4 subdomains are supported by azure anyway.
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).