Apache's mod_rewrite or Digital Ocean's DNS Records?

Posted on May 17, 2013

I was trying to figure out how to redirect a website such that www.example.com will lead to example.com instead of giving me a 404 error when I saw this Apache guide:

http://httpd.apache.org/docs/2.4/rewrite/remapping.html

I am wondering will this be better than using the DNS records in Digital Ocean’s GUI, considering that the DNS records are still not working despite setting them up last night (They should have propagated by now…)

Thanks!

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Kamal Nasser

May 17, 2013

You have to have DNS records for your subdomains to resolve to your droplet. You should also configure apache properly to redirect from non-www to www (or from www to non-www).

gioarteaga

May 18, 2013

Make sure you point the IP of the server to your dns records. @ A xxx.xxx.xxx.xx www CNAME @ or www A xxx.xxx.xxx.xx Add the following to your .htaccess. # From www to non-www <IfModule mod_rewrite.c> RewriteEngine On RewriteBase / RewriteCond %{HTTP_HOST} ^www.domain.com$ [NC] RewriteRule ^(.)$ http://domain.com/$1 [R=301,L] </IfModule> From non-www to www # Force www in HTTP RewriteEngine On # line below is optional # RewriteCond %{REQUEST_URI} !^/(blog|blog.domain.com) RewriteCond %{HTTP_HOST} ^domain.com # RewriteCond %{SERVER_PORT} 80 RewriteRule ^(.)$ http://www.domain.com/$1 [R=301,L]