主机名无法解析为本地IP地址 [英] Hostname not resolving to local IP address

查看:884
本文介绍了主机名无法解析为本地IP地址的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我在vmware Fusion中运行Windows 8 VM。它运行在运行OSX 10.10(Yosemite)的Mac中。 VM的计算机名称为Proud。当我从内部ping VM时,即 ping -a 192.168.0.138 我收到如下响应:

I am running a Windows 8 VM inside of vmware Fusion. It runs inside a Mac running OSX 10.10 (Yosemite). The VM has a computer name of "Proud". When I ping the VM from within itself, i.e. ping -a 192.168.0.138 I get a response like:

Ping with Proud [192.168.0.138],包含32个字节的数据:
来自192.168.0.138的回复:bytes = 32 time< 1ms TTL = 128

然而每当我从Yosemite ping Proud时,即 ping Proud 我得到的回复如下:

However whenever I ping Proud from Yosemite, i.e. ping Proud I get a response like:

PING引以为傲(199.101.28.130):56个数据字节
来自199.101.28.130的64字节:icmp_seq = 0 ttl = 46 time = 418.646 ms

虚拟机正在使用桥接网络。

The VM is using bridged networking.

为什么Proud会解析为该IP地址?这是不对的,意味着我无法使用主机名(必需品),以便我可以从Mac连接到它。

Why does Proud resolve to that IP address? It is not correct and means I am unable to use the hostname (a necessity) so that I can connect to it from the Mac.

推荐答案

这似乎是Mac OS的功能。如果我尝试ping任何主机名,它将从该IP地址返回ping - 即使主机名是虚构的。我不知道为什么OS X会这样做。

This seems to be a 'feature' of Mac OS. If I attempt to ping any hostname it will return the ping from this IP address - even if the hostname is fictional. I do not know why OS X does this.

这篇关于主机名无法解析为本地IP地址的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆