dns - NSLOOKUP Default Server: UnKnown How to fix it

30
2014-04

Peretz

I execute NSLOOKUP and see

C:>NSLOOKUP

Default Server: UnKnown

Address: 192.168.1.1

I am guessing that it should be something like

C:> nslookup

Default Server: nameserver1.domain.com

Address: 192.168.1.1

How to fix it?

Could it be the reason why I cannot ping the Domain Controller by its full name?

P.S. Network settings of the workstation

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Realtek RTL8102E/RTL8103E Family PCI-E Fa
st Ethernet NIC (NDIS 6.20)
   Physical Address. . . . . . . . . : 90-E6-BA-BD-87-20
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.1.124(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Wednesday, December 11, 2013 2:56:39 PM
   Lease Expires . . . . . . . . . . : Friday, December 13, 2013 5:20:41 PM
   Default Gateway . . . . . . . . . : 192.168.1.1
   DHCP Server . . . . . . . . . . . : 192.168.1.1
   DNS Servers . . . . . . . . . . . : 192.168.1.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Answers

techie007

It appears you are using a basic router/gateway device as your Gateway, DHCP and most importantly DNS (192.168.1.1).

Assuming that, then that router is not a real DNS server, and is actually just forwarding your DNS requests to the DNS server setup in the WAN-side of the router.

Since the router is not a real DNS server it has no name (or at least it doesn't report a name when queried), so NSLookup doesn't know its name and instead reports "unknown" as the name.

Try using a specific DNS server with NSlookup, like say Google's (8.8.8.8):

nslookup - 8.8.8.8

(using - instead of a host name puts NSLookup into interactive mode like just a plain nslookup does, except using Google's DNS server for queries).

That command should return something more like what you expect:

Default Server: google-public-dns-a.google.com
Address: 8.8.8.8

Your question "Could it be the reason why I cannot ping the Domain Controller by its full name?" is hard to answer, as you haven't provided any real information on the setup of your network. If you are trying to setup an actual Active Directory domain, and contact an actual AD "Domain Controller", then you need to reconfigure this client to properly use the AD-integrated resources (DNS, DHCP, etc.) instead of the gateway device.

Related Question

windows - DNS request timed out. Server: UnKnown Address: 192.168.1.1

windows networking dns

Mat

I have some problem with my DNS server configuration or my Router i guess.

In the browser, i can't open any pages. i can't ping www.google.com but i can ping the ipadress.

nslookup www.google.com yelds

DNS request timed out.
    timeout was 2 seconds.
Server:  UnKnown
Address:  192.168.1.1

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to UnKnown timed-out

ipconfig /all yelds:

IP Configuration for Windows

   Computer name. . . . . . . . . : Asus-PC
   The main DNS-suffix. . . . . . :
   Node Type. . . . . . . . . . . . . : Hybrid
   IP-routing is enabled. . . . : No
   WINS-proxy enabled. . . . . . . : No

Wireless LAN adapter Wireless Network Connection:

   DNS-suffix for this connection. . . . . :
   Description. . . . . . . . . . . . . : Atheros AR9285 Wireless Network Adapter
   Physical Address. . . . . . . . . : 00-25-D3-06-C6-4C
   DHCP is enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled. . . . . . : Yes
   Local IPv6-address channel. . . : Fe80:: 3d91: 1dce: a561: d209% 11 (main)
   IPv4-address. . . . . . . . . . . . : 192.168.1.101 (primary)
   Subnet mask. . . . . . . . . . : 255.255.255.0
   Rent received. . . . . . . . . . : May 9, 2011 12:06:42
   The lease term expires. . . . . . . . . . : May 9, 2011 14:06:41
   Default Gateway. . . . . . . . . : 192.168.1.1
   DHCP-server. . . . . . . . . . . : 192.168.1.1
   DNS-servers. . . . . . . . . . . : 192.168.1.1
   NetBios over TCP / IP. . . . . . . . : Enabled

Tunnel adapter Local Area Connection * 2:

   Media State. . . . . . . . : Media disconnected
   DNS-suffix for this connection. . . . . :
   Description. . . . . . . . . . . . . : Isatap. {CFA53C79-5BEB-445C-A626-772598C5F
CA4}
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP is enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled. . . . . . : Yes

Tunnel adapter Local Area Connection * 6:

   Media State. . . . . . . . : Media disconnected
   DNS-suffix for this connection. . . . . :
   Description. . . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 02-00-54-55-4E-01
   DHCP is enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled. . . . . . : Yes

any idea what could be the problem? if i login to my router, two dns entries are set.

Home

dns - NSLOOKUP Default Server: UnKnown How to fix it