I created LAMP server with a wordpress site. I created a sites-available file for the wordpress file pointing to the wordpress directory. Within my server it goes to the site properly. However I also made this server a DNS server, had another test pc use it as a DNS server and it only got the default apache page unless I added /wordpress to the url which makes it point to the directory within /var/www/ that it belongs, but then the wordpress links don't work and this is not what I want it to do anyway. I do not understand why it is working properly internally but not externally. It makes me think maybe the sites-available file is not allowing outside access appropriate permission to use it or something. Can somebody please point me in the right direction I have been working on this for weeks and I am starting to get really frustrated with it. Tell me what config files can help you figure out my issue. Also I eliminated the default index.html file so it wouldn't use it, then placed the index.php file from wordpress in /var/www/ root but in that configuration it doesn't load anything by default but will still work if you point to /wordpress. I believe I have to make some change to my apache2 configs to allow outside PCs to be pointed to the right root directory for the virtual host like is being done internally, I just don't know where to start. Thank you.

Here is my sites-available config file-
NameVirtualHost www.mysite.local:80

<VirtualHost www.mysite.local:80>
ServerAdmin myname@localhost
ServerName www.mysite.local

DocumentRoot /var/www/wordpress/
<Directory />
Options Indexes FollowSymLinks MultiViews
AllowOverride None
</Directory>
<Directory /var/www/wordpress/>
Options Indexes FollowSymLinks MultiViews
AllowOverride None
Order allow,deny
allow from all
</Directory>

ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/
<Directory "/usr/lib/cgi-bin">
AllowOverride None
Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch
Order allow,deny
Allow from all
</Directory>

ErrorLog ${APACHE_LOG_DIR}/error.log

# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
LogLevel warn

CustomLog ${APACHE_LOG_DIR}/access.log combined

Alias /doc/ "/usr/share/doc/"
<Directory "/usr/share/doc/">
Options Indexes MultiViews FollowSymLinks
AllowOverride None
Order deny,allow
Deny from all
Allow from 127.0.0.0/255.0.0.0 ::1/128
</Directory>

</VirtualHost>

Hi,

Once you've created a vhost file under sites-available (e.g. /etc/apache2/sites-available/mysite.local), you should run:
to create the needed symlinks and of course reload apache.
BTW, there is a /etc/apache2/conf.d/virtual.conf, where NemeVirtualHost is defined and it's better to use:
Then in /etc/apache2/sites-available/mysite.local use just:Regards

that does not work it instead brings up an error that states the virtualhost is not named. Please somebody help, I'm guessing this is either a DNS issue or it is an issue where the virtual host naming feature is not working. By the way I already used the a2ensite command to enable the site. Also I do not have virtual.conf file in my conf.d directory and when I create it like you said it only brings about that no name for virtual host error.

I discovered that the issue was that I needed to add a line to my /etc/hosts file that had my ip address paired with the host names I was using.

i was looking for some in formation on virtual host on server..
Any body here to help me.