If you want to determine the name of a Windows machine without DNS, you should try Nbtstat. But that will only work on Windows: For example, NBTSTAT -A 10.10.10.10 On Linux, you should try nmblookup that does nearly the same.
For those who don’t have an account on the forums (or don’t wish to login): if your main issue is not to ping but to ssh, you can create/edit your ~/.ssh/config adding lines like these: Host fakehost1 Hostname real-hostname Host fakehost2 Hostname real-hostname2 Host fakehost3 Hostname real-hostname3
Since the previous answers to this question were written, there have been a couple of RFCs that alter the guidance somewhat. RFC 6761 discusses special-use domain names without providing specific guidance for private networks. RFC 6762 still recommends not using unregistered TLDs, but also acknowledges that there are cases where it will be done anyway. … Read more
I would choose a consistent approach across the entire environment. Both solutions work fine and will remain compatible with most applications. There is a difference in manageability, though. I go with the short name as the HOSTNAME setting, and set the FQDN as the first column in /etc/hosts for the server’s IP, followed by the … Read more
There isn’t a great deal of difference between the two; 127/8 (eg: 127.0.0.0 => 127.255.255.255) are all bound to the loopback interface. The reason why is documented in the Debian manual in Ch. 5 Network Setup – 5.1.1. The hostname resolution. Ultimately, it is a bug workaround; the original report is 316099.
This is a subdomain system to identify subdomains. ww8 means that is the 8th subdomain. This system is used to balance load on the server side
Use the descriptively-named function socket.getfqdn():
Use socket and its gethostname() functionality. This will get the hostname of the computer where the Python interpreter is running: