On 8/18/18, Doug Barton wrote:
> On 08/18/2018 04:53 PM, Barry Margolin wrote:
>> In article ,
>> Grant Taylor wrote:
>>
>>> On 08/18/2018 07:25 AM, Bob McDonald wrote:
I don't think anyone hates nslookup (well maybe a few do ) I
suppose the immense dislike stems from the fact that it
On 08/19/2018 12:11 PM, Lee wrote:
On 8/18/18, Doug Barton wrote:
nslookup uses the local resolver stub. That's fine, if that's what you
want/need to test. If you want to test specific servers, or what is
visible from the Internet, etc. dig is the right tool, as the answers
you get from nsloo
On 8/19/18, Doug Barton wrote:
> On 08/19/2018 12:11 PM, Lee wrote:
>> On 8/18/18, Doug Barton wrote:
>
>>> nslookup uses the local resolver stub. That's fine, if that's what you
>>> want/need to test. If you want to test specific servers, or what is
>>> visible from the Internet, etc. dig is the
nslookup applies the search list by default and doesn’t stop on a NODATA
response.
Some versions of nslookup have been modified by OS vendors to use /etc/hosts
for address lookups.
nslookup doesn’t display the entire response by default.
> On 20 Aug 2018, at 12:28 pm, Lee wrote:
>
> On 8/19
And don't forget NIS, and NSSwitch. And don't get me started on the
tricks that the windows resolver plays.
On 08/19/2018 07:59 PM, Mark Andrews wrote:
nslookup applies the search list by default and doesn’t stop on a NODATA
response.
Some versions of nslookup have been modified by OS vendors
5 matches
Mail list logo
