BIND 10 #3058: BIND10-1.1.0 Resolver fails to answer some Queries

BIND 10 Development do-not-reply at isc.org
Wed Jul 17 14:45:58 UTC 2013


#3058: BIND10-1.1.0 Resolver fails to answer some Queries
-------------------------------------+-------------------------------------
            Reporter:  thozza        |                         Type:
              Status:  new           |  defect
           Milestone:  New Tasks     |                     Priority:
            Keywords:                |  medium
           Sensitive:  0             |                    Component:
         Sub-Project:  DNS           |  Unclassified
Estimated Difficulty:  0             |                 CVSS Scoring:
         Total Hours:  0             |              Defect Severity:  High
                                     |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
 Hi.

 When running latest bind10-1.1.0 recursive resolver with default
 configuration it fails
 to answer some Queries. It returns SERVFAIL. The host that I'm running the
 resolver on
 has only link local IPv6 address. The problem seems to be that resolver
 fails to send
 DNS Query to IPv6 address.

 Here is an output from system log when running 'dig @127.0.0.1 nic.cz'
 when BIND10 resolver
 is running on localhost:

 -- Logs begin at Mon 2013-07-08 09:57:45 CEST, end at Wed 2013-07-17
 16:25:07 CEST. --
 Jul 17 16:25:07 localhost.localdomain bind10[3576]: 2013-07-17
 16:25:07.482 ERROR [b10-resolver.asiodns/3582] ASIODNS_SEND_DATA error 101
 sending data using UDP to 2001:628:453:420::48(53)
 Jul 17 16:25:05 localhost.localdomain bind10[3576]: 2013-07-17
 16:25:05.481 ERROR [b10-resolver.asiodns/3582] ASIODNS_SEND_DATA error 101
 sending data using UDP to 2001:678:f::1(53)
 Jul 17 16:25:00 localhost.localdomain bind10[3576]: 2013-07-17
 16:25:00.353 INFO  [b10-stats.stats/3583] STATS_STARTING starting
 Jul 17 16:25:00 localhost.localdomain bind10[3576]: 2013-07-17
 16:25:00.234 INFO  [b10-resolver.resolver/3582] RESOLVER_STARTED resolver
 started
 Jul 17 16:25:00 localhost.localdomain bind10[3576]: 2013-07-17
 16:25:00.232 INFO  [b10-init.init/3576] BIND10_SOCKET_CREATED successfully
 created socket 24
 Jul 17 16:25:00 localhost.localdomain bind10[3576]: 2013-07-17
 16:25:00.231 INFO  [b10-init.init/3576] BIND10_SOCKET_GET requesting
 socket [127.0.0.1]:53 of type UDP from the creator
 Jul 17 16:25:00 localhost.localdomain bind10[3576]: 2013-07-17
 16:25:00.228 INFO  [b10-init.init/3576] BIND10_SOCKET_CREATED successfully
 created socket 23
 Jul 17 16:25:00 localhost.localdomain bind10[3576]: 2013-07-17
 16:25:00.228 INFO  [b10-init.init/3576] BIND10_SOCKET_GET requesting
 socket [127.0.0.1]:53 of type TCP from the creator
 Jul 17 16:25:00 localhost.localdomain bind10[3576]: 2013-07-17
 16:25:00.226 INFO  [b10-init.init/3576] BIND10_SOCKET_CREATED successfully
 created socket 22
 Jul 17 16:25:00 localhost.localdomain bind10[3576]: 2013-07-17
 16:25:00.224 INFO  [b10-init.init/3576] BIND10_SOCKET_GET requesting
 socket [::1]:53 of type UDP from the creator
 Jul 17 16:25:00 localhost.localdomain bind10[3576]: 2013-07-17
 16:25:00.222 INFO  [b10-init.init/3576] BIND10_SOCKET_CREATED successfully
 created socket 20
 Jul 17 16:25:00 localhost.localdomain bind10[3576]: 2013-07-17
 16:25:00.221 INFO  [b10-init.init/3576] BIND10_SOCKET_GET requesting
 socket [::1]:53 of type TCP from the creator
 Jul 17 16:25:00 localhost.localdomain bind10[3576]: 2013-07-17
 16:25:00.206 INFO  [b10-resolver.resolver/3582] RESOLVER_SET_QUERY_ACL
 query ACL is configured
 Jul 17 16:25:00 localhost.localdomain bind10[3576]: 2013-07-17
 16:25:00.206 WARN  [b10-resolver.resolver/3582] RESOLVER_NO_ROOT_ADDRESS
 no root addresses available
 Jul 17 16:25:00 localhost.localdomain bind10[3576]: 2013-07-17
 16:25:00.206 INFO  [b10-resolver.resolver/3582] RESOLVER_RECURSIVE running
 in recursive mode
 Jul 17 16:25:00 localhost.localdomain bind10[3576]: 2013-07-17
 16:25:00.204 INFO  [b10-resolver.resolver/3582] RESOLVER_STARTING starting
 resolver with command line 'b10-resolver'
 Jul 17 16:25:00 localhost.localdomain bind10[3576]: 2013-07-17
 16:25:00.183 INFO  [b10-init.init/3576] BIND10_STARTUP_COMPLETE BIND 10
 started
 Jul 17 16:25:00 localhost.localdomain bind10[3576]: 2013-07-17
 16:25:00.178 INFO  [b10-init.init/3576] BIND10_STARTING_PROCESS starting
 process b10-cmdctl
 Jul 17 16:25:00 localhost.localdomain bind10[3576]: 2013-07-17
 16:25:00.177 INFO  [b10-init.init/3576] BIND10_COMPONENT_START component
 b10-cmdctl is starting
 Jul 17 16:25:00 localhost.localdomain bind10[3576]: 2013-07-17
 16:25:00.170 INFO  [b10-init.init/3576] BIND10_STARTING_PROCESS starting
 process b10-stats
 Jul 17 16:25:00 localhost.localdomain bind10[3576]: 2013-07-17
 16:25:00.169 INFO  [b10-init.init/3576] BIND10_COMPONENT_START component
 b10-stats is starting
 Jul 17 16:25:00 localhost.localdomain bind10[3576]: 2013-07-17
 16:25:00.167 INFO  [b10-init.init/3576] BIND10_STARTING_PROCESS starting
 process b10-resolver
 Jul 17 16:25:00 localhost.localdomain bind10[3576]: 2013-07-17
 16:25:00.166 INFO  [b10-init.init/3576] BIND10_COMPONENT_START component
 b10-resolver is starting
 Jul 17 16:25:00 localhost.localdomain bind10[3576]: 2013-07-17
 16:25:00.166 INFO  [b10-init.init/3576] BIND10_CONFIGURATOR_RECONFIGURE
 reconfiguring running components
 Jul 17 16:25:00 localhost.localdomain bind10[3576]: 2013-07-17
 16:25:00.165 INFO  [b10-init.init/3576] BIND10_READING_INIT_CONFIGURATION
 reading b10-init configuration
 Jul 17 16:25:00 localhost.localdomain bind10[3576]: 2013-07-17
 16:25:00.156 INFO  [b10-init.init/3576] BIND10_STARTING_CC starting
 configuration/command session
 Jul 17 16:25:00 localhost.localdomain bind10[3576]: 2013-07-17
 16:25:00.156 INFO  [b10-init.init/3576] BIND10_STARTING_PROCESS starting
 process b10-cfgmgr
 Jul 17 16:25:00 localhost.localdomain bind10[3576]: 2013-07-17
 16:25:00.156 INFO  [b10-init.init/3576] BIND10_COMPONENT_START component
 cfgmgr is starting
 Jul 17 16:25:00 localhost.localdomain bind10[3576]: 2013-07-17
 16:25:00.156 INFO  [b10-init.init/3576] BIND10_STARTING_PROCESS starting
 process b10-msgq
 Jul 17 16:25:00 localhost.localdomain bind10[3576]: 2013-07-17
 16:25:00.156 INFO  [b10-init.init/3576] BIND10_COMPONENT_START component
 msgq is starting
 Jul 17 16:25:00 localhost.localdomain bind10[3576]: 2013-07-17
 16:25:00.155 INFO  [b10-init/3576] BIND10_SETUID setting UID to 25
 Jul 17 16:25:00 localhost.localdomain bind10[3576]: 2013-07-17
 16:25:00.155 INFO  [b10-init.init/3576] BIND10_SETGID setting GID to 25
 Jul 17 16:25:00 localhost.localdomain bind10[3576]: 2013-07-17
 16:25:00.154 INFO  [b10-init.init/3576] BIND10_SOCKCREATOR_INIT
 initializing socket creator parser
 Jul 17 16:25:00 localhost.localdomain bind10[3576]: 2013-07-17
 16:25:00.154 INFO  [b10-init.init/3576] BIND10_COMPONENT_START component
 Socket creator is starting
 Jul 17 16:25:00 localhost.localdomain bind10[3576]: 2013-07-17
 16:25:00.153 INFO  [b10-init.init/3576] BIND10_CONFIGURATOR_START bind10
 component configurator is starting up
 Jul 17 16:25:00 localhost.localdomain bind10[3576]: 2013-07-17
 16:25:00.152 INFO  [b10-init.init/3576] BIND10_STARTING starting BIND10:
 bind10 20110223 (BIND 10 1.1.0)
 Jul 17 16:24:59 localhost.localdomain bind10[3576]: 2013-07-17
 16:24:59.199 INFO  [b10-cfgmgr.cfgmgr/3580] CFGMGR_CONFIG_FILE
 Configuration manager starting with configuration file:
 /var/bind10/b10-config.db


 # dig @127.0.0.1 nic.cz

 ; <<>> DiG 9.9.3-rl.156.01-P1-RedHat-9.9.3-3.P1.fc19 <<>> @127.0.0.1
 nic.cz
 ; (1 server found)
 ;; global options: +cmd
 ;; Got answer:
 ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 39672
 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

 ;; OPT PSEUDOSECTION:
 ; EDNS: version: 0, flags:; udp: 4096
 ;; QUESTION SECTION:
 ;nic.cz.                                IN      A

 ;; Query time: 4000 msec
 ;; SERVER: 127.0.0.1#53(127.0.0.1)
 ;; WHEN: Wed Jul 17 16:37:25 CEST 2013
 ;; MSG SIZE  rcvd: 35


 What is strange, that subsequent calls to dig return DNS Response
 successfully:

 # dig @127.0.0.1 nic.cz

 ; <<>> DiG 9.9.3-rl.156.01-P1-RedHat-9.9.3-3.P1.fc19 <<>> @127.0.0.1
 nic.cz
 ; (1 server found)
 ;; global options: +cmd
 ;; Got answer:
 ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 46683
 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 7

 ;; OPT PSEUDOSECTION:
 ; EDNS: version: 0, flags:; udp: 4096
 ;; QUESTION SECTION:
 ;nic.cz.                                IN      A

 ;; ANSWER SECTION:
 nic.cz.                 1781    IN      A       217.31.205.50

 ;; AUTHORITY SECTION:
 nic.cz.                 1781    IN      NS      a.ns.nic.cz.
 nic.cz.                 1781    IN      NS      b.ns.nic.cz.
 nic.cz.                 1781    IN      NS      d.ns.nic.cz.

 ;; ADDITIONAL SECTION:
 a.ns.nic.cz.            1781    IN      A       194.0.12.1
 b.ns.nic.cz.            1781    IN      A       194.0.13.1
 d.ns.nic.cz.            1781    IN      A       193.29.206.1
 a.ns.nic.cz.            1781    IN      AAAA    2001:678:f::1
 b.ns.nic.cz.            1781    IN      AAAA    2001:678:10::1
 d.ns.nic.cz.            1781    IN      AAAA    2001:678:1::1

 ;; Query time: 5 msec
 ;; SERVER: 127.0.0.1#53(127.0.0.1)
 ;; WHEN: Wed Jul 17 16:37:44 CEST 2013
 ;; MSG SIZE  rcvd: 234

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


More information about the bind10-tickets mailing list