Date: Mon, 21 Nov 2005 22:37:47 +0900
From: Hideshi Enokihara <Hideshi.Enokihara@jp.yokogawa.com>
Subject: [users:00168] Re: How to send DNS server status query
To: "PRAMENDRA  SINGH" <parma_it@rediffmail.com>
Cc: users@tahi.org
Message-Id: <20051121223747.3b308e04.Hideshi.Enokihara@jp.yokogawa.com>
In-Reply-To: <20051121125902.27306.qmail@webmail31.rediffmail.com>
References: <20051121125902.27306.qmail@webmail31.rediffmail.com>
X-Mail-Count: 00168

Hi Pramendra,

Thank you for your report.

"OPCODE:3" is just typo by TAHI.
Correct number of a server status request is 2.
This type will be fixed in next version.
And I don't know implementation that can send query for server status request.

OPCODE:2 is Experimental in RFC.
So, I think that almost implementation doesn't support this type.


You are always helpful for us,
Thank you.

On 21 Nov 2005 12:59:02 -0000
"PRAMENDRA  SINGH" <parma_it@rediffmail.com> wrote:

> Hi to all,
> 
> 
> As per Rfc 1035 OPCODE: 2 means a server status request. But I dint get anywhere how to send this type of query using dig. The bind-9.2.4 also has not implemented this option. But Tahi has newly introduced some DNS Client test case where the test case no. 18 speaks of this one. Most surprising thing is that they are expecting OPCODE=3 , which doesn't tele with RFCs......Plz help me out is there any way of sending this type of query...even if its possible then why Tahi people are expecting this OPCODE value as 3.
> 
> thanks & regards
> Pramendra Singh
> 
> 


-- 
*************************************
Hideshi Enokihara
IPv6 Business
Network & Software Development Dept.
Yokogawa Electric Corporation