BIND 10 #1386: fallback from EDNS over UDP to plain DNS or EDNS/DNS over TCP is needed in real life

[BIND 10 Development]

#1386: fallback from EDNS over UDP to plain DNS or EDNS/DNS over TCP is needed in
real life
-------------------------------------+-------------------------------------
                   Reporter:  dvv    |                 Owner:  dvv
                       Type:         |                Status:  accepted
  defect                             |             Milestone:
                   Priority:  major  |  Sprint-20111220
                  Component:         |            Resolution:
  resolver                           |             Sensitive:  0
                   Keywords:  EDNS   |           Sub-Project:  DNS
  fallback                           |  Estimated Difficulty:  0
            Defect Severity:  High   |           Total Hours:  0
Feature Depending on Ticket:         |
  resolver                           |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Replying to [comment:4 dvv]:
 > Added EDNS fallback functionality: first to EDNS over TCP and, if it
 fails, non-EDNS over UDP.

 Just wondering: what's the rationale of this behavior?  At least it seems
 to be quite
 different from BIND 9's fallback algorithm.

 > TODO: cache EDNS failure info for server addresses

 Considering it already takes several weeks, I'd suggest deferring this
 part to
 a separate task.

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