<P>
Hi<BR>
I also have an issue regarding test case no. 47....<BR>
th=

e NUT receives response where the most significant bit of the TTL<BR>
is =

set. So that NUT should consider it as zero....Now in the next step<BR>
N=

UT is supossed to send query within 10 secs...& that should not reach t=

o<BR>
the TN...that means it should be able to reply from its cache itsel=

f....<BR>
Now the most surprising thing is that how can the NUT reply fro=

m<BR>
its cache coz it got the response with TTL as zero...&amp; as per a=

ll <BR>
RFCs(1034, 1035), the data with TTL value zero should not be cach=

ed<BR>
(Reference RFC1035, 3.2.1, RFC1034, 3.6, RFC2065 4.4)... if the TT=

L value is zero..<BR>
Please comment....<BR>
<BR>
thanks &amp; regard=

s<BR>
<BR>
Prem&nbsp; <BR>

</P>
<br><br>
<a href="http://adw=

orks.rediff.com/cgi-bin/AdWorks/sigclick.cgi/www.rediff.com/signature-home.=

htm/1507191490@Middle5?PARTNER=3"><IMG SRC="http://adworks.rediff.com/c=

gi-bin/AdWorks/sigimpress.cgi/www.rediff.com/signature-home.htm/1963059423@=

Middle5?OAS_query=null&PARTNER=3" BORDER=0 VSPACE=0 HSPACE=0></a>=