BIND 10 #2247: "RRSIG is being added, but no RR of covered type found" should not be fatal

BIND 10 Development do-not-reply at isc.org
Mon Sep 10 15:36:37 UTC 2012


#2247: "RRSIG is being added, but no RR of covered type found"  should not be
fatal
-------------------------------------+-------------------------------------
            Reporter:  jreed         |                        Owner:
                Type:  defect        |                       Status:  new
            Priority:  medium        |                    Milestone:  New
           Component:  data source   |  Tasks
           Sensitive:  0             |                     Keywords:
         Sub-Project:  DNS           |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
 "AUTH_SERVER_FAILED server failed: RRSIG is being added, but no RR of
 covered type found" is fatal (via isc_throw) causing b10-auth and then
 bind10 to shutdown at startup.  An error in a zone file should not cause
 the auth server to shutdown (since may server other working zones) and
 certainly should not shutdown boss (which makes it so you can't
 reconfigure).

 This is from
 https://lists.isc.org/pipermail/bind10-users/2012-September/000393.html

 The code is in
 src/lib/datasrc/memory_datasrc.cc

 Also to be discussed: why do we have log sentences hard-coded versus using
 unique logging messages. (This means we can't have explanations and can't
 do translations easily.)

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


More information about the bind10-tickets mailing list