Nslookup not showng TTL

[Kevin Darcy]

John Horne wrote:
> On Thu, 2009-10-15 at 10:47 +0200, Adam Tkac wrote:
>   
>> On Thu, Oct 15, 2009 at 09:06:56AM +0100, John Horne wrote:
>>     
>>> How can I see the TTL value using nslookup?
>>>       
>> I'm not sure how force nslookup to show TTL but the `dig` utility is
>> far more better tool for getting such information:
>>
>>     
> I agree, it's not for me though :-)
>
> I have to teach some Windows people about the DNS, and wanted to show
> them that they could use 'nslookup' on either the Linux box provided, or
> their own Windows PC's. In this instance the TTL is important. So I was
> hoping that the MS and BIND nslookup commands would display something
> pretty much similar to each other so as not to confuse the people too
> much.
>
> As far as I can tell no BIND 9 nslookup command shows the TTL. I am
> currently looking at an 8.2.3 version to see if I can patch the 9.5.1
> one to display TTL's again. It may, however, be better to introduce them
> to dig rather than having to maintain the nslookup command.
>   
Removing features from nslookup gets us that much closer to KILLING and 
BURYING it. Forever.

If I had a nickel for every time someone mis-read the output of nslookup 
and mistook the nameserver's name, for the name of the server they're 
actually looking up, well, let's just say I probably wouldn't be posting 
to bind-users from my work account...

(Fortunately nslookup's whole "won't do a lookup because I can't 
reverse-resolve my resolver" bogosity isn't really an issue at Chrysler, 
since we maintain proper reverse mappings, but that's another popular 
"nslookup sucks, don't use it"-category posting to this mailing list)

                                                                         
                           - Kevin