elearn
By:
elearn

why the actual DNS was not displayed on the screen?

August 20, 2015 1.8k views
DNS

Here is my zone file on my dns.

$ORIGIN f10.work.
$TTL 1800
f10.work. IN SOA ns1.digitalocean.com. hostmaster.f10.work. 1439986690 10800 3600 604800 1800
f10.work. 1800 IN NS ns1.digitalocean.com.
f10.work. 1800 IN NS ns2.digitalocean.com.
f10.work. 1800 IN NS ns3.digitalocean.com.
f10.work. 1800 IN A 128.199.164.28
*.f10.work. 1800 IN CNAME f10.work.
f10.work. 1800 IN MX 1 mail.f10.work.


root@pengsir:/home/debian8# nslookup  f10.work
Server:             223.5.5.5
Address:    223.5.5.5#53

Non-authoritative answer:
Name:       f10.work
Address: 128.199.164.28


ping ns1.digitalocean.com
PING ns1.digitalocean.com (173.245.58.51) 56(84) bytes of data.

In fact the 173.245.58.51 is my dns,why the actual DNS was not displayed on the screen?

Log In to Comment
2 Answers
Woet August 20, 2015

nslookup's server is referring to your recursor, not the nameserver.

Reply
dnscheck August 22, 2015

nslookup looks like it's returning the correct data. The f10.work A record points to 128.199.164.28, which matches the address that nslookup is reporting under the "Non-authoritative answer" heading.

Dig can produce more concise output. For example, to query one of Digital Ocean's nameservers, you could run:

$ dig a +short f10.work @ns1.digitalocean.com
128.199.164.28
Reply
Have another answer? Share your knowledge.

Related Questions