Error message "sudo: unable to resolve host (none)"

Question

When I run sudo the terminal is stuck for a few seconds and then outputs an error message. My terminal looks like this:

ubuntu@(none):~$ sudo true
sudo: unable to resolve host (none)

What can I do to solve it?

score 1330 · Accepted Answer · edited Dec 22 '16 at 00:23

Two things to check (assuming your machine is called my-machine, you can change this as appropriate):

That the /etc/hostname file contains just the name of the machine.

That /etc/hosts has an entry for localhost. It should have something like:

 127.0.0.1    localhost.localdomain localhost
 127.0.1.1    my-machine

If either of these files aren't correct (since you can't sudo), you may have to reboot the machine into recovery mode and make the modifications, then reboot to your usual environment.

score 257 · Answer 2 · edited Apr 13 '17 at 12:24

Edit /etc/hosts and append your new hostname to the 127.0.0.1 line (or create a new line if you prefer that).

Mine looks like:

127.0.0.1       localhost localhost.localdomain penguin

# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

Replace penguin in the above example by your new hostname as stated in the /etc/hostname file.

score 95 · Answer 3 · answered Sep 15 '14 at 16:03

95

Add your hostname to /etc/hosts like so:

echo $(hostname -I | cut -d\  -f1) $(hostname) | sudo tee -a /etc/hosts

answered Sep 15 '14 at 16:03

Collin Anderson

3,356

score 38 · Answer 4 · edited Apr 13 '17 at 12:23

38

Note, this is an answer to this question which has been merged with this one.

Your hostname (dave00-G31M-ES2L) is not represented in /etc/hosts. Add an L to this line:

127.0.1.1   dave00-G31M-ES2

So it becomes:

127.0.1.1   dave00-G31M-ES2L

In order to accomplish this, open a console (press Ctrl+Alt+T) and type:

sudo gedit /etc/hosts

Add the letter L as mentioned, save and exit.

edited Apr 13 '17 at 12:23

Community

1

answered Aug 18 '12 at 11:02

Thor

3,678

score 22 · Answer 5 · answered Apr 01 '13 at 01:18

I had this issue when I was using ubuntu on a VPS. I solved it editing /etc/hosts file.

run this command:

sudo nano /etc/hosts

and then add:

127.0.0.1   localhost.localdomain localhost
127.0.1.1   ubuntu

I hope that will solve your issue :)

PS: Remember to reboot your computer!

score 14 · Answer 6 · answered Aug 13 '14 at 13:50

I was having the same issue even though the hostname in my /etc/hostname file and /etc/hosts file matched.

My hostname was "staging_1". It turns out that you can't have an underscore in your hostname, which is why I was getting this error. Changing the underscore to a hyphen fixed my problem.

score 12 · Answer 7 · answered Jan 15 '15 at 05:15

12

In AWS, go to your vpc and turn on "DNS Hostnames".

answered Jan 15 '15 at 05:15

Erick

137
1
2

score 10 · Answer 8 · answered Jul 28 '18 at 17:24

Everybody advises to modify /etc/hosts. But in some cases this may not be possible (for example inside a docker container). So, I had to find a better way and I came up with this:

echo "alias sudo='sudo -h 127.0.0.1'" >> ~/.bash_aliases
source ~/.bashrc

Aliases don't work in bash scripts, but we can use variables: sudo='sudo -h 127.0.0.1'

Brent Bradburn · Answer 9 · 2017-09-18T22:23:24.730

The symptom given in the question may correlate strongly with this more specific problem:

$ hostname --fqdn
hostname: Temporary failure in name resolution

There are different ways that this could be resolved, one of which is to add your hostname as localhost in /etc/hosts (as shown in several other answers). This may be the right thing to do in general, but it isn't the only possible resolution.

A "fully qualified domain name" may be supplied by an external DNS server or similar (if such is available on your network). In this case, sudo will not complain, despite the missing entry in /etc/hosts.

Note: sudo attempts to dereference the hostname, even though it isn't necessarily required, due to optional capabilities in the sudoers file. See sudo command trying to search for hostname.

As long as the delay isn't too long, this error message is typically harmless.

score 6 · Answer 10 · answered Feb 13 '16 at 11:44

I encountered this same error message. I think this discussion thread at AWS Developer Forums is a better solution:

"Go the the VPC management console, select the VPC, click on Actions, select Edit DNS Hostnames and select Yes."

https://forums.aws.amazon.com/thread.jspa?messageID=699718

score 6 · Answer 11 · answered Jun 19 '16 at 16:29

Some terminal emulators will not update prompt with the correct hostname until you close and restart the emulator (lxterminal, I'm talking to you).

I spent 30min fighting with this error after editing my hostname and hosts files and running sudo service hostname restart until I ran sudo hostname and saw that the hostname was the new value, even though the prompt was showning the old value.

score 5 · Answer 12 · answered Jan 09 '14 at 22:24

In my case it was the problem, I changed the hostname to man because I wanted to know if there are some parameters you can use on hostname. Instead it changed my hostname to man and I always got the same message like you

sudo: unable to resolve host (none)

after changing the hostname back to `localhost everything worked fine again

hostname localhost

score 4 · Answer 13 · answered Aug 31 '11 at 19:16

4

Sorry I can't help you much but, since it says "can't resolve host" try running:

hostname

And see if the output is the hostname of the machine. If not, the problem is the host configuration, not sudo.

answered Aug 31 '11 at 19:16

animaletdesequia

8,552

score 2 · Answer 14 · answered May 21 '19 at 06:45

In case your problem is that /etc/hostname file and /etc/hosts, both files have your desired hostname and still your machine is showing the error

sudo: unable to resolve host

Try, forcing the hostname

sudo hostname -F /etc/hostname

You will probably still get the same error, but try logging out and logging back in. It worked for me.

score 2 · Answer 15 · answered Apr 13 '14 at 05:19

OP wrote:

It was all in /etc/hostname. On two of our sick servers it looked like this:
ubuntu@(none):~$ cat /etc/hostname
linux-web-n ip-10-128-##-##
While on a server without this issue we had:
ubuntu@ip-10-128-##-###:~$ cat /etc/hostname
ip-10-128-##-###
Removed the linux-web-n portion, rebooted and everything was fine.

score 2 · Answer 16 · answered Jan 18 '15 at 03:26

2

you might be getting an error if your hosts or hostname file contain illegal characters. Only these symbols are permitted: a-z, A-Z, 0-9

answered Jan 18 '15 at 03:26

M.G.

121
2

score 2 · Answer 17 · answered Aug 24 '16 at 15:07

2

if you can't sudo you CAN log in as root via su. IE: su root (in an x-term). then give the root password when prompted, then you can edit the files with nano. The root password in 'buntu is the same as the password you would use for sudo.

answered Aug 24 '16 at 15:07

ken scharf

21

score 2 · Answer 18 · answered Jan 10 '17 at 02:18

I had this same problem! I changed my VPS's name through the online admin control panel which did not change the machine name in the hosts file All I did was run:

sudo nano /etc/hosts

Then I edited it from this:

127.0.1.1 Megabyte Megabyte
127.0.0.1 localhost

To this:

127.0.1.1 Debian Debian
127.0.0.1 localhost

and that fixed my error! Hope this helped!

score 1 · Answer 19 · edited Mar 26 '16 at 17:59

1

I had the same problem. I solved it by editing the /etc/hosts and /etc/hostname files... on the /etc/hosts file, just edit the top part as shown below.

#vi /etc/hosts
    127.0.0.1   localhost
    127.0.1.1   localhost  myhostname




#vi /etc/hostname
    myhostname

edited Mar 26 '16 at 17:59

muru

207,228

answered Mar 26 '16 at 17:53

Centy

21

score 1 · Answer 20 · answered Jul 13 '17 at 07:27

1

If you are using Vagrant, then login into the guest and run apt-get --no-install-recommends install virtualbox-guest-utils

answered Jul 13 '17 at 07:27

tanmoy

91
1
4

Error message "sudo: unable to resolve host (none)"

20 Answers20

Linked

Related