So I try to do:
and it tells me:
ssh: Could not resolve hostname woofy: Name or service not known
It knows that its own hostname is "woofy"; why can't it connect to itself?
So we know
The short answer is that you need to add an entry for
Keep a backup of the previous version of
The long answer is that how hostnames are resolved to IP addresses is controlled by a set of configuration files which vary slightly between Unix variants. You can configure your Unix system to resolve host names by hosts file (
Edit: if this still causes a DNS lookup, the problem is probably that your Name Service Switch configuration consults DNS before
Unix systems have a notion of host name that isn't related to the network subsystem. That name is what the
For your sanity, you had better make sure that this host name agrees with what your neighborhood DNS server says, and with what (if anything) your system thinks it's called. In fact, DNS names are not associated with machines, but with network interfaces, so your DNS name will be associated with one of your network interfaces. On machines with no actual network connection, the host name should be associated with the loopback interface.
In practice, the hostname is stored in the file