NSLOOKUP Output

I am trying  the NSLOOKUP, but it gives me the same result either with hostname or IP address:

H:\>nslookup 10.10.10.10
Server:  UnKnown
Address:  10.10.10.11

Name:aaaa.bbb.com
Address: 10.10.10.10

H:\>nslookup 10.10.10.11
Server:  UnKnown
Address:  10.10.10.11

*** UnKnown can't find 10.10.10.11: Non-existent domain
===============
I am not sure the meaning of "Unknow" keyword. I believe it refers to DNS server name that resolved the address, but why it is not showing its name.

Thank you
jskfanAsked:
Who is Participating?
 
Bruno PACIConnect With a Mentor IT ConsultantCommented:
Hi,

It's not about a "A" record... it's about a "PTR" record, of if you prefer a reverse DNS record, that sort of record that associate a name to an IP address (a "A" record associates an IP address to a name).

What NSLOOKUP tries to do before launching your DNS request is just to give your the fqdn name of the dns server it will interrogate. So it takes the IP address of the DNS server and makes a reverse DNS query for this address.
So the first lines in the result that say
"Server:  UnKnown
Address:  10.10.10.11"
just mean that there is no PTR (reverse DNS) record for this IP address 10.10.10.11 and that NSLOOKUP is unable to give you the name of the DNS server... It's not a big deal anyway because PTR records are not a requirement.
The PTR record as nothing to do with the A record as you can have a A record but no PTR...

So even if your DNS server has its own A records in the DNS zone the NSLOOKUP won't be able to resolve 10.10.10.11 to a name because to do that it needs a reverse DNS record (PTR).
As I said, this is not really important. What is important is that NSLOOKUP is able to resolve the query you asked him. The first 2 lines of the NSLOOKUP answer is not important.
0
 
Lior KarasentiConnect With a Mentor Commented:
If reverse DNS for that IP address is not setup correctly, then NSLOOKUP cannot determine the name associated with the IP address.
On Windows Vista/2008, it then says "Default Server: UnKnown".
On earlier Windows versions, it displays the error message "*** Can't find server name for address ...".



http://www.simpledns.com/kb.aspx?kbid=1159
0
 
jskfanAuthor Commented:
it resolved the name:
Name:aaaa.bbb.com
Address: 10.10.10.10


But, the server that has resolved it , is Unknown.
why is it showing Unknow ??
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
msallamConnect With a Mentor Commented:
What is not resolving to a name is the DNS server IP (10.10.10.11) and NOT the name next to the nslookup command.

To confirm type:
nslookup 10.10.10.11

The second nslookup proves this.
0
 
jskfanAuthor Commented:
That s what I was asking ...why the DNS server name is showin as Unknow ?
0
 
msallamConnect With a Mentor Commented:
Simply because the client - from where you are running the nslookup - is not able to resolve the name.
This can be because of several reasons:
1. It is not available in the resolver cache (on the client)
2. The DNS server does not have an A record for itself (or for the IP 10.10.10.11 if it has several IPs).

The solution can be by ensuring the DNS server has an A record for the IP 10.10.10.11, or the entry is added manually to the hosts file on the machine you are running the nslookup from.
0
 
footechConnect With a Mentor Commented:
See the first response that liorkr gave.  Again, because you don't have a reverse DNS (PTR) record set up for the IP.
0
 
jskfanAuthor Commented:
if I ping with -a switch I get the hostname

ping -a 10.10.10.10

Pinging aaaa.bbb.com [10.10.10.10] with 32 bytes of data:
Reply from 10.10.10.10: bytes=32 time=1ms TTL=57
Reply from 10.10.10.10: bytes=32 time=1ms TTL=57
Reply from 10.10.10.10: bytes=32 time=1ms TTL=57
Reply from 10.10.10.10: bytes=32 time=1ms TTL=57

Ping statistics for 10.10.10.10:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 1ms, Average = 1ms


======================

it is just the DNS server name that does not show up ....
As Msallam said above:
<<2. The DNS server does not have an A record for itself (or for the IP 10.10.10.11 if it has several IPs).
>>

the company does not use Windows DNS, it uses infoblox.
something must have been changed, because I used to get the DNS server name when I run Nslookup against any host in the network
0
 
msallamConnect With a Mentor Commented:
On Infoblox (as with most other DNS servers) the A record for the DNS server is auto-created with any DNS zone created (under a view - if you are using DNS views-).

Just to rule out the possibility that the auto-created record is not the one for the IP (10.10.10.11) - assuming that you your Infoblox is configured to listen on more than one IP -; can you add an A record in the hosts file of the affected machine?

You can check - if it is a local issue or not - by replicating the scenario from another machine (preferably on the same subnet) to know if the problem is from the machine itself or is it a common thing.

Let us know about the results.
0
 
msallamCommented:
It is as liorkr, footech and Pac1B stated. Thx for pointing it out.

It is the PTR record is the one that maps an IP to a name.
It is a mistake from my end that I stated and built on it what was stated later. I was a bit busy with other stuff.

This (PTR record) is Auto-created too when you create the relevant reverse-lookup zone on Infoblox.

Check if it the same case for other machines as I proposed in the last post.
0
 
jskfanAuthor Commented:
Thank you guys
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.