Sample query:
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?
Error message “sudo: unable to resolve host (none)” [solution]
Two things to check (assuming your machine is called my-machine, you can change this as appropriate):
- That the
/etc/hostnamefile contains just the name of the machine. - That
/etc/hostshas an entry forlocalhost. 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.
Answer #2:
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.
Answer #3:
Add your hostname to /etc/hosts like so:
echo $(hostname -I | cut -d\ -f1) $(hostname) | sudo tee -a /etc/hostsAnswer #4:
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.
Answer #5:
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!
Answer #6:
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.
Answer #7:
In AWS, go to your vpc and turn on “DNS Hostnames”.
Error message “sudo: unable to resolve host (none)”- Resolved
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.
As long as the delay isn’t too long, this error message is typically harmless.
Answer #8:
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'
Answer #9:
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.”
Answer #10:
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.
Answer #11:
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 localhostAnswer #12:
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!
Hope you learned something from this post.
Follow Programming Articles for more!