BIND 10 #2841: deal with inet_pton that doesn't recognize AF_INET6

BIND 10 Development do-not-reply at isc.org
Tue Mar 5 21:24:37 UTC 2013


#2841: deal with inet_pton that doesn't recognize AF_INET6
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  UnAssigned
  jinmei                             |                Status:  new
                       Type:         |             Milestone:  New Tasks
  defect                             |              Keywords:
                   Priority:         |             Sensitive:  0
  medium                             |           Sub-Project:  DNS
                  Component:  build  |  Estimated Difficulty:  0
  system                             |           Total Hours:  0
               CVSS Scoring:         |
            Defect Severity:  N/A    |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
 I've received a feedback from a user who tried to build and used BIND
 10.  The OS is CentOS6 (reportedly), disables IPv6 in the kernel, and
 apparently its inet_pton doesn't recognize AF_INET6 (not sure it's
 related to the kernel support of IPv6; API-wise it should be
 independent).

 This caused at least two known issues:

 - some test data (generated by src/lib/util/python/gen_wiredata.py)
   can't be generated because the genetator script fails to create AAAA
   rdata.
 - b10-resolver (and I suspect b10-auth also) failed to start up
   because its default config has ::1/53 for listen_on, which is
   considered a syntax error.

 I'm not sure whether we want to help such environment; it seems to me
 inet_pton that doesn't recognize AF_INET6 is so broken and wouldn't
 worth introducing another layer of complexity in our code.  But if
 such a deployment is actually not so uncommon, we may have to do
 something in our side.

 At the moment my suggestion is to discuss it; so it's probably not
 estimatable.

-- 
Ticket URL: <http://bind10.isc.org/ticket/2841>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development


More information about the bind10-tickets mailing list