SUDO UNABLE TO RESOLVE HOST BPC WINDOWS

The problem is caused when one of the loopback addresses does not have the proper hostname assigned, or has no name assigned, or there is only one line for this address. There should be two entries for the loopback address (127.0.0.1).check your /etc/hosts file you may see something like this:.get your hostname from /etc/hostname, or:.I don't know what causes this issue, but here's something that may fix it: Since you took the time to reply, and so that we can be precise, I have changed my hostname to 'himayloco' for the time being. I then restarted the machine and nothing.the problem is still there. Sudo: unable to resolve host : Name or service not known to change the hosts file to be that new host name. In other words, the command executes as it should, but the annoying error message appears after each use of sudo: Sudo: unable to resolve host the_name: Name or service not knownĠ upgraded, 0 newly installed, 0 to remove and 0 not upgraded. To fix it, you need to specify the IP address manually which matches the host name. failed outright but at least one could not be resolved for some reason.

SUDO UNABLE TO RESOLVE HOST BPC WINDOWS

The problem manifests itself when a command is issued under sudo. Under Windows 10, Bash on Ubuntu cant resolve the host name defined in the standard configuration file /etc/hostname. If Exim is called under the name mailq, it behaves as if the option -bp were.

Sudo unable to resolve host bpc