As long as you know what to compare the result to, yes.
A far easier way would be to perform a lookup directly against the authoritative nameserver for the domain in question. For facebook.com that would be:
Code:
# nslookup -q=ns facebook.com 8.8.8.8
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
facebook.com nameserver = a.ns.facebook.com.
facebook.com nameserver = b.ns.facebook.com.
...
a.ns.facebook.com and
b.ns.facebook.com, which have the IP addresses:
Code:
# nslookup -q=a a.ns.facebook.com
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
Name: a.ns.facebook.com
Address: 69.171.239.12
# nslookup -q=a b.ns.facebook.com
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
Name: b.ns.facebook.com
Address: 69.171.255.12
...
69.171.239.12 and 69.171.255.12 respectively, unless 8.8.8.8 has been successfully poisoned by a spoofing attack already, that is.
Performing a direct lookup against an authoritative name server is the closest you can get to a surefire way of avoiding spoofing. If such a server gives the wrong answer, the server itself or possibly the entire zone must have been hijacked through some other means, and in that case all bets are off anyway.
