THE QUESTION IS HOWEVER if there is some easy way of FORCING such hardware adresses to cause resolution of FQDN, hostnames such as indeed id.local in OTHER contexts than eg macOS or Homebrew SSH which accidentally does support Bonjour but connects, as environment on the remote host shows (the MAC addresses, I think?, of the Mac that makes the connection, the environment shown is for the host one connects to, whereby such variables are set, but not with IP for Bonjour, but for hardware addresses).īasically, it would be suoerb, especially in combination with DHCP, to have a lightwegith way of resolving hardware addresses to IP addresses and also FQDN. We can also run various DNS servers, bind and whatnot. 10.10.10.10 or 192.158.255.1 or whatever your local network or even WAN is using.

In the host file we can obviously deal with higher-level of TCP/IP. MAC here of course does not at all refer to Mac as in Apple etc, but to networking since the 60ies or so, an acronoymfor Machine Address C…? etc. Q: is it possible to somehow bind fa20::907:1051:3cc9:0a33 or other, presumably so-called MAC-axresses aka hardware addresees per interface. However, with “ssh CHOSENBONJOURNAME.local” working too, I am ASKING A QUESTION here which seems beyond trivial Google search research. So, with ping CHOSENBONJOURNAME.local specifically on Mac OS X and macOS we can fetch the IP address. (in the environment, using eg “env | grep SSH” on macOS High Sierra, and surely many other platforms for that matter, incl beyond BSD, Darwin, macOS etc ALTHOUGH the Bonjour serviices maybe are not available? On QNAP NAS, for example it is though, under the name avahi, if my memory serves…)

Is it possible to use the address given from eg

Open terminal in mac os 9.2