Ok I tried and changed NameVirtualHost <a href="http://192.168.0.105">192.168.0.105</a> for all virtual hosts and I still got the same result. You can see only the first <NameVirtualHost <a href="http://192.168.0.105">192.168.0.105</a>> page. Every outside connection will come on this address, port 80, and it works with the first site but not the others. Do I have to put a different internal address and how do I tell the computer to add another internal address? Is it because I use the same settings for all virtual hosts that the computer can't find it. I would think it is my problem but I don't know how to solve it. I tried to put the first with my public IP and the others with <a href="http://192.168.0.105">192.168.0.105</a> but it didn't change the result. Thanks Meg <div class="gmail_quote">On Feb 3, 2008 7:25 PM, Karl Auer <<a href="mailto:kauer@biplane.com.au">kauer@biplane.com.au</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">On Sun, 2008-02-03 at 18:34 -0500, Ashley Benton wrote: > I am trying to set up apache2 to see more than one virtual host but > don't find my error. Each time I try to see one of the three examples, > Apache served me the first site I configured and can't find the > others. </div>It sounds like you didn't use the NameVirtualHost directive. ... NameVirtualHost <IP address of server> ... <VirtualHost <IP address of server>> ... </VirtualHost> <VirtualHost <IP address of server>> ... </VirtualHost> ... <div class="Ih2E3d"> > Just one more question, do I need to Buy a DNS if I need them on > internet later? and for now do I need to install bind9 and configure > it? </div>Name service is needed if you want to find the sites by name. As long as you are accessing these sites from only one or two machines, you can use /etc/hosts on those machines, and you can use private addresses. If you want to go public, and have your sites visible on the Internet, you will need to obtain public IP addresses, advertise them in the global DNS, and (obviously) change the Apache config to use those addresses. A (poor) alternative would be to put the server behind a NAT and direct all your site names to the same IP address using a dynamic name server. Regards, K. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Karl Auer (<a href="mailto:kauer@biplane.com.au">kauer@biplane.com.au</a>) +61-2-64957160 (h) <a href="http://www.biplane.com.au/%7Ekauer/" target="_blank">http://www.biplane.com.au/~kauer/</a> +61-428-957160 (mob) GPG fingerprint: DD23 0DF3 2260 3060 7FEC 5CA8 1AF6 D9E3 CFEE 6B28 Public key at : <a href="http://random.sks.keyserver.penguin.de" target="_blank">random.sks.keyserver.penguin.de</a> -- ubuntu-users mailing list <a href="mailto:ubuntu-users@lists.ubuntu.com">ubuntu-users@lists.ubuntu.com</a> Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/ubuntu-users" target="_blank">https://lists.ubuntu.com/mailman/listinfo/ubuntu-users</a> </blockquote></div>