Jontas » hostname http://www.f15ijp.com My digital notepad (notes etc) Wed, 28 Dec 2011 18:24:47 +0000 en hourly 1 http://wordpress.org/?v=3.3.1 apache2 could not reliably determine the server’s fully qualified domain name using 127.0.0.1 http://www.f15ijp.com/2010/01/25/apache2-could-not-reliably-determine-the-servers-fully-qualified-domain-name-using-127-0-0-1/ http://www.f15ijp.com/2010/01/25/apache2-could-not-reliably-determine-the-servers-fully-qualified-domain-name-using-127-0-0-1/#comments Mon, 25 Jan 2010 13:02:24 +0000 jontas http://f15ijp.com/?p=231 When apache complains like this.

  • check that the virtualhosts so that ServerName is set to a FQDN
  • check /etc/hostname [should be a fqdn] (after you have updated this, run “/bin/hostname -F /etc/hostname”
  • check /etc/hosts
  • Hint: use “apache2ctl configtest” to see if it helps
]]> http://www.f15ijp.com/2010/01/25/apache2-could-not-reliably-determine-the-servers-fully-qualified-domain-name-using-127-0-0-1/feed/ 0 sudo: unable to resolve host hostname http://www.f15ijp.com/2010/01/21/sudo-unable-to-resolve-host-hostname/ http://www.f15ijp.com/2010/01/21/sudo-unable-to-resolve-host-hostname/#comments Thu, 21 Jan 2010 13:38:15 +0000 jontas http://f15ijp.com/?p=193 If using sudo gives the error message “unable to resolve host hostname” then one solution is to add the hostname in /etc/hosts

127.0.0.1	hostname.domain.com	hostname localhost
]]> http://www.f15ijp.com/2010/01/21/sudo-unable-to-resolve-host-hostname/feed/ 0