Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
This may be a dumb question, but the following not clear to me:
I want to host a couple of public vanity web sites. Just a couple. I don't want to run DNS at all if I can help it. One is my domain, another for running another for a crazy site idea I had. If I get my dns/domain provider to point both domains to my server, then what I -think- should happen on my server is:
/etc/network/interfaces
Add a second virtual IP address off of eth0.
eth0 192.168.XX.YY
#static IP and everything else I need to add
eth0:1 192.168.XX.YY+1
#static IP and ...
/etc/hosts
revise file for two IP/names.
127.0.0.1 localhost
192.168.XX.YY Myvanitydomain.com
192.168.XX.YY+1 Mycrazywebsite.com
/etc/apache2/virtual-hosts
myvanitydomain.com pointing to /home/dir1
mycrazysite.com pointing to /home/dir2.
Firewall
Currently my firewall correctly forwards webserver traffic to my server where a single place holder sits. I don't think I need to do anything with the firewall.
hmmm, not really where you want to be going at all really... not sure how multiple ip's are supposed to help you on an internal LAN. if you had multiple *public* ip's then that's a different A record in DSN for each domain, which is fine, but under a private LAN they're no use unless your router can proxy at http level.
essentially all you need to do is read up on virtualhosts a bit more and you'll see it's actaully a *lot* easier to do than you think. a virtualhost will take the host header of an http request and match that to a different site, so one ip is all you need.
hmmm, not really where you want to be going at all really... not sure how multiple ip's are supposed to help you on an internal LAN. if you had multiple *public* ip's then that's a different A record in DSN for each domain, which is fine, but under a private LAN they're no use unless your router can proxy at http level.
essentially all you need to do is read up on virtualhosts a bit more and you'll see it's actaully a *lot* easier to do than you think. a virtualhost will take the host header of an http request and match that to a different site, so one ip is all you need.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.