How To Fix: Could not determine the server's fully qualified domain name
How To Fix: Could not determine the server's fully qualified domain name
How, To, Fix:, Could, not, determine, the, server's, fully, qualified, domain, name


Thu Nov 12, 2009 9:05 pm - How To Fix: Could not determine the server's fully qualified domain name
#773
How To Fix: Could not determine the server's fully qualified domain name
author: toyer
Leave Your Comments
name
comments
Share
Share this post by copy and paste this URL and put it on your forums or use it on your profile like myspace, friendster, Facebook, Twitter or others and add in with your comments.
URL Link: ask
Use this HTML code to embed this topic, just copy the code from the "Embed" box. Once you've copied the code, just paste it into your website or blog to embed it.
Embed: ask
BBCODE is use on forums. You can put this code on all your BBCODE enabled forums like PhpBB, vBulletin® and others. Just Copy and Paste this code on with Posts and Replies on your forums
BBCODE: ask
| More
Thu Jul 20, 2006 9:51 am - Re: How To Fix: Could not determine the server's fully qualified domain name
#944
toyer
Loging to your Redhat server with the SSH account that was provided by our staff. Make sure you are logged in as root. If you don't have your password or forgot, please contact our support team. otherwise, execute these commands if you have your root password:


     Code:
echo HOST.DOMAIN.com > /etc/hostname

HOST = Your host name
DOMAIN = Your Domain Name

Now execute the next command in the shell:

     Code:
/bin/hostname -F /etc/hostname


Now that your server has a hostname and a domain name, restart your server with the following command:

     Code:
/etc/init.d/httpd restart


After you have restarted your server, you shouldn't see the error.
Thu Feb 08, 2007 3:27 am - Re: How To Fix: Could not determine the server's fully qualified domain name
#945
piwi
does this work on other linux distributions like Mandrake Mandriva Red Hat Fedora Core SuSE Linux Debian Woody Sarge Ubuntu Hoary Hedgehog Breezy Badger Dapper DrakeEdgy Eft CentOS
Mon Feb 19, 2007 6:08 pm - Re: How To Fix: Could not determine the server's fully qualified domain name
#946
Nithin,
I am also facing the same prob but the above reply dint worked for me plz can anyone help me
Mon Feb 19, 2007 8:03 pm - Re: How To Fix: Could not determine the server's fully qualified domain name
#947
piwe
hey Nithin, send this command:

cat /etc/hostname
if you don't have a hostname, you need to give your server a good hostname and a domain name. for example: hostname.domainname.com
make sure you only have one entry, its possible that you have a corupted hostname file, so i would clear it all and run the command on this post
MAKE SURE TO RESTART YOUR SERVER
Mon May 28, 2007 1:39 am - Re: How To Fix: Could not determine the server's fully qualified domain name
#948
Kike
you have to edit the /etc/apache2/apache2.conf and, at the end of the file, add:

# added servername to avoid the could not determine fqdn error
servername myserver

place your server name in place of myserver.

it worked for me.
Fri Jul 20, 2007 11:37 am - Re: How To Fix: Could not determine the server's fully qualified domain name
#949
MerlinGuy
thanks.

that worked great.
Sun Sep 02, 2007 4:14 am - Re: How To Fix: Could not determine the server's fully qualified domain name
#950
nihat
it's a verry good
it work !!!
thanks
Tue Dec 18, 2007 12:12 am - Re: How To Fix: Could not determine the server's fully qualified domain name
#951
burf
thanks kike, it worked for me too
Mon Mar 03, 2008 12:22 am - Re: How To Fix: Could not determine the server's fully qualified domain name
#952
helper
also check this file:

/etc/hosts

make sure it matches your hostname

i was getting this error

starting httpd: httpd: apr_sockaddr_info_get() failed for hostname.domain

httpd: could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for servername

Mon Mar 03, 2008 12:39 am - Re: How To Fix: Could not determine the server's fully qualified domain name
#953
var
http://tgrove.com/2007/12/02/httpd-apr_sockaddr_info_get-failed-for-hostname/
Wed Mar 05, 2008 6:58 am - Re: How To Fix: Could not determine the server's fully qualified domain name
#954
Boomer
ah it was /etc/hosts.
thanks
Wed Mar 05, 2008 3:37 pm - Re: How To Fix: Could not determine the server's fully qualified domain name
#955
Hoddi
thanks, it works
Fri Jun 19, 2009 5:02 am - Re: How To Fix: Could not determine the server's fully qualified domain name
#956
adhi
getting same error
Sun Jul 12, 2009 2:23 pm - Re: How To Fix: Could not determine the server's fully qualified domain name
#957
comfi
how do you make qualified domain name on your linux server?
Mon Jul 13, 2009 8:08 pm - Re: How To Fix: Could not determine the server's fully qualified domain name
#958
apah
how about if i get this:

httpd: apr_sockaddr_info_get() failed for hostname httpd: could not reliably determine the servers fully qualified domain name, using 127.0.0.1 for servername
Fri Jul 31, 2009 12:31 am - Re: How To Fix: Could not determine the server's fully qualified domain name
#959
tiorios
when httpd restart showing error fully qualified domain name. i tried on fqdn, ubuntu which both have apache2
Sun Aug 02, 2009 2:38 pm - Re: How To Fix: Could not determine the server's fully qualified domain name
#960
jessiesss
what i need to know is how to fix need to be called by 3 domain names
Sat Oct 17, 2009 11:45 am - Re: How To Fix: Could not determine the server's fully qualified domain name
#2598
steve
tarting httpd: httpd: apr_sockaddr_info_get() failed for "my domain"
httpd: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
[FAILED]
Mon Nov 09, 2009 4:26 pm - Re: How To Fix: Could not determine the server's fully qualified domain name
#2767
mandrake
some help with this please:

mandriva starting httpd: httpd: could not reliably determine the servers fully qualified domain name, using 127.0.0.1 for servername (98)address already in use: make_sock: could not bind to address [::]:80 (98)address already in use: make_sock: could not
Wed Feb 10, 2010 8:50 pm - Re: How To Fix: Could not determine the server's fully qualified domain name
#3445
CoderX
make sure you dont have a duplicate http.conf file. in my case i had /etc/httpd/conf/httpd.conf and /etc/httpd/conf.d/system-config-httpd.conf (from the configurator app).
renaming or deleting one should fix the issue

regards
Thu Jul 15, 2010 5:52 pm - Re: How To Fix: Could not determine the server's fully qualified domain name
#4161
Jose
i have a debian lenny.
i edited the /etc/apache2/apache2.conf and at the end of the file, added:

servername here-the-name-of-your_server

it worked for me.