Domain Forward in Plesk - dns

I have mysite.eu working fine, and I have registered a new site mysite.co.uk which I would like to forward to mysite.eu. According to various articles on the net, this is a pretty straightforward procedure yet, I can't make it to work since when i type mysite.co.uk I get a "This site can’t be reached www.***uppies.co.uk’s server DNS address could not be found". Here are my current settings:
and the .co.uk site hosting settings
Do i also have to edit the DNS settings maybe?

Error massage you have see is about domain name and DNS, not about forwarding.
If you have recently register new domain, than DNS record of .co.uk site may be not propagated to all DNS servers and you have to wait about 24 hours.
Also check that you have www record of your new .co.uk domain:
Check for no-www record:
nslookup <you domain name here>.co.uk
Check for with-www record:
nslookup www.<you domain name here>.co.uk
If you need www part for domain you can add in your domain's registration panel.

Turns out the domain registar had not completed the .co.uk domain registration properly.

Related

How to redirect naked domain to www in Google Domain?

I have a domain name mydomain.com registered at Google Domain. I would like to use it for a static website in Azure.
I would really love to use my naked domain rather than the www version, but I don't think it is possible since when I try to create a CNAME from mydomain.com, I get CNAME records for the root domain are not supported. If anyone has a solution, I am interested.
Custom domain in Azure portal tells me to create a CNAME from www.mydomain.com to diamnis.z16.web.core.windows.net, which I did.
Now, how do I get traffic from the naked domain mydomain.com to go to www.mydomain.com in Google Domains?
You can do that in google domain dns. Follow the below steps -
After you have done the CNAME mapping for www.chartvibes.com, do as mentioned below -
To configure the naked domain, add a "Synthetic Record", and set up a
"Subdomain Forward." In the subdomain text box, enter the # sign and
nothing else.
Select option to 'Forward path'. That should do the root domain forwarding.
You can refer to the below official link too - https://support.google.com/domains/answer/4522141

Having trouble configuring custom domains on Xervo

I have a meteor project deployed on Xervo here. I have a domain bought from GoDaddy, ustechland.com. I'm configuring custom domains in my project's administration panel on Xervo.
2
*.ustechland.com means all subdomains of this domain will point to this project. Now when I hit ustechland.com in the address bar, the URL changes to the project URL (https://utl-95476.app.xervo.io), which I don't want to happen.
I have configured CNAME records in my GoDaddy's domain DNS as specified by the Xervo Docs here.
Here is my list of CNAME DNS Records in GoDaddy:
4
Although, the Xervo custom domain docs specify to add two CNAME records, I'm able to add one CNAME record with www subdomain pointing to Joyent Servo in US-East. Another record with naked domain (#) must be added pointing to the same. But I'm not able to add this record as GoDaddy says the record already exists.
Now, is the URL changing because I'm not able to add the CNAME record required? Do try hitting ustechland.com or www.ustechland.com and see the URL change.
And at times, both these URL's take me to 'Future home of something quite cool' page.
I have found several sources that claim that godaddy does not support root cname flattening (which is what you want).
Check out these ideas for how to deal with this.
CNAME Flattening With GoDaddy.
Quora Answer
Good luck!

Domain without WWW on Cloudflare?

I created an app on Openshift and added aliases.
My registrar doesn't allow me to add a CNAME without WWW. So I started using the Cloudflare DNS servers and added 2 CNAME records. In the records page it looks like this:
CNAME porta8080.com.br is an alias of blog-porta8080.rhcloud.com Automatic
CNAME www is an alias of blog-porta8080.rhcloud.com Automatic
I changed it like 3 or 4 ours ago and the domain status is already Active.
If I go to my website it won't be displayed if I omit the subdomain www. . But works well with www.
I wonder if I can do this with Cloudflare (with and without www.) and/or cloudflare is alrady routing for me. I got a free plan.
Thank you
#edit
Now I got a ERR_TOO_MANY_REDIRECTS error. Any ideas on what could this be?
CloudFlare Partner set-ups usually are done via a CNAME set-up. Unfortunately it doesn't strictly comply with an RFC to support a CNAME record on a root domain, accordingly you can either set-up your own CloudFlare account (you won't get RailGun if your host are not just a normal CloudFlare Partner but an Optimised Partner).
The way around this is either get them to support the Full Host set-up which CloudFlare now support or set-up your own CloudFlare account and use a nameserver install.

DNS Settings: OpenShift with CloudFlare / rhcloud

I am trying to set up DNS forwarding on CloudFlare, to my Openshift page (the-domain.rhcloud.com).
But when I go into the CloudFlare DNS settings and try to change the A setting, I get this error:
You entered 'the-domain.rhcloud.com' which is not a valid IP address.
It seems to be asking for a static ip address. It seems that other hosting services can provide a numerical ip address for DNS settings, but I cannot find anything like that on rhcloud / OpenShift.
How can I find my domain's ip address on rhcloud OpenShift? What should basic DNS settings look like on CloudFlare when forwarding to an rhcloud host?
Should I use any of the default A and AAAA settings from my registrar?
It's a bit unusual, but when using services like Openshift/Heroku etc, there is no A record for the domain in your DNS. This is because there is no single A record corresponding to your site or app on the service.
If you've already set up the domain at your registrar using Cloudflare's nameservers (you need to do this!) there should be no need to do anything else at the registrar.
You need to set up one (or more) CNAMEs for the site/app at Cloudlare (if it's a website, you may want one each for e.g. example.com and www.example.com).
Assuming you do need the 'naked' domain and the www version, you'd do this:
Openshift
Make sure you have domains set up for both the 'naked' domain and the www subdomain.
Cloudflare:
Back it up!
Cloudflare lets you export your DNS settings; do this before making any changes.
Naked domain
go to the DNS settings page
choose CNAME from the selector at bottom
enter the-domain in the first field
enter the-domain.rhcloud.com in the second ("is an alias of") field
www subdomain
repeat steps 1-4 from above, but enter www for step 3.
go to the "Page Rules" page
add a new "page forwarding" rule that either:
redirects http://the-domain.com/* to http://www.the-domain.com/$1 or
redirects http://www.the-domain.com/* to http://the-domain.com/$1
choose '301' for the redirect type
If you want your domain name to start with https://www, take a look at the steps bellow that worked for me.
Let's say we want to configure cloudflare and openshift for this domain name: example.org.
Cloudflare
DNS page
I have two records set:
Type: CNAME Name: example.org Value: example-example.rhcloud.com (you should see CNAME flattening sign for this one)
Type: CNAME Name: www Value: example.org
"Page rules" page
Two rules:
http://www.example.org/* Settings: Always use HTTPS
example.org/* Settings: Forwarding url, 301 — Permanent redirect, https://www.example.org/$1
OpenShift
Add one alias:
www.example.org

Azure Websites DNS

I have an azure website at yis3.azurewebsites.net - I have promoted this to be a "shared" site so that I can use a custom domain. I have the domain yorkshireimagescanning.co.uk that I bought from 123-reg.co.uk. I have configured this to give a CName record with dnsname of "awverify" and destination of awverify.yis3.azurewebsites.net.
I've waited over 12 hours and checked on digwebinterface.com and all looks good but when I click to "Manage custom domains" from the Azure portal , I enter a domain name of "yorkshireimagescanning.co.uk" but it won't accept it.
Please help
* Edit *
I've now waited a couple of days for domain propagation. Here's a screen grab from my domain registrar:
In the azure portal I've tried to add the following custom domains for the yis3.azurewebsites.net site but it won't accept any:
awverify.www.yorkshireimagescanning.co.uk
www.yorkshireimagescanning.co.uk yorkshireimagescanning.co.uk
awverify.yorkshireimagescanning.co.uk
Here's a screen grab from the portal:
To use yorkshireimagescanning.co.uk
To use your domain without the www. prefix you need to add an A Record in addition to the CNAME you've added for "awverify".
First, make sure you've added the domain to the Azure portal by following the instructions under "Set the domain name in management portal" here.
Next, follow the instructions under "Configure an A record for the domain name" on the same page. This involves pointing your domain directly at the IP address of the Azure web site. You should then have added 2 DNS records in total:
CNAME awverify.www awverify.yis3.azurewebsites.net
A xx.xx.xx.xx (your website's IP address)
I've marked the next option as "preferred" because it points your domain at the Azure hostname "yis3.azurewebsites.net" instead of directly at the IP address. The IP address of your Azure website won't change, but if you ever need to deploy your website elsewhere it will have a different IP, so there will be a delay while the DNS change propagates.
To use www.yorkshireimagescanning.co.uk (preferred)
To use your domain with a www. prefix you need to add another CNAME record in addition to the one you've already added.
First, make sure you've added the domain to the Azure portal by following the instructions under "Set the domain name in management portal" here.
Next, follow the instructions under "Configure the CNAME on your domain registrar" on the same page. This involves adding a CNAME that points "www" to your Azure website's hostname (yis3.azurewebsites.net). You should then have added 2 DNS records in total:
CNAME awverify.www awverify.yis3.azurewebsites.net
CNAME www yis3.azurewebsites.net
A note about domain forwarding: Don't use 301 forwarding unless your site has been permanently moved. Use 302 for temporary redirection. More details here.
I finally figured out what was wrong. I was deploying a new version of an existing site but the old version still had www.yorkshireimagescanning.co.uk set on the custom domains page. Once I deleted it then I was able to add the domain on the new azure site.

Resources