Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have two domains, and

When I go to, everything works. When I go to, it also goes to the front page. If I go to, it goes to the forum subdirectory of as expected.

The virtual host directives in apache look like this, my server is running CentOS, if that makes a difference:

NameVirtualHost *:80
<VirtualHost *:80>
    DocumentRoot /var/www/mycommunitysite
    ErrorLog logs/

<VirtualHost *:80>
    DocumentRoot /var/www/mypersonalblog
    ErrorLog logs/

The output of apachectl -S

httpd: Could not reliably determine the server's fully qualified domain name, using for ServerName
VirtualHost configuration:
wildcard NameVirtualHosts and _default_ servers:
*:80                   is a NameVirtualHost
         default server (/etc/httpd/conf/httpd.conf:1015)
         port 80 namevhost (/etc/httpd/conf/httpd.conf:1015)
         port 80 namevhost (/etc/httpd/conf/httpd.conf:1025)
         port 80 namevhost (/etc/httpd/conf/httpd.conf:1035)
         port 80 namevhost (/etc/httpd/conf/httpd.conf:1053)
Syntax OK
share|improve this question
Do you have both the default and a virtual host for ""?? – Chris S Sep 19 '12 at 14:04

Add a global directive ServerName to httpd.conf
Be sure you're DNS has forward and reverse looking working correctly for all domain names and IPs.

share|improve this answer
I added the ServerName directive, which has stopped the complaining about FQDN on apache, but my problem still persists. How do I know if Forward and Reverse Lookup is working correctly> – DVG Sep 19 '12 at 15:06
dig and dig -x If you can not get DNS configured correctly for whatever reason, adding the relevant entries to the servers /etc/hosts file will cheat the server into thinking that you have DNS configured. – Chris S Sep 19 '12 at 17:44

If /etc/hosts is missing an entry for the IP that Apache is trying to bind to, it will complain about not being able to determine the FQDN. This seems to affect VirtualHosts.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.