Windows nslookup“默认服务器:未知”是什么意思


12

我想在您的帮助下解决有关Windows上nslookup的问题。请在下面查看我的CMD命令(在WinXP SP2上运行)。

C:\>ipconfig /all

Windows IP Configuration

        Host Name . . . . . . . . . . . . : vchjXPsp3MUI
        Primary Dns Suffix  . . . . . . . :
        Node Type . . . . . . . . . . . . : Hybrid
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter LAN1-hostvn1:

        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : VMware Accelerated AMD PCNet Adapter

        Physical Address. . . . . . . . . : 00-0C-29-E0-68-00
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 192.168.11.120
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.11.1
        DHCP Server . . . . . . . . . . . : 192.168.11.1
        DNS Servers . . . . . . . . . . . : 172.27.0.12
        Primary WINS Server . . . . . . . : 172.27.0.12
        Lease Obtained. . . . . . . . . . : Wednesday, August 03, 2011 8:58:19 AM
        Lease Expires . . . . . . . . . . : Thursday, August 02, 2012 8:58:19 AM

Ethernet adapter LAN2-bridged:

        Media State . . . . . . . . . . . : Media disconnected
        Description . . . . . . . . . . . : VMware Accelerated AMD PCNet Adapter

        Physical Address. . . . . . . . . : 00-0C-29-E0-68-0A

C:\>ipconfig /flushdns

Windows IP Configuration

Successfully flushed the DNS Resolver Cache.

C:\>nslookup
*** Can't find server name for address 172.27.0.12: Non-existent domain
*** Default servers are not available
Default Server:  UnKnown
Address:  172.27.0.12

> chj.dev.nls
Server:  UnKnown
Address:  172.27.0.12

Name:    chj.dev.nls
Address:  172.27.0.120

>

您可以看到我已经在我的IP配置中分配了DNS服务器,但是为什么nslookup喷口

*** Can't find server name for address 172.27.0.12: Non-existent domain
*** Default servers are not available
Default Server: Unknown

说“不可用”和“未知”是什么意思?

DNS服务器(172.27.0.12)正常工作,因为它按预期方式回答chj.dev.nls的查询。DNS服务器是Win2003 SP2。

一些详细信息:

> set debug
> chj.dev.nls
Server:  UnKnown
Address:  172.27.0.12

------------
Got answer:
    HEADER:
        opcode = QUERY, id = 4, rcode = NOERROR
        header flags:  response, auth. answer, want recursion, recursion avail.
        questions = 1,  answers = 0,  authority records = 1,  additional = 0

    QUESTIONS:
        chj.dev.nls, type = A, class = IN
    AUTHORITY RECORDS:
    ->  dev.nls
        ttl = 3600 (1 hour)
        primary name server = nlserver.dev.nls
        responsible mail addr = hostmaster.dev.nls
        serial  = 14716
        refresh = 900 (15 mins)
        retry   = 600 (10 mins)
        expire  = 86400 (1 day)
        default TTL = 3600 (1 hour)

------------
------------
Got answer:
    HEADER:
        opcode = QUERY, id = 5, rcode = NOERROR
        header flags:  response, auth. answer, want recursion, recursion avail.
        questions = 1,  answers = 0,  authority records = 1,  additional = 0

    QUESTIONS:
        chj.dev.nls, type = A, class = IN
    AUTHORITY RECORDS:
    ->  dev.nls
        ttl = 3600 (1 hour)
        primary name server = nlserver.dev.nls
        responsible mail addr = hostmaster.dev.nls
        serial  = 14716
        refresh = 900 (15 mins)
        retry   = 600 (10 mins)
        expire  = 86400 (1 day)
        default TTL = 3600 (1 hour)

------------
Name:    chj.dev.nls

>

任何想法?谢谢。

Answers:


15

Nslookup将尝试通过对IP地址执行反向查找来解析客户端上配置为主DNS服务器的DNS服务器IP地址的名称。如果您没有为网络/子网设置rDNS区域,则会收到“服务器未知”消息,因为nslookup将无法解析IP地址的名称。

这不是错误情况,不会对正常的AD和DNS操作造成任何问题。


但是我在家庭网络中遇到此错误,其中唯一失败的Windows计算机是家庭FIOS路由器上的特定WIndows 10家庭版,而所有其他Windows系统(家庭和专业版)从不显示此错误。我没有运行常规的DNS服务器,而只是运行路由器。superuser.com/questions/1448118/…–
Gilbert,

8

您的服务器未返回其名称的反向查询。这就是为什么您在那里看到“未知”的原因。您将需要创建适当的反向查找区域,以允许您的服务器将其自身的IP地址反向解析回其名称。


3

好了,向我的内部DNS服务器添加反向查询之后,Default Server现在显示我的DNS服务器的域名。

样本输出:

C:\>nslookup
Default Server:  nlserver.dev.nls
Address:  172.27.0.12

注意:如果有多个映射到172.27.0.12的名称,Default Server将随机显示其中一个名称。

在此处输入图片说明

By using our site, you acknowledge that you have read and understand our Cookie Policy and Privacy Policy.
Licensed under cc by-sa 3.0 with attribution required.