[trac1038] Removed $PREFIX from message file

src/lib/datasrc/datasrc_messages.mes

@@ -12,483 +12,482 @@
 # OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
 # PERFORMANCE OF THIS SOFTWARE.
 
-$PREFIX DATASRC_
 $NAMESPACE isc::datasrc
 
 # \brief Messages for the data source library
 
-% CACHE_CREATE creating the hotspot cache
+% DATASRC_CACHE_CREATE creating the hotspot cache
 Debug information that the hotspot cache was created at startup.
 
-% CACHE_DESTROY destroying the hotspot cache
+% DATASRC_CACHE_DESTROY destroying the hotspot cache
 Debug information. The hotspot cache is being destroyed.
 
-% CACHE_INSERT inserting item '%1' into the cache
+% DATASRC_CACHE_INSERT inserting item '%1' into the cache
 Debug information. It means a new item is being inserted into the hotspot
 cache.
 
-% CACHE_OLD_FOUND older instance of cache item found, replacing
+% DATASRC_CACHE_OLD_FOUND older instance of cache item found, replacing
 Debug information. While inserting an item into the hotspot cache, an older
 instance of an item with the same name was found. The old instance will be
 removed. This should be directly followed by CACHE_REMOVE.
 
-% CACHE_FULL cache is full, dropping oldest
+% DATASRC_CACHE_FULL cache is full, dropping oldest
 Debug information. After inserting an item into the hotspot cache, the
 maximum number of items was exceeded, so the least recently used item will
 be dropped. This should be directly followed by CACHE_REMOVE.
 
-% CACHE_REMOVE removing '%1' from the cache
+% DATASRC_CACHE_REMOVE removing '%1' from the cache
 Debug information. An item is being removed from the hotspot cache.
 
-% CACHE_NOT_FOUND the item '%1' was not found
+% DATASRC_CACHE_NOT_FOUND the item '%1' was not found
 Debug information. It was attempted to look up an item in the hotspot cache,
 but it is not there.
 
-% CACHE_FOUND the item '%1' was found
+% DATASRC_CACHE_FOUND the item '%1' was found
 Debug information. An item was successfully looked up in the hotspot cache.
 
-% CACHE_EXPIRED the item '%1' is expired
+% DATASRC_CACHE_EXPIRED the item '%1' is expired
 Debug information. There was an attempt to look up an item in the hotspot
 cache. And the item was actually there, but it was too old, so it was removed
 instead and nothing is reported (the external behaviour is the same as with
 CACHE_NOT_FOUND).
 
-% CACHE_SLOTS setting the cache size to '%1', dropping '%2' items
+% DATASRC_CACHE_SLOTS setting the cache size to '%1', dropping '%2' items
 The maximum allowed number of items of the hotspot cache is set to the given
 number. If there are too many, some of them will be dropped. The size of 0
 means no limit.
 
-% CACHE_ENABLE enabling the cache
+% DATASRC_CACHE_ENABLE enabling the cache
 The hotspot cache is enabled from now on.
 
-% CACHE_DISABLE disabling the cache
+% DATASRC_CACHE_DISABLE disabling the cache
 The hotspot cache is disabled from now on. It is not going to store
 information or return anything.
 
-% QUERY_SYNTH_CNAME synthesizing CNAME from DNAME on '%1'
+% DATASRC_QUERY_SYNTH_CNAME synthesizing CNAME from DNAME on '%1'
 Debug information. While answering a query, a DNAME was met. The DNAME itself
 will be returned, but along with it a CNAME for clients which don't understand
 DNAMEs will be synthesized.
 
-% QUERY_EMPTY_DNAME the DNAME on '%1' is empty
+% DATASRC_QUERY_EMPTY_DNAME the DNAME on '%1' is empty
 During an attempt to synthesize CNAME from this DNAME it was discovered the
 DNAME is empty (it has no records). This indicates problem with supplied data.
 
-% QUERY_GET_NS_ADDITIONAL addition of A/AAAA for '%1' requested by NS '%2'
+% DATASRC_QUERY_GET_NS_ADDITIONAL addition of A/AAAA for '%1' requested by NS '%2'
 Debug information. While processing a query, a NS record was met. It
 references the mentioned address, so A/AAAA records for it are looked up
 and put it into the additional section.
 
-% QUERY_GET_MX_ADDITIONAL addition of A/AAAA for '%1' requested by MX '%2'
+% DATASRC_QUERY_GET_MX_ADDITIONAL addition of A/AAAA for '%1' requested by MX '%2'
 Debug information. While processing a query, a MX record was met. It
 references the mentioned address, so A/AAAA records for it are looked up
 and put it into the additional section.
 
-% QUERY_FOLLOW_CNAME following CNAME at '%1'
+% DATASRC_QUERY_FOLLOW_CNAME following CNAME at '%1'
 Debug information. The domain is a CNAME (or a DNAME and we created a CNAME
 for it already), so it's being followed.
 
-% QUERY_EMPTY_CNAME CNAME at '%1' is empty
+% DATASRC_QUERY_EMPTY_CNAME CNAME at '%1' is empty
 There was an CNAME and it was being followed. But it contains no records,
 so there's nowhere to go. There will be no answer. This indicates a problem
 with supplied data.
 We tried to follow
 
-% QUERY_TOO_MANY_CNAMES CNAME chain limit exceeded at '%1'
+% DATASRC_QUERY_TOO_MANY_CNAMES CNAME chain limit exceeded at '%1'
 A CNAME led to another CNAME and it led to another, and so on. After 16
 CNAMEs, the software gave up. Long CNAME chains are discouraged, and this
 might possibly be a loop as well. Note that some of the CNAMEs might have
 been synthesized from DNAMEs. This indicates problem with supplied data.
 
-% QUERY_CHECK_CACHE checking cache for '%1/%2'
+% DATASRC_QUERY_CHECK_CACHE checking cache for '%1/%2'
 Debug information. While processing a query, lookup to the hotspot cache
 is being made.
 
-% QUERY_NO_CACHE_ANY_SIMPLE ignoring cache for ANY query (%1/%2 in %3 class)
+% DATASRC_QUERY_NO_CACHE_ANY_SIMPLE ignoring cache for ANY query (%1/%2 in %3 class)
 Debug information. The hotspot cache is ignored for ANY queries for consistency
 reasons.
 
-% QUERY_NO_CACHE_ANY_AUTH ignoring cache for ANY query (%1/%2 in %3 class)
+% DATASRC_QUERY_NO_CACHE_ANY_AUTH ignoring cache for ANY query (%1/%2 in %3 class)
 Debug information. The hotspot cache is ignored for authoritative ANY queries
 for consistency reasons.
 
-% DO_QUERY handling query for '%1/%2'
+% DATASRC_DO_QUERY handling query for '%1/%2'
 Debug information. We're processing some internal query for given name and
 type.
 
-% QUERY_NO_ZONE no zone containing '%1' in class '%2'
+% DATASRC_QUERY_NO_ZONE no zone containing '%1' in class '%2'
 Lookup of domain failed because the data have no zone that contain the
 domain. Maybe someone sent a query to the wrong server for some reason.
 
-% QUERY_CACHED data for %1/%2 found in cache
+% DATASRC_QUERY_CACHED data for %1/%2 found in cache
 Debug information. The requested data were found in the hotspot cache, so
 no query is sent to the real data source.
 
-% QUERY_IS_SIMPLE simple query (%1/%2)
+% DATASRC_QUERY_IS_SIMPLE simple query (%1/%2)
 Debug information. The last DO_QUERY is a simple query.
 
-% QUERY_IS_AUTH auth query (%1/%2)
+% DATASRC_QUERY_IS_AUTH auth query (%1/%2)
 Debug information. The last DO_QUERY is an auth query.
 
-% QUERY_IS_GLUE glue query (%1/%2)
+% DATASRC_QUERY_IS_GLUE glue query (%1/%2)
 Debug information. The last DO_QUERY is query for glue addresses.
 
-% QUERY_IS_NOGLUE query for non-glue addresses (%1/%2)
+% DATASRC_QUERY_IS_NOGLUE query for non-glue addresses (%1/%2)
 Debug information. The last DO_QUERY is query for addresses that are not
 glue.
 
-% QUERY_IS_REF query for referral (%1/%2)
+% DATASRC_QUERY_IS_REF query for referral (%1/%2)
 Debug information. The last DO_QUERY is query for referral information.
 
-% QUERY_SIMPLE_FAIL the underlying data source failed with %1
+% DATASRC_QUERY_SIMPLE_FAIL the underlying data source failed with %1
 The underlying data source failed to answer the simple query. 1 means some
 error, 2 is not implemented. The data source should have logged the specific
 error already.
 
-% QUERY_AUTH_FAIL the underlying data source failed with %1
+% DATASRC_QUERY_AUTH_FAIL the underlying data source failed with %1
 The underlying data source failed to answer the authoritative query. 1 means
 some error, 2 is not implemented. The data source should have logged the
 specific error already.
 
-% QUERY_GLUE_FAIL the underlying data source failed with %1
+% DATASRC_QUERY_GLUE_FAIL the underlying data source failed with %1
 The underlying data source failed to answer the glue query. 1 means some error,
 2 is not implemented. The data source should have logged the specific error
 already.
 
-% QUERY_NOGLUE_FAIL the underlying data source failed with %1
+% DATASRC_QUERY_NOGLUE_FAIL the underlying data source failed with %1
 The underlying data source failed to answer the no-glue query. 1 means some
 error, 2 is not implemented. The data source should have logged the specific
 error already.
 
-% QUERY_REF_FAIL the underlying data source failed with %1
+% DATASRC_QUERY_REF_FAIL the underlying data source failed with %1
 The underlying data source failed to answer the query for referral information.
 1 means some error, 2 is not implemented. The data source should have logged
 the specific error already.
 
-% QUERY_INVALID_OP invalid query operation requested
+% DATASRC_QUERY_INVALID_OP invalid query operation requested
 This indicates a programmer error. The DO_QUERY was called with unknown
 operation code.
 
-% QUERY_ADD_RRSET adding RRset '%1/%2' to message
+% DATASRC_QUERY_ADD_RRSET adding RRset '%1/%2' to message
 Debug information. An RRset is being added to the response message.
 
-% QUERY_COPY_AUTH copying authoritative section into message
+% DATASRC_QUERY_COPY_AUTH copying authoritative section into message
 Debug information. The whole referral information is being copied into the
 response message.
 
-% QUERY_DELEGATION looking for delegation on the path to '%1'
+% DATASRC_QUERY_DELEGATION looking for delegation on the path to '%1'
 Debug information. The software is trying to identify delegation points on the
 way down to the given domain.
 
-% QUERY_ADD_SOA adding SOA of '%1'
+% DATASRC_QUERY_ADD_SOA adding SOA of '%1'
 Debug information. A SOA record of the given zone is being added to the
 authority section of the response message.
 
-% QUERY_ADD_NSEC adding NSEC record for '%1'
+% DATASRC_QUERY_ADD_NSEC adding NSEC record for '%1'
 Debug information. A NSEC record covering this zone is being added.
 
-% QUERY_ADD_NSEC3 adding NSEC3 record of zone '%1'
+% DATASRC_QUERY_ADD_NSEC3 adding NSEC3 record of zone '%1'
 Debug information. A NSEC3 record for the given zone is being added to the
 response message.
 
-% QUERY_NO_DS_NSEC3 there's no DS record in the '%1' zone
+% DATASRC_QUERY_NO_DS_NSEC3 there's no DS record in the '%1' zone
 An attempt to add a NSEC3 record into the message failed, because the zone does
 not have any DS record. This indicates problem with the provided data.
 
-% QUERY_NO_DS_NSEC there's no DS record in the '%1' zone
+% DATASRC_QUERY_NO_DS_NSEC there's no DS record in the '%1' zone
 An attempt to add a NSEC record into the message failed, because the zone does
 not have any DS record. This indicates problem with the provided data.
 
-% QUERY_WILDCARD looking for a wildcard covering '%1'
+% DATASRC_QUERY_WILDCARD looking for a wildcard covering '%1'
 Debug information. A direct match wasn't found, so a wildcard covering the
 domain is being looked for now.
 
-% QUERY_WILDCARD_PROVENX_FAIL unable to prove nonexistence of '%1' (%2)
+% DATASRC_QUERY_WILDCARD_PROVENX_FAIL unable to prove nonexistence of '%1' (%2)
 While processing a wildcard, it wasn't possible to prove nonexistence of the
 given domain or record.  The code is 1 for error and 2 for not implemented.
 
-% QUERY_WILDCARD_REFERRAL unable to find referral info for '%1' (%2)
+% DATASRC_QUERY_WILDCARD_REFERRAL unable to find referral info for '%1' (%2)
 While processing a wildcard, a referral was met. But it wasn't possible to get
 enough information for it.  The code is 1 for error, 2 for not implemented.
 
-% QUERY_PROCESS processing query '%1/%2' in the '%3' class
+% DATASRC_QUERY_PROCESS processing query '%1/%2' in the '%3' class
 Debug information. A sure query is being processed now.
 
-% QUERY_RRSIG unable to answer RRSIG query
+% DATASRC_QUERY_RRSIG unable to answer RRSIG query
 The server is unable to answer a direct query for RRSIG type, but was asked
 to do so.
 
-% QUERY_MISPLACED_TASK task of this type should not be here
+% DATASRC_QUERY_MISPLACED_TASK task of this type should not be here
 This indicates a programming error. A task was found in the internal task
 queue, but this kind of task wasn't designed to be inside the queue (it should
 be handled right away, not queued).
 
-% QUERY_TASK_FAIL task failed with %1
+% DATASRC_QUERY_TASK_FAIL task failed with %1
 The query subtask failed. The reason should have been reported by the subtask
 already. The code is 1 for error, 2 for not implemented.
 
-% QUERY_MISSING_NS missing NS records for '%1'
+% DATASRC_QUERY_MISSING_NS missing NS records for '%1'
 NS records should have been put into the authority section. However, this zone
 has none. This indicates problem with provided data.
 
-% UNEXPECTED_QUERY_STATE unexpected query state
+% DATASRC_UNEXPECTED_QUERY_STATE unexpected query state
 This indicates a programming error. An internal task of unknown type was
 generated.
 
-% QUERY_FAIL query failed
+% DATASRC_QUERY_FAIL query failed
 Some subtask of query processing failed. The reason should have been reported
 already. We are returning SERVFAIL.
 
-% QUERY_BAD_REFERRAL bad referral to '%1'
+% DATASRC_QUERY_BAD_REFERRAL bad referral to '%1'
 The domain lives in another zone. But it is not possible to generate referral
 information for it.
 
-% QUERY_WILDCARD_FAIL error processing wildcard for '%1'
+% DATASRC_QUERY_WILDCARD_FAIL error processing wildcard for '%1'
 During an attempt to cover the domain by a wildcard an error happened. The
 exact kind was hopefully already reported.
 
-% QUERY_MISSING_SOA the zone '%1' has no SOA
+% DATASRC_QUERY_MISSING_SOA the zone '%1' has no SOA
 The answer should have been a negative one (eg. of nonexistence of something).
 To do so, a SOA record should be put into the authority section, but the zone
 does not have one. This indicates problem with provided data.
 
-% QUERY_PROVENX_FAIL unable to prove nonexistence of '%1'
+% DATASRC_QUERY_PROVENX_FAIL unable to prove nonexistence of '%1'
 The user wants DNSSEC and we discovered the entity doesn't exist (either
 domain or the record). But there was an error getting NSEC/NSEC3 record
 to prove the nonexistence.
 
-% QUERY_UNKNOWN_RESULT unknown result of subtask
+% DATASRC_QUERY_UNKNOWN_RESULT unknown result of subtask
 This indicates a programmer error. The answer of subtask doesn't look like
 anything known.
 
-% META_ADD adding a data source into meta data source
+% DATASRC_META_ADD adding a data source into meta data source
 Debug information. Yet another data source is being added into the meta data
 source. (probably at startup or reconfiguration)
 
-% META_ADD_CLASS_MISMATCH mismatch between classes '%1' and '%2'
+% DATASRC_META_ADD_CLASS_MISMATCH mismatch between classes '%1' and '%2'
 It was attempted to add a data source into a meta data source. But their
 classes do not match.
 
-% META_REMOVE removing data source from meta data source
+% DATASRC_META_REMOVE removing data source from meta data source
 Debug information. A data source is being removed from meta data source.
 
-% MEM_ADD_WILDCARD adding wildcards for '%1'
+% DATASRC_MEM_ADD_WILDCARD adding wildcards for '%1'
 Debug information. Some special marks above each * in wildcard name are needed.
 They are being added now for this name.
 
-% MEM_CNAME_TO_NONEMPTY can't add CNAME to domain with other data in '%1'
+% DATASRC_MEM_CNAME_TO_NONEMPTY can't add CNAME to domain with other data in '%1'
 Someone or something tried to add a CNAME into a domain that already contains
 some other data. But the protocol forbids coexistence of CNAME with anything
 (RFC 1034, section 3.6.2). This indicates a problem with provided data.
 
-% MEM_CNAME_COEXIST can't add data to CNAME in domain '%1'
+% DATASRC_MEM_CNAME_COEXIST can't add data to CNAME in domain '%1'
 This is the same problem as in MEM_CNAME_TO_NONEMPTY, but it happened the
 other way around -- adding some other data to CNAME.
 
-% MEM_DNAME_NS DNAME and NS can't coexist in non-apex domain '%1'
+% DATASRC_MEM_DNAME_NS DNAME and NS can't coexist in non-apex domain '%1'
 It was requested for DNAME and NS records to be put into the same domain
 which is not the apex (the top of the zone). This is forbidden by RFC
 2672, section 3. This indicates a problem with provided data.
 
-% MEM_SINGLETON trying to add multiple RRs for domain '%1' and type '%2'
+% DATASRC_MEM_SINGLETON trying to add multiple RRs for domain '%1' and type '%2'
 Some resource types are singletons -- only one is allowed in a domain
 (for example CNAME or SOA). This indicates a problem with provided data.
 
-% MEM_OUT_OF_ZONE domain '%1' doesn't belong to zone '%2'
+% DATASRC_MEM_OUT_OF_ZONE domain '%1' doesn't belong to zone '%2'
 It was attempted to add the domain into a zone that shouldn't have it
 (eg. the domain is not subdomain of the zone origin). This indicates a
 problem with provided data.
 
-% MEM_WILDCARD_NS NS record in wildcard domain '%1'
+% DATASRC_MEM_WILDCARD_NS NS record in wildcard domain '%1'
 The software refuses to load NS records into a wildcard domain.  It isn't
 explicitly forbidden, but the protocol is ambiguous about how this should
 behave and BIND 9 refuses that as well. Please describe your intention using
 different tools.
 
-% MEM_WILDCARD_DNAME DNAME record in wildcard domain '%1'
+% DATASRC_MEM_WILDCARD_DNAME DNAME record in wildcard domain '%1'
 The software refuses to load DNAME records into a wildcard domain.  It isn't
 explicitly forbidden, but the protocol is ambiguous about how this should
 behave and BIND 9 refuses that as well. Please describe your intention using
 different tools.
 
-% MEM_ADD_RRSET adding RRset '%1/%2' into zone '%3'
+% DATASRC_MEM_ADD_RRSET adding RRset '%1/%2' into zone '%3'
 Debug information. An RRset is being added to the in-memory data source.
 
-% MEM_DUP_RRSET duplicate RRset '%1/%2'
+% DATASRC_MEM_DUP_RRSET duplicate RRset '%1/%2'
 An RRset is being inserted into in-memory data source for a second time.  The
 original version must be removed first. Note that loading master files where an
 RRset is split into multiple locations is not supported yet.
 
-% MEM_DNAME_ENCOUNTERED encountered a DNAME
+% DATASRC_MEM_DNAME_ENCOUNTERED encountered a DNAME
 Debug information. While searching for the requested domain, a DNAME was
 encountered on the way.  This may lead to redirection to a different domain and
 stop the search.
 
-% MEM_NS_ENCOUNTERED encountered a NS
+% DATASRC_MEM_NS_ENCOUNTERED encountered a NS
 Debug information. While searching for the requested domain, a NS was
 encountered on the way (a delegation). This may lead to stop of the search.
 
-% MEM_RENAME renaming RRset from '%1' to '%2'
+% DATASRC_MEM_RENAME renaming RRset from '%1' to '%2'
 Debug information. A RRset is being generated from a different RRset (most
 probably a wildcard). So it must be renamed to whatever the user asked for. In
 fact, it's impossible to rename RRsets with our libraries, so a new one is
 created and all resource records are copied over.
 
-% MEM_FIND find '%1/%2'
+% DATASRC_MEM_FIND find '%1/%2'
 Debug information. A search for the requested RRset is being started.
 
-% MEM_DNAME_FOUND DNAME found at '%1'
+% DATASRC_MEM_DNAME_FOUND DNAME found at '%1'
 Debug information. A DNAME was found instead of the requested information.
 
-% MEM_DELEG_FOUND delegation found at '%1'
+% DATASRC_MEM_DELEG_FOUND delegation found at '%1'
 Debug information. A delegation point was found above the requested record.
 
-% MEM_SUPER_STOP stopped at superdomain '%1', domain '%2' is empty
+% DATASRC_MEM_SUPER_STOP stopped at superdomain '%1', domain '%2' is empty
 Debug information. The search stopped at a superdomain of the requested
 domain. The domain is a empty nonterminal, therefore it is treated  as NXRRSET
 case (eg. the domain exists, but it doesn't have the requested record type).
 
-% MEM_WILDCARD_CANCEL wildcard match canceled for '%1'
+% DATASRC_MEM_WILDCARD_CANCEL wildcard match canceled for '%1'
 Debug information. A domain above wildcard was reached, but there's something
 below the requested domain. Therefore the wildcard doesn't apply here.  This
 behaviour is specified by RFC 1034, section 4.3.3
 
-% MEM_NOTFOUND requested domain '%1' not found
+% DATASRC_MEM_NOTFOUND requested domain '%1' not found
 Debug information. The requested domain does not exist.
 
-% MEM_DOMAIN_EMPTY requested domain '%1' is empty
+% DATASRC_MEM_DOMAIN_EMPTY requested domain '%1' is empty
 Debug information. The requested domain exists in the tree of domains, but
 it is empty. Therefore it doesn't contain the requested resource type.
 
-% MEM_EXACT_DELEGATION delegation at the exact domain '%1'
+% DATASRC_MEM_EXACT_DELEGATION delegation at the exact domain '%1'
 Debug information. There's a NS record at the requested domain. This means
 this zone is not authoritative for the requested domain, but a delegation
 should be followed. The requested domain is an apex of some zone.
 
-% MEM_ANY_SUCCESS ANY query for '%1' successful
+% DATASRC_MEM_ANY_SUCCESS ANY query for '%1' successful
 Debug information. The domain was found and an ANY type query is being answered
 by providing everything found inside the domain.
 
-% MEM_SUCCESS query for '%1/%2' successful
+% DATASRC_MEM_SUCCESS query for '%1/%2' successful
 Debug information. The requested record was found.
 
-% MEM_CNAME CNAME at the domain '%1'
+% DATASRC_MEM_CNAME CNAME at the domain '%1'
 Debug information. The requested domain is an alias to a different domain,
 returning the CNAME instead.
 
-% MEM_NXRRSET no such type '%1' at '%2'
+% DATASRC_MEM_NXRRSET no such type '%1' at '%2'
 Debug information. The domain exists, but it doesn't hold any record of the
 requested type.
 
-% MEM_CREATE creating zone '%1' in '%2' class
+% DATASRC_MEM_CREATE creating zone '%1' in '%2' class
 Debug information. A representation of a zone for the in-memory data source is
 being created.
 
-% MEM_DESTROY destroying zone '%1' in '%2' class
+% DATASRC_MEM_DESTROY destroying zone '%1' in '%2' class
 Debug information. A zone from in-memory data source is being destroyed.
 
-% MEM_LOAD loading zone '%1' from file '%2'
+% DATASRC_MEM_LOAD loading zone '%1' from file '%2'
 Debug information. The content of master file is being loaded into the memory.
 
-% MEM_SWAP swapping contents of two zone representations ('%1' and '%2')
+% DATASRC_MEM_SWAP swapping contents of two zone representations ('%1' and '%2')
 Debug information. The contents of two in-memory zones are being exchanged.
 This is usual practice to do some manipulation in exception-safe manner -- the
 new data are prepared in a different zone object and when it works, they are
 swapped. The old one contains the new data and the other one can be safely
 destroyed.
 
-% MEM_ADD_ZONE adding zone '%1/%2'
+% DATASRC_MEM_ADD_ZONE adding zone '%1/%2'
 Debug information. A zone is being added into the in-memory data source.
 
-% MEM_FIND_ZONE looking for zone '%1'
+% DATASRC_MEM_FIND_ZONE looking for zone '%1'
 Debug information. A zone object for this zone is being searched for in the
 in-memory data source.
 
-% STATIC_CREATE creating the static datasource
+% DATASRC_STATIC_CREATE creating the static datasource
 Debug information. The static data source (the one holding stuff like
 version.bind) is being created.
 
-% STATIC_BAD_CLASS static data source can handle CH only
+% DATASRC_STATIC_BAD_CLASS static data source can handle CH only
 For some reason, someone asked the static data source a query that is not in
 the CH class.
 
-% STATIC_FIND looking for '%1/%2'
+% DATASRC_STATIC_FIND looking for '%1/%2'
 Debug information. This resource record set is being looked up in the static
 data source.
 
-% SQLITE_FINDREC looking for record '%1/%2'
+% DATASRC_SQLITE_FINDREC looking for record '%1/%2'
 Debug information. The SQLite data source is looking up records of given name
 and type in the database.
 
-% SQLITE_ENCLOSURE looking for zone containing '%1'
+% DATASRC_SQLITE_ENCLOSURE looking for zone containing '%1'
 Debug information. The SQLite data source is trying to identify which zone
 should hold this domain.
 
-% SQLITE_ENCLOSURE_NOTFOUND no zone contains it
+% DATASRC_SQLITE_ENCLOSURE_NOTFOUND no zone contains it
 Debug information. The last SQLITE_ENCLOSURE query was unsuccessful; there's
 no such zone in our data.
 
-% SQLITE_PREVIOUS looking for name previous to '%1'
+% DATASRC_SQLITE_PREVIOUS looking for name previous to '%1'
 Debug information. We're trying to look up name preceding the supplied one.
 
-% SQLITE_PREVIOUS_NO_ZONE no zone containing '%1'
+% DATASRC_SQLITE_PREVIOUS_NO_ZONE no zone containing '%1'
 The SQLite data source tried to identify name preceding this one. But this
 one is not contained in any zone in the data source.
 
-% SQLITE_FIND_NSEC3 looking for NSEC3 in zone '%1' for hash '%2'
+% DATASRC_SQLITE_FIND_NSEC3 looking for NSEC3 in zone '%1' for hash '%2'
 Debug information. We're trying to look up a NSEC3 record in the SQLite data
 source.
 
-% SQLITE_FIND_NSEC3_NO_ZONE no such zone '%1'
+% DATASRC_SQLITE_FIND_NSEC3_NO_ZONE no such zone '%1'
 The SQLite data source was asked to provide a NSEC3 record for given zone.
 But it doesn't contain that zone.
 
-% SQLITE_FIND looking for RRset '%1/%2'
+% DATASRC_SQLITE_FIND looking for RRset '%1/%2'
 Debug information. The SQLite data source is looking up a resource record
 set.
 
-% SQLITE_FIND_BAD_CLASS class mismatch looking for an RRset ('%1' and '%2')
+% DATASRC_SQLITE_FIND_BAD_CLASS class mismatch looking for an RRset ('%1' and '%2')
 The SQLite data source was looking up an RRset, but the data source contains
 different class than the query was for.
 
-% SQLITE_FINDEXACT looking for exact RRset '%1/%2'
+% DATASRC_SQLITE_FINDEXACT looking for exact RRset '%1/%2'
 Debug information. The SQLite data source is looking up an exact resource
 record.
 
-% SQLITE_FINDEXACT_BAD_CLASS class mismatch looking for an RRset ('%1' and '%2')
+% DATASRC_SQLITE_FINDEXACT_BAD_CLASS class mismatch looking for an RRset ('%1' and '%2')
 The SQLite data source was looking up an exact RRset, but the data source
 contains different class than the query was for.
 
-% SQLITE_FINDADDRS looking for A/AAAA addresses for '%1'
+% DATASRC_SQLITE_FINDADDRS looking for A/AAAA addresses for '%1'
 Debug information. The data source is looking up the addresses for given
 domain name.
 
-% SQLITE_FINDADDRS_BAD_CLASS class mismatch looking for addresses ('%1' and '%2')
+% DATASRC_SQLITE_FINDADDRS_BAD_CLASS class mismatch looking for addresses ('%1' and '%2')
 The SQLite data source was looking up A/AAAA addresses, but the data source
 contains different class than the query was for.
 
-% SQLITE_FINDREF looking for referral at '%1'
+% DATASRC_SQLITE_FINDREF looking for referral at '%1'
 Debug information. The SQLite data source is identifying if this domain is
 a referral and where it goes.
 
-% SQLITE_FINDREF_BAD_CLASS class mismatch looking for referral ('%1' and '%2')
+% DATASRC_SQLITE_FINDREF_BAD_CLASS class mismatch looking for referral ('%1' and '%2')
 The SQLite data source was trying to identify if there's a referral. But
 it contains different class than the query was for.
 
-% SQLITE_CREATE SQLite data source created
+% DATASRC_SQLITE_CREATE SQLite data source created
 Debug information. An instance of SQLite data source is being created.
 
-% SQLITE_DESTROY SQLite data source destroyed
+% DATASRC_SQLITE_DESTROY SQLite data source destroyed
 Debug information. An instance of SQLite data source is being destroyed.
 
-% SQLITE_SETUP setting up SQLite database
+% DATASRC_SQLITE_SETUP setting up SQLite database
 The database for SQLite data source was found empty. It is assumed this is the
 first run and it is being initialized with current schema.  It'll still contain
 no data, but it will be ready for use.
 
-% SQLITE_OPEN opening SQLite database '%1'
+% DATASRC_SQLITE_OPEN opening SQLite database '%1'
 Debug information. The SQLite data source is loading an SQLite database in
 the provided file.
 
-% SQLITE_CLOSE closing SQLite database
+% DATASRC_SQLITE_CLOSE closing SQLite database
 Debug information. The SQLite data source is closing the database file.