Skip Menu |

This queue is for tickets about the Net-DNS CPAN distribution.

Report information
The Basics
Id: 37281
Status: resolved
Priority: 0/
Queue: Net-DNS
People
Owner: Nobody in particular
Requestors: kvs [...] binarysolutions.dk
Cc:
AdminCc:
Bug Information
Severity: Important
Broken in: 0.63
Fixed in: (no value)

History Show all quoted text
  Tue Jul 01 06:40:01 2008 kvs [...] binarysolutions.dk - Ticket created
Subject: Net::DNS::Packet's over 64 KB are invalid
I'm trying to build an AXFR-server, and ran into the problem that transfers over 64 KB in size get funny errors, due to the fact that $reply->data's length is written as an unsigned short (as is required). I'm not strong in my RFCs, but I think the fix requires Net::DNS::Nameserver to split its answers up between multiple Net::DNS::Packet-replies? I'd be happy to try and create a patch, if somebody could point me to the right solution :-) /Kenneth
  Thu Aug 28 08:00:19 2008 OLAF [...] cpan.org - Correspondence added
On Tue Jul 01 06:40:01 2008, kvs@binarysolutions.dk wrote: Show quoted text
> I'm trying to build an AXFR-server, and ran into the problem that > transfers over 64 KB in size get funny errors, due to the fact that > $reply->data's length is written as an unsigned short (as is required). >
That is correct. In the DNS packet the size of the data is indicated by a two octet field (cf RFC1035 4.2.2). If your zone is bigger then you will need more answer packets on the same stream. Currently there is some clarification work going on within the IETF. You might find section 2 of http://tools.ietf.org/html/draft-ietf-dnsext-axfr-clarify interesting. Show quoted text
> I'm not strong in my RFCs, but I think the fix requires > Net::DNS::Nameserver to split its answers up between multiple > Net::DNS::Packet-replies? I'd be happy to try and create a patch, if > somebody could point me to the right solution :-) >
since I do not think further action is needed, I'll close the ticket I'll close the ticket. --Olaf
  Thu Aug 28 08:00:31 2008 The RT System itself - Status changed from 'new' to 'open'
  Thu Aug 28 08:00:35 2008 OLAF [...] cpan.org - Status changed from 'open' to 'resolved'
  Thu Aug 28 08:00:36 2008 OLAF [...] cpan.org - Correspondence added
On Tue Jul 01 06:40:01 2008, kvs@binarysolutions.dk wrote: Show quoted text
> I'm trying to build an AXFR-server, and ran into the problem that > transfers over 64 KB in size get funny errors, due to the fact that > $reply->data's length is written as an unsigned short (as is required). >
That is correct. In the DNS packet the size of the data is indicated by a two octet field (cf RFC1035 4.2.2). If your zone is bigger then you will need more answer packets on the same stream. Currently there is some clarification work going on within the IETF. You might find section 2 of http://tools.ietf.org/html/draft-ietf-dnsext-axfr-clarify interesting. Show quoted text
> I'm not strong in my RFCs, but I think the fix requires > Net::DNS::Nameserver to split its answers up between multiple > Net::DNS::Packet-replies? I'd be happy to try and create a patch, if > somebody could point me to the right solution :-) >
since I do not think further action is needed, I'll close the ticket I'll close the ticket. --Olaf
  Thu Aug 28 08:00:41 2008 The RT System itself - Status changed from 'resolved' to 'open'
  Thu Aug 28 08:00:44 2008 OLAF [...] cpan.org - Status changed from 'open' to 'resolved'