Or one can use nslookup from BIND 9 which doesn't have that
restriction.
nslookups with this restriction are at least 10 years old now and
there have been new types added. DNSSEC has been completely
overhauled in that time.
Mark
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Aust
On Fri, Mar 16, 2012 at 5:03 PM, G.W. Haywood wrote:
You didn't tell the OP what to use instead of nslookup!
sorry :-)
On 16.03.12 19:33, Ashok Agarwal wrote:
If PTR is present then it works pretty well. My concern is without PTR
record.
Ya I can use "dig" instead to nslookup
you can also u
If PTR is present then it works pretty well. My concern is without PTR
record.
Ya I can use "dig" instead to nslookup but I need to fix it in nslookup as
well.
If anybody has any clue or can tell how it be fixed then it will really
help me and it be highly appreciated.
-Ashok
On Fri, Mar 16, 2012
Hi there,
On Fri, 16 Mar 2012, Matus UHLAR - fantomas wrote:
the main problem is nslookup itself, and this is just one of reasons
nslookup is not recommended for use.
You didn't tell the OP what to use instead of nslookup!
It's 'dig'.
--
73,
Ged.
___
On 16.03.12 14:57, Ashok Agarwal wrote:
I am trying to nslookup nameserver through IPv6 address. but nslookup is
failing to resolv nameserver when nameserver's PTR record is missing.
Kindly let me know if anybody has any fix for this problem.
the main problem is nslookup itself, and this is jus
Hi,
I am using BIND 9.3 as my DNS server.
I am trying to nslookup nameserver through IPv6 address. but nslookup is
failing to resolv nameserver when nameserver's PTR record is missing.
Kindly let me know if anybody has any fix for this problem.
Thanks in anticipation.
Regards,
-Ashok
6 matches
Mail list logo
