Ubuntu
gnome-nettool package

unable to resolve hostname

Asked by bill purvis

I upgraded to Ubuntu 8.04 a couple of days ago. Since then I have found several emails from
root to root saying:

felix : May 15 07:35:07 : root : unable to resolve host felix

I have both felix and felix.billp.org in /etc/hosts.

felix is my laptop which is connected to a LAN. Internet access is via a server (Mandriva)
which acts as firewall, so all the LAN IP addresses are 192.168.0.???. I don't run a
local DNS server - I did try at one time to set one up, but never managed to get it
working.

This problem did not occur on Ubuntu 7.10.

The only clue I have is that one of the messages was reported by
   /etc/cron.daily/apt
but there's a lot going on in that script that I have yet to understand so
I don't know what is causing it.
I do have a couple of scripts that run overnight and which move stuff between the
laptop and the server (using rsync).

Any suggestions on how to get rid of these messages welcomed....

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu gnome-nettool Edit question
Assignee:
No assignee Edit question
Solved by:
Elfy
Solved:
Last query:
Last reply:
Revision history for this message
Elfy (elfy) said : 		#1

Just to check can you run

sudo apt-get update

do you get

sudo: unable to resolve host

If so this should be a great help

http://ubuntuforums.org/showthread.php?t=723361

Revision history for this message
bill purvis (bill-billp) said : 		#2

Yes, I do get the message. Also, ran update manager and got two more emails
from that.

How can I stop these?

Revision history for this message
Best Elfy (elfy) said : 		#3

Follow the thread I have left in first post - basically you need to edit the hosts file

open a terminal

gksudo gedit /etc/hosts

remove .billp.org from second line so it just says felix

save and exit, reboot

Revision history for this message
bill purvis (bill-billp) said : 		#4

Thanks forestpixie, that solved my question.

Revision history for this message
bill purvis (bill-billp) said : 		#5

I didn't need to reboot....

Did the upgrade modify /etc/hosts? I had

....
192.168.0.150 felix felix.billp.org

but after upgrading it changed to

192.168.0.150 felix.billp.org felix.billp.org

removing the .billp.org on the first name has sorted the problem.