Opened 8 years ago

Closed 6 years ago

#1936 closed enhancement (wontfix)

What packet resulted in AUTH_PACKET_PARSE_ERROR ?

Reported by: jreed Owned by:
Priority: medium Milestone: Remaining BIND10 tickets
Component: Unclassified Version: bind10-old
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: DNS Feature Depending on Ticket:
Estimated Difficulty: 0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no


2012-05-01 23:27:33.825 DEBUG [b10-auth.auth] AUTH_PACKET_PARSE_ERROR unable to 
parse received DNS packet: RDLENGTH mismatch: 2 != 0

What packet resulted in AUTH_PACKET_PARSE_ERROR?

Getting around 17000 queries per second so hard to know. I got this error 984 times in about 11 seconds. (1000 SERVFAILs were sent.)

Documentation has:

AUTH_PACKET_PARSE_ERROR unable to parse received DNS packet: %1

    This is a debug message, generated by the authoritative server when an attempt to parse a received DNS packet has failed due to something other than a protocol error. The reason for the failure is given in the message; the server will return a SERVFAIL error code to the sender. 


Change History (3)

comment:1 Changed 8 years ago by shane

  • Milestone New Tasks deleted
  • Type changed from defect to enhancement

Interesting. This is a DEBUG message, so this error is not something that we would normally see. However, it may be interesting. (I think the particular message indicates that there was not enough data in the packet considering the length used for the RDATA packet.)

We can't really display too much about the packet, since the parse failed. Perhaps the right thing to do is add a facility for the administrator to log bogus packets? (Ultimately this is exactly right for a hook, but perhaps we can get something sooner?)

comment:2 Changed 6 years ago by tomek

  • Milestone set to Remaining BIND10 tickets

comment:3 Changed 6 years ago by tomek

  • Resolution set to wontfix
  • Status changed from new to closed
  • Version set to old-bind10

This issue is related to bind10 code that is no longer part of Kea.

If you are interested in BIND10/Bundy framework or its DNS components,
please check

Closing ticket.

Note: See TracTickets for help on using tickets.