123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420 |
- # Copyright (C) 2011 Internet Systems Consortium, Inc. ("ISC")
- #
- # Permission to use, copy, modify, and/or distribute this software for any
- # purpose with or without fee is hereby granted, provided that the above
- # copyright notice and this permission notice appear in all copies.
- #
- # THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
- # REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
- # AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
- # INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
- # LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
- # 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_CREAT Creating the hotspot cache
- + Debug information that the hotspot cache was created at startup.
- CACHE_DESTROY Destroying the hotspot cache
- + Debug information. The hotspot cache is being destroyed.
- CACHE_INSERT Inserting item '%s' 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
- + 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
- + 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 '%s' from the cache
- + Debug information. An item is being removed from the hotspot cache.
- CACHE_LOOKUP Looking up '%s' in the cache
- + Debug information. We are trying to look up an item in the hotspot cache.
- + Further progress and result will follow.
- CACHE_NOT_FOUND The item was not found
- + Debug information. The item we tried to look in the last CACHE_LOOKUP was
- + not found in the hotspot cache.
- CACHE_FOUND The item was found
- + Debug information. The last CACHE_LOOKUP was successful, eg. we have found
- + the requested item in the hotspot cache.
- CACHE_EXPIRED The item is expired
- + Debug information. The item requested in the last CACHE_LOOKUP was in the
- + hotspot cache, but it was old. We're going to remove it and report we don't
- + have it (the external result will be the same as with CACHE_NOT_FOUND).
- CACHE_SLOTS Setting the cache size to '%d'
- + The maximum allowed number of items of the hotspot cache is set to the given
- + number. If there are too many, we're going to drop them right now. The size
- + of 0 means no limit.
- CACHE_ENABLE Enabling the cache
- + The hotspot cache is enabled from now on.
- 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 '%s'
- + Debug info. While answering a query, we met a DNAME. We'll return the DNAME,
- + but we're creating a CNAME for clients that don't understand DNAMEs.
- QUERY_EMPTY_DNAME The DNAME on '%s' is empty
- + We tried to synthesize a CNAME from this DNAME, but it contains no records.
- + This indicates problem with supplied data.
- QUERY_GET_NS_ADDITIONAL Addition of A/AAAA for '%s' requested by NS '%s'
- + Debug information. While processing a query, we met a NS record. It
- + references the mentioned address, so we want to look up A/AAAA records for it
- + and put it into the additional section.
- QUERY_GET_MX_ADDITIONAL Addition of A/AAAA for '%s' requested by MX '%s'
- + Debug information. While processing a query, we met a MX record. It
- + references the mentioned address, so we want to look up A/AAAA records for it
- + and put it into the additional section.
- QUERY_FOLLOW_CNAME Following CNAME at '%s'
- + Debug information. The domain is a CNAME (or a DNAME and we created a CNAME
- + for it already), so we're following it.
- QUERY_EMPTY_CNAME CNAME at '%s' is empty
- + We tried to follow a CNAME, but contains no records. We have nothing to
- + follow, so we will have nothing in the answer. This indicates a problem with
- + supplied data.
- QUERY_TOO_MANY_CNAMES CNAME chain limit exceeded at '%s'
- + While answering a query, we followed a CNAME. Then another one. And after 16
- + CNAMEs we decided it's enough and we won't follow more. Long CNAME chains
- + are discouraged, and this might be a loop as well. Note that some of the
- + CNAMEs might have been synthesised from DNAMEs internally. This indicates
- + a problem with supplied data.
- QUERY_CHECK_CACHE Checking cache for '%s/%s'
- + Debug information. While processing a query we're looking into the hotspot
- + cache.
- QUERY_NO_CACHE_ANY_SIMPLE Ignoring cache for ANY query
- + Debug information. We don't really want to use cache for simple ANY query
- + (ANY as the type or class).
- QUERY_NO_CACHE_ANY_AUTH Ignoring cache for ANY query
- + Debug information. We don't really want to use cache for authoritative ANY
- + query (ANY as the type or class).
- DO_QUERY Handling query for '%s/%s'
- + Debug information. We're processing some internal query for given name and
- + type.
- QUERY_NO_ZONE No zone containing '%s' in class '%s'
- + We tried to get the domain but there's no zone in our data that encloses
- + the name. Maybe someone sent a query to wrong server for some reason.
- QUERY_CACHED Data found in cache
- + Debug information. We found the requested data in cache, so we're not
- + querying the real data source.
- QUERY_IS_SIMPLE Simple query
- + Debug information. The last DO_QUERY is a simple query.
- QUERY_IS_AUTH Auth query
- + Debug information. The last DO_QUERY is an auth query.
- QUERY_IS_GLUE Glue query
- + Debug information. The last DO_QUERY is query for glue addresses.
- QUERY_IS_NOGLUE Query for non-glue addresses
- + Debug information. The last DO_QUERY is query for addresses that are not
- + glue.
- QUERY_IS_REF Query for referral
- + Debug information. The last DO_QUERY is query for referral information.
- QUERY_SIMPLE_FAIL The underlying data source failed with %u
- + We queried the data source to answer a simple query and it returned error
- + (1 is some error, 2 is not implemented). The data source should have log
- + the specific error already.
- QUERY_AUTH_FAIL The underlying data source failed with %u
- + We queried the data source to answer authoritative query and it returned
- + error (1 is some error, 2 is not implemented). The data source should have
- + log the specific error already.
- QUERY_GLUE_FAIL The underlying data source failed with %u
- + We queried the data source to answer query for glue addresses and it returned
- + error (1 is some error, 2 is not implemented). The data source should have
- + log the specific error already.
- QUERY_NOGLUE_FAIL The underlying data source failed with %u
- + We queried the data source to answer query for non-glue addresses and it
- + returned error (1 is some error, 2 is not implemented). The data source
- + should have log the specific error already.
- QUERY_REF_FAIL The underlying data source failed with %u
- + We queried the data source to answer query for referral and it
- + returned error (1 is some error, 2 is not implemented). The data source
- + should have log the specific error already.
- 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 '%s/%s' to message
- + Debug information. We're adding the rrset to answer message.
- QUERY_COPY_AUTH Copying authoritative section into message
- + Debug information. We're copying referral information into authoritative
- + section of the response message.
- QUERY_DELEGATION Looking for delegation on the path to '%s'
- + Debug information. We're looking if there's a delegation point on the way
- + down to the given domain.
- QUERY_ADD_SOA Adding SOA of '%s'
- + Debug information. We're adding a SOA record for the given zone into the
- + authority section.
- QUERY_ADD_NSEC Adding NSEC record for '%s'
- + Debug information. We're adding NSEC record for this domain.
- QUERY_ADD_NSEC3 Adding NSEC3 record of zone '%s'
- + Debug information. We're adding an NSEC3 record for this zone.
- QUERY_NO_DS_NSEC3 There's no DS record in the '%s' zone
- + We tried to insert a NSEC3 record into the message. But we didn't find a DS
- + record for this zone.
- QUERY_NO_DS_NSEC There's no DS record in the '%s' zone
- + We tried to insert a NSEC record into the message. But we didn't find a DS
- + record for this zone.
- QUERY_WILDCARD Looking for a wildcard covering '%s'
- + Debug information. We didn't find a direct match, so we're trying to find if
- + there's a wildcard we could use to answer the query.
- QUERY_WILDCARD_PROVENX_FAIL Unable to prove nonexistence of '%s' (%u)
- + While processing a wildcard, we tried 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 '%s' (%u)
- + While processing a wildcard we met a referral. But we were not able to get
- + information for it. The code is 1 for error, 2 for not implemented.
- QUERY_PROCESS Processing query '%s/%s' in the '%s' class
- + Debug information. We're starting to process a user query.
- 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
- + This indicates a programming error. We found a task in the internal task
- + queue which wasn't supposed to ever be put into the queue, but handled
- + directly.
- QUERY_TASK_FAIL Task failed with %u
- + 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 '%s'
- + We wanted to put the nameserver records into the authority section, but we
- + discovered the zone doesn't have them. This indicates problem with provided
- + data.
- UNEXPECTED_QUERY_STATE Unexpected query state
- + This indicates a programming error. We generated an internal task of type
- + unknown to us.
- 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 '%s'
- + We discovered that the domain lives in another zone. But we are not able to
- + generate referral information to it.
- QUERY_WILDCARD_FAIL Error processing wildcard for '%s'
- + We tried to find a wildcard to cover the domain, but there happened to be
- + some (hopefully already reported) error for it.
- QUERY_MISSING_SOA The zone '%s' has no SOA
- + We tried to answer negatively, but there's no SOA record in the zone.
- QUERY_PROVENX_FAIL Unable to prove nonexistence of '%s'
- + 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
- + This indicates a programmer error. The answer of subtask doesn't look like
- + anything we would know.
- META_ADD Adding a data source into meta data source
- + Debug information. We add yet another data source into the meta data source
- + (probably at startup or reconfiguration).
- META_ADD_CLASS_MISMATCH Mismatch between classes '%s' and '%s'
- + We tried to add a data source of one class into a meta data source of a
- + different type. The types must be the same.
- META_REMOVE Removing data source from meta data source
- + Debug information. We take a data source out of meta data source (probably
- + at shutdown or reconfiguration).
- MEM_ADD_WILDCARD Adding wildcards for '%s'
- + Debug information. We need some special marks above each * in wildcard name
- + in the in-memory data source. We are adding the marks for this name now.
- MEM_CNAME_TO_NONEMPTY Can't add CNAME to domain with other data in '%s'
- + 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 '%s'
- + This is the same problem as in MEM_CNAME_TO_NONEMPTY, but it happened the
- + other way around -- adding some outher data to CNAME.
- MEM_DNAME_NS DNAME and NS can't coexist in non-apex domain '%s'
- + 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 '%s' and type '%s'
- + 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 '%s' doesn't belong to zone '%s'
- + 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 '%s'
- + We refuse to load NS record into a wildcard domain. It is'n explicitly
- + forbidden, but the protocol is ambiguous about how this should behave and
- + bind 9 refuses that as well. We don't like your zone, please describe it
- + using different tools.
- MEM_WILDCARD_DNAME DNAME record in wildcard domain '%s'
- + We refuse to load DNAME record into a wildcard domain. It is'n explicitly
- + forbidden, but the protocol is ambiguous about how this should behave and
- + bind 9 refuses that as well. We don't like your zone, please describe it
- + using different tools.
- MEM_ADD_RRSET Adding RRset '%s/%s' into zone '%s'
- + Debug information. We're adding an RRset to the zone of in-memory data
- + source.
- MEM_DUP_RRSET Duplicate rrset '%s/%s'
- + An RRset is being inserted into in-memory data source for a second time.
- + The original version must be removed first. Note that we don't support
- + loading master files where an RRset is split into multiple locations yet.
- MEM_DNAME_ENCOUNTERED Encountered a DNAME
- + Debug information. While searching for the requested domain, we encountered
- + a DNAME on the way. This may lead to redirection to a different domain and
- + stop the search.
- MEM_NS_ENCOUNTERED Encountered a NS
- + Debug information. While searching for the requested domain, we encountered
- + a NS on the way (a delegation). This may lead to stop of the search.
- MEM_RENAME Renaming rrset from '%s' to '%s'
- + Debug information. We generate an RRset from a different RRset (most probably
- + a wildcard). So we need to rename it to whatever the user asked for. In fact,
- + we can't rename RRset (it's not possible with our libraries), so we create
- + a new one and copy everything.
- MEM_FIND Find '%s/%s'
- + Debug information. We're going to search the in-memory data source to find
- + requestet RRset.
- MEM_DNAME_FOUND DNAME found at '%s'
- + Debug information. We found a DNAME instead of the requested record.
- MEM_DELEG_FOUND Delegation found at '%s'
- + Debug information. We found a delegation point above the requested record.
- MEM_SUPER_STOP Stopped at superdomain, domain is empty
- + Debug information. The search stopped at a superdomain of the requested
- + domain. The domain is a empty nonterminal, therefore we treat it as NXRRSET
- + case (eg. the domain exists, but it doesn't have the requested record type).
- MEM_WILDCARD_CANCEL Wildcard match canceled
- + Debug information. We reached a domain above wildcard, 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 not found
- + Debug information. The requested domain does not exist.
- MEM_DOMAIN_EMPTY Requested domain 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
- + 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 successful
- + Debug information. The domain was found and we answer an ANY type query by
- + providing everything we found inside the domain.
- MEM_SUCCESS Query successful
- + Debug information. We found the record we searched for.
- MEM_CNAME CNAME at the domain
- + Debug information. The requested domain is an alias to a different domain,
- + returning the CNAME instead.
- MEM_NXRRSET No such type
- + Debug information. The domain exists, but it doesn't hold any record of the
- + requested type.
- MEM_CREATE Creating zone '%s' in '%s' class
- + Debug information. We're creating representation of a zone for the in-memory
- + data source.
- MEM_DESTROY Destroying zone '%s' in '%s' class
- + Debug information. We're destroying the representation of zone in the
- + in-memory data source.
- MEM_LOAD Loading zone '%s' from file '%s'
- + Debug information. We're loading the content of zone from a master file.
- MEM_SWAP Swapping contents of two zone representations ('%s' and '%s')
- + Debug information. We exchange contents of the zones. This is usual practice
- + to do some manipulation in exception-safe manner -- we prepare the new data
- + in a different zone object and when it works, we swap it with the old, then
- + we can safely destroy the old one.
- MEM_ADD_ZONE Adding zone '%s/%s'
- + Debug information. We're adding this zone into the in-memory data source.
- MEM_FIND_ZONE Looking for zone '%s'
- + Debug information. We're looking for a zone in the in-memory data source.
- STATIC_CREATE Creating the static datasource
- + Debug information. We're creating the static data source (the one holding
- + stuff like version.bind).
- 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 '%s/%s'
- + Debug information. We're looking for this resource record set in the static
- + data source.
|