What is non-authoritive answer in nslookup?

Does it mean the answer I got is not from the reliable source? how to get the 'authoritative' answer?
bash-3.2$ nslookup google.com
Server:		4.2.2.1
Address:	4.2.2.1#53
 
Non-authoritative answer:
Name:	google.com
Address: 74.125.67.100
Name:	google.com
Address: 209.85.171.100
Name:	google.com
Address: 74.125.45.100

Open in new window

beer9Asked:
Who is Participating?
 
fdduranConnect With a Mentor Commented:
It means your dns server (4.2.2.1) had to query google's dns servers for obtaining ns lookup answer. You may ask googles ns server directly by using the code below.
It works in the following way:
nslookup   name_to_lookup   server_to_ask_to
Otherwise it defaults to your local network (or your ISP) dns server.
~$ nslookup google.com ns1.google.com
Server:		ns1.google.com
Address:	216.239.32.10#53
 
Name:	google.com
Address: 74.125.67.100
Name:	google.com
Address: 74.125.45.100
Name:	google.com
Address: 209.85.171.100

Open in new window

0
 
arnoldConnect With a Mentor Commented:
Not Authoritative DNS response means that the DNS server providing the answer is not directly responsible for the zone.  I.e. from a Caching server.
The 4.2.2.1 is your Providers Caching DNS server.

This is similar to you asking person A for some information. Person A does not have the information, but person A knows that person B should have the information.  Person A gets the answer from Person B and provides it to you.
While you received a response, it is not authoritative since it did not come directly from Person B.

Is there a particular concern you are trying to address?
0
 
beer9Author Commented:
I see this configuration in /etc/resolv.conf where 192.168.0.1 is my netgear wifi router. so 192.168.0.1 is serving as both the default gateway and default DNS server. I am not sure whether there is any DNS server is running on 192.168.0.1. But still it is helping to resolve the DNS name. I can not telnet to 192.168.0.1 on port 53

I have configured 4.2.2.1 and 4.2.2.2 as the primary and secondary DNS server in my wifi router(192.168.0.1). How this name query transaction is happening?
bash-3.2$ cat /etc/resolv.conf 
nameserver 192.168.0.1
 
---
 
bash-3.2$ telnet 192.168.0.1 53
Trying 192.168.0.1...
^C
bash-3.2$
 
---
 
bash-3.2$ nslookup google.com 
Server:		192.168.0.1
Address:	192.168.0.1#53
 
Non-authoritative answer:
Name:	google.com
Address: 74.125.67.100
Name:	google.com
Address: 209.85.171.100
Name:	google.com
Address: 74.125.45.100

Open in new window

0
Cloud Class® Course: Ruby Fundamentals

This course will introduce you to Ruby, as well as teach you about classes, methods, variables, data structures, loops, enumerable methods, and finishing touches.

 
arnoldCommented:
In short DNS works on both UDP and TCP port 53.  The TCP connection mode is used for large data transfers.  Normally routers that provide dns responses only listen on UDP 53 port only.
0
 
beer9Author Commented:
Thank you :-)
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.