Kevin Darcy wrote:
> 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` utili
In message <76d7097b-28a4-4bbb-a2c8-05bf5b822...@conundrum.com>, Matthew Pounse
tt writes:
>
> On 15-Oct-2009, at 16:03, John Horne wrote:
>
> > On Thu, 2009-10-15 at 13:15 -0400, Kevin Darcy wrote:
> >>>
> >> Removing features from nslookup gets us that much closer to KILLING
> >> and
> >> BU
On 15-Oct-2009, at 16:03, John Horne wrote:
On Thu, 2009-10-15 at 13:15 -0400, Kevin Darcy wrote:
Removing features from nslookup gets us that much closer to KILLING
and
BURYING it. Forever.
So why does the ISC still distribute it?
(Although I guess the answer may simply be "because peop
On Thu, 2009-10-15 at 13:15 -0400, Kevin Darcy wrote:
> >
> Removing features from nslookup gets us that much closer to KILLING and
> BURYING it. Forever.
>
So why does the ISC still distribute it?
(Although I guess the answer may simply be "because people still use
it".)
Don't get me wrong h
You can do an "ipconfig /displaydns" to see some TTL info.
Frank
-Original Message-
From: bind-users-boun...@lists.isc.org
[mailto:bind-users-boun...@lists.isc.org] On Behalf Of John Horne
Sent: Thursday, October 15, 2009 3:07 AM
To: Bind users
Subject: Nslookup not showng
In article ,
Kevin Darcy wrote:
> (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 posti
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 suc
In article ,
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
Sent: Thursday, October 15, 2009 5:46:27 AM
Subject: Re: Nslookup not showng TTL
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
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
On Thu, Oct 15, 2009 at 09:06:56AM +0100, John Horne wrote:
> Hello,
Hi,
> Using BIND 9.5.1 it seems that the nslookup command is not showing the
> TTL value of found records. It makes no difference if I set 'debug' or
> 'd2'. Example:
>
>
Hello,
Using BIND 9.5.1 it seems that the nslookup command is not showing the
TTL value of found records. It makes no difference if I set 'debug' or
'd2'. Example:
==
nslookup
> set debug
> www.plymouth.ac.uk
Server: 127.0.0.1
Ad
12 matches
Mail list logo