ping -a 192.168.99.3不能parsingvcl.nailit.lab主机名，但是为networking上的其他主机如pfsense.nailit.lab 。
nslookup vcl.nailit.lab和ping vcl.nailit.lab正常工作。 见输出：
C:\Users\Administrator.NAILIT>ping -a 192.168.99.3 Pinging 192.168.99.3 with 32 bytes of data: Reply from 192.168.99.3: bytes=32 time<1ms TTL=64 Ping statistics for 192.168.99.3: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\Users\Administrator.NAILIT>ping vcl.nailit.lab Pinging vcl.nailit.lab [192.168.99.3] with 32 bytes of data: Reply from 192.168.99.3: bytes=32 time<1ms TTL=64 Ping statistics for 192.168.99.3: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\Users\Administrator.NAILIT>nslookup vcl.nailit.lab Server: UnKnown Address: 192.168.99.13 Name: vcl.nailit.lab Address: 192.168.99.3 C:\Users\Administrator.NAILIT>ping -a 192.168.99.1 Pinging pfsense.nailit.lab [192.168.99.1] with 32 bytes of data: Reply from 192.168.99.1: bytes=32 time<1ms TTL=64 Ping statistics for 192.168.99.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms**
DNSlogging似乎没问题 – 对于pfsense和vcl是相同的。 DNS在MS Server 2012上
ping到底如何parsing主机名？ 为什么除了'ping -a 192.168.99.3'正常工作？
ping到底如何parsing主机名？
这被称为反向DNS。 转发DNS将名称parsing为IP地址。 反向DNS将IP地址parsing为名称。 当你inputping -a 1.2.3.4到你的计算机时，它发出DNS查询PTR 4.3.2.1.in-addr.arpa 。 PTR代表指针logging。
为什么除了'ping -a 192.168.99.3'正常工作？
我的直觉告诉我，你错过了该IP地址的PTRlogging。 在你的DNS服务器上，你应该看到像168.192.in-addr.arpa这样的反向查找区域。 在那里应该存在该networking上的所有设备的PTRlogging。 Windows设备通常会尝试注册自己的正向和反向DNSlogging，但是如果整个反向查找区域丢失，则不能这样做。