hope someone can help me after my update to plesk 11.
I have 4 domains and 2 of them are not reachable after update to plesk 11.
Before all domains were reachable:
http://www.mydomain.com
www.mydomain.com
mydomain.com
now it only works with:
mydomain.com
If i go to www.mydomain.com there is a default page:
It works!
This is the default web page for this server.
The web server software is running but no content has been added, yet.
check with your cname record for domains www added and also check with your dns template
Related
OK, please go gentle on me as I am a bit of a beginner when it comes to domains.
My old website was hosted by Squarespace and the Domain provided by GoDaddy and was set up to use SSL (by ticking that option within the Squarespace settings). For this example, let's say the domain was myoldsite.co.uk
This site is now closed down and no longer active on Squarespace.
All of my backlinks over the last 3 years have been created for https://myoldsite.co.uk
Recently, I have created a new Wordpress site again using SSL using the domain name: https://mynewsite.co.uk
Within the GoDaddy admin console for myoldsite.co.uk, I have created a 301 redirect going to https://mynewsite.co.uk
This is working well when I enter http://myoldsite.co.uk, I am forwarded to https://mynewsite.co.uk
However, when I enter https://myoldsite.co.uk, nothing happens and I am not forwarded.
So I have 2 questions:
Is it posible for all old backlinks created using https://myoldsite.co.uk to correctly forward?
By creating the 301 redirect, does this work at the domain level and http / https is not relevant when passing down all the SEO juice?
Thanks in advance,
Duncs
I want to refer one subdomain from another server to another subdomain on other server.
For example.
new.example.com is on SERVER1
dev.mydomain.com is on SERVER2
I need that when customer enter to new.example.com he see the website of dev.mydomain.com
I changed the DNS A records of new.example.com to the IP of dev.mydomain.com, but I need to do something on dev.mydomain.com
What configurations can I do on dev.mydomain via WHM .
Thanks
Instead working with DNS & IP the smart thing you could do is redirect new.example.com to dev.mydomain.com. You can do this by accessing Redirection option under example.com Cpanel account.
I have two hosting accounts (Personal one and a work one). I am doing some testing and would like to create a subdomain of a work domain (manage.domain.com) and host it on my personal account. Currently, my personal host is through 1and1 and is dedicated while the work one is shared with GoDaddy.
Work
I have gone into go daddy and created the subdomain. I have also added DNS records such as A, AAAA AND NS (i did not record a CNAME). I have noticed that if is type manage.domain.com it is redirecting to my personal server. However, it is directing to the blank admin page of the root of the server (which is maintained using Plesk).
Personal
Using Plesk I added the website (domain.com) and created the subdomain (manage.domain.com). I have also updated the websites hosting access using Plesk and assigned it the default values of my personal account. Using Plesk I also set the subdomain to the particular location of the files I want to test. However, I cannot get my server to recognize the address and redirect it to the proper location.
Any help is greatly appreciated!
J
You can just create:
in personal account domain(not subdomain) manage.domain.com
on domain.com add DNS record of type A, name "manage" and IP address of personal hosting:
After that "manage.domain.com" will resolving to hosting of your personal account and can be accessed because such domain exists.
I figured it out
What i did above was correct expect do not change the name servers on the work DNS(godaddy).
Add the website to plesk - it will give you an error about not being able to control the DNS settings which you have already adjusted on the original server (godaddy)
Add a subdomain of the website.
*** Ensure the subdomain is pointed to the correct folder within your server
Done
This has to be simple. I have an A record that points to my server just fine. However, I just added a CNAME for a "www".website.com that points to website.com, but it is now just returning an Nginx 404 error. For reference, I'm using Laravel Forge to deploy the server and of course AWS Route 53 for DNS.
I want to post an answer in case anyone comes across this issue like I did. I was unaware that this can be solved by configuring the Nginx config file and through Laravel Forge, it's pretty easy.
On my server, I have 2 sites (one pointing to site.com and one pointing to www.site.com). In my DNS provider (AWS Route 53), I have an A record for each URL and both point to the public IP of my server.
So, I go into the Nginx config (through Laravel Forge) for the site I want to redirect (in this case I want to go from www to non-www) and edit the config file to include the following.
server_name www.site.com;
return 301 $scheme://site.com$request_uri;
Works perfectly now!
To replace a legacy web site, a client has pointed their DNS at my server where a new version of the website exists.
However they still serve http://support.example.com from their own server.
I have noticed that non-www requests, e.g. http://example.com still point to their own server, therefore show the old web site.
How can I point non-www requests, http://example.com at my server without breaking the functionality of their 'support' sub-domain?
The client's server is a Microsoft server, mine is Linux/Apache
Edit: Changing the DNS 'A' record will not break the existing sub-domain
I know I could add an index.html page to the front of the old site, but if it was ever deleted the page requests would cease to work
I can't use mod-rewrite because I don't have access to their web server files
PROPOSED SOLUTION:
On the client DNS, create an A
record for:
support.example.com – IP of the client's server
example.com – IP of my server
www.example.com - IP of my server
No need for any DNS changes on my server regarding this domain
Changing the A record for example.com won't affect the A record for support.example.com.