CODEWITHSUNDEEP
apache2hostnamefqdn
Peter Stone
Peter Stone

Reputation: 3776

How does Apache determine the FQDN?

I'm using Apache2, and when reloading/restarting the server I get this warning:

apache2: Could not reliably determine the server's fully qualified domain name, using (my FQDN) for ServerName

Everything works fine, but I'm trying to figure out what's causing the error. I'm grabbing the source to see if can find it, but since my C's not very good....

Some notes:

Versions:

Apache/2.2.9
Linux 2.6.24-23-xen x86_64
Description:    Debian GNU/Linux 5.0 (lenny)

Any ideas?

Upvotes: 3

Views: 16480

Answers (3)

Jay
Jay

Reputation: 179

On Debian, the hostname is set at startup thanks to the script /etc/init.d/hostname.sh which uses the file /etc/hostname. We can use this file to update the computer hostname and its FQDN (fully qualified domain name).

If ServerName in your vhost is my-computer.my-domain.ext make sure to copy the exact name in /etc/hosts

Caution: in the /etc/hosts file, the hostname and FQDN order must be respected. First the fqdn then the hostname and localhost at the end.

~$ echo "my-computer" > /etc/hostname
~$ echo "127.0.0.1 my-computer.my-domain.ext my-computer localhost" > /etc/hosts
~$ /etc/init.d/hostname.sh

You can check the change with the following lines:

~$ hostname
my-computer
~$ hostname --fqdn
my-computer.my-domain.ext

The old hostname may still be present in the command line prompt. Just logoff then login to make it disappear.

Upvotes: 1

Motsel
Motsel

Reputation: 548

For further information about setting hostname and FQDN on debian (which also prevents the warning) check this: http://movealong.org/hostname.html

Upvotes: 0

David Z
David Z

Reputation: 131730

Are you sure you have a ServerName directive with the proper value - outside any <VirtualHost> blocks? (You also need a ServerName inside each <VirtualHost> block, of course)

When Apache gives out that error message, usually it means that it's not finding a ServerName for the server as a whole. If you do have that directive set properly, I can't imagine why Apache would still be complaining...

Upvotes: 8

Related Questions