Re: ANY queries to tinydns

I don't think this is the right response. The only useful information in
a truncated response is the number of records you are supposed to get.  
The rest of the data in the packet is just garbage, as it can't be used
or cached, or even read completely (length of last RR may be past the
end of packet)  I can't imagine why firewall should have problems with
such a packet, but that's on the firewall.

		--Dean

On Wed, 31 Mar 2010, Matthew Dempsky wrote:

> On Wed, Mar 31, 2010 at 9:32 AM, David Hubbard
> <[email protected]> wrote:
> > Can someone tell me what the official behavior of
> > tinydns is supposed to be when an ANY query is
> > sent to it?  And preferably when the response
> > would be and wouldn't be larger than a udp packet.
> > Using wireshark it reports malformed response on
> > ANY queries to domains with a lot of records.
> 
> Try applying the patch below.  When tinydns sends a truncated
> response, it leaves the numrecords fields set to the number of records
> it wanted to send, not the number actually sent.  Some firewalls
> apparently don't like this behavior though.
> 
> 
> --- response.c.orig	2010-03-31 09:50:48.000000000 -0700
> +++ response.c	2010-03-31 09:50:56.000000000 -0700
> @@ -117,5 +117,6 @@
>  void response_tc(void)
>  {
>    response[2] |= 2;
> +  byte_zero(response + 6,6);
>    response_len = tctarget;
>  }
> 
> 

-- 
Av8 Internet   Prepared to pay a premium for better service?
www.av8.net         faster, more reliable, better service
617 256 5494