BIND 10 #834: no EDNS0 on outgoing queries

BIND 10 Development do-not-reply at isc.org
Mon May 23 14:27:14 UTC 2011


#834: no EDNS0 on outgoing queries
-------------------------------------+-------------------------------------
                   Reporter:  jelte  |                 Owner:  jelte
                       Type:         |                Status:  reviewing
  defect                             |             Milestone:  Year 3 Task
                   Priority:  major  |  Backlog
                  Component:         |            Resolution:
  resolver                           |             Sensitive:  0
                   Keywords:         |           Sub-Project:  DNS
            Defect Severity:         |  Estimated Difficulty:  1.0
  Medium                             |           Total Hours:  0
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jelte):

 since it was still assigned to me, i just did even though it was not
 really on the short-term goal

 only the last commit (41139644452bb11a162254b442ab611644ceb603) is really
 relevant, the earlier ones are an initial change (which also was kind of
 in master already) and a merge from master.

 now actually sets edns0, but does not set DO bit (which appears to break
 the resolver as far as the resolver works already). updated test to
 reflect the added EDNS0 message.

 there's no fallback for edns lameness (yet), it would make much more sense
 to do that after we pull dns logic out of iofetch

-- 
Ticket URL: <http://bind10.isc.org/ticket/834#comment:8>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development


More information about the bind10-tickets mailing list