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
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:
>
>
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
If you didn't know, you can download dig for Windows.
For example:
http://ftp.isc.org/isc/bind9/9.6.1-P1/BIND9.6.1-P1.zip
Just stick dig.exe and the dll files in a directory that makes sense in your
environment and enjoy!
HTH
- Original Message
From: John Horne
To: Bind users
Sent:
Hi,
recently,i want to modify source code of BIND9.6.1 to adding new RR
.Now,i just begin to check RR to see how it work,but i find this method
exhausting me.i don't think this way is effective,so i'm very appreciate
some one could give me a guid, or some example:souce code is perfect
--
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
Can you set more than one Active Directory to use tkey-gssapi-
credential and tkey-domain in bind?
ie.
Two keytabs:
DNS/foo.example.org at AD1.EXAMPLE.ORG
DNS/foo.example.org at AD2.EXAMPLE.ORG
-- named.conf
--
On 15.10.09 21:29, aihua zhang wrote:
> recently,i want to modify source code of BIND9.6.1 to adding new RR.
Don't do that. You bind will be incompatible with any other DNS server and
it could lead to
> Now,i just begin to check RR to see how it work,but i find this method
> exhausting me.i
Hello BIND users,
I am following the steps provided in the README.pkcs11 from the BIND 9.7.0a3 on
a RHEL5 box. I seem to be having trouble getting the OpenSSL PKCS11 engine
patch applied. I have run:
./Configure linux-generic32 -m32 -pthread \
--pk11-libname=/opt/pkcs11/usr
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 ,
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
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 TTL
Hello,
Us
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
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
In message <20091015135428.ga19...@fantomas.sk>, Matus UHLAR - fantomas writes:
> On 15.10.09 21:29, aihua zhang wrote:
> > recently,i want to modify source code of BIND9.6.1 to adding new RR.
>
> Don't do that. You bind will be incompatible with any other DNS server and
> it could lead to
As lo
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
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
Hi,
we're getting quite a lot of messages like the ones below recently. The server
is a resolver running bind 9.6.1-P1 (compiled from source on debian etch).
16-Oct-2009 08:28:50.430 dispatch: dispatch 0xeed08400: shutting down due to
TCP receive error: [IP REMOVED]#53: connection reset
16-Oct-
18 matches
Mail list logo