CapnPugwash Posted December 17, 2014 Posted December 17, 2014 We have an Ubuntu server running Apache, from which we host our website (Joomla) & VLE (Moodle). Each has a separate IP address. In the new year we are changing the name of our school, so we are in the process of registering a new domain name. for a couple of months both the old domain name and the new one will exist. I want both domain names to point to the same sites. Is this as easy as creating new virtual host files in apache2/sites-available and enabling them? Example : In my sites available I currently have four virtual host files, myschool, myschool-ssl, myschoolvle, myschoolvle-ssl. Can I create four more virtual host files myNEWschool, myNEWschool-ssl, myNEWschoolvle, myNEWschoolvle-ssl, pointing at the same website/VLE and IP address but with different domain names? *NOTE* I know I'll need new SSL certs!
Blue_Cookeh Posted December 17, 2014 Posted December 17, 2014 You can do this with non-SSL websites for sure, and it is just a case of using virtualhosts as you outlined... but (and I may be wrong!) adding SSL using just one IP address gets a little more complex and involves extra setup. I can't remember the name of the configs now though, sorry
Bradlys Posted December 17, 2014 Posted December 17, 2014 Forgive me if I'm missing this. If you're still hosting the old site on one of the IP addresses, you can use .htaccess to redirect. make a file called .htaccess in the root of your old site and paste this in it: # This allows you to redirect your entire website to any other domain Redirect 301 / http://newdomain.com/
dhicks Posted December 17, 2014 Posted December 17, 2014 Is this as easy as creating new virtual host files in apache2/sites-available and enabling them? Should be even easier - both domain names will point to the same IP address, your Apache server will simply serve web pages, no matter what domain name the browser thinks it's looking at.
CapnPugwash Posted December 17, 2014 Author Posted December 17, 2014 OK, thanks everyone. It looks like HTTP is easy and HTTPS is a bit more complicated. We get our SSL certs through the LEA. It looks like we can use a SAN cert (a bit like a fancy wildcard cert?) that will cover usage for both domains AND all sub domains. This isn't the kind of stuff I do every day but it *looks* like I shouldn't have too many problems... !!!!!!!!!!!
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now