BIND 10 #833: [b10-resolver] Nameservers unreachable but really are

[BIND 10 Development]

#833: [b10-resolver] Nameservers unreachable   but really are
-------------------------------------+-------------------------------------
                   Reporter:  jreed  |                 Owner:  dvv
                       Type:         |                Status:  assigned
  defect                             |             Milestone:
                   Priority:  minor  |  Sprint-20111122
                  Component:         |            Resolution:
  resolver                           |             Sensitive:  0
                   Keywords:         |           Sub-Project:  DNS
            Defect Severity:  High   |  Estimated Difficulty:  7.0
Feature Depending on Ticket:         |           Total Hours:  0
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by dvv):

 I've added more log output and am trying to run the resolver in my
 environment. Another nasty little problem that gets in the way of using
 the resolver cropped up: some heavily used name servers treat EDNS in a
 weird way: they reject EDNS requests over UDP with FORMERR no matter what
 UDP size is adviced, but happily accept them over TCP. An immediate
 example is ns[12345].msft.net. My suspicion is that most if not all non-
 bind Windows-based servers might exhibit the same behavior. I'm dealing
 with it right now. I can keep it as a part of this ticket or put this one
 on hold (as I haven't really been able to reproduce "nameservers are
 unreachable" while trying to use the resolver in real life without hitting
 the EDNS problem) and open a new ticket.

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