DNS Log Message Reference

Level Log message Message description

ERROR [DNS name]/NS '[DNS name]' (out of Canonical name record is out of zone while checking the name
zone) is a CNAME '[DNS name]' (illegal) server record.

ERROR [DNS name]/NS '[DNS name]' (out of Address record or IPv6 address record is out of zone while checking
zone) has no addresses records (A or the name server record.
AAAA)

INFO getaddrinfo([DNS name]) failed: [error Cannot to get an IP address of a domain name when checking the
message] name server record.
ERROR [DNS name]/NS '[DNS name]'extra GLUE There is an extra GLUE A record when checking the name server
A record ([IP address]) record.

ERROR [DNS name]/NS '[DNS name]' extra GLUE There is an extra GLUE AAAA record when checking the name server
AAAA record ([IP address]) record.

ERROR [DNS name]/NS '[DNS name]' missing Glue records are required when you wish to set the name servers of
GLUE [type] record ([IP address]) a domain name to a hostname under the domain name itself. It is
the IP address of a name server held at the domain name registry.
Without the glue records, DNS requests never resolve to the correct
IP address because the domain registry does not associate the IP
with the correct records.
N/A [DNS name]/MX '[DNS name]' (out of Canonical name record is out of zone when checking the mail
zone) is a CNAME '[DNS name]' (illegal) exchange (MX) record.

ERROR [DNS name]/MX '[DNS name]' (out of named-checkzone cannot resolve address record (A) or IPv6 address
zone) has no addresses records (A or record (AAAA – “Quad A”) for a mail exchanger record. The zone has
AAAA) no these address records thus “out of zone” message.

INFO getaddrinfo([DNS name]) failed: [error Getting an IP address of a domain name when checking the mail
message] exchanger record (MX record) failed.
N/A [DNS name]/SRV '[DNS name]'(out of When checking the Service locator a canonical name record (CNAME
zone) is a CNAME [DNS name] (illegal) record) is found to be out of zone.

ERROR [DNS name]/SRV '[DNS name]' (out of When checking the Service locator an address record or IPv6 address
zone) has no addresses records (A or record is found to be out of zone.
AAAA)

INFO getaddrinfo(DNS name) failed:[error Getting an IP address of a domain name when checking the Service
message] record (SRV record) failed.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 1 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR change directory to '[directory]' failed: Cannot change directory that includes directives in the named
[error message] configuration file.
ERROR setting timeout: [error message] Setting the specified timeout for a request on a TCP connection
failed.

WARNING error sending response: [warning Sending response on TCP connection failed.
message]

ERROR Unable to determine view to log Cannot determine a view to log a response.
response.

INFO [info message] The content of a Message that is sent to a client.

INFO Allow access since the client is from Access is allowed to clients that belong to a match list of IP
special source address [IP address] that address(es) which are allowed to issue queries to the server and in
matches view [view name] conjunction with a view clause.

ERROR UDP client handler shutting down due to UDP client handler is shutting down due to a fatal receive error.
fatal receive error: [error message]

ERROR Error creating GSS-TSIG signer name: The GSS-TSIG signer name cannot be created.
[error message]

ERROR request has invalid signature: TSIG [DNS NS client reverse request sent through TCP or UDP connection has
name] ([DNS name]): [error message] an invalid transaction signature(TSIG). TSIG has a creator.
([TSIG code])

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 2 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR request has invalid signature: TSIG [DNS The reverse request that NS client sends to the name server through
name]: [error message] ([TSIG code]) TCP or UDP connection has an invalid Transaction SIGnature. The
Secret Key Transaction Authentication for DNS (TSIG) protocol
provides transaction level authentication for DNS. For more
information, see RFC 3645, Generic Security Service Algorithm for
Secret Key Transaction Authentication for DNS (GSS-TSIG).
ERROR request has invalid signature: [error The reverse request that NS client sends to the name server through
message] ([TSIG code]) TCP or UDP connection has an invalid signature.

WARNING no more TCP clients: [warning message] This message appears when the quota for simultaneous lookup
requests that server will perform on behalf of its clients is exceeded.

ERROR Error creating GSS-TSIG signer name: GSS-TSIG signer name cannot be created because of the signature
[error message] length mismatch. This message appears during NS access control list
check.

ERROR Error converting DHCP key to string: An internal error. DHCP key cannot be converted to a string because
[error message] it may contain an unknown character. This message appears during
NS access control list check.
ERROR Error converting signer to string: [error An internal error. NS client signer cannot be converted to a string
message] because it may contain an unknown character. This message
appears during NS access control list check.
N/A [opname] denied An access control list validity check failure.

N/A client [client name] [client signer] [dns Client information: client name, signer, DNS name, view name for a
name] [view name for client]: [message] client.

ERROR unknown class [class] An unknown class of DNS record found while getting a configured
class.
ERROR unknown type [type] An unknown type of DNS record found while configuring named. An
"RR of unknown type" is an RR whose RDATA format is not known to
the DNS implementation at hand. For more information, see
RFC2929, section 3.1.
ERROR port [port] out of range Invalid port found while getting the list of IP addresses.
ERROR port [port] out of range Invalid port found while getting the list of IP addresses and keys.
ERROR masters [masters list] not found Key masters are not found while getting the list of IP addresses and
keys.
ERROR port [port] out of range Invalid port found while getting a configured port.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 3 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

N/A received control channel command The description of the command received by the Remote Name
[command] Daemon Control utility (rndc).

WARNING unknown control channel command The Remote Name Daemon Control utility (rndc) received a
[command] command that is not present in the configuration file (rndc.conf).

N/A stopping command channel on [socket] Named stops listening on a TCP socket when it shuts down.

WARNING error sending command response to Sending command response from a command channel to rndc
[socket]: [error] socket failed. The reason of failure is specified.

ERROR invalid command from [socket]:[error] Command channel received an invalid command from rndc. The
reason of failure is specified.

WARNING rejected command channel message Name server control tries to declare a command channel to be used
from [socket] by rndc. The message is rejected because its TCP address is not in a
listener ACL.

WARNING dropped command channel from Name server control tried to declare a command channel to be used
[socket]: [warning] by rndc and failed because listener cannot connect to a rndc socket.

WARNING Couldn't find key [key] for use with Cannot find key in configured key list for a socket listener while
command channel [socket] registering keys.

WARNING unsupported algorithm [algorithm] in When named configures name server controls, it finds the key for a
key [key] for use with command channel command channel but algorithm for this key is unsupported by a
[socket] name server.

WARNING secret for key [key] on command When named configures name server controls it finds the key for a
channel [socket]: [warning] command channel but cannot decode it.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 4 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

WARNING сouldn't register key [key]': out of When named configures name server controls it finds a key for a
memory command channel but this key cannot be registered due to a lack of
available memory.
WARNING unsupported algorithm [algorithm] in When named configures name server controls it finds the key for a
key [key] for use with command channel command channel but algorithm for this key is unsupported for use
on this command channel.

WARNING secret for key [key] on command When named configures name server controls it finds the key for a
channel: [socket] command channel but cannot decode it on this socket.

WARNING couldn't register key [key]: out of When named configures name server controls it finds a key for a
memory command channel but this key cannot be registered due to a lack of
available memory.
WARNING couldn't install new keys for command Named cannot install a new key for command channel (ns control)
channel [socket]: [warning] when it tries to configure name server controls.

WARNING couldn't install new keys for command Named cannot install a new key for command channel(rdns) when it
channel [socket]: [warning] tries to configure name server controls.

WARNING couldn't install new acl for command Named cannot install a new ACL for command channel(ns control)
channel [socket]: [warning] when it tries to configure name server controls.

WARNING couldn't install new acl for command Named cannot install a new ACL for command channel(rdns) when it
channel [socket]: [warning] tries to configure name server controls.

WARNING couldn't update ownership/permission named cannot update ownership/permission for a command
for command channel [socket] channel when it tries No configure name server controls.

WARNING couldn't install keys for command Named cannot install keys for a command channel when it tries to
channel [socket]: [warning] configure name server controls.

N/A command channel listening on [socket] Named successfully adds a command channel while configuring
name server controls.

WARNING couldn't add command channel [socket]: Named tries to configure name server controls but cannot add the
[warning] command channel.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 5 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

N/A couldn't add command channel [socket]: Named tries to configure name server controls but cannot add the
[warning] command channel.

ERROR ns_interface_create() failed: unknown UDP shadow sockets for IPv4/IPv6 cannot be created because the
number of worker threads on [interface] number of worker threads is unknown.

ERROR ns_interface_create() failed: error Named created an interface manager. Although the number of
creating shadow UDP socket on worker threads are known, an attempt to create UDP shadow
[interface]: [error] sockets for IPv4/IPv6 failed due to the failure of the
infoblox_socket_create_shadowudp() function to create UDP
shadow socket.
ERROR ns_interface_create() failed: error Named created an interface manager. Although the number of
binding shadow UDP socket on worker threads are known, an attempt to create UDP shadow
[interface]: [error] sockets for IPv4/IPv6 failed due to the failure to bind the local
address to the raw socket created.
ERROR ns_clientmgr_create() failed:[error] Named cannot create an interface manager due to the specified
reason of failure.

ERROR could not listen on UDP socket: [error] An interface manager cannot listen on one of UDP sockets due to
the specified reason of failure.

ERROR creating TCP socket: [error] Named created an interface manager. The interface manager
accepts TCP socket but TCP socket cannot be created for the
interface manager due to the specified reason of failure.
ERROR binding TCP socket: [error] Named created an interface manager. The interface manager
accepts a TCP socket but TCP socket cannot be assigned to an
address due to the specified error.
ERROR listening on TCP socket: [error] Named created an interface manager. The interface manager
accepts a TCP socket but listening on TCP socket is not possible due
to the specified error.
INFO no longer listening on [socket] This message may appear in the following situations:
- when interface manager shuts down, it detaches from all
interfaces;
- named goes through the interface list and deletes everything that
does not have the current generation number while scanning the
operating system list of network interfaces.
WARNING omitting IPv4 interface [interface] from When named scans the operating system list of network interfaces,
localnets ACL: [warning] it omits IPv4 interface from localnets ACL due to the specified
reason.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 6 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

INFO listening on IPv6 interfaces, port [port] Socket listener is open to listen for IPv6 queries.

ERROR listening on all IPv6 interfaces failed While named scans the operating systems list of network interfaces,
an interface manager cannot find IPv6 interface for IP address.

INFO [[additionally]or[]] listening on Named is listening on IPv4 or IPv6 interface.

[[IPv4]or[IPv6]] interface [interface
name], [socket]

ERROR creating [[IPv4]or[IPv6]] interface Named cannot create IPv4 or IPv6 interface when scanning the
[interface name] failed; interface ignored operating system list of network interfaces due to the error in the
ns_interface_setup() function.

ERROR ignoring [[IPv4]or[IPv6]] interface Named ignores IPv4 or IPv6 interfaces while scanning the operating
[interface name]: [error message] system list of network interfaces because localnets are not set.

WARNING not listening on any interfaces Named does not listen on any interface in lwresd-only mode when
updating the listening interfaces.
ERROR unknown logging category '[category A message contains an unknown logging category and is ignored.
name]' ignored

ERROR logging channel '[chanel name]': [error Named cannot assign a logging category and a logging channel when
message] it sets up a logging channel according to the named.conf data.

ERROR channel '[chanel name]': exactly one of Exactly one of the predefined channel name values such as file,
file, syslog, null, and stderr must be syslog, null, or stderr must be present for the logging channel.
present

N/A created client [client], manager Initializing lwd client for a lightweight daemon client manager
[manager] object.
N/A destroying client [client], manager Deleting lwd client for a lightweight daemon client manager object.
[manager]
N/A destroying manager [manager] Destroying lightweight daemon client manager object.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 7 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

N/A invalid packet header received An error is found in a request header when parsing a client request.
N/A opcode [operation code] This log message displays the operational code for a client's packet.
N/A unknown opcode [operation code] An unknown operational code of a client’s packet.
N/A restarting client [client]... Restarting lwd client.
N/A event received: task [task], length The message received from an lwd client.
[length], result [result] ([message])

ERROR could not start lwres client handler: A lightweight resolver cannot be started.
[error message]

N/A got shutdown event, task [task], Shutdown event carried out when closing an object.
lwdclientmgr [manager]
N/A destroying client [client], manager Deleting lwd client for a lightweight daemon client manager object.
[manager]
ERROR could not start lwres client handler: A lightweight resolver cannot be started.
[error message]

N/A task [task] for client [client] got send- Executing lwd client task.
done event
N/A cleaning up client [client] Cleaning up lwd client.
N/A adding address [address], family [family], Addresses are added to an lwres list.
length [length]

N/A generating gabn reply for client [client] Generating gabn reply for lwd client.
N/A find done for task [task], client [client] Search for lwd client task is completed.
N/A starting find for client [client] Search for lwd client task is started.
N/A found alias, restarting query Alias found, query is restarted.
N/A out of buffer space adding alias Alias cannot be rendered due to insufficient buffer size.

N/A find returned [result] ([message]) An lwd client task search result.
N/A client [client] ipv4 satisfied by find [client IPv4 client satisfied by a search result.
find]
N/A client [client] ipv6 satisfied by find [client IPv6 client satisfied by a search result.
find]
N/A event will be sent An event will be sent.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 8 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

N/A no event will be sent No event will be sent.
N/A client [client] looking for addrtypes Lwd client is looking for address types.
[client find]
N/A byaddr event result = [message] DNS name search for a lwd client is completed.
N/A found name [DNS name] DNS name is found.

N/A client [client] looking for addrtype An lwd client is looking for an address type.
[family]
N/A lookup event result = [message] DNS names search for a lwd client is completed.
N/A found name [DNS name] DNS name is found.

N/A filled in [number] rdata[[s]or[]] The number of records received from a DNS recordset.

N/A filled in [number] signature[[s]or[]] The number of signature records received from a DNS recordset.

ERROR error constructing getrrsetbyname An lwd client cannot send a replay.

response
N/A client [client] looking for type [record An lwd client is looking for an address type.
type]
ERROR processing sortlist: [netmask] is not a The specified netmask found during the sortlist processing is invalid.
valid netmask

WARNING couldn't find view [view name] DNS view list cannot be found.

WARNING couldn't create searchlist The lightweight resolver daemon manager cannot create a
searchlist.

WARNING invalid name [DNS name] in searchlist The lwresd manager finds an invalid name in a searchlist.

WARNING couldn't update searchlist The lightweight resolver daemon manager (lwresd) cannot update a
searchlist.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 9 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

WARNING failed to create lwres socket: [warning The lightweight resolver daemon manager (lwresd) cannot create a
message] socket listener.

WARNING failed to add lwres socket: [socket]: The lightweight resolver daemon manager (lwresd) cannot add a
[warning message] socket listener.

ERROR could not start lwres client handler: The lightweight resolver daemon manager (lwresd) cannot start
[error message] lwres client when it configures a listener.

WARNING lwres failed to configure [socket]: The lightweight resolver daemon manager (lwresd) cannot create a
[warning message] listener.

WARNING lwres: failed to start [socket]: [warning The lightweight resolver daemon manager (lwresd) cannot start
message] lwres clients.

N/A lwres listening on [socket] The lightweight resolver server is listening on a socket.

N/A lwres no longer listening on [socket] The lightweight resolver server stops listening on a socket.

ERROR exiting (due to early fatal error) Named is exiting due to early fatal error.

CRITICAL [file]:[line]: [error]([condition]) failed[[, Assertion failure. The particular file, line number and condition that
back trace]or[]] caused it are indicated.

CRITICAL [number of trace][trace] in [file] Cannot process the file. The backtrace symbol is available to
()+[offcet] investigate the error.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 10 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

CRITICAL [number of trace][trace] in ?? Cannot process the file. The backtrace symbol is not available to
investigate the error.

CRITICAL exiting (due to assertion failure) Named is exiting due to an assertion failure.

ERROR [file]:[line]: fatal error: Fatal error in a library. The source file and the line number are
indicated.

ERROR exiting (due to fatal error in library) Named is exiting due to a fatal error in a library.

ERROR [file]:[line]: unexpected error: Unexpected error in library. The source file and line number are
indicated.

INFO found [number] CPU[[s]or[]], using Number of CPUs and worker threads found.
[number] worker thread[[s]or[]]

INFO using [UDP] UDP listener[[s]or[]] per The number of currently utilized UDP listeners per interface.
interface

INFO using up to [socket] sockets The maximum number of sockets that can be used.

N/A starting BIND [version][command line] The start of named loading procedure with the version number
indicated.

N/A built with [configuration arguments] Starting BIND. Build version and configuration arguments location is
displayed.

N/A ---------------------------------------------------- divider

N/A BIND 9 is maintained by Internet BIND copyright info line1

Systems Consortium,

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 11 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

N/A Inc. (ISC), a non-profit 501(c)(3) public- BIND copyright info line 2
benefit

N/A corporation. Support and training for BIND copyright info line 3
BIND 9 are

N/A available at https://www.isc.org/support BIND copyright info line 4

N/A ---------------------------------------------------- divider

N/A adjusted limit on open files from %" The limit of simultaneously opened files is adjusted (increased) for
[number] to [number] safety reason.

N/A exiting Named is exiting.

N/A notify question section empty The notify question section is empty, nothing to process.
N/A notify question section contains multiple The question section of DNS query contains multiple Resource
RRs Records (RRs). There should be only one record.
N/A notify question section contains multiple The question section of DNS query contains multiple Resource
RRs Records (RRs). There shall be only one record.
N/A notify question section contains no SOA The notify question section does not contain Authority Resource
Record (SOA) for a zone. There shall be one SOA record.
INFO received notify for zone [DNS NOTIFY for a zone is received.
name][TSIG]
N/A received notify for zone [DNS NS client cannot examine the incoming DNS message to determine
name][TSIG]: not authoritative an appropriate zone. Possible causes:
- Zone name from Question section of DNS message is not found in
zone table;
- Zone type from Question section of DNS message is not a master,
slave or stub.
INFO [message] denied NS client cannot check zone ACL.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 12 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

INFO [disabled]srpz [type] [policy] rewrite Due to the specified policy, DNS address is rewritten to a new
[DNS name] via [DNS name] address.

INFO CEF:0|Infoblox|NIOS|[version]|RPZ- RPZ (Request Policy Zone) message in CEF format.

[type]|[policy]|4|app=DNS
dst=[destination] src=[source]
spt=[source port] view=[view name]
qtype=[type] msg=[message]

INFO [message] RPZ (Request Policy Zone) message.

INFO Suppressed [number] messages for view Suppressed messages for a client view regarding RPZ zones that are
[client view] regarding RPZ zones that not loaded.
have not been loaded

ERROR rpz [rpz type] rewrite [DNS name] via RPZ with the specified type cannot rewrite a DNS client query with
[DNS name] [rpz type] failed: [error an RPZ query.
message]

INFO [message] denied NS client cannot check cache ACL.

WARNING recursive-clients soft limit exceeded When the soft limit of recursive clients is exceeded, the oldest query
([used]/[soft]/[max]), aborting oldest is always dropped.
query

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 13 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

WARNING no more recursive clients The quota for recursive clients is exceeded.
([used]/[soft]/[max]): [warning message]

WARNING ns_client_replace() failed: [warning Recursive client may be "mortal" or it is not a TCP client.
message]

WARNING RFC 1918 response from Internet for If the IN-ADDR.ARPA name covered refers to an internal address
[DNS name] space you are using, then you have failed to follow RFC 1918 usage
rules and are leaking queries to the Internet. You should establish
your own zones for these addresses to prevent querying the
Internet's name servers for these addresses.
WARNING expected a exact match NSEC3, got a Query result. Expecting a matching NSEC3, but received a covering
covering record record.

WARNING expected covering NSEC3, got an exact Expecting a matching NSEC3, but received a covering record. The
match final NSEC3 record does not contain any data or wildcard.

ERROR Error adding blacklist match result for Cannot add a blacklist match result for a NS client query to a cache
[DNS name] to cache for view [view]: for a view.
[error message]

INFO Intercept (blacklist rule): [DNS name] Query is intercepted according to the blacklist rule: query name
matched ruleset-pattern (redirect): [rs matched ruleset pattern and was redirected.
name] -- [pattern] ([net address])

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 14 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

INFO Intercept (blacklist rule): [DNS name] Query is intercepted according to the blacklist rule: query name
matched ruleset-pattern (refusal): [rs matched ruleset pattern and was refused.
name] – [pattern] ([net address])

INFO Intercept (blacklist rule): [DNS name] Query is intercepted according to the blacklist rule: query name
matched ruleset-pattern (pass): [rs matched ruleset pattern and was passed.
name] – [pattern] ([net address])

ERROR Error adding NXDOMAIN match result Cannot add NXDOMAIN match result for a query name to a cache
for [DNS name] to cache for view [view]: for a view.
[error message]

INFO Intercept (NXDOMAIN rule): [DNS name] Query is intercepted according to the NXDOMAIN rule: query name
matched ruleset-pattern (redirect): [rs matched ruleset pattern and was redirected.
name] – [pattern] ([net address])

INFO Intercept (blacklist rule): [rs name] – Query is intercepted according to the NXDOMAIN rule: query name
[pattern] ([net address]) matched ruleset pattern and was passed.

INFO Intercept (NXDOMAIN rule): [DNS name] Query is intercepted according to the NXDOMAIN rule: query name
matched ruleset-pattern (modify): [rs matched ruleset pattern and was modified.
name] – [pattern] ([net address])

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 15 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR Error adding whitelist entry for [DNS Cannot add whitelist entry for a NS client query to cache for a view.
name] to cache for view [view]: [error
message]

INFO rewriting query name [DNS name] to Rewriting query name to the Infoblox query name.
[DNS name], type [type]

ERROR [function]: unexpected result code from Dns_rbt_findnode() function has been updated in a backward
dns_rbt_findnode([DNS name]): [error incompatible way, or there may be a serious internal bug.
message]

INFO Query rewrite skipped for non-IPv4 Query rewrite is skipped for a non-IPv4 client.
client

ERROR Unable to obtain buffer for query name Cannot obtain a buffer for a query name rewrite.
rewrite

ERROR Unable to get temporary name for query Cannot get a temporary name for a query name rewrite.
name rewrite

ERROR Error constructing prepended label for Cannot construct a prepended label for a query rewrite.
query rewrite: [error message]

INFO Error concatenating name for query Cannot concatenate a name for a query rewrite.
rewrite: [error message]

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 16 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR Unable to obtain buffer for original Cannot obtain a buffer for original query name before a rewrite.
query name before rewrite"

ERROR Unable to get temporary name for query Cannot get temporary name for a query name rewrite.
name rewrite

ERROR check-names failure [DNS Host name does not comply with RFC 952 and RFC 1123 or name's
name]/[type]/[class] owner cannot be verified.

ERROR zone not loaded and not found in zone Zone is not loaded and not found in a zone table.
table: [error message]

ERROR No NS records; zone may have been No NS records found. The zone may have been deleted, but this
deleted could also be due to some more serious problems.
INFO Redirected NXDOMAIN query: [DNS NXDOMAIN query is redirected.
name] ([net address])

INFO DNAME and query rewrite cannot DNAME and query rewrite cannot coexist.
coexist

WARNING missing signature for [DNS name] NS client query signature is missing.

ERROR Error adding RPZ white list entry for Cannot add a RPZ whitelist entry for a NS client query to a cache for
[DNS name] to cache for view [view]: a view.
[error message]

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 17 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR Error matching the requested domain Cannot match the requested domain name against the query log
name [DNS name] against the query log table.
table: [error message]

N/A query: [DNS name][class][type] [[+]or[-]] The detailed information that describes an NS client query.
[[S]or[]] [[E]or[]] [[T]or[]][[D]or[]][[C]or[]]
([net address])

ERROR query failed ([error NS client query failed.

message])[separator][DNS
name][separator][class][separator][type]
at [File]:[Line]

ERROR failed to add [object] for [configuration Cannot add DNS fixed name to a red-black-tree database.
name]: [error message]

ERROR managed key [key]: invalid initialization Invalid initialization method is used for a managed key.
method [initialization method]

WARNING [[managed]or[trusted]] key [key name] Managed or trusted key has a weak exponent.
has a weak exponent

ERROR ignoring [[managed]or[trusted]] key for Ignoring managed or trusted key, no crypto support.
[key name]: no crypto support

WARNING skipping [[managed]or[trusted]] key for Skipping managed or trusted key.

[key name]: [warning message]

ERROR configuring [[managed]or[trusted]] key Configuring managed or trusted key.

for [key name]: [error message]

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 18 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR negative trust anchor [object] was Negative trust anchor was rejected due to a conflict with the other
rejected due to conflict with other positive/negative anchor.
positive/negative anchor

ERROR couldn't create keytable Keytable cannot be created.

WARNING using built-in DLV key for view [view] Using built-in DLV key for a view.

WARNING using built-in root key for view [view] Using built-in root key for a view.

INFO using specific query-source port Using specific query-source port that suppresses port randomization
suppresses port randomization and can and can be insecure.
be insecure.

ERROR could not get query source dispatcher Named cannot get a dispatcher appropriate for the resolver of a
([socket]) given view. Named is not started.

ERROR invalid algorithm An invalid algorithm.

INFO dns64 reverse zone[separator][view The information about DNS64 reverse zone.
name]: [reverse]

ERROR invalid zone [zone name] Invalid zone.

ERROR invalid zone [zone name] Invalid zone.
ERROR invalid zone [zone name] Invalid zone.
ERROR unknown zone [zone name] Unknown zone.
ERROR zone [zone name] is neither master nor Zone is neither master nor slave.
slave
ERROR duplicate [zone name] Named found duplicated DNS name.
ERROR invalid cname [cname] Named found an invalid cname.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 19 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR failed to create a filtering tree for query Named cannot create a filtering tree for a query logging.
logging: [error message]

ERROR failed to create an exclusion tree for Named cannot create an exclusion tree for a query logging.
query logging: [error message]

INFO failed to add [object] for infoblox-query- Cannot add a configuration object for the infoblox-query-log-domain
log-domain: [info message] while configuring a view.

INFO failed to add [object] for infoblox-query- Cannot add a configuration object for the infoblox-query-log-domain
not-log-domain:[info message] while configuring a view.

ERROR max-acache-size [value] is too large The cache size is found to be too large while creating an additional
cache for this view and zones under the view.

INFO loading additional zones for view [view] Named loads additional zones for a view.

ERROR max-cache-size [value] is too large The cache size for a view and zones under the view is found to be
too large while obtaining configuration parameters.

ERROR views [primaryview] and [view] can't Two views cannot share the cache due to a configuration parameter
share the cache due to configuration mismatch.
parameter mismatch

ERROR error configuring NXDOMAIN/blacklist Named cannot configure NXDOMAIN/blacklist cache for a view.
cache for view [view]: [error message]

WARNING no root hints for view [view] The 'non-IN' view with no "hints zone" is configured.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 20 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

WARNING additional-from-auth no' is only The additional-from-auth controls the behavior when zones have
supported with 'recursion no' additional (out-of-zone) data or when following CNAME or DNAME
records. THe cache is disabled. BIND will not follow out-of-zone
records even if it is in the cache e.g. it will not follow the MX record
specifying mail.example.net for zone example.com for which it is
authoritative (master or slave). It will return REFUSED for the out-of-
zone record. This option is only effective if recursion "no" is
specified in a global options clause or in a view clause.
WARNING additional-from-cache no' is only The additional-from-cachecontrols the behavior when zones have
supported with 'recursion no' additional (out-of-zone) data or when following CNAME or DNAME
records. Cache disabled. BIND will NOT follow out-of-zone records
even if it is in the cache e.g. it will NOT follow the MX record
specifying mail.example.net for zone example.com for which it is
authoritative (master or slave). It will return REFUSED for the out-of-
zone record. This option is only effective if recursion "no" is
specified in a global options clause or in a view clause.
INFO automatic empty zone[separator][view Automatic empty zone for a view.
name]: [zone name]

ERROR error configuring RPZ white list for view Named cannot configure RPZ whitelist for view.
[view name]: [error message]

INFO configured RPZ white list for view [view RPZ whitelist for a view is configured.
name] (maxsize=[cache size], ttl=[cache
ttl])

WARNING Warning[separator][view name]: Unable Named cannot initialize top query client table.
to initialize top query client table:
[warning message]

WARNING Warning[separator][view name]: Unable Named cannot initialize a lock for the top query client table.
to initialize lock for top query client
table: [warning message]

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 21 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

WARNING Warning[separator][view name]: Unable Named cannot initialize top query name table.
to initialize top query name table:
[warning message]

WARNING Warning[separator][view name]: Unable Named cannot initialize lock for top query name table.
to initialize lock for top query name
table: [warning message]

WARNING Warning[separator][view name]: Unable Named cannot initialize top query RR type table.
to initialize top query RR type table:
[warning message]

WARNING Warning[separator][view name]: Unable Named cannot initialize lock for top query RR type table.
to initialize lock for top query RR type
table: [warning message]

WARNING Warning[separator][view name]: Unable Named cannot initialize top query per-zone client table.
to initialize top query per-zone client
table: [warning message]

WARNING Warning[separator][view name]: Unable Named cannot initialize top query per-FQDN client table.
to initialize top query per-FQDN client
table: [warning message]

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 22 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

INFO Non-empty 'infoblox-query-rewrite- Non-empty 'infoblox-query-rewrite-prefix' must be specified.
prefix' must be specified

ERROR port [port] out of range Port is out of range.

ERROR port [port] out of range Port is out of range.

ERROR port [port] out of range Port is out of range.

WARNING no forwarders seen; disabling forwarding Forwarding is disabled due to the absence of forwarders (no
forwarders seen).
WARNING could not set up forwarding for domain Named cannot set up forwarding for a domain.
[DNS name]: [warning message]

ERROR zone [zone name]: wrong class for view Zone class does not correspond to a view record class.
[view name]

ERROR zone [zone name] 'type' not specified Zone type is not specified.
ERROR zone [zone name]: 'file' not specified File is not specified for a zone.

ERROR сould not configure root hints from Named cannot configure root hints for a view from a hints file.
[hints file]: [error message]

WARNING gnoring non-root hint zone [zone name] Named ignores non-root hint zone because DNS fixed name is equal
to DNS root name.

ERROR redirect zone already exists A redirect zone already exists.

ERROR zone [zone name] already exists A zone already exists.
INFO set up managed keys zone for view [view The managed keys zone for a view is set.
name], file [file name]

WARNING option 'directory' contains relative path The 'directory' option contains a relative path.
[directory]

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 23 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR change directory to [directory] failed: Cannot change a directory.
[error message]
WARNING could not adjust the listen-on list; some The listen-on list cannot be adjusted because some interfaces may
interfaces may not work not work.

INFO ([type]) removed The zone of the specified type is removed.

INFO generating session key for dynamic DNS Generation of a session key for dynamic DNS.

ERROR could not create [file name] Named cannot create a file.

ERROR failed to generate session key for Cannot generate session key for dynamic DNS.
dynamic DNS: [error message]

ERROR unsupported or unknown algorithm Unsupported or unknown algorithm.

[algorithm][[s]or[]]

INFO loading configuration from [file name] Named loads configuration from a file.

INFO loading configuration from [file name] Named loads configuration from a file.

INFO reading built-in trusted keys from file Named reads built-in trusted keys from a file.
[file name]

WARNING max open files ([number files] The maximum number of open files is smaller than the maximum
ISC_PRINT_QUADFORMAT "u) is smaller number of sockets.
than max sockets ([max sockets])

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 24 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

WARNING less than 128 UDP sockets available after The number of available UDP sockets after applying 'reserved-
applying 'reserved-sockets' and sockets' and 'maxsockets' parameters is less than 128.
'maxsockets'

INFO Option infoblox-deny-rpz parsed. Nodes: Configuration option 'infoblox-deny-rpz' for a view ACL is parsed.
[node count]

INFO using default UDP/IPv4 port range: [[udp Named uses default UDP/IPv4 port range.
port low], [udp port high]]

INFO using default UDP/IPv6 port range: [[udp Named uses default UDP/IPv6 port range.
port low], [udp port high]]

INFO sizing zone task pool based on [number Zone manager sets task pool size based on the previously counted
zones] zones number of zones.

INFO no source of entropy found No source of entropy found.

INFO could not open entropy source [entropy An entropy source cannot be opened.
source]: [info message]

INFO using pre-chroot entropy source entropy Named uses pre-chroot entropy source.
source

ERROR the working directory is not writable The working directory is not writable.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 25 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

INFO ignoring config file logging statement Config file logging statement is ignored due to -g option.
due to -g option

WARNING waiting for network to come up took too Waiting for a network to come up takes too long. Network interfaces
long; reconfiguring network interfaces are reconfigured.
anyway

WARNING failed while spinning on network status Named failed while spinning on network status file: Proceed
file: [warning message]. Proceed anyway.
anyway.

N/A all zones loaded All zones are loaded.

INFO [number] zone[[s]or[]] from database Count of all zones from a database.

INFO [number] zone[[s]or[]] from zone files Count of zones from zone files.

INFO shutting down - zone load abandoned Named shuts down - zone load abandoned.

ERROR Error deallocating memory for zone Named cannot deallocate memory for a zone validation cache.
validation cache

INFO zone load done, initiating shutdown Zone load done, named initiates shutdown.

ERROR error shutting down; aborting: [error Named shuts down with indicated error.
message]

N/A running Named is running.

N/A shutdown request was received during Named receives shutdown request during initialization.
initialization

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 26 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

WARNING unable to load cached view Named cannot load a cached view configuration.
configuration: [warning message]

ERROR unable to cache view configuration: Named cannot cache a view configuration.
[error message]

INFO shutting down[[: flushing changes]or[]] : Named shuts down with flushing changes (or not).
flushing changes

CRITICAL [message]: [error message] Detailed information about error when named is exiting (due to a
fatal error).

ERROR exiting (due to fatal error) Named exits due to a fatal error.

CRITICAL destroying ZRQ consumer Named destroys ZRQ consumer.

WARNING unable to create dispatch for reserved Named cannot create dispatch for a reserved port.
port [socket address]: [warning message]

INFO reloading configuration succeeded Configuration successfully reloaded.

ERROR reloading configuration failed: [error Named cannot reload configuration.

message]

WARNING zones not loaded, reload request ignored Zones not loaded, reload request is ignored.

INFO reloading zones succeeded Zones reloading succeeded.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 27 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR reloading zones failed: [error message] Zones reloading failed.

WARNING zones not loaded, reconfig request Zones are not loaded; reconfig request is ignored.
ignored

INFO any newly configured zones are now Any newly configured zones are now loaded.
loaded

ERROR loading new zones failed: [error Loading of new zones failed.
message]

INFO initiate shutting down for a fresh restart Named initiates shutdown for a fresh restart.

INFO received SIGHUP signal to reload zones Named receives SIGHUP signal to reload zones.

INFO query logging is now [[on]or[off]] Query logging status.

INFO Failed to insert item [net address] from Named cannot insert item from infoblox-top-query-ip-block into the
infoblox-top-query-ip-block [name] into ip-block tree.
the ip-block tree

INFO Unexpected item has occured at position Unexpected item has occurred at position # in the infoblox-top-
[position] in infoblox-top-query-ip-block query-ip-block function.
[name]

ERROR port value [port] is out of range Port value is out of range.

INFO dumpstats complete Statistics dump completed.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 28 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR dumpstats failed: [error message] Statistics dump failed.

ERROR dumpibstats failed: [error message] Infoblox statistics dump failure.

INFO dumpdb complete Dumpdb completed.

ERROR dumpdb failed: [error message] Dumpdb failed.

INFO dumpdb started[separator][arguments] Dumpdb started.

INFO dumpsecroots complete Secroots dump completed.

ERROR dumpsecroots failed: [error message] Secroots dump failed.

INFO dumprecursing complete Dumprecursing is completed.

ERROR dumprecursing failed: [error message] Dumprecursing failed.

ERROR flushing cache in view [view name] Named cannot flush cache in a view.
failed: [error message]

ERROR fixing cache in view [view name] failed: Named cannot fix cache in a view.
[error message]

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 29 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

INFO flushing cache in view [view name] Flushing cache in view succeeded.
succeeded

INFO flushing caches in all views succeeded Flushing caches in all views succeeded.

ERROR flushing cache in view [view name] Named cannot flush cache in a view.
failed: view not found

ERROR ushing [[tree]or[name]] '[target]' in Named cannot flush in cache view.

cache view '[view name]' failed: [error
message]

INFO flushing [[tree]or[name]] '[target]' in Flushing in cache view succeeded.

cache view '[view name]' succeeded

INFO flushing [[tree]or[name]] '[target]' in all Flushing in all cache views succeeded.
cache views succeeded, tree : name

ERROR "flushing [[tree]or[name]] '[target]' in Named cannot flush in cache view: view not found.
cache view [view name] failed: view not
found", tree : name

INFO dumping all zones[[removing journal Named dumps all zones.

files]or[]]: [info message]

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 30 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

INFO sync: dumping zone '[zone Dumping zone updates to a disk. The journal file may be removed.
name]/[class]'[separator][view name][[,
removing journal file]or[]]:[info message]

INFO [[freezing]or[thawing]] all zones: [info Result of freezing (thawing) all zones from a command channel.
message]

INFO [[freezing]or[thawing]] zone Detailed information about freezing (or thawing) of a zone.
'[zonename]/[class]'[separator][view
name]:[info message]

INFO addzone failed; reverting. named tried to add zone and failed to load a zone from the master
file.

INFO addzone failed; reverting. Zone is added to a view via addzone.

WARNING deleted zone [zone name] was missing Deleted zone is missing from new zone file.
from new zone file

INFO zone [zone name] removed via delzone Zone is removed via delzone.

N/A topping statistics channel on [socket] Named stops statistics channel on a socket address.

WARNING rejected statistics connection from Named rejected statistics connection from a socket address.
[socket]

N/A statistics channel listening on [socket] Statistics channel listening on a socket address.

WARNING couldn't install new acl for statistics Cannot install new access list for a statistics channel.
channel [socket]: [warning message]

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 31 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

WARNING statistics-channels specified but not Statistics-channels are specified but not effective due to a missing
effective due to missing XML library XML library.

WARNING couldn't allocate statistics channel Cannot allocate a statistics channel.

[socket]: [warning message]

ERROR key '[key id]': has a unsupported The key has an unsupported algorithm.
algorithm [algorithm]

ERROR configuring key '[key id]': [error Configuring a key.

message]
N/A updating zone '[DNS name]/[class]': Named updates a zone.
[message]

N/A [message] Named sends message to a log file.

N/A update '[DNS name]/[class]' denied due Update is denied due to allow-query.
to allow-query

INFO update '[DNS name]/[class]' denied Update is denied.

INFO signer [DNS name] [info message] Named overrides the default ACL logging when checking whether a
client can update the zone or whether the request can be forwarded
to the master based on IP address. Signer of NS client is displayed.

N/A [type of operation] '[DNS name]/[class]' Named overrides the default ACL logging when checking whether a
[message] client can update the zone or whether the request can be forwarded
to the master based on IP address. Detailed information about this
action is provided.
INFO Update rejected because TTL differs Update is rejected because TTL differs from existing unmodifiable
from existing unmodifiable entry: Use entry.
TTL [ttl]

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 32 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR could not create update response Update response message cannot be created.
message: [error message]

ERROR [DNS name]/MX: [DNS name]: [error The MX is an IP address. Should be a <domain-name> which
message] specifies a host willing to act as a mail exchange for the owner
name.

WARNING [DNS name]/MX: warning: [DNS name]: The MX is an IP address. Should be a <domain-name> which
[warning message] specifies a host willing to act as a mail exchange for the owner
name.

ERROR [DNS name]/MX '[DNS name]' has no The Zone/MX has no address records (A or AAAA).
address records

ERROR [DNS name]/MX '[DNS name]' is a The Zone/MX is a CNAME record that is invalid. Found while
CNAME (illegal) checking an MX record.
ERROR [DNS name]/MX '[DNS name]' is below a the Zone/MX is below DNAME record that is ivalid. Found while
DNAME '[DNS name]' (illegal) checking an MX record.

ERROR NSEC only DNSKEYs and NSEC3 chains NSEC only, DNSKEYs and NSEC3 chains are not allowed. There is at
not allowed least one DNSKEY with an algorithm that predates NSEC3, and
therefore a zone cannot have a valid NSEC3 chain.
ERROR too many NSEC3 iterations ([number Too many NSEC3 iterations for the weakest DNSKEY. The iterations
iterations]) for weakest DNSKEY ([max parameter defines the number of additional times the hash function
number])" has been performed. A higher value results in greater resiliency
against dictionary attacks, at a higher computational cost for both
the server and resolver.
ERROR DDNS update failed due to hos checking DDNS update failed due to a host checking policy.
policy on '[DNS name]'

WARNING update RR has incorrect class [class] Update RR has an incorrect class.

N/A attempt to add [type] ignored An attempt to add MF or MD is ignored.

N/A attempt to add wildcard [type] record An attempt to add a wildcard record is ignored.
ignored

N/A attempt to add CNAME alongside non- An attempt to add CNAME alongside with non-CNAME is ignored.
CNAME ignored

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 33 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

N/A attempt to add non-CNAME alongside An attempt to add non-CNAME alongside with CNAME is ignored.
CNAME ignored

N/A attempt to create 2nd SOA ignored An attempt to create 2nd SOA is ignored.

N/A SOA update failed to increment serial, SOA update failed to increment serial and was ignored.
ignoring it

N/A attempt to add a private type ([type]) An attempt to add a private type record is rejected, internal use
record rejected internal use only only.

N/A attempt to add NSEC3PARAM record An attempt to add NSEC3PARAM record with non OPTOUT flag.
with non OPTOUT flag

N/A attempt to add NSEC3PARAM record An attempt to add NSEC3PARAM record is ignored.
ignored
WARNING warning: ownername [DNS name] The ownername contains the specified non-terminal wildcard.
contains a non-terminal wildcard

N/A adding an RR at '[DNS name]' [record Adding a resource record to the specified zone.
data type]
N/A delete all rrsets from name '[DNS name]' All resource recordsets are deleted from the specified zone.

N/A attempt to delete an NSEC3PARAM An attempt to delete an NSEC3PARAM record is ignored.

record ignored

N/A "attempt to delete all SOA or NS records An attempt to delete all SOA or NS records is ignored.
ignored
N/A deleting rrset at '[DNS name]' [record Deleting resource record set from the specified zone.
data type]

N/A attempt to delete SOA ignored An attempt to delete SOA is ignored.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 34 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

N/A attempt to delete last NS ignored An attempt to delete last NS is ignored.

N/A deleting an RR at '[DNS name]' [record Deleting a resource record from the specified zone.
data type]
ERROR error setting up deletion of TXT at '[DNS Cannot set up a deletion of a TXT record at the specified zone.
name]': [error message]

N/A deleting rrset at '[DNS name]' TXT A resource recordset at a zone TXT is deleted.

ERROR error deleting TXT at '[DNS name]' : Deleting recordset at a zone TXT failed for the specified reason.
[error message]
N/A update rejected: post update name Update is rejected. The post update name server sanity check failed.
server sanity check failed

N/A update rejected: all DNSKEY records Update is rejected. All DNSKEY records are removed and 'dnssec-
removed and dnssec-secure-to-insecure' secure-to-insecure' is not set.
not set

ERROR RRSIG/NSEC/NSEC3 update failed: [error RRSIG/NSEC/NSEC3 update failure.

message]

WARNING failed to open journal [journal name] due Cannot open journal due to insufficient file permissions. The journal
to insufficient file permissions; journal and IXFR are disabled. To remedy the situation try to restart DNS
and IXFR will be disabled; try to restart service to fix the issue.
DNS service to fix the issue

N/A Resetting journal [journal name] Named is resetting a journal.

ERROR Error unlinking journal file [journal file] Named cannot unlink journal file for a reset.
for reset: [error message]

ERROR dns_zone_signwithkey failed: [error The dns_zone_signwithkey function failed.

message]

ERROR dns_zone_addnsec3chain failed: [error The dns_zone_addnsec3chain function failed.

message]

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 35 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

N/A [message] Resource record is not too large to print.

N/A <RR too large to print> Resource record is too large to print.
WARNING [DNS record datatype] request denied: AXFR or IXFR request is denied.
[warning message]

ERROR zone transfer '[DNS name]/[class]' Zone transfer is denied.

denied

WARNING RR too large for zone transfer ([number] Resource record is too large for a zone transfer.
bytes)
WARNING failed to register AXFR client for Named cannot register AXFR client for multimaster consistency and
multimaster consistency: [warning may be unable to provide future IXFR.
message]; may be unable to provide
future IXFR

INFO [query type] ended The AXFR or IXFR is ended.

ERROR [xfr message]: [error message] The AXFR or IXFR error.
N/A transfer of '[DNS name]/[class]': The message containing a result of a zonename/rdclass transfer.
[message]

ERROR '[DNS name]' is not a valid name The textual representation of a DNS name at source cannot be
converted into an uncompressed wire form stored in a target.
ERROR error copying origin: [error message] Named cannot copy a DNS name.

ERROR '[DNS name]' is not a valid name The textual representation of a DNS name at source cannot be
converted into an uncompressed wire form stored in a target.
ERROR '[record data type]' is not a valid type DNS rdatatype is invalid.
ERROR failed to enable auto DDNS policy for Named cannot enable auto DDNS policy for a zone because session
zone %s: session key not found key is not found.

ERROR port is not configurable for static stub Port is not configurable for a static stub server-addresses.
server-addresses
ERROR scoped address is not allowed for static The scoped address is not allowed for static stub server-addresses.
stub server-addresses

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 36 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR server-name '[DNS name]' is not a valid The server-name is not a valid name.
name

ERROR server-name '[server name]' must not be The server-name must not be a subdomain of a zone name.
a subdomain of zone name '[zone name]'

ERROR No NS record is configured for a static- No NS record is configured for a static-stub zone.
stub zone '[zone name]'

ERROR zone '[zone name]': 'file' not specified Zone: 'file' not specified.

ERROR max-journal-size [size] is too large The configuration option 'max-journal-size' value is too large for a
zone.

WARNING failed to initialize transfer tracker for Failed to initialize transfer tracker for multi master zone. Tracking is
multi master zone; disabled tracking disabled.

ERROR max-journal-size [size] is too large The configuration option 'max-journal-size' value is too large for a
zone.

WARNING zone '[zone name]' allows updates by IP Zone allows updates by IP address. This is insecure.
address, which is insecure

WARNING interpreting sig-validity-interval as To avoid excessive delays in testing, you should resign zones quickly.
seconds Treat signature-validity-interval as seconds instead of days and
compensate accordingly.
ERROR dlz_dlopen: library '[path]' is missing The dlz_dlopen driver: required symbol cannot be loaded due to a
required symbol '[symbol]' missing library.

ERROR dlz_dlopen driver for '[dlz name]' needs The dlz_dlopen driver for dlz needs a path to the shared library.
a path to the shared library

ERROR dlz_dlopen failed to open library '[path]' The dlz_dlopen driver failed to open a library.
– [error message]

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 37 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR dlz_dlopen: incorrect version [version] An incorrect version of dlz_dlopen driver.
should be [version] in '[path]'

ERROR dlz_dlopen of '[dlz name]' failed The dlz_dlopen of DLZ failed.

N/A Registering DLZ_dlopen driver Registering DLZ_dlopen driver.
N/A Unregistering DLZ_dlopen driver Unregistering DLZ_dlopen driver.
ERROR dlz_dlopen: library '[path]' is missing The dlz_dlopen driver: required symbol cannot be loaded due to a
required symbol '[symbol]' missing library.

ERROR dlz_dlopen driver for '[path]' needs a The dlz_dlopen driver for dlz needs a path to the shared library.
path to the shared library

ERROR dlz_dlopen failed to open library '[path]' The dlz_dlopen driver failed to open a library.
– [error message]

ERROR dlz_dlopen: incorrect version [version] The dlz_dlopen driver reports a incorrect API version.
should be [version] in '[path]'

ERROR '[dlz name]' failed The dlz_dlopen dlz driver failed.

N/A Registering DLZ_dlopen driver Registering DLZ_dlopen driver.
N/A Unregistering DLZ_dlopen driver Unregistering DLZ_dlopen driver.
CRITICAL Unspecified category and unspecified Testing unspecified category and unspecified module to stderr
module to stderr (standard error).

CRITICAL Specified category and unspecified Testing specified category and unspecified module to stderr
module to stderr (standard error).

WARNING Using the predefined channels to Using the predefined channels to syslog+stderr.
syslog+stderr

INFO This is to null and should not appear! Informational message.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 38 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR This message to the redefined default This message to the redefined default category should be second in
category should, be second in syslog syslog.

N/A This should be rolled over and not This should be rolled over and not appear!
appear!

N/A should be in file [message]/[file version] Message should be in a file.

N/A should be in base file Message should be in a base file.

N/A This is message [number] in the log file This is a message № ... in the log file.

ERROR bdbhpt driver ttl must be a positive The bdbhpt driver: Error of converting ttl string to integer. ttl must
number be a positive number.

ERROR bdbhpt could not initialize [db name] The bdbhpt driver failed to initialize a database.
database. bdbhpt error: [error message]

ERROR bdbhpt could not set flags for [db name] The bdbhpt driver failed to set flags for a database.
database. bdbhpt error: [error message]

ERROR bdbhpt could not open [db name] The bdbhpt driver failed to open a database in file.
database in [db file]. bdbhpt error: [error
message]

ERROR bdbhpt driver requires at least 3 The bdbhpt driver requires at least 3 command line arguments.
command line args.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 39 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR bdbhpt driver requires the operating The bdbhpt driver requires the operating mode to be set to P or C or
mode be set to P or C or T. You specified T.
[operating mode]

ERROR Could not allocate memory for database Cannot allocate memory for a database instance object.
instance object.

ERROR bdbhpt environment could not be The bdbhpt driver environment cannot be created.
created. bdbhpt error: [error message]

ERROR bdbhpt environment at '[command line The bdbhpt driver environment cannot be opened.
argument]' could not be opened. bdbhpt
error: [error message]

ERROR BDB driver ttl must be a positive number The Berkeley DB driver: Cannot convert TTL string to an integer. TTL
value must be a positive number.

ERROR BDB could not initialize [db name] The Berkeley DB driver failed to initialize a database.
database. BDB error: [error message]

ERROR BDB could not set flags for [db name] The Berkeley DB driver failed to set flags for a database.
database. BDB error: [error message]

ERROR BDB could not open [db name] database The Berkeley DB driver failed to open a database in file.
in [db file]. BDB error: [error message]

ERROR Berkeley DB driver requires at least 2 The Berkeley DB driver requires at least 2 command line arguments.
command line args.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 40 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR Could not allocate memory for database Memory for database instance object cannot be allocated.
instance object.

ERROR BDB environment could not be created. The Berkeley DB environment cannot be created.
BDB error: [error message]

ERROR BDB environment at '[command line The Berkeley DB environment cannot be opened. An appropriate
argument]' could not be opened. BDB error is indicated.
error: [error message]

ERROR BDB could not associate [dlz host] The Berkeley DB could not associate the host secondary database
database with [dlz data]. BDB error: with the primary database.
[error message]

ERROR BDB could not associate [dlz zone] The Berkeley DB could not associate the zone secondary database
database with [dlz data]. BDB error: with the primary database.
[error message]

ERROR dlz_dlopen: library '[path]' is missing The dlz_dlopen driver: required symbol cannot be loaded due to a
required symbol 'symbol' missing library.

ERROR dlz_dlopen driver for '[dlz name]' needs The dlz_dlopen driver for dlz: a path to the shared library is needed.
a path to the shared library

ERROR dlz_dlopen failed to open library '[path]' The dlz_dlopen driver failed to open a library.
– [error message]

ERROR dlz_dlopen: incorrect version [version] The dlz_dlopen driver reports an incorrect API version.
should [version] in '[path]'

ERROR dlz_dlopen of '[dlz name]' failed THE dlz_dlopen driver of dlz failed.
N/A Registering DLZ_dlopen driver Registering DLZ_dlopen driver.
N/A Unregistering DLZ_dlopen driver Unregistering DLZ_dlopen driver.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 41 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR Filesystem driver unable to allocate Filesystem driver cannot allocate memory in create_path() function.
memory in create_path().

ERROR Filesystem driver: [directory] could not Filesystem driver reports that directory entry cannot be parsed
be parsed properly properly.

ERROR Filesystem driver: [directory] could not Filesystem driver reports that directory entry cannot be parsed
be parsed properly properly.

ERROR Filesystem driver ttl must be a positive Filesystem driver cannot convert a TTL string to an integer. The TTL
number value must be a positive number.

ERROR Unable to open [directory] directory to Cannot open directory to read entries.
read entries.

ERROR Unable to open [directory] directory to Cannot open directory to read entries.
read entries.

ERROR Unable to open [directory] directory to Cannot open directory to read entries.
read entries.

ERROR Filesystem driver requires 6 command File system driver requires 6 command line arguments.
line args.

ERROR Filesystem driver can only accept a single File system driver can only accept a single character for a separator.
character for separator.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 42 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR Base dir parameter for filesystem driver Base dir parameter for file system driver should end with either '/' or
should end with either '/' or '\\' '\\'

ERROR Directory split count must be zero (0) or Directory split count must be zero (0) or a positive number.
a positive number

ERROR Filesystem driver unable to allocate File system driver cannot allocate memory for the configuration
memory for config data data.

ERROR [LDAP] query is not a valid LDAP URL LDAP URL query is invalid.

ERROR parsing [LDAP] query failed LDAP URL query cannot be parsed.

ERROR [LDAP] query must specify at least LDAP URL query must contain more attributes.
[number] attributes to return

ERROR [LDAP] query must not specify a host LDAP URL query should not specify a host.

ERROR [LDAP] query must not specify a port LDAP URL query should not specify a port.

ERROR [LDAP] query must specify a search base LDAP URL query should specify a search base.

ERROR [LDAP] uses extensions. The driver does The LDAP URL driver does not support LDAP extensions.
not support LDAP extensions.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 43 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

INFO LDAP driver unable to find available LDAP driver cannot find an available connection after exhausting the
connection after searching %d times quota of search attempts.

INFO LDAP no entries to process LDAP query failed to process the first entry.

ERROR LDAP driver unable to allocate memory LDAP driver failed to allocate memory while processing results.
while processing results

ERROR LDAP driver ttl must be a positive LDAP driver query TTL value must be a positive number.
number

ERROR LDAP driver unable to retrieve DNS type LDAP driver failed to retrieve DNS type.

ERROR LDAP driver unable to retrieve DNS data LDAP driver failed to retrieve DNS data.

ERROR dlz-ldap: putnamedrr failed for "[host] Failed to put resource record to BIND due to the specified reason.
[type] [ttl] [data]", [error message]

ERROR dlz-ldap: putrr failed for "[type] [ttl] Failed to put resource record to BIND due to the specified reason.
[data]", [error message]

ERROR LDAP driver failed while sending data to The LDAP driver failed while sending data to BIND.
BIND

INFO LDAP driver attempting to re-connect LDAP driver attempts to re-connect.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 44 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

INFO LDAP driver attempting to re-connect LDAP driver attempts to re-connect.

ERROR LDAP error: [error message] LDAP driver failed with non declared error.

ERROR LDAP driver requires at least 8 command LDAP driver receives less than nine command line arguments.
line args

ERROR LDAP driver cannot accept more than 11 LDAP driver failed to accept more than 11 command line arguments.
command line args

ERROR LDAP driver protocol must be either Incorrect LDAP driver protocol version.
[version] or [version]

ERROR LDAP driver authentication method must Incorrect LDAP driver authentication method.
be one of [SIMPLE], [KRB41]or [KRB42]

ERROR LDAP driver database connection count LDAP driver database connection count is incorrect (negative).
must be positive

ERROR LDAP driver could not create database LDAP driver Cannot create a database instance object.
instance object

ERROR LDAP driver could not allocate memory LDAP driver failed to allocate memory for the specified database
for connection number [connection instance (DBI).
number]

ERROR LDAP driver could not allocate memory LDAP driver failed to allocate memory for a database instance (DBI).
for connection

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 45 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR LDAP driver could not set protocol LDAP driver failed to set a protocol version.
version

ERROR LDAP driver could not bind connection LDAP driver failed to bind indicated database instance (DBI) to
number [connection number] to server named.

ERROR LDAP driver could not bind connection to LDAP driver failed to bind a database instance (DBI) to named.
server

ERROR mysql driver ttl must be a positive The MySQL driver query TTL must be a positive number.
number

ERROR mysql driver unable to allocate memory The MySQL driver failed to allocate memory for a temporary string
for temporary string when processing MySQL result sets for lookup and authority.

ERROR mysql driver ttl must be a positive The MySQL driver query TTL must be a positive number.
number

ERROR dns_sdlz_putrr returned error. Error The dns_sdlz_putrr() function returned an error when processing
code was: [error message] MYSQL result sets for lookup and authority.

ERROR mysql driver unable to return result set The MySQL driver failed to return resultset from database for a
for findzone query zone.

ERROR mysql driver unable to return result set The MySQL driver failed to return resultset for allow xfr query when
for allow xfr query determining whether the client is allowed to perform a zone
transfer.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 46 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR mysql driver unable to return result set The client is allowed to perform a zone transfer but failed to get all
for all nodes query the nodes in the zone. MySQL driver cannot return result set for all
nodes query.

ERROR mysql driver too few fields returned by The client is allowed to perform a zone transfer but failed to get all
all nodes query the nodes in the zone. Result of all nodes query from a result set
contains less than four fields.

ERROR mysql driver ttl must be a positive The client is allowed to perform a zone transfer and gets all the
number nodes in the zone. Nevertheless, the MySQL driver failed to convert
TTL value from a string to a long type because it must be a positive
number.
ERROR mysql driver unable to allocate memory The MySQL driver failed to allocate memory for a temporary string
for temporary string when it tries to concatenate the last fields (all fields after the 3rd)
received as a result of all nodes query.

ERROR dns_sdlz_putnamedrr returned error. The client is allowed to perform a zone transfer but when it tries to
Error code was: [error message] get all the nodes in the zone, dns_sdlz_putnamedrr()
function returns indicated error code.

ERROR mysql driver unable to return result set The MySQL driver failed to get the result set for the authority query
for authority query from the database.

ERROR mysql driver unable to return result set The MySQL driver failed to get the result set for a lookup from the
for lookup query database.

ERROR mysql driver requires at least 4 There are less than four command line arguments passed to MySQL
command line args driver when it tries to create a driver instance.

ERROR mysql driver cannot accept more than 7 The MySQL driver Cannot create an instance because the number of
command line args command line parameters is more than seven.

ERROR mysql driver requires a dbname The dbname parameter is missing in command line parameters
parameter passed to the MySQL driver. Required to create a MySQL Driver
instance.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 47 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR Mysql driver port must be a positive The MySQL driver Cannot create an instance of the MySQL driver
number because port parameter value passed as the command line
argument is not a positive number.

ERROR mysql driver could not create database The MySQL driver Cannot create a driver instance because the
instance object number of command line parameters is incorrect.

ERROR mysql driver could not allocate memory The MySQL driver failed to allocate memory for a database
for database connection connection.

WARNING mysql driver failed to set The MySQL driver failed to set the MYSQL_OPT_RECONNECT option
MYSQL_OPT_RECONNECT option, when it tries to reconnect to a database.
continuing

ERROR mysql driver failed to create database The MySQL driver Cannot create a database connection after four
connection after 4 attempts attempts.

ERROR Odbc driver unable to allocate memory The ODBC driver failed to allocate memory for a connection object
when trying to connect to a database.

ERROR Odbc driver unable to allocate memory The ODBC driver failed to allocate memory for a connection object
when trying to connect to a database.

ERROR Odbc driver unable to connect The ODBC driver cannot connect to a database.

ERROR Odbc driver unable to allocate memory The ODBC driver cannot allocate memory for a ODBC statement
when trying to connect to a database.

INFO Odbc driver unable to find available The ODBC driver cannot connect to a database after the number of
connection after searching [number] indicated attempts.
times

ERROR Odbc driver unable to process result set The ODBC driver cannot process a result set from the database for a
lookup and authority.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 48 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR Odbc driver ttl must be a positive The ODBC driver failed to convert TTL value from a string to long
number type when processing ODBC result sets for lookup and authority
because the value is not a positive number.

ERROR dns_sdlz_putrr returned error. Error The dns_sdlz_putrr() function returned indicated error when it
code was: [error message] processed ODBC result sets for a lookup and authority.

ERROR Odbc driver unable to return result set Although the client is allowed to perform a zone transfer, the The
for all nodes query ODBC driver cannot return a result set for the all nodes query.

ERROR Odbc driver unable to process result set The client is allowed to perform a zone transfer but The ODBC driver
failed to get a number of columns from a result set when it trieds to
get all the nodes in the zone.

ERROR Odbc driver too few fields returned by all The client is allowed to perform a zone transfer but failed to get all
nodes query the nodes in the zone. Result of all nodes query from a result set
contains less than four fields.

ERROR Odbc driver ttl must b a positive number The client is allowed to perform a zone transfer and gets all the
nodes in the zone. Nevertheless, the The ODBC driver failed to
convert TTL value from a string to a long type because it must be a
positive number.

ERROR dns_sdlz_putnamedrr returned error. The client is allowed to perform a zone transfer but failed to get all
Error code was: [error message] the nodes in the zone, dns_sdlz_putnamedrr() function returns
indicated error.

ERROR Odbc driver unable to return result set The ODBC driver failed to get the result set for authority query from
for authority query the database.

ERROR Odbc driver unable to return result set The ODBC driver failed to get the result set for a lookup query from
for lookup query the database.

ERROR Odbc driver requires at least 4 command The ODBC driver Cannot create its instance because it requires at
line args least four command line arguments.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 49 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR Odbc driver cannot accept more than 7 The ODBC driver Cannot create an instance because the number of
command line args command line parameters is more than seven.

ERROR Odbc driver database connection count The ODBC driver Cannot create a driver instance because the value
must be positive of the database connection count parameter passed as command
line argument must be a positive number.

ERROR odbc driver requires a dns parameter The ODBC driver Cannot create a driver instance because the DNS
parameter is missing.

INFO Odbc driver unable to allocate memory The ODBC driver failed to allocate memory for SQL environment
when it creates the driver instance.

INFO Unable to configure ODBC environment The ODBC driver failed to set the VERSION attribute for SQL
environment when it creates the driver instance.

ERROR Odbc driver could not create database The ODBC driver Cannot create a database instance object because
instance object the number of command line parameters is incorrect.

ERROR Odbc driver failed to create database The ODBC driver Cannot create a database connection for the
connection number [connection specified thread after three attempts.
number] after 3 attempts

ERROR Odbc driver failed to create database The ODBC driver Cannot create a database connection after three
connection after 3 attempts attempts.

INFO Postgres driver unable to find available The Postgres driver failed to find an available connection after the
connection after searching [number] searching indicated number of times.
times

ERROR [dlz thread number] Getting DBI The Postgres driver tries to get a database instance (DBI).

ERROR [dlz thread number] Got DBI - checking The Postgres driver is checking the query.
query

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 50 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR [dlz thread number] checked query The Postgres driver checked the query.

ERROR [dlz thread number] did zone The Postgres driver added zone to a database instance for the
specified thread.
ERROR [dlz thread number] did record The Postgres driver added a record to a database instance for the
specified thread.
ERROR [dlz thread number] did client The Postgres driver added a record to a database instance for the
specified thread.
ERROR [dlz thread number] built query The Postgres driver built a query for the specified thread.

ERROR [dlz thread number] query is [query] The Postgres driver displays the query for the specified thread.

ERROR [dlz thread number] executing query for The Postgres driver executes the query up to three times for the
[number] time specified thread.

ERROR [dlz thread number] resetting connection The Postgres driver resets a connection to a database for the
specified thread.

ERROR [dlz thread number] rs ok The Postgres driver received a result set for the specified thread.

ERROR [dlz thread number] clearing rs The Postgres driver cleans up an unsuccessful result set for the
specified thread.

ERROR [dlz thread number] cleaning up The Postgres driver cleans up a database instance (DBI) for the
specified thread.
ERROR [dlz thread number] unlocking mutex The Postgres driver unlocks mutex for the specified thread.

ERROR [dlz thread number] returning The Postgres driver returns the specified thread.

ERROR Postgres driver ttl must be a positive The Postgres driver failed to convert TTL value from a string to a
number long type when processing Postgres result sets for a lookup and
authority query. The reason is that TTL value must be a positive
number.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 51 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR Postgres driver unable to allocate The Postgres driver cannot allocate memory for temporary string
memory for temporary string when processing Postgres result sets for a lookup and authority
query.

ERROR Postgres driver ttl must be a positive The Postgres driver failed to convert TTL value from a string to a
number long type when processing Postgres result sets for a lookup and
authority query. The reason is that TTL value must be a positive
number.

ERROR Error code was: [error message] The dns_sdlz_putrr() function returns the specified error when
processing Postgres result sets for a lookup and authority query.

ERROR Postgres driver unable to return result The Postgres driver cannot return a result set for a find zone query.
set for findzone query

ERROR Postgres driver unable to return result The Postgres driver cannot return a result set for an allow xfr query.
set for allow xfr query

ERROR Postgres driver unable to return result The Postgres driver cannot return a result set for all nodes query.
set for all nodes query

ERROR ostgres driver too few fields returned by The Postgres driver returns less then four fields by all nodes query
all nodes query from a result set.

ERROR Postgres driver ttl must be a positive The Postgres driver cannot convert TTL value from a string to a long
number type when processing Postgres result sets for all the nodes in the
zone query because the TTL value is not a positive number.

ERROR Postgres driver unable to allocate The Postgres driver cannot allocate memory for a temporary string
memory for temporary string when processing Postgres result sets for all the nodes in the zone
query.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 52 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR dns_sdlz_putnamedrr returned error. The dns_sdlz_putnamedrr() function returned the specified error
Error code was: [error message] when processing Postgres result sets for all the nodes in the zone
query.

ERROR Postgres driver unable to return result The Postgres driver cannot return a result set for an authority query.
set for authority query

ERROR Postgres driver unable to return result The Postgres driver cannot return a result set for a lookup query.
set for lookup query

ERROR Postgres driver requires at least 4 The Postgres driver Cannot create a driver instance because it
command line args requires at least four command line arguments.

ERROR Postgres driver cannot accept more than The Postgres driver Cannot create a driver instance because it does
7 command line args. not accept more that seven command line arguments.

ERROR Postgres driver database connection The Postgres driver Cannot create a driver instance because the
count must be positive database connection count parameter passed as command line
arguments is not a positive number.

ERROR Postgres driver could not create The Postgres driver Cannot create a driver instance because the
database instance object number of command line parameters is incorrect.

ERROR Postgres driver could not allocate The Postgres driver fails to allocate memory for a database
memory for database connection connection.

ERROR Postgres driver failed to create database The Postgres driver Cannot create a database connection for the
connection number [connection specified database instance (DBI) after four attempts.
number] after 4 attempts

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 53 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR Postgres driver failed to create database The Postgres driver Cannot create a database connection for the
connection after 4 attempts database instance (DBI) after four attempts.

INFO Loading '[DLZ name]' using DLZ_stub Loading DLZ using DLZ_stub driver with the specified parameters
driver. Zone: [zone], Name: [name] IP: from a command line.
[IP address]

ERROR Required token $client$ not found The SDLZ driver failed to find the required client token while
constructing a query list by parsing a string into query segments.

ERROR Required token $record$ not found The SDLZ driver failed to find the required record token while
constructing a query list by parsing a string into query segments.

ERROR Required token $zone$ not found. The SDLZ driver failed to find the required zone token while
constructing a query list by parsing a string into query segments.

ERROR Could not allocate memory for database The SDLZ driver failed to allocate memory for a database instance
instance object. object while constructing a SQL database instance (DBI).

ERROR Could not build all nodes query list The SDLZ driver failed to build all nodes query list while constructing
a SQL database instance (DBI).

ERROR Could not build allow xfr query list The SDLZ driver failed to build allow xfr query list while constructing
a SQL database instance (DBI).

ERROR Could not build authority query list The SDLZ driver failed to build allow xfr query list while constructing
a SQL database instance (DBI).

ERROR Could not build find zone query list The SDLZ driver failed to build find zone query list while constructing
a SQL database instance (DBI).

ERROR Could not build count zone query list The SDLZ driver failed to build count zone query list while
constructing a SQL database instance (DBI).

ERROR Could not build lookup query list The SDLZ driver failed to build lookup query list while constructing a
SQL database instance (DBI).

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 54 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR db_create The BDB SDB driver Cannot create a database instance.

ERROR sc_file_exists: [filename] The BDB SDB driver Cannot create a database instance because
filename passed as a command line argument is invalid.

ERROR DB->open: [error message] The BDB SDB driver failed to open a database from a file.

ERROR DB->cursor: [error message] The BDB SDB driver failed to return a result set for a lookup query.

ERROR dns_sdb_putrr The BDB SDB driver failed to put a record data into a database for a
lookup query.

ERROR DB->cursor: [error message] The BDB SDB driver failed to return a result set for all nodes query.

ERROR dns_sdb_putnamedrr The BDB SDB driver failed to put a named record data into a
database for all nodes query.

ERROR LDAP sdb zone '[zone]': bind failed LDAP SDB driver failed to bind zone data with database data.

ERROR LDAP sdb zone '[zone]': name [name] too The SDB LDAP driver detects that the length of a name for a zone is
long too long.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 55 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR LDAP sdb zone '[zone]': search failed, The SDB LDAP driver failed to find a zone in a database.
filter [filter]

ERROR LDAP sdb zone '[zone]': ldap_result The SDB LDAP driver failed to find a search entry for a record data in
returned [error message] a result message.

ERROR LDAP sdb zone '[zone]': ldap_first_entry The SDB LDAP driver failed to find first entry for a record data in a
failed result message.

ERROR LDAP sdb zone '%s': dns_sdb_put... failed The SDB LDAP driver detects that the value of a record data of result
for [value of a record data] message is invalid.

ERROR LDAP sdb zone '[zone]': URL: extension Cannot create The SDB LDAP driver because URL extension for a
syntax error zone has a syntax error.

ERROR LDAP sdb zone '[zone]': URL: unknown Cannot create The SDB LDAP driver because URL for a zone has an
critical extension unknown critical extension.

ERROR LDAP sdb zone '[zone]': URL: bad hex Cannot create The SDB LDAP driver because URL extension for a
values zone has a bad hex values.

ERROR initializing tcldb: loading 'lookup.tcl' Cannot create the The SDB TSLDB driver.
failed: [error message]

ERROR zone '[zone]': tcl lookup function failed: The SDB TSLDB driver failed to connect to a database for a zone
[error message] lookup query.

ERROR zone '[zone]': malformed return value The SDB TSLDB driver failed to return result set for a zone lookup
from tcl lookup function: [error message] query or count of fields in a result set is not equal to three.

ERROR rrset-order: invalid class '[class]' DNS record class name is not CHAOS as defined by the rrset-order
statement.
ERROR rrset-order: invalid type '[type]' DNS record data type length does not comply with the rrset-order
statement value.
ERROR rrset-order: invalid name '[name]' DNS name is invalid according to the rrset-order statement.

ERROR rrset-order: keyword 'order' missing The "order" field is missing from the rrset-order statement.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 56 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR rrset-order: missing ordering The "order" field is missing from the rrset-order statement.
WARNING rrset-order: order 'fixed' was disabled at The rrset-order statement order "fixed" was disabled at a
compilation time compilation time.

ERROR rrset-order: invalid order '[order object]' The rrset-order statement contains an invalid value for order.

ERROR port '[port]' out of range The port value found is out of range when checking dual-stacked
(IPv4/IPv6) servers.
ERROR bad name '[DNS name]' An invalid DNS name was found when checking dual-stacked
(IPv4/IPv6) servers.
ERROR port '[port]' out of range The port value found is out of range when checking dual-stacked
(IPv4/IPv6) servers.
ERROR forwarders declared in root zone and in These are forwarders declared in the root zone and in general
general configuration: [file]:[line] configuration.

ERROR no matching 'forwarders' statement Forwarders are not declared in a root zone.
ERROR bad domain name '[DNS name]' Bad DNS name is detected when disabling the use of DNS security
algorithm.
ERROR invalid algorithm '[algorithm]' DNS security algorithm defined in a configuration file was found
invalid when disabling the use of DNS security algorithm.

ERROR bad domain name '[DNS name]' Bad DNS name is detected when checking dnssec-must-be-secure
configuration option.
ERROR dns64 requires a IPv6 prefix The "dns64" configuration option requires an IPv6 prefix.
ERROR bad prefix length [prefix length] The IPv6 prefix has an incorrect length required by the dns64
[32/40/48/56/64/96] configuration option.

ERROR dns64 requires a IPv6 suffix The "dns64" configuration option requires an IPv6 suffix.
ERROR bad suffix '[net address]' leading The IPv6 suffix has an incorrect length for a dns64 configuration
[number] octets not zeros option.

WARNING both "recursion no;" and "[ACL]" active[[ The "allow-recursion" and "allow-recursion-on ACLs" options are
for view ]or[]] [view name] inconsistent with the "recursion" option configuration.

WARNING both \"filter-aaaa-on-v4 [yes];\" and The state of "filter-aaaa-on-v4" option. If "filter-aaaa-on-v4" option
\"filter-aaaa\" is 'none;'[[ for view ]or[]] is set to 'yes', AAAA records are not included in the response if the
[view name], break-dnssec : yes client falls within the filter-aaaa address match list and no DNSSEC
signatures are included. If this option is set to 'no', such filtering is
not performed and AAAA records are returned. If set to 'break-
dnssec', the AAAA records are not included even if DNSSEC
signatures exist.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 57 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

WARNING both \"filter-aaaa-on-v4 no;\" and The state of "filter-aaaa-on-v4" option. If "filter-aaaa-on-v4" option
\"filter-aaaa\" is set[[ for view ]or[]] is set to 'yes', AAAA records are not included in the response if the
[view name] client falls within the filter-aaaa address match list and no DNSSEC
signatures are included. If this option is set to 'no', such filtering is
not performed and AAAA records are returned. If set to 'break-
dnssec', the AAAA records are not included even if DNSSEC
signatures exist.
ERROR [interval name] '[interval value]' is out of The "unit of time" field value is out of range.
range (0..[interval max value])

ERROR [interval name] '[interval value]' is out of The "unit of time" field value is out of range.
range
ERROR Max-rsa-exponent-size '[interval value]' The max-rsa-exponent-size is only applicable to recursive name
is out of range (35..4096) servers (full service resolvers) and allows the user to define the
maximum number of bits in the RSA key when validating RRSIG
RR(s). The number of bits may be in the range 35 to 4096, with the
value 0 (the default) indicating 4096. If any signed zone uses an RSA
algorithm with a key size greater than bits then the zone will not be
validated and the zone's results will be marked "insecure."
ERROR [sig-validity-interval] '[interval value]' is "sig-validity-interval" configuration option value is out of range
out of range (1..3660) (1..3660). Specifies the number of days into the future when DNSSEC
signatures are automatically generated when dynamic updates
expire.
ERROR [sig-validity-interval] '[interval value]' is "sig-validity-interval" configuration option value is out of range
out of range (0..3660), sig-validity- (0..3660). Specifies the number of days into the future when DNSSEC
interval signatures are automatically generated when dynamic updates
expire.
ERROR [sig-validity-interval] '[interval value]' is "sig-validity-interval (re-sign)" configuration option value is out of
out of range (1..3660), sig-validity- range (1..3660).
interval (re-sign)

ERROR validity interval ([number] days) less The value of the validity interval is less than the re-signing interval
than re-signing interval ([re-signing value.
interval] [[days]or[hours]])

ERROR preferred-glue unexpected value '[type]' The value of "preferred-glue" configuration option does not match
any of the following types: "a", "aaaa" or "none". This option defines
the order of preference in which glue records are listed in the
additional section of the response. If not specified, they are listed in
the order they appear in the zone file.
ERROR bad domain name '[DNS name]' Bad domain name is found when checking configuration option
"root-delegation-only".
ERROR bad domain name '[DNS name]' Bad domain name is found when checking configuration option
"dnssec-lookaside"

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 58 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR dnssec-lookaside '[DNS name]': non-root DNSSEC lookaside validation does not yet support non-root usage.
not yet supported

ERROR bad domain name '[DNS name]' Bad domain name is found during DNSSEC lookaside validation.

ERROR dnssec-lookaside requires either 'auto' DNSSEC lookaside validation parameters should be one of the
or 'no', or a domain and trust anchor following: auto', 'no', or a 'domain trust-anchor DLV_domain'.

ERROR auto-dnssec may only be activated at the The auto-dnssec zone statement is set to 'off' and not at the zone
zone level level.

ERROR [server contact]: invalid name '[DNS DNS name is invalid for server contacts.
name]'
ERROR disable-empty-zone: invalid name '[DNS The 'disable-empty-zone' statement contains an invalid DNS name.
name]'

ERROR server-id' too big (>1024 bytes) Length of 'server-id' configuration option exceeds 1024 bytes.
ERROR unexpected token '[configuration The 'masters' statement contains an unexpected token key.
object]'
ERROR unable to find masters list '[master list]' The 'masters list' is missing.

ERROR '[DNS name]' is not a valid name The 'update-policy' configuration option contains an invalid domain
name.
ERROR '[DNS name]' is not a valid name The 'update-policy' configuration option contains an invalid
nametype.
ERROR '[DNS name]' is not a wildcard The 'update-policy' configuration option contains an invalid
wildcard.
ERROR '[record datatype]' is not a valid type The 'update-policy' configuration option contains an invalid DNS
record datatype.
ERROR '[configuration option]' must not be zero the specified configuration option should not be zero.
ERROR zone '[zone]': type not present Verification of zone statements for syntactical correctness and
absence of duplicate zones failed to get configured zone type.
ERROR zone '[zone]': invalid type [type] Verification of zone statements for syntactical correctness and
absence of duplicate zones finds an invalid zone type.
ERROR redirect zones must be called "." Verification of zone statements for syntactical correctness and
absence of duplicate zones finds that redirect zone name does not
contain "." symbol.
ERROR zone '[zone]': invalid class [class] Verification of zone statements for syntactical correctness and
absence of duplicate zones finds an invalid zone class.
ERROR zone '[zone]': class '[zone]' does not Verification of zone statements for syntactical correctness and
match view/default class absence of duplicate zones finds that a zone class does not match
the view/default class.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 59 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR zone '[zone]': is not a valid name Verification of zone statements for syntactical correctness and
absence of duplicate zones finds that a zone name is invalid for the
existing zone.
ERROR option '[option name]' is not allowed in Verification of zone statements for syntactical correctness and
'[type]' zone '[zone name]' absence of duplicate zones finds that configuration options for the
specified zone type is not "allow-update" or the zone type is not
SLAVEZONE.
WARNING option '[option name]' is not allowed in Verification of zone statements for syntactical correctness and
'[type]' zone '[zone name]' absence of duplicate zones finds that indicated option is not allowed
in this particular zone.

ERROR zone '[zone name]': missing 'masters' Verification of zone statements for syntactical correctness and
entry absence of duplicate zones failed to find 'masters' entry is missing.
ERROR zone '[zone name]': empty 'masters' Verification of zone statements for syntactical correctness and
entry absence of duplicate zones finds that 'masters' entry is empty.

ERROR zone '[zone name]': 'allow-update' is Verification of zone statements for syntactical correctness and
ignored when 'update-policy' is present" absence of duplicate zones finds that 'allow-update' configuration
option is ignored because 'update-policy' option is present.

ERROR auto-dnssec [off];' requires[[ dynamic When 'auto-dnssec' option is set to 'off' it requires dynamic DNS or
DNS or]or[]] inline-signing to be 'inline-signing' option to be configured for the master zone or the
configured for the zone slave zone.

ERROR auto-dnssec create;' is not yet Verification of zone statements for syntactical correctness and
implemented absence of duplicate zones finds that 'create' parameter is not yet
implemented for 'auto-dnssec' option.
ERROR sig-signing-type: [type] out of range Configuration value for the 'sig-signing-type' type is out of range
[[0xff00U]..[0xffffU]] [0xff00U..0xffffU].

ERROR dialup type '[dialup type]' is not allowed The 'dialup' configuration option is not allowed for the specified
in '[zone type]' zone '[zone]' zone.

ERROR invalid dialup type '[dialup type]' in zone The 'dialup' configuration option is not allowed for the specified
[zone name] zone.

ERROR port is not configurable for static stub The port value is not configurable for static stub server-addresses.
server-addresses 'server-addresses' statement defines the ip-address(es) (either IPv4
or IPv6) that will be configured as glue RRs using A (IPv4) or AAAA
(IPv6) for the name server either defined by the server-names or in
its absence for a name server at the apex of the static-stub zone.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 60 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR scoped address is not allowed for static Scoped address is not allowed for a static stub server-addresses.
stub server-addresses

ERROR server-name '[server name]' is not a The 'name' parameter is invalid for the 'server-names' statement.
valid name Only used when zone type is static-stub. This defines one or more
dom-name(es) that will be synthesized as the NS RR(a) for the zone.
If no server-addresses are defined, then these names must be out-
of-zone static-stub zone to allow A/AAAA resolution (inside the zone
they would require glue A/AAAA records.)
ERROR server-name '[server name]' must not be The 'name' parameter of the 'server-names' statement should not
a subdomain of zone name '[zone name]' be a subdomain of a zone name.

ERROR zone '[zone name]': missing 'file' entry If the zone type is rbt or rbt64 then master or hint zones require the
'file' clause.
ERROR key '[key name]' must have both 'secret' The key (name indicated) should have both 'secret' and 'algorithm'
and algorithm' defined defined. Check these parameters.

ERROR bad secret '[error message]' The key list contains bad secret.

ERROR unknown algorithm '[algorithm]' The key list contains unknown algorithm defined.
ERROR key '[key name]' digest-bits too large The value of indicated key digest-bits is too large.
[[(algorithm size)/2]..[algorithm size]]

ERROR key '[key name]' digest-bits not multiple The value of indicated key digest-bits is not a multiple of eight.
of 8

WARNING key '[key name]' digest-bits too small The value of indicated key digest-bits is too small.
[<[(algorithm size)/2]]

ERROR key '[key name]': unable to parse digest- Failed to parse digest-bits for the specified key.
bits

ERROR key '[key name]': bad key name The specified key has a bad name.
ERROR key '[key name]': already exists previous Key list verification finds that previous definition of the specified key
definition: [file]:[line] already exists.

ERROR server '[net address]/[prefix]': invalid The server net address has an invalid prefix.
prefix (extra bits specified)

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 61 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR server '[net address]/[prefix]': [xfr] not The specified server is not legal.
legal
ERROR server '[net address]/[prefix]': already Previous definition of a server already exists.
exists previous definition: [file]:[line]

ERROR bad key name '[key name]' The specified key has a bad key name.
ERROR unknown key '[key name]' The specified key is unknown.
WARNING bad key name: [key name] Bad key name is detected when checking a trusted key.

WARNING flags too big: [flags] The trusted key flags value is too big.
WARNING protocol too big: [protocol] The trusted key protocol value is too big.
WARNING algorithm too big: [algorithm] The trusted key algorithm value is too big.
ERROR managed key '[key name]': invalid the specified managed key uses an invalid initialization method.
initialization method '[initialization
method]'
ERROR [error message] The trusted key is invalid.
WARNING [[managed]or[trusted]] key '[key name]' The managed or trusted key has a weak exponent.
has a weak exponent, managed : trusted

WARNING dnssec-validation [validation status];' The dnssec-validation status. It indicates that a resolver (a caching or
and 'dnssec-enable no caching-only name server) attempts to validate replies from DNSSEC
enabled (signed) zones. The dnssec-enable indicates that a secure
DNS service is being used.
ERROR channel '[channal name]': exactly one of Exactly one of the following values: 'file', 'syslog', 'null', or 'stderr'
file, syslog, null, and stderr must be must be present for a channel.
present

ERROR undefined category: '[category name]' An undefined logging category is detected.

ERROR undefined channel: '[channel name]' An undefined logging channel is detected.

ERROR unknown key '[key name]' An unknown key is found when checking controls key.
ERROR unix control '[path]': path too long The unix control path value is too long.

WARNING unix control '[path]' allows access to The specified Unix control allows access to everyone.
everyone

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 62 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

WARNING unix control '[path]' allows access to The specified control does not allow access to anyone.
nobody

ERROR when using 'view' statements, all zones When using 'view' statements, all zones must be assigned views in
must be in views named configuration.
ERROR view '[view]': invalid class [class] The specified view has an invalid class defined.

ERROR view '[view]': already exists previous Verification of the named configuration finds that a view is already
definition: [file]:[line] exists in previous definition.

ERROR attempt to redefine builtin view '[view]' An attempt to redefine built-in view when verifying the named
configuration.

ERROR cache-file' cannot be a global option if The 'cache-file' option cannot be set to global if views are present.
views are present
ERROR attempt to redefine builtin acl '[acl An attempt to redefine built-in ACL when verifying the named
name]' configuration.

ERROR attempt to redefine acl '[acl name]' An attempt to redefine previous definition of an ACL when verifying
previous definition: [file]:[line] the named configuration.

ERROR attempt to redefine kal '[name]' previous An attempt to redefine previous definition of an kal when verifying
definition: [file]:[line] the named configuration.

N/A acache [acache] stats: hits=[number] acache statistics are displayed while cleaning the acache.
misses=[number] queries=[number]
adds=[number] deleted=[number]
cleaned=[number]
cleaner_runs=[number]
overmem=[number]
overmem_nocreates=[number]
nomem=[number]

N/A acache is still in overmem state after The acache is still in the overmen state after the cleanup.
cleaning

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 63 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

WARNING could not set acache cleaning interval: Cannot set an acache cleaning interval.
[warning message]

N/A acache [acache] cleaning interval set to The acache cleaning interval is set to the specified value.
[value]

N/A Access Control List: start of output The start of Access Control List output.
N/A IP Table start: ACL, start of the IP Table.
N/A IP Table size is [size] elements ACL, count of elements of IP Table.
N/A [IP address], [[positive]or[negative]], ACL, radix tree node number.
Node num: [node number]

N/A IP Table end ACL, end of the IP Table .

N/A Number of elements: [number] ACL, count of elements value.
N/A Element [element number]: ACL, element.
N/A Node num: [node number] ACL, node element number.
N/A Status: [[negative]or[positive]] ACL, status(negative or positive) element.

N/A Element type: ipprefix ACL, element type: ipprefix.

N/A Name: [key name] ACL, element name for a type: ipprefix .
N/A Element type: Key ACL, element type: key .
N/A Name: [key name] ACL, element name for a type: key .
N/A Element type: nested ACL ACL, element type: nested ACL,.
N/A Details ACL, element details for a type: nested ACL,.
N/A Element type: Local host ACL, element type: Local host.
N/A Name: [key name] ACL, element name for a type: Local host .
N/A Element type: Local networks ACL, element type:Local networks .
N/A Name: [key name] ACL, element name for a type: Local networks.
N/A Element type: Any\n ACL, element type: Any.
N/A Name: [key name] ACL, element name for a type: Any.
N/A Element type: UNKNOWN\n ACL, element type: UNKNOWN.
N/A Access Control List: end of output\n The end of Access Control List output.
WARNING error dumping cache: [error message] Cannot dump the cache to a file when the cache shuts down.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 64 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

WARNING could not set cache cleaning interval: Cannot set the cache cleaning interval.
[warning message]

WARNING cache cleaner could not create iterator: Cannot create the cache cleaner iterator.
[warning message]

ERROR unsupported database type '[db type]' Cannot create a new database using implementation 'db_type'
parameter value.

WARNING '[DNS name]/[record data type]/[record The TTL value in record dataset differs from a record data list TTL
data class]': TTL differs in rdataset, value. TTL value is adjusted to match the data list TTL value.
adjusting [ttl]->[ttl]

WARNING resign requested with 0 resign interval The merge of the record dataset into the database is successful.
Resign parameter of diff object is set to 0.

WARNING [DNS name]/[record data class]: The incremental database update failed.
dns_diff_apply: update with no effect

WARNING dns_diff_load: update with no effect The loading of an incremental database update failed.

N/A dispatchmgr [manager]: [message] Information regarding dispatch manager and a message.

N/A dispatch [dispatch]: [message] Information regarding DNS dispatch and a message.

N/A dispatch [dispatch] response [response] Information regarding DNS dispatch, response and accompanying
[socket address]: [message] message.

N/A dispatch dispatch req/resp Information regarding DNS dispatch, request/response and message
[[request]or[response]]: [message] into log.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 65 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

N/A shutting down; detaching from sock Named destroyed a DNS dispatch and detaches from a socket. Task
[socket], task [task] is indicated.

WARNING open_socket([socket]) -> [warning Named is picking up a random UDP port and tries to open a new
message]: continuing socket with it. Socket is not open yet.

N/A got packet: requests [number], buffers Description of the packet received from the UDP socket.
[number], recvs [number]

ERROR odd socket result in udp_recv(): [error The udp_recv() function generates odd socket result (indicated).
message]

N/A blackholed packet from [net address] The blackholed packet is received from the specified net address.

N/A got garbage packet A garbage packet is received.

N/A got valid DNS message header, /QR The received DNS message header is valid.
[[1]or[0]], id [id]

N/A search for response in bucket [bucket]: Search result for response in the specified bucket: found or not
[[not found]or[found]] found.

N/A response to an exclusive socket doesn't The corresponding response to an exclusive socket does not match.
match
N/A [a] Sent event [event] buffer [buffer] len Description of the response sent to the UDP socket.
[buffer length] to task [task]

N/A got TCP packet: requests [requests], Description of the packet received from the TCP socket.
buffers [tcp buffers], recvs [receive
pending]

N/A shutting down on EOF Named is shutting down on EOF.

ERROR receive error: [socket address]: [error Named is shutting down due to the specified TCP receive error.
message]
N/A result [result], length == [address TCP message description: result, length, address.
length], addr = [address]

N/A got garbage packet A garbage packet is received.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 66 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

N/A got valid DNS message header, /QR The received DNS message header is valid.
[[1]or[0]], id [id]

N/A search for response in bucket [bucket]: Search result for response in the specified bucket: found or not
[[not found]or[found]] found.

N/A [b] Sent event [event] buffer [buffer] len Description of the response sent to the TCP socket.
[buffer length] to task [task]

N/A destroy_mgr_ok: Named destroyed a dispatch manager.

shuttingdown=[number],
listnonempty=[number],
epool=[number], rpool=[number],
dpool=[number]

N/A destroy: killit=[killit] Named destroyed a dispatch manager.

N/A created TCP dispatcher [dispatcher] TCP dispatcher is created.
N/A created task [task] Task for TCP dispatcher is created.
ERROR avoid-v[[4]or[6]]-udp-ports: unable to The avoid-v4[v6]-udp-ports statement defines a list of port numbers
allocate an available port that will not be used by BIND when initiating queries. This list may
be used to avoid ports that are blocked by a firewall. This option can
be defined in the global options clause only.

N/A UDP dispatch for [address] with socket fd UDP dispatch is created for the specified address and socket fd.
[socket fd]

N/A created UDP dispatcher [dispatche] UDP dispatcher is created.

N/A created task [task] Task for UDP dispatcher is created.
N/A created socket [socket] Socket for UDP dispatcher is created.
N/A detach: refcount [reference count] The references count to DNS dispatch while detaching.
N/A attached to task [task] Response attached to the specified task.
N/A starttcp [task] TCP dispatch starts.
N/A detaching from task [task] Response is detaching from a task.
N/A cancel: failsafe event [event] -> task The shutdown failesafe event is sent for this response.
[task]

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 67 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

INFO Loading '[dlz name]' using driver [driver Loading Dynamically Loadable Zones (DLZ) using the specified driver
name] .

ERROR unsupported DLZ database driver '[driver Unsupported DLZ database driver. DLZ is not loaded.
name]'. [dlz name] not loaded.

ERROR DLZ driver failed to load. The DLZ driver failed to load.

INFO No ssumatch method for DLZ database There is no ssumatch method available for a DLZ database.

INFO sucessfully validated after lower casing DNSSEC is successfully validated after the lower casing signer.
signer '[DNS name]'

WARNING dns_dnssec_findzonekeys2: error The dns_dnssec_findzonekeys2() function. Cannot read the specified
reading private key file [DNS private key file.
name]/[algorithm]/[key id]: [warning
message]

WARNING dns_dnssec_findmatchingkeys: error The dns_dnssec_findmatchingkeys() function. Cannot read the

reading key file [directory name]: [error specified private key file.
message]

WARNING dns_dnssec_keylistfromrdataset: error The dns_dnssec_keylistfromrdataset() function. Cannot read the

reading private key file [DNS specified private key file.
name]/[algorithm]/[key id]: [warning
message]

INFO GSS-TSIG key created: [DNS name] The GSS-TSIG key is created.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 68 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

INFO GSS-TSIG key created The GSS-TSIG key is created.

WARNING Permissions on the file [filename] have Permissions for the specified file is changed.
changed from 0[mode] to 0600 as a
result of this operation.

ERROR failed gss_inquire_cred: [error message] The status of a GSS credential. Return
value:GSS_S_CREDENTIALS_EXPIRED – the credentials have expired.
Credential information is still returned for an expired credential, but
the lifetime value is returned as zero.
GSS_S_DEFECTIVE_CREDENTIAL – the credentials are not valid.
GSS_S_FAILURE – the routine failed for reasons that are not defined
at the GSS level. The minor_status return parameter contains a
mechanism-dependent error code describing the reason for the
failure. GSS_S_NO_CRED -– the cred_handle parameter does not
refer to a valid credential or there are no default credentials
available.
ERROR failed gss_display_name: [error The textual representation of an opaque internal name. The return
message] value is one of the following status codes: SS_S_BAD_NAME – the
provided name is invalid. GSS_S_BAD_NAMETYPE – the internal
name provided does not have an internal representation for any of
the supported mechanisms. GSS_S_COMPLETE – the routine
completed successfully. GSS_S_FAILURE – the routine failed for
reasons that are not defined at the GSS level. The minor_status
return parameter contains a mechanism-dependent error code
describing the reason for the failure.
N/A gss cred: "[GSS name]", [usage option], The information about a GSS credential.
[lifetime]
ERROR failed gss_release_buffer: [error The gss_release_buffer() function releases storage associated with a
message] gss_buffer_t buffer. The routine failed for reasons that are not
defined at the GSS level.
ERROR failed gss_release_name: [error The gss_release_name() function releases storage associated with a
message] gss_name_t internal name. The return value is one of the following
status codes: GSS_S_BAD_NAME – the specified name is invalid.
GSS_S_COMPLETE – the routine completed successfully.
GSS_S_FAILURE – the routine failed for reasons that are not defined
at the GSS level. The minor_status return parameter contains a
mechanism-dependent error code describing the reason for the
failure.
ERROR tkey-gssapi-credential ([GSS name]) The tkey-gssapi-credential doesn't start with "DNS/".
should start with 'DNS'

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 69 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR Unable to initialise krb5 context The krb5_init_context() function creates a new Kerberos context
and initializes it with default values obtained from the Kerberos
configuration file. Each application needs at least one Kerberos
context. A context may be shared by multiple threads within the
same process. Use the krb5_free_context() routine to release the
context when it is no longer needed. If no errors occur, the return
value is 0. Otherwise, a Kerberos error code is returned.
ERROR Unable to get krb5 default realm The krb5_get_default_realm() function returns the default realm for
the local system. The default realm is set by the
krb5_set_default_realm() routine. If the default realm has not been
set, it is obtained from the default_realm entry in the [libdefaults]
section of the Kerberos configuration file. If no errors occur, the
return value is 0. Otherwise, a Kerberos error code is returned.
ERROR tkey-gssapi-credentials ([GSS name]) The tkey-gssapi-credentials are badly formatted.
ERROR default realm from krb5.conf ([realm]) The default realm in /etc/krb5.conf and the tkey-gssapi-credential
does not match tkey-gssapi-credential bind config option don't match.
([GSS name])

ERROR failed gss_import_name: [error message] The gss_import_name() function converts a printable name to the
GSS internal format. The return value is one of the following status
codes: GSS_S_BAD_NAME – the input name is not formatted
properly or is invalid. GSS_S_BAD_NAMETYPE – the name type
specified by the input_name_type parameter is invalid.
GSS_S_COMPLETE – the routine completed successfully.
GSS_S_FAILURE – the routine failed for reasons that are not defined
at the GSS level. The minor_status return parameter contains a
mechanism-dependent error code describing the reason for the
failure.
N/A acquiring credentials for %s Acquiring credentials for tkey-gssapi-credential.
N/A acquiring credentials for ? Acquiring credentials for tkey-gssapi-credential = NULL
ERROR failed to acquire [[initiate]or[accept]] Cannot acquire initiate or accept credentials for tkey-gssapi-
credentials for [[GSS name]or[?]]: [error credential.
message]

N/A Acquired [[initiate]or[accept]] Acquired 'initiate' or 'accept' credentials for tkey-gssapi-credential.

credentials for [[GSS name]or[?]]

ERROR failed releasing credential: [error Cannot release a credential.

message]

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 70 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

N/A Failure initiating security context: [error The gss_init_sec_context() function initiates a security context for
message] use by two communicating applications. The return value is one of
the following status codes: GSS_S_COMPLETE – The routine
completed successfully. GSS_S_FAILURE – the routine failed for
reasons that are not defined at the GSS level. The minor_status
return parameter contains a mechanism-dependent error code
describing the reason for the failure. GSS_S_BAD_BINDINGS – the
channel bindings are not valid. GSS_S_BAD_MECH – the request
security mechanism is not supported. GSS_S_BAD_NAME – the
target_name parameter is invalid. GSS_S_BAD_SIG – the input token
contains an incorrect integrity check value.
GSS_S_CONTINUE_NEEDED – to complete the context, the
gss_init_sec_context() routine must be called again with a token
created by the gss_accept_sec_context() routine.
GSS_S_CREDENTIALS_EXPIRED – the supplied credentials are no
longer valid. GSS_S_DEFECTIVE_CREDENTIAL – consistency checks
performed on the credential failed. GSS_S_DEFECTIVE_TOKEN –
consistency checks performed on the input token failed.
GSS_S_DUPLICATE_TOKEN – the token is a duplicate of a token that
has already been processed. GSS_S_NO_CONTEXT – the context
handle provided by the caller does not refer to a valid security
context. GSS_S_NO_CRED – the supplied credential handle does not
refer to a valid credential, the supplied credential is invalid for
context initiation, or there are no default credentials available.
GSS_S_OLD_TOKEN – the token is too old to be checked for
duplication against previous tokens which have already been
processed.
ERROR failed GSS Kerberos5. Registration of an acceptor failed for the specified
gsskrb5_register_acceptor_identity([gssa reason.
pi_keytab]): [error message]

INFO [client]: GSS-TSIG authentication failed: NTLM negotiation is not supported and the mechanism may block
NTLM negotiation not supported while attempting to resolve services for an NTLMSSP_NEGOTIATE
request.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 71 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR failed gss_accept_sec_context: [error The gss_accept_sec_context() function accepts a security context
message] created by the context initiator. The return value is one of the
following status codes: GSS_S_BAD_BINDINGS – the input_token
parameter contains different channel bindings from those specified
with the input_chan_bindings parameter. GSS_S_BAD_MECH – the
security mechanism used by the context initiator is not available on
the acceptor system. GSS_S_BAD_SIG – the received input token
contains an incorrect signature. GSS_S_COMPLETE – the routine
completed successfully. GSS_S_CONTINUE_NEEDED – control
information in the returned output token must be sent to the
initiator and a response must be received and passed as the
input_token argument to a continuation call to the
gss_accept_sec_context() routine. GSS_S_CREDENTIALS_EXPIRED –
credentials are no longer valid. GSS_S_DEFECTIVE_CREDENTIAL –
consistency checks performed on the credential structure
referenced by the verifier_cred_handle parameter failed.
GSS_S_DEFECTIVE_TOKEN – consistency checks performed on the
input token failed. GSS_S_DUPLICATE_TOKEN – the token is a
duplicate of a token that already has been processed. This is a fatal
error during context establishment. GSS_S_FAILURE – the routine
failed for reasons that are not defined at the GSS level. The
minor_status return parameter contains a mechanism-dependent
error code describing the reason for the failure.
GSS_S_NO_CONTEXT – the context identifier provided by the caller
does not refer to a valid security context. GSS_S_NO_CRED – No
credentials are available or the credentials are valid for context
initiation use only. GSS_S_OLD_TOKEN – the token is too old to be
checked for duplication against previous tokens. This is a fatal error
during context establishment.
ERROR failed gss_display_name: [error The gss_display_name() function returns the textual representation
message] of an opaque internal name. The return value is one of the following
status codes: SS_S_BAD_NAME – the provided name is invalid.
GSS_S_BAD_NAMETYPE – the internal name provided does not have
an internal representation for any of the supported mechanisms.
GSS_S_COMPLETE – the routine completed successfully.
GSS_S_FAILURE – the routine failed for reasons that are not defined
at the GSS level. The minor_status return parameter contains a
mechanism-dependent error code describing the reason for the
failure.
N/A gss-api source name (accept) is [GSS The gss-api source name (accept) is a Kerberos principal name.
name]
N/A gss-api converted source name (accept) The gss-api source name (accept) is a DNS name.
is [GSS name]

ERROR failed gss_release_buffer: [error The gss_release_buffer() function releases storage associated with a
message] gss_buffer_t buffer. The routine failed for reasons that are not
defined at the GSS level.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 72 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR failed gss_release_name: [error The gss_release_name() function releases storage associated with a
message] gss_name_t internal name. The return value is one of the following
status codes: GSS_S_BAD_NAME – the specified name is invalid.
GSS_S_COMPLETE – the routine completed successfully.
GSS_S_FAILURE – the routine failed for reasons that are not defined
at the GSS level. The minor_status return parameter contains a
mechanism-dependent error code describing the reason for the
failure.
ERROR Failure deleting security context [error Cannot delete the context from the GSS provider
message]
ERROR [error message]: GSS-TSIG failure. Check The GSS-TSIG failure. Please check configuration and clock
configuration and clock synchronization. synchronization.

ERROR GSS sign error: [error message] The gss_get_mic() function generates a cryptographic signature for a
message and returns this signature in a token that can be sent to a
partner application. The partner application then calls the
gss_verify_mic() routine to validate the signature. The return value
is one of the following status codes: GSS_S_BAD_QOP – the
requested quality of protection value is invalid. GSS_S_COMPLETE –
the routine completed successfully. GSS_S_CONTEXT_EXPIRED – the
referenced context has expired. GSS_S_CREDENTIALS_EXPIRED – the
credentials associated with the referenced context have expired.
GSS_S_FAILURE – the routine failed for reasons that are not defined
at the GSS level. The minor_status return parameter contains a
mechanism-dependent error code describing the reason for the
failure. GSS_S_NO_CONTEXT – the context identifier provided by the
caller does not refer to a valid security context.
ERROR GSS verify error: [error message] The gss_verify_mic() function verifies that the cryptographic
signature for a message is correct. This ensures that the message
has not been modified since the signature was generated. The
return value is one of the following status codes: GSS_S_BAD_SIG –
the input token contains an incorrect signature. GSS_S_COMPLETE –
the routine completed successfully. GSS_S_CONTEXT_EXPIRED – the
context identifier provided by the caller has expired.
GSS_S_CREDENTIALS_EXPIRED – the credentials associated with the
referenced context have expired. GSS_S_DEFECTIVE_CREDENTIAL –
the credential is defective. GSS_S_DEFECTIVE_TOKEN – consistency
checks performed on the input token failed.
GSS_S_DUPLICATE_TOKEN – the token is a duplicate of a token that
has already been processed. GSS_S_FAILURE – the routine failed for
reasons that are not defined at the GSS level. The minor_status
return parameter contains a mechanism-dependent error code
describing the reason for the failure. GSS_S_GAP_TOKEN – One or
more predecessor tokens have not been processed.
GSS_S_NO_CONTEXT – the context identifier provided by the caller
does not refer to a valid security context. GSS_S_OLD_TOKEN – the

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 73 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

token is too old to be checked for duplication against previous
tokens. This is a fatal error during context establishment.

INFO GSS-TSIG key destroyed: [DNS name] The GSS-TSIG key is destroyed: DNS name is converted to a string.

INFO GSS-TSIG key destroyed The GSS-TSIG key is destroyed: DNS name cannot be converted to a
string.

ERROR Failed to write GSS-TSIG counters: [error Cannot write GSS-TSIG counters.
message]

INFO GSS-TSIG accept stats: [accept ok] ok, The GSS-TSIG counters accept the specified statistics values.
[accept fail] failed ([accept fail ntlmssp]
NTLM, [accept fail no principal] principal,
[accept fail no crypto] key,
[accept_fail_integrity] integrity, [accept
fail time] time

INFO GSS-TSIG verify stats: [ok] ok, [fail] failed The GSS-TSIG counters verify statistics values.
([integrity] integrity, [time] time

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 74 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

N/A [client]: GSS-TSIG [message] The content of gssd end reporting message.

WARNING [file]:[line]: FOR TESTING ONLY (server: This message is for testing purposes only.
[server], value: [value])

N/A view [view name]: [message] View log module.

ERROR failed to allocate master selection Cannot allocate master selection cleanup event, cleanup is skipped.
cleanup event, skipping cleanup

ERROR failed to close master selection file on Cannot close master selection file on shutdown.
shutdown: [error message]

ERROR could not construct master selection file Cannot construct a master selection file name.
name: [error message]

ERROR could not create master selection Cannot create a master selection directory.
directory: [error message]

ERROR could not open master selection Cannot open a master selection directory.
directory: [error message]

ERROR could not close master selection file: Cannot close a master selection file.
[error message]

ERROR isc_file_mktemplate() failed while doing The isc_file_mktemplate() function failed while doing master
master selection file cleanup: [error selection file cleanup.
message]

ERROR failed to create temporary file for master Cannot create temporary file for a master selection file cleanup.
selection file cleanup: [error message]

ERROR failed to determine zone name while Cannot determine zone name while cleaning up master selection
cleaning up master selection file: [error file.
message]
ERROR failed to write to master selection file Cannot write to a master selection file after a cleanup.
after cleanup: [error message]

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 75 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR could not close temporary file while Temporary file cannot be closed while doing master selection file
doing master selection file cleanup: cleanup.
[error message]

WARNING failed to close master selection file for Cannot close master selection file for minimization.
minimization: [warning message]

ERROR could not replace old master selection The old master selection file cannot be replaces with the new one.
file with new one: [error message]

ERROR could not open master selection file: Cannot open the master selection file.
[error message]

ERROR failed to append newline to possibly Cannot append a newline to possibly truncated master selection file.
truncated master selection file: [error
message]

WARNING failed to minimize master selection file: Cannot minimize a master selection file.
[warning message]

ERROR failed to format master selection string Cannot format master selection string while writing master switch to
while writing master switch to [address] master address for a zone.
for zone [zone]: [error message]

ERROR failed to write master switch to master Cannot write master switch to a master selection file.
selection file: [master selection]: [error
message]
WARNING too long record found in master The record found in master selection file appears to be too long.
selection file
WARNING no newline at the end of master There is no newline at the end of a master selection record.
selection record: [master selection]
WARNING failed to parse master selection record: Cannot parse a master selection record.
[master selection]

WARNING failed to initialize zone name [zone Cannot initialize a zone name.
name]: [warning message]

WARNING failed while searching for zone [zone] for Failure while searching for the specified zone for master selection
master selection persistency: [warning persistency.
message]

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 76 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

WARNING failed to recognize master [IP address] Cannot recognize master for a master selection persistency.
for master selection persistency

WARNING failed to associate master [IP address] Cannot associate master with the database based on persistent
with database based on persistent data: data.
[warning message]

WARNING failed to associate master [IP address] Cannot associate master with last selection registration based on a
with last selection registration based on persistent data.
persistent data: [warning message]

WARNING failed to set master [IP address] as Cannot set master as a current based on persistent data.
current based on persistent data:
[warning message]

ERROR could not close master selection file: Cannot close master selection file.
[error message]

ERROR could not load master selection data Cannot load master selection data from a file.
from file: [error message]

ERROR failed to reopen/recreate master Cannot reopen or recreate a master selection file for a zone.
selection

ERROR failed to close master selection on Cannot close master selection on disable.
disable: [error message]

WARNING delete_node: dns_rbt_findnode(nsec): Cannot find the node while deleting the corresponding node from
[warning message] the auxiliary NSEC tree before deleting it from the main tree.

WARNING elete_nsecnode(): The dns_rbt_deletenode() function failure while deleting the

dns_rbt_deletenode(nsecnode): corresponding node from the auxiliary NSEC tree before deleting it
[warning message] from the main tree.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 77 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

WARNING delete_nsecnode(): dns_rbt_deletenode: Cannot delete the corresponding node from the auxiliary NSEC tree
[warning message] before deleting it from the main tree.

INFO decrement_reference: failed to allocate The decrement_reference() function failed to allocate pruning
pruning event event. You can ignore this error case, but then the stale node will
unlikely be purged except via a rare condition such as manual
cleanup.

ERROR previous_closest_nsec(): [error message] There should always be a node in the main tree with the same name
as the node in the auxiliary NSEC tree, except for nodes in the
auxiliary tree that are awaiting deletion.

ERROR rpz_findips findnode([DNS name]) failed: Cannot find the node corresponding to CDIR tree entry.
[error message]

INFO disabled rpz [type] [policy] rewrite [DNS When RPZ Policy is disabled, the query is still being processed and
name] via [DNS name] result that includes information about what address could be
overwritten is logged. The policy in a log message is declared as
applied but the response is returned to a user without applying
policy rules because it is disabled.

N/A overmem cache: [[FORCE]or[check]] The debug message for a cache. Check the specified node.
[node name]

N/A overmem cache: stale [node name] This is debug message. the specified node is stale.

N/A overmem cache: reprieve by RETAIN() This is debug message. the specified node is reprieved.
[node name]

N/A overmem cache: saved [node name] This is debug message. the specified node is saved.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 78 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

WARNING addnode: NSEC node already exists The NSEC node already exists.

WARNING loading_addrdataset: If a node cannot be added to a tree, it is deleted and the reason of
dns_rbt_deletenode: [NSEC result] after this error is the specified.
dns_rbt_addnode(NSEC): [node result]

ERROR Unable to determine MNAME for active Cannot determine MNAME for active master.
master.
WARNING Active master's MNAME has changed. Active master's MNAME is changed. Zone will be reloaded.
Zone will be reloaded.
ERROR ZRQ saw SOA whose name is not the Zone Replication Queue saws SOA which name is not the original.
origin.
ERROR ZRQ metadata conversion failed for [ZRQ Zone Replication Queue metadata conversion from s string failed
metadata]: '[convertion data]' due to the specified reason.

ERROR RQ data conversion failed for [ZRQ data] Zone Replication Queue metadata conversion from s string failed.
'[conversion data]'
ERROR ZRQ has no RDATA to apply for [ZRQ Zone Replication Queue has no RDATA.
data] '[data]'
ERROR ZRQ failed to determine TTL for add: Zone Replication Queue failed to determine TTL for "add record"
[error message] operation.
ERROR ZRQ failed to determine TTL for delete: Zone Replication Queue failed to determine TTL for "delete record"
%s operation.
ERROR Failed to update SOA MNAME to match Cannot update SOA MNAME to match the active master.
active master: [error message]

ERROR ZRQ failed to apply ZRQ update to zone: Zone Replication Queue (ZRQ) failed to apply ZRQ update to a zone.
[error message]
INFO ZRQ applying RESET for zone. Zone Replication Queue applies RESET for a zone.
INFO ZRQ applying [type] for zone. Both COMMAND/DELETE and COMMAND/DISABLE mark the zone as
read-only and it stops accepting updates. A read-only zone can be
restored by a subsequent RESET or reload. Logically, this can only
occur for a disabled zone as a deleted zone will not exist to
reset/reload. But we treat DELETE/DISABLE as equivalent in BIND,
distinguishing them only for clearer logging.
ERROR ZRQ saw unexpected COMMAND type Zone Replication Queue saw the specified unexpected COMMAND
'[type]' type.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 79 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

WARNING ZRQ ignoring invalid type '[type]' Zone Replication Queue ignoring the specified invalid COMMAND
type.
ERROR ZRQ operation '[operation]' is unknown. Zone Replication Queue operation is unknown.
ERROR ZRQ failed to apply [[ADD] or[DELETE]] Zone Replication Queue failed to apply "ADD" or "DELETE" for
for '[reverse name(]': [ttl] IN [command reverse name.
type] [data] ([[meta]or[none]])
INFO ZRQ applied to apply [[ADD] or[DELETE]] Zone Replication Queue applies "ADD" or "DELETE" for revers name.
for '[reverse name(]': [ttl] IN [command
type] [data] ([[meta]or[none]])
ERROR Zone serial ([old SOA serial]) can not be Zone serial cannot be incremented to Zone Replication Queue
incremented to ZRQ transaction serial transaction serial. Zone will be reloaded.
([new SOA serial]). Zone will be reloaded.

WARNING Mismatch between updated SOA serial Mismatch between updated SOA serial and transaction SOA serial.
([new SOA serial]) and transaction SOA Transaction SOA serial ignored.
serial ([SOA serial]). Transaction SOA
serial ignored.

WARNING ZRQ transaction did not include SOA Zone Replication Queue transaction did not include SOA serial
serial update. Zone is signed and will be update. Zone is signed and will be reloaded.
reloaded.
WARNING ZRQ transaction did not include SOA Zone Replication Queue transaction did not include SOA serial
serial update. Incrementing serial. update. Incrementing serial.

INFO ZRQ ignored transaction [transaction id]. Zone Replication Queue ignored transaction. The zone was already
The zone was already read-only and was read-only and was not changed.
not changed."
WARNING ZRQ updating zone without a journal. ZRQ updates zone without a journal.
INFO ZRQ applied transaction [transaction ID] Zone Replication Queue applies transaction with an SOA serial. New
with SOA serial [SOA serial]. Zone version zone version is displayed.
is now [version]"PRIu64".

INFO ZRQ applied transaction [transaction id]. Zone Replication Queue applies transaction. New zone version is
Zone version is now [version]"PRIu64". displayed.

INFO Saw ZRQ command to reload all zones. Saw Zone Replication Queue command to reload all zones.

INFO ZRQ processing suspended until zone has Zone Replication Queue processing suspended until zone is loaded.
loaded.
ERROR Cannot obtain zonedb: [error message] Cannot obtain zonedb.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 80 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR ZRQ transaction unusable: zone ID ([zone Zone Replication Queue transaction unusable: zone ID in transaction
id]"PRIu64") in transaction does not does not match the zone ID being served by named. Reload
match the zone ID ([zone id]"PRIu64") required.
being served by named. Reload required

INFO ZRQ applying transaction [transaction Zone Replication Queue applies RESET transaction for disabled zone.
id]: RESET for disabled zone.
INFO ZRQ ignored transaction [transactionid] Zone Replication Queue ignores transaction for disabled zone.
for disabled zone.
INFO version ([zone version]"PRIu64") is not Zone Replication Queue transaction ignored because the transaction
more recent than the zone version version is not more recent than the zone version.
([zone version]"PRIu64").

INFO Transaction zone version ([zone Transaction zone version is more recent than the current zone
version]"PRIu64) is more recent than version.
current zone version ([zone
version]"PRIu64").

ERROR Transaction zone version ([zone Transaction zone version does not follow current zone version.
version]"PRIu64) does not follow current
zone version ([zone version]"PRIu64")

INFO ZRQ applying transaction [transaction id] Zone Replication Queue applies each item in the transaction in
sequence.
ERROR ZRQ transaction [transaction id] failed to Zone Replication Queue failed to apply each item in the transaction
apply: [error message] in sequence.

INFO Starting reload for all zones. Starting reload for all zones.

INFO There is a pending ZRQ RESET. All zones There is a pending Zone Replication Queue RESET. All zones will be
will be redumped. redumped.

INFO ached zone invalidated: view Cached zone invalidated: view configuration has changed.
configuration has changed.
INFO Cached zone invalidated: not previously Cached zone invalidated: not previously a zone of interest.
a zone of interest.
WARNING Cached zone invalidated: no longer Cached zone invalidated: no longer disabled.
disabled.
WARNING Cached zone invalidated: validation Cached zone invalidated: validation cache not loaded.
cache not loaded.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 81 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

WARNING Cached zone invalidated: cannot obtain Cached zone invalidated: cannot obtain zone version/ID.
zone version/ID.
INFO Cached zone invalidated: not a zone of Cached zone invalidated: not a zone of interest.
interest.
ERROR Cached zone invalidated: zone version Cached zone invalidated: zone version not found.
not found.
ERROR Cached zone invalidated: zone ID not Cached zone invalidated: zone ID not found.
found.
INFO Cached zone invalidated: DB zone Cached zone invalidated: DB zone version is not the same as cached
version ([version]) is not the same as zone version.
cached zone version ([version]).

INFO Cached zone invalidated: DB zone ID Cached zone invalidated: DB zone ID is not the same as cached zone
([version]) is not the same as cached ID.
zone ID ([version]).

INFO Cached zone invalidated: zone version in Cached zone invalidated: zone version in Zone Replication Queue
ZRQ transaction ([version]) does not transaction does not follow zone version in cached zone.
follow zone version in cached zone
([version]).

INFO Cached zone invalidated: ZRQ RESET Cached zone invalidated: Zone Replication Queue RESET found for
found for zone. zone.
ERROR Zone version mismatch ([zone Zone version mismatch. Reloading zone.
version]"PRIu64" != [zone
version]"PRIu64"). Reloading zone.
ERROR [filename]: seek: [error message] Cannot find a journal file.

ERROR [filename]: read: [error message] Cannot read from a journal file.

ERROR [filename]: write: [error message] Cannot write into a journal file.

ERROR [filename]: flush: [error message] Cannot make a flush operation for a journal file

ERROR [filename]: fsync: [error message] Cannot make a fsync operation for a journal file.

ERROR [filename]: create: [error message] Cannot open a journal file.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 82 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR [filename]: write: [error message] Cannot write into a journal file.

ERROR [filename]: close: [error message] Cannot close a journal file.

ERROR [filename]: open: [error message] Cannot open a journal file.

ERROR [filename]: journal format not The journal format is not recognized.
recognized

ERROR [filename]: journal file corrupt: expected Serial number of journal file is corrupt.
serial [serial], got [serial] -------------------
OR --------------------------
(journal_next)[filename]: journal file
corrupt:
expected serial [serial], got [serial]

ERROR [filename]: offset too large An wraparound offset value is too large for a journal.

ERROR [filename]: malformed transaction: [SOA Сonsistency check issue. Malformed transaction for a journal related
serial number] SOAs to SOA.

ERROR [filename]: malformed transaction: serial Сonsistency check issue. Malformed transaction for a journal: serial
number would decrease number would decrease.

ERROR malformed transaction: [filename] last Сonsistency check issue. Malformed transaction for a journal: last
serial [serial] != transaction first serial serial is not equal to the transaction first serial.
[serial]

INFO (informational) Gap in journal [filename] There is a gap in the journal: last serial is not equal transaction first
(last serial [serial] != transaction first serial. The serial will be reset.
serial [serial]), which will be reset.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 83 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR [filename]: journal file corrupt: missing The journal file is corrupt: the initial SOA is missing.
initial SOA

ERROR journal open failure: [error message]: Journal open failure.

[filename]

ERROR [filename]: journal file corrupt: missing The journal file is corrupt: missing initial SOA.
initial SOA

ERROR [filename]: cannot print: journal file The journal cannot be printed: journal file is corrupt.
corrupt

ERROR [filename]: journal corrupt: empty The journal is corrupt: empty transaction.
transaction

ERROR [filename]: journal file corrupt: expected The journal file is corrupt: received serial number does not match an
serial [serial], got [serial] ------------------- expected value.
OR --------------------------
(read_one_rr)[filename]: journal file
corrupt:
expected serial [serial], got [serial]

ERROR [filename]: journal corrupt: impossible The journal file is corrupt: incorrect Resource Record size is
RR size ([number] bytes) encountered.

ERROR dumping to master file: [filename]: flush: Dumping to a master file failed due to a flush operation.
[error message]

ERROR dumping to stream: flush: [error Dumping to a stream failed due to a flush operation.
message]

ERROR dumping to master file: [filename]: Dumping to a master file failed due to a fsync operation.
fsync: [error message]

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 84 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR dumping to stream: fsync: [error Dumping to a stream failed due to a fsync operation.
message]

ERROR dumping master file: [filename]: fclose: Dumping to a master file failed due to a fcloce operation.
[error message]

ERROR dumping master file: rename: [filename]: Dumping to a master file failed due to a rename operation.
[error message]

INFO dumping master file in raw format: Dumping a master file in raw format failed because isc_stdtime_t
stdtime is not 32bits datatype is not a 32-bit integer.

ERROR dumping master file: [filename]: open: Dumping to a master file failed because of open file operation.
[error message]

ERROR dumping node to file: [filename]: open: Dumping a node to file failed because of open file operation.
[error message]

ERROR dumping master file: [filename]: dump: Dumping to a master file failed because of dump file operation.
[error message]

ERROR dumping master file: [filename]: close: Dumping to a master file failed because of close file operation.
[error message]

WARNING [function name] failed Failure of an the specified function.

INFO [error message]:[file]:[Line in file]:[data Detailed information about the error: error message, file, line in file,
in line] data in line.

WARNING delete_node: dns_rbt_findnode(nsec): Cannot find the corresponding node from the auxiliary NSEC tree
[warning message] before deleting it from the main tree.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 85 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

WARNING delete_nsecnode(): The corresponding node found in the auxiliary NSEC tree before
dns_rbt_deletenode(nsecnode): deleting it from the main tree.
[warning message]

WARNING delete_nsecnode(): dns_rbt_deletenode: Cannot delete the corresponding node from the auxiliary NSEC tree
[warning message] before deleting it from the main tree.

INFO decrement_reference: failed to allocate The decrement_reference() function: Cannot allocate a pruning
pruning event event.

ERROR previous_closest_nsec(): [error message] Cannot find the node of the NSEC/NSEC3 record.

ERROR rpz_findips findnode([DNS name]) failed: Cannot find the node corresponding to CDIR tree entry.
[error message]

INFO disabled rpz [type] [policy] rewrite [DNS When RPZ Policy is disabled, the query is still being processed and
name] via [DNS name] result that includes information about what address could be
overwritten is logged. The policy in a log message is declared as
applied but the response is returned to a user without applying
policy rules because it is disabled.

N/A overmem cache: [[FORCE]or[check]] The debug message for a cache. Check the specified node.
[node name]

N/A overmem cache: stale [DNS name] The debug message for a cache. the specified node is stale.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 86 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

N/A overmem cache: reprieve by RETAIN() The debug message for a cache. the specified node is reprieved.
[DNS name]

N/A overmem cache: saved [DNS name] The debug message for a cache. the specified node is saved.

WARNING addnode: NSEC node already exists NSEC node already exists.

WARNING loading_addrdataset: If a node cannot be added to a tree, it is deleted and the reason of
dns_rbt_deletenode: [NSEC result] after this error is indicated.
dns_rbt_addnode(NSEC): [node result]

N/A clients-per-query increased to [number] The new (increased) number of recursive simultaneous clients for
any given query that the server accepts.

INFO success resolving '[ctx info]' (in '[DNS Deferred Extension Mechanisms for DNS (EDNS) timeout message.
name]'?) after [ctx reason]

INFO error ([reason][[]or[ ]][code]) resolving Servers are added to the list of bad servers.
'[DNS name]/[record data type]/[record
data class]': [socket address]

INFO lame server resolving '[DNS name]' (in The name servers specified as authoritative for this domain's zone
'[DNS name]'?): [socket address] are not actually authoritative.

WARNING Check-names [[failure]or[warning]] [DNS This is an error or warning issued during RR dataset check. The
name]/[record data type]/[record data details regarding DNS record name, RR dataset type and RR dataset
class] class are indicated.

N/A answer address [net address] denied for The client address is filtered according to the rules of the exclusion
[DNS name]/[record data type]/[record list. Client address and DNS record name are indicated.
data class]

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 87 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

N/A [record data type] target [DNS name] Cannot apply filters on the specified target name.
denied for [DNS name]/[record data
class]

N/A received NSID '[hex version of the NSID]' DNS Name Server Identifier received.
from [socket address]
N/A received packet:\n%.[length of line in The amount of memory left in a buffer after receiving a packet.
multiline debug messages]

ERROR could not mark server as lame: [error Cannot mark server as lame for the specified reason.
message]

N/A enforced delegation-only for '[DNS Delegations is enforced only for NET and COM zones.
name]' ([DNS name]/[record data
type]/[record data class]) from [socket
address]

N/A clients-per-query decreased to [count] The new (decreased) number of recursive simultaneous clients for
any given query that the server accepts.

N/A createfetch: [DNS name] [record data DNS resolver creates the specified fetch.
type]

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 88 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

INFO fetch completed at [file]:[line] for [info] A log message is dumped on internal state at the completion of the
in [duration]. 06[duration] : specified resolver fetch.
[result]/[vresult] [domain:[DNS
name],referral:[number],restart:[numbe
r],qrysent:[number],
timeout:[number],lame:[number],neterr:
[number],badresp:[number],
adberr:[number],findfail:[number],valfail
:[number]

WARNING extra data in root hints [[filename]or Extra data detected in root hints from the file specified.
[<BUILT-IN>]]

WARNING checkhints[separator][view name]: [DNS Cannot find hint server for the specified DNS view and a record.
name]/[record data type] ([data])
missing from hints

WARNING checkhints[separator][view name]: [DNS The hints query returned extra records. It might happen when one
name]/[record data type] ([data]) extra of the root server changes an IP address but the server is still
record in hints working at the old IP. Since both servers answered, you receive extra
records.

WARNING heckhints[separator][view name]: unable Cannot find root NS rrset from hints due to the specified reason.
to get root NS rrset from hints: [warning
message]

WARNING checkhints[separator][view name]: Cannot find root NS rrset from a cache due to the specified reason.
unable to get root NS rrset from cache:
[warning message]

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 89 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

WARNING checkhints[separator][view name]: Cannot find root NS in hints.
unable to find root NS '[DNS name]' in
hints

WARNING checkhints[separator][view name]: extra Extra NS records are found in hints. That usually happens when a
NS '[DNS name]' in hints root server changes an IP address.

N/A invalid rpz IP address "[DNS The Response policy zone (RPZ) has an invalid IP address.
name]"[message1][message2]

ERROR rpz add failed; "[DNS name]" is a Cannot add an IP address to the radix tree of a response policy
duplicate name database. DNS name is a duplicate name.

ERROR sdlz newversion on origin [DNS name] The SDLZ driver new version() function failed to start a new
failed : [error message] ’transaction'.

ERROR sdlz closeversion on origin [DNS name] The SDLZ driver cancels the transaction.
failed
ERROR sdlz getoriginnode failed : [error The SDLZ driver getoriginnode() function failed with the specified
message] error.
ERROR SDLZ driver failed to load. The SDLZ driver failed to load.
N/A ssu_external: socket path '[path]' longer The implementation of simple secure update rules for external
than system maximum [length] application: socket path is longer than a system maximum value.
N/A ssu_external: unable to create socket – The implementation of simple secure update rules for external
[error message] application: Cannot create a socket.
N/A ssu_external: unable to connect to " The implementation of simple secure update rules for external
"socket '[path]' – [error message] application: Cannot to connect to a socket.
N/A ssu_external: invalid socket path '[DNS The implementation of simple secure update rules for external
name]' application: invalid socket path.
N/A ssu_external: unable to send request - The implementation of simple secure update rules for external
[error message] application: Cannot send request.
N/A ssu_external: unable to receive reply - The implementation of simple secure update rules for external
[error message] application: Cannot receive a reply.
N/A ssu_external: denied external auth for The implementation of simple secure update rules for external
'[DNS name]' application: denied external authentication for a requested element.
N/A ssu_external: allowed external auth for The implementation of simple secure update rules for external
'[DNS name]' application: allowed external authentication for requested element.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 90 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

N/A ssu_external: invalid reply 0x[reply] The implementation of simple secure update rules for external
application: invalid reply.
N/A process_dhtkey: tkey-dhkey not defined The process_dhtkey() function error: TKEY that was designed to
generate a shared secret using a Diffie-Hellman key exchange is not
defined.
N/A process_dhtkey: algorithms other than The process_dhtkey() function error: algorithms other than hmac-
hmac-md5 are not supported md5 are not supported.
N/A process_dhtkey: found an incompatible The process_dhtkey() function error: an incompatible Diffie-Hellman
key key is found.
N/A process_dhtkey: failed to find a key The process_dhtkey() function error: Cannot find a Diffie-Hellman
key.
N/A process_dhtkey: failed to compute The process_dhtkey() function error: Cannot compute a shared
shared secret: [error mmessage] secret.
N/A process_dhtkey: failed to obtain The process_dhtkey() function error: Cannot obtain entropy.
entropy: [error message]
N/A process_gsstkey(): no tkey-gssapi- You have to define either a gss credential (principal) to accept with
credential or tkey-gssapi-keytab tkey-gssapi-credential, or you have to configure a specific keytab
configured (with tkey-gssapi-keytab) in order to use gsstkey.
ERROR process_gsstkey(): dns_tsigerror_badalg The process_gsstkey() function error: invalid algorithm for GSS-TSIG
is found.
ERROR process_gsstkey(): dns_tsigerror_badkey The process_gsstkey() function error: invalid key for GSS-TSIG is
found.
ERROR process_gsstkey(): dns_tsigerror_noerror The process_gsstkey() function finished successfully.
N/A process_gsstkey(): [message] The process_gsstkey() function failed with the specified error.
N/A dns_tkey_processquery: couldn't find a The dns_tkey_processquery() function error: failed to find a TKEY
TKEY matching the question that match the question.
N/A properly signed - rejecting The dns_tkey_processquery() function error: query was not properly
signed thus rejected.
N/A dns_tkey_processquery: tkey-domain The dns_tkey_processquery() function error: tkey-domain is not set.
not set
ERROR ns_tkey_processdhresponse: tkey mode The dns_tkey_processdhresponse() function error: tkey mode
invalid or error set(1) invalid or error set(1).
N/A dns_tkey_processdhresponse: failed to The dns_tkey_processdhresponse() function error: Cannot find a
find server key server key.
ERROR dns_tkey_processgssresponse: tkey The dns_tkey_processgssresponse() function error: tkey mode
mode invalid or error set(2) invalid or error set(2).
ERROR ns_tkey_processdeleteresponse: tkey The dns_tkey_processgssresponse() function error: tkey mode
mode invalid or error set(3) invalid or error set(3).
ERROR dns_tkey_processdhresponse: tkey The dns_tkey_processgssresponse() function error: tkey mode
mode invalid or error set(4) invalid or error set(4).

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 91 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

N/A tsig key '[DNS name]' ([DNS name]): The information about TSIG key.
[message]

N/A tsig key '[DNS name]': [message] The information about TSIG key.

INFO the key '[DNS name]' is too short to be The specified TSIG key is too short to be secure.
secure

N/A tsig expire: deleting TSIG key is expired and deleted.

N/A key name and algorithm do not match The TSIG key name and algorithm does not match the query.
N/A unknown key Cannot find TSIG key based on keyname.
N/A signature has expired TSIG has expired.
N/A signature is in the future TSIG will be use in the future.
N/A signature length to big TSIG length is too long.
N/A signature length below minimum TSIG length is below minimum size.
N/A truncated signature length too small The truncated TSIG length is too small.

N/A signature length too small TSIG length is too short.

N/A signature failed to verify(1) TSIG failed to be verified.
N/A signature was empty TSIG is empty.
N/A key name and algorithm do not match The TSIG key name and algorithm does not match the query.

N/A signature has expired TSIG is expired.

N/A signature is in the future TSIG will be use in the future.
N/A signature is empty TSIG is empty.
N/A gnature failed to verify(2) TSIG failed to be verified.
ERROR secure zone with no NSECs Secure zone does not contain NSEC resource records.
ERROR found no active private keys, unable to Cannot generate signatures because no active private keys are
generate any signatures found.
ERROR could not get zone keys for secure Cannot get zone keys for a secure dynamic update.
dynamic update
WARNING must be secure failure, no DS and this is When the DS record doesn't exist and the query name corresponds
a delegation to a delegation point you are transitioning from a secure zone to an
unsecure zone.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 92 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

WARNING must be secure failure, no DS and this is The absence of the DS record and the fact that query name
a delegation corresponds to a delegation point proposes that a zone is unsecure.

INFO bad cache hit ([DNS name]/[record The DNS resolver bad cache hit.
datatype])
INFO accepted expired %sRRSIG (keyid=%u), An expired RR signature with the specified key for the record dataset
wildcard : is accepted.

INFO verify failed due to bad signature The rdataset verification failed due to a bad signature key received.
(keyid=[key id]): [info message]

INFO no valid signature found The rdataset verification failed because no valid signature is found.
WARNING must be secure failure, no supported DNS validator security failure: no supported DNSSEC Lookaside
algorithm/digest (dlv) Validation (DLV) Resource Record (RR) Type Digest Algorithms.

WARNING must be secure failure, not beneath DNS validator security failure: the key is not signed by a trusted key.
secure root

N/A unable to find a DNSKEY which verifies Cannot find DNSKEY which verifies the DNSKEY RRset and also
the DNSKEY RRset and also matches a matches the specified trusted key.
trusted key for '[DNS name]'

N/A please check the 'trusted-keys' for '[DNS The key to verify this DNSKEY RRset is nor found. Since it is a secure
name]' in named.conf. entry point (SEP) one has to assume that the RRset is invalid.

WARNING must be secure failure, insecure DS DNS validator security failure: insecure DS set.

WARNING must be secure failure, no supported DNS validator security failure: no supported Delegation Signer (DS)
algorithm/digest (DS) Resource Record (RR) Type Digest Algorithms.

INFO no valid signature found (DS) No valid signature is found for Delegation Signer (DS).
WARNING [DNS name] is under DLV Possible security failure. Cannot track secure delegation. For more
(startfinddlvsep) information, see RFC 4431.

WARNING must be secure failure, [DNS name] is Possible security failure. Cannot track secure delegation. For more
under DLV (finddlvsep) information, see RFC 4431.

WARNING must be secure failure, not beneath Possible security failure. Cannot check signed parent. For more
secure root information, see RFC 4431.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 93 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

WARNING must be secure failure at '[DNS name]', Possible security failure. Cannot find a source, defined by the
can't fall back to DLV dnssec-lookaside statement. For more information, see RFC 4431.

WARNING must be secure failure, no DS at zone cu DNS validator failed. There is no Delegation Signer (DS) at a zone cut.

WARNING can't validate existing negative DNS validator failed to validate existing negative responses (no
responses (no DS) Delegation Signer (DS)).
WARNING must be secure failure, [DNS name] is a DNS validator failure. DNS name is a delegation.
delegation

WARNING must be secure failure, no supported DNS validator failed. There is no supported Delegation Signer (DS).
algorithm/ digest ([DNS name]/DS)

WARNING can't validate existing negative DNS validator cannot validate existing negative responses (not a
responses (not a zone cut) zone cut).

INFO got insecure response; parent indicates DNS validator receives an insecure response when parent indicates
it should be secure it should be secure.

N/A [ *]validating @[validator]: [DNS name] Logged information of DNS validator.

[record datatype]: [message]

N/A [ *]validator @[validator]: [message] Logged information of DNS validator.

ERROR got incremental response to AXFR Incremental Zone Transfers (IXFR) received an incremental response
request to AXFR request.
ERROR non-SOA response to SOA query Response to SOA query does not contain SOA.
ERROR first RR in zone transfer must be SOA There is only one SOA record allowed in a zone file and it must be
the first RR in the zone.
ERROR IXFR out of sync: expected serial [current The IXFR client is out of sync with the IXFR server because of an
serial], got [SOA serial] unexpected serial received.

INFO resetting Zone Transfer reset.

ERROR [message]: [error message] Information regarding failed Zone Transfer.
INFO connected using [socket address] The XFR is connected using the specified socket.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 94 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

INFO Transfer completed: [count] messages, Information regarding completed transfer.
[count] records, [count] bytes, [count]
secs ([count] bytes/sec)

N/A transfer of '[zone]' from [master]: Incoming zone transfer messages are logged in a following format:
[message] "transfer of <zone> from <address>: <message>"

INFO // "set latency check to +[count] sec ---------------------------------------

from now", delay);
ERROR failed to cleanup file [filename] Cannot cleanup a zone file.

ERROR [function]: Error converting mname to Cannot convert SOA mname to internal format.
internal format: [error message]

ERROR [function]: Error creating new DB Cannot create new DNS DB version.
version: [error message]

ERROR [function]: Error creating DEL difftuple: Cannot create DNS DEL difftuple for a Resource Record.
[error message]

ERROR [function]: Error creating ADD difftuple: Cannot create DNS ADD difftuple for a Resource Record.
[error message]

ERROR [function]: Error obtaining SOA from Cannot convert the SOA to a structure that you can change.
rdata: [error message]

ERROR [function]: Error creating SOA rdata: Cannot create SOA record data.
[error message]

ERROR [function]: Error applying DEL difftuple: Cannot apply DNS DEL difftuple for a Resource Record.
[error message]

ERROR [function]: Error applying ADD difftuple: Cannot apply DNS ADD difftuple for a Resource Record.
[error message]

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 95 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR [function]: Error writing zone dump and Cannot write zone dump and remove journal.
removing journal: [error message]

ERROR [function]: No address-to-vnode table Cannot obtain the vnode OID corresponding to the specified IP
address.
ERROR [function]: Error obtaining vnode from Cannot obtain the vnode from the specified master IP.
master IP [master IP]: [error message]

ERROR [function]: No vnode found for master IP No vnode is found for the specified master IP.
[master IP]: [error message]

WARNING failed to reset AXFR clients tracker used Cannot reset AXFR clients tracker used for multimaster consistency
for multimaster consistency (IXFR won't (IXFR won't be impossible for the zone).
be impossible for the zone): [warning
message]

ERROR assumption violation: zdb is expected Assumption violation: DNS zone is not zdb.
but isn't
ERROR zone has no view The zone has no view.
ERROR failed to determine zone name while Cannot determine zone name when registering the specified master
registering master switch: [error switch.
message]

WARNING failed to update SOA mname; master Cannot update SOA mname, the specified master switch is not
switch not completed: [warning completed.
message]

INFO initially selected master [current server] The specified initial master is selected.
ERROR failed to change masterfile name: zone Cannot change zone masterfile name because zone dump is in
dump in progress progress.
ERROR journal rollforward failed: [error Zone's journal rollforward failure.
message]
ERROR journal rollforward failed: " journal out Zone's journal rollforward failure: zone's journal is out of sync with
of sync with zone the zone.
ERROR Error reloading zone from DB: [error Cannot reload zone from the specified DB: possibly obsolete zone
message]; possibly obsolete zone data data will be used.
will be used.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 96 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

WARNING zone file cleanup requested; cleaning up Zone file cleanup is requested, cleanup is in process.

ERROR "master file is not configured The master file is not configured.
INFO ZDB is non-persistent (envvar ZDB is non-persistent (environment variable
INFOBLOX_ZDB_PERSISTENT). Forcing INFOBLOX_ZDB_PERSISTENT). Forcing redump for the specified
redump for masterfile '[zone master file]' masterfile.

WARNING ZDB masterfile '[zone masterfile]' is not ZDB masterfile is not available. Redump is required.
available. Redump required.

ERROR oading zone: creating database: [error Cannot create database while loading zone.
message]
ERROR loading zdb zone: initial load error: [error The specified initial load error appears during loading of ZDB zone.
message]

WARNING zdb zone is loaded from a file non- This is an unexpected case and should not happen. For initial load
incrementally; forcing redump only incremental loading is done because any reload requires
redump, and on reconfig (in case of transition to HA active) no new
zone is added. If this warning is logged, please contact technical
support.
ERROR loading zone for incremental signing: Cannot retrieve the specified label when loading zone for an
retrieve label: [error message] incremental signing.

ERROR loading zone for incremental signing: zdb Cannot load zdb zone for incremental signing from OneDB. Records
from onedb: [error message] that are required to sign the name are the specified.

ERROR loading zone: no master file configured Master file is not configured when a zone is being loaded.

INFO loading zone: no master file configured: Master file is not configured when a zone is being loaded. Loading is
continuing continued.
ERROR loading zone: Rescheduling zone loading Cannot reschedule a zone loading during zone dump.
during zone dump failed: [error
message]

N/A [DNS name]/MX '[DNS name]' has no The MX record check finds that Zone/MX has no address records (A
address records (A or AAAA) or AAAA).

N/A [DNS name]/MX '[DNS name]' is a The MX record check finds that Zone/MX is a CNAME record that is
CNAME (illegal) illegal.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 97 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

N/A [DNS name]/MX '[DNS name]' is below a The MX record check finds that Zone/MX is below DNAME record
DNAME '[DNS name]' (illegal) that is illegal.

N/A [DNS name]/SRV '[DNS name]' has no The MX record check finds that Zone/SRV has no address records (A
address records (A or AAAA) or AAAA).

N/A [DNS name]/SRV '[DNS name]' is a The SVR record check finds that Zone/SRV is CNAME record that is
CNAME (illegal) illegal.
N/A [DNS name]/SRV '[DNS name]' is below a The SVR record check finds that Zone/SRV is below DNAME record
DNAME '[DNS name]' (illegal) that is illegal.

N/A address records (A or AAAA) The Glue record check finds that Zone/NS has no address records (A
or AAAA).
N/A [DNS name]/NS '[DNS name]' is a CNAME The Glue record check finds that Zone/NS is CNAME record that is
(illegal) illegal.
N/A [DNS name]/NS '[DNS name]' is below a The Glue record check finds that Zone/NS is below DNAME record
DNAME '[DNS name]' (illegal) that is illegal.

N/A semantically identical records Zone has semantically identical records.

WARNING weak [algorithm] ([dns key algorithm]) RSA keys with exponent 3 is found.
key found (exponent=3)

ERROR zone_signwithkey failed: [error message] Cannot sign a zone with a key.

INFO zone_addnsec3chain([hash Internal parameters of zone_addNSEC3chain() function.

algorithm],[flags],[iterations],[salt])

ERROR zone_addnsec3chain failed: [error Cannot incrementally add a NSEC3 chain to a zone.
message]

ERROR nsec3param lookup failure: [error NSEC3 parameters lookup failed during NSEC3 parameters check.
message]
ERROR nsec3param lookup failure: [error NSEC3 parameters lookup failed during NSEC3 parameters check.
message]
WARNING nsec3 test \"unknown\" hash algorithm The unknown hash algorithm is found during NSEC3 parameters
found: [hash algorithm] check.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 98 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR unsupported nsec3 hash algorithm in The unsupported NSEC3 hash algorithm is found in dynamic zone
dynamic zone: [hash algorithm] during NSEC3 parameters check.

WARNING unsupported nsec3 hash algorithm: The unsupported NSEC3 hash algorithm is found during NSEC3
[hash algorithm] parameters check.

ERROR no supported nsec3 hash algorithm A supported NSEC3 hash algorithm for a zone is not found.
ERROR No valid trust anchors for '[DNS name]' There is no valid trust anchors for a key table.

ERROR [number of revoked keys ] key(s) Number of key(s) revoked and still pending.
revoked, [number of pending keys ] still
pending
ERROR All queries to '%s' will fail All queries to key tables will fail.
ERROR [error message]:dns_journal_open -> %s Cannot open zone journal file.

ERROR Resetting journal "[journal file]" Resetting zone journal.

ERROR Error unlinking journal file "journal file" Cannot unlink zone journal file for a reset.
for reset: [error message]

ERROR [caller]:dns_journal_write_transaction -> Cannot write a set of changes applied to a zone to a journal.
[error message]

ERROR add_soa:dns_db_newversion -> [error Cannot open a new version of a database for reading and writing
message] when creating an SOA record for a newly-created zone.
ERROR add_soa:dns_soa_buildrdata -> [error Cannot build SOA record data when creating an SOA record for a
message] newly-created zone.
ERROR sync_keyzone:dns_db_newversion -> Cannot open a new version of database for reading and writing
[error message] when synchronizing the set of initializing keys found in managed-
keys {} statements with the set of trust anchors found in the
managed-keys.bind zone.
ERROR loading from master file [master file] Cannot load from a master file.
failed: [error message]

N/A loading from master file [master file] Cannot load from a master file.
failed: [error message]

ERROR journal rollforward failed: [error Zone's journal rollforward failed.

message]

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 99 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR journal rollforward failed: journal out of Zone's journal rollforward failed: zone's journal is out of sync with a
sync with zone zone.
ERROR could not find NS and/or SOA records No NS and/or SOA records are found.

INFO journal file is out of date: removing Zone journal file is out of date. Attempt to remove zone journal file.
journal file
WARNING unable to remove journal '[journal]': Cannot remove the specified zone journal.
'[error message]'

ERROR as [count] SOA records Zone has more than one SOA record. There should be only one.
ERROR has no NS records Zone has no NS records.
INFO ixfr-from-differences: unchanged Zone serial and zone are unchanged.

ERROR ixfr-from-differences: new serial ([serial]) The new zone serial is out of range.
out of range [[serial min] – [serial max]]"

ERROR zone serial ([serial]/[old serial]) has gone Zone serial has gone backwards. New and old serial values are the
backwards specified.

ERROR zone serial ([serial]) unchanged. zone Zone serial unchanged therefore zone may fail to transfer updates
may fail to transfer to slaves. to slaves.

WARNING sig-re-signing-interval less than 3 Zone resigning interval is less than three (zone refresh interval).

WARNING signed dynamic zone has no resign event The signed dynamic zone has no resign event scheduled.
schedule
INFO loaded serial [serial][[ (DNSSEC The status of a loaded zone serial (has or has not a DNSSEC
signed)]or[]] signature).

WARNING unable to load from [masterfile]; file Cannot to load a zone from a master file. The file is removed.
removed

ERROR not loaded due to errors Zone is not loaded due to errors.
N/A NS '[DNS name]' has no address records The NS record check reveals that the zone/NS has no address
(A or AAAA) records (A or AAAA).
N/A NS '[DNS name]' is a CNAME (illegal) The NS record check reveals that the zone/NS is a CNAME record
that is illegal.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 100 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

N/A NS '[DNS name]' is below a DNAME 'DNS The NS record check reveals that the zone/NS is below DNAME
name' (illegal) record that is illegal.
ERROR DNSKEY RRSIG(s) have expired The DNSKEY RRSIG(s) has expired.
WARNING DNSKEY RRSIG(s) will expire within 7 The DNSKEY RRSIG(s) will expire in 7 days.
days: [time]

N/A setting keywarntime to [time] The key expiry warning time is set to the specified value.
WARNING Key [DNS name]/[DNS name]/[key id] The RRSIG key is missing or inactive and has no replacement. The
missing or inactive and has no signatures are retained. It happened while deleting expired RRsigs
replacement: retaining signatures. and any RRsigs that are about to be re-signed.

WARNING key expiry warning time out of range The zone key expiry warning time value is incorrect for sc_stdtime_t
datatype .
INFO zone_resigninc: deferred as ZRQ seemed The zone_resigninc() function is deferred as ZRQ seems to be busy.
to be busy

ERROR zone_resigninc:dns_db_newversion -> The zone_resigninc() function cannot open a new version of
[error message] database for reading and writing.

ERROR zone_resigninc:find_zone_keys -> [error The zone_resigninc() function failed to find DNSSEC keys for a zone.
message]
ERROR zone_resigninc:dns_db_getsigningtime - The zone_resigninc() function failed to get a signing time value.
> [error message]

ERROR zone_resigninc:del_sigs -> [error The zone_resigninc() function cannot delete expired RRsigs and any
message] RRsigs that are about to be re-signed.
ERROR zone_resigninc:add_sigs -> [error The zone_resigninc() function Cannot add RRsig that are about to be
message] re-signed.
ERROR zone_resigninc: Signing took longer than The zone_resigninc() function error: RW transaction value is longer
[timeout] sec than the Thales sign timeout.

ERROR "zone_resigninc:dns_db_getsigningtime - The zone_resigninc() function failed to get a signing time value.
> [error message]

ERROR zone_resigninc:del_sigs -> [error The zone_resigninc() function failed to delete expired RRsigs and any
message] RRsigs that are about to be re-signed.
ERROR zone_resigninc:update_soa_serial -> The zone_resigninc() function Cannot update SOA serial.
[error message]

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 101 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR zone_resigninc:add_sigs -> [error The zone_resigninc() function Cannot add RRsig that are about to be
message] re-signed.
INFO zone_resigninc:infoblox_zdb_update_ibz The zone_resigninc() function Cannot update the ZRQ version in the
one -> [error message] IBZONE record of a zdb.

INFO Re-generated [number] signatures The specified signatures are re-generated.

ERROR update_sigs:del_sigs -> [error message] The update_sigs() function failed to delete expired RRsigs and any
RRsigs that are about to be re-signed.
ERROR update_sigs:add_sigs -> [error message] The update_sigs() function Cannot add RRsig that are about to be re-
signed.
ERROR zone_nsec3chain:dns_db_newversion -> The zone_nsec3chain() function failed to open a new version of a
[error message] database for reading and writing.

ERROR zone_nsec3chain:find_zone_keys -> The zone_nsec3chain() function failed to find DNSSEC keys for a
[error message] zone.

ERROR zone_nsec3chain: dns_nsec3_addnsec3 - Cannot add a new NSEC3 for the specified reason.
> [error message]

ERROR zone_nsec3chain: dns_dbiterator_next - The zone_nsec3chain() function failed to move the node cursor to
> [error message] the next node in the database.

ERROR one_nsec3chain: need_nsec_chain -> Creating a new NSEC3 chain failed for the specified reason.
[error message]

ERROR zone_nsec3chain fixup_nsec3param -> Fixing NSEC3 parameters failed for the specified reason.
[error message]

ERROR zone_nsec3chain: deletematchingnsec3 - The zone_nsec3chain() function failed to delete NSEC3 records.
> [error message]

ERROR zone_nsec3chain: fixup_nsec3param -> Fixing NSEC3 parameters failed for the specified reason.
[error message]

ERROR zone_nsec3chain: dns_dbiterator_next - The zone_nsec3chain() function failed to move the node cursor to
> [error message] the next node in the database.

ERROR dns_db_allrdatasets -> [error message] Making an iterator for all record datasets failed for the specified
reason.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 102 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR zone_nsec3chain: updatesecure -> [error The zone_nsec3chain() function Cannot update secure zone.
message]

ERROR zone_nsec3chain: dns_nsec3_addnsec3s Cannot add a new secure NSEC3 for the specified reason.
-> [error message]

ERROR zone_nsec3chain: update_sigs -> [error The zone_nsec3chain() function Cannot update signatures for NSEC3
message] records.

ERROR zone_nsec3chain: update_sigs -> [error The zone_nsec3chain() function Cannot update signatures for
message] NSEC3PARAM records.

ERROR zone_nsec3chain: updatesecure -> [error The zone_nsec3chain() function Cannot update a secure zone.
message]

ERROR zone_nsec3chain: update_sigs -> [error The zone_nsec3chain() function Cannot update signatures for NSEC
message] records.

ERROR zone_nsec3chain: del_sigs -> [error The zone_nsec3chain() function failed to delete expired RRsigs and
message] any Rrsigs that are about to be re-signed.

ERROR zone_nsec3chain: update_soa_serial -> The zone_nsec3chain() function Cannot update SOA serial.
[error message]

ERROR zone_nsec3chain: add_sigs -> [error The zone_nsec3chain() function add RRsig that are about to be re-
message] signed.

ERROR zone_nsec3chain: [error message] The zone_nsec3chain() function failed to incrementally build and
sign a new NSEC3 chain using the requested parameters.
ERROR zone_sign:dns_db_newversion -> [error The zone_sign() function failed to open a new version of database
message] for reading and writing.
ERROR zone_sign:find_zone_keys -> [error The zone_sign() function failed to find DNSSEC keys for a zone.
message]
ERROR updatesecure -> [error message] The zone_sign() function Cannot update secure zone.

ERROR updatesignwithkey -> [error message] Cannot update the zone with a zone signing key for the specified
reason.

ERROR zone_sign:dns_dbiterator_next -> [error The zone_sign() function failed to move the node cursor to the next
message] node in the database.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 103 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR update_sigs -> [error message] The zone_sign() function Cannot update signatures for NSEC
records.
ERROR zone_sign:del_sigs -> [error message] The zone_sign() function failed to delete expired RRsigs and any
RRsigs that are about to be re-signed.
ERROR zone_sign:update_soa_serial -> [error The zone_sign() function Cannot update SOA serial.
message]
ERROR zone_sign:add_sigs ->[error message] The zone_sign() function Cannot add RRsig that are about to be re-
signed.
WARNING Unable to fetch DNSKEY set '[DNS The keyfetch_done() function: a DNSKEY set has not been fetched
name]': [error message] from the zone apex of a zone whose trust anchors are being
managed.
WARNING No DNSKEY RRSIGs found for '[DNS No DNSKEY RRSIGs is found for a DNS name.
name]': [error message]

WARNING Pending key unexpectedly missing from Pending key is missing unexpectedly from a DNS name. Acceptance
[DNS name]; restarting acceptance timer timer is restarting.

WARNING Active key unexpectedly missing from Active key is missing unexpectedly from a DNS name.
[DNS name]

WARNING Active key for zone '[DNS name]' is Active key for a zone is revoked but did not self-sign. This key is
revoked but did not self-sign; ignoring. ignored.

WARNING Initializing automatic trust anchor Initializing automatic trust anchor management for a zone. DNSKEY
management for zone '[DNS name]'; ID is now trusted, waiving the normal 30-day waiting period.
DNSKEY ID [DNS key tag] is now trusted,
waiving the normal 30-day waiting
period.

WARNING Failed to create fetch for DNSKEY update Cannot create a fetch for a DNSKEY update.

WARNING dump failed: [warning message] The dumping of a zone failed.

ERROR dns_journal_compact failed: [error The DNS journal compacting failed.

message]

WARNING expired Time of zone expired.

ERROR cannot refresh: no masters Cannot refresh DNS zone. There are no masters for a zone.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 104 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

WARNING failed to determine current master Cannot determine the current master latency from a latency
([current server]) latency from latency tracking manager. The zone refresh is skipped.
tracking manager: [error message];
skipping"

WARNING failed to determine candidate master Cannot determine the candidate master latency. The zone refresh is
([socket address]) latency: [warning skipped.
message]; skipping
WARNING isc_time_nowplusinterval() failed: Cannot set the next refresh time for a zone.
[warning message]

ERROR dns_journal_compact failed: [error The DNS journal compacting failed.

message]

ERROR failed to determine zone name while Failed to determine zone name while unregistering the old master.
unregistering master: [error message]

ERROR failed to determine zone name while Failed to determine zone name while zdb secondary zone switches
registering master switch: [error to a different master.
message]

ERROR NOTIFY to [socket address] not sent. NOTIFY to address is not sent. Peer TSIG key lookup failure.
Peer TSIG key lookup failure.

INFO sending notifies (serial [serial]) Sending notify request for 'also-notify' server.

INFO sending notifies (serial [serial]) Sending notify request for DNS server.

INFO could not refresh stub from master Cannot refresh a stub from a master.
[socket address] (source [socket
address]): [info message]

INFO refreshing stub: unexpected rcode An unexpected rcode received from a master while refreshing a
([rcode]) from [socket address] (source stub.
[socket address])

INFO refreshing stub: truncated TCP response A truncated TCP response received from a master while refreshing
from master [socket address] (source stub.
[socket address])

INFO refreshing stub: non-authoritative A non-authoritative answer received from a master while refreshing
answer from master [socket address] stub.
(source [socket address])

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 105 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

INFO refreshing stub: unexpected CNAME An unexpected CNAME response received from a master while
response from master [socket address] refreshing stub.
(source [socket address])

INFO refreshing stub: no NS records in no NS records are received in response from a master while
response from master [socket address] refreshing stub.
(source [socket address])

INFO refreshing stub: unable to save NS Cannot save NS records from a master while refreshing stub.
records from master [socket address]
(source [socket address])

INFO refresh: retry limit for master [socket The retry limit for a master is exceeded after the SQA query is
address] exceeded (source [socket completed.
address])
INFO refresh: failure trying master [socket Failed to reach the master after the SOA query is completed.
address] (source [socket address]): [info
message]

INFO refresh: failure trying master [socket Failed to reach the master after the SOA query is completed.
address] (source [socket address])

INFO refresh: unexpected rcode ([rcode]) from An unexpected rcode received from a master after the SOA query is
master [socket address] (source [socket completed.
address])

INFO refresh: truncated UDP answer, initiating A truncated UDP answer received from a master; initiating TCP zone
TCP zone xfer for master [socket xfer for master after the SOA query is completed.
address] (source [socket address])

INFO refresh: truncated TCP response from A truncated TCP response received from a master after the SOA
master [socket address] (source [socket query is completed.
address])

INFO refresh: non-authoritative answer from A non-authoritative answer received from a master after the SOA
master [socket address] (source [socket query is completed.
address])

INFO refresh: CNAME at top of zone in master CNAME at top of a zone in master after the SOA query is completed.
[socket address] (source [socket
address])
INFO refresh: referral response from master A referral response received from a master after the SOA query is
[socket address] (source [socket completed.
address])

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 106 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

INFO refresh: NODATA response from master NODATA response received from a master after the SOA query is
[socket address] (source [socket completed.
address])
INFO refresh: answer SOA count ([SOA count]) The SOA count received from master is not equal to one from
!= 1 from master [socket address] master.
(source [socket address])
INFO refresh: unable to get SOA record from Cannot get SOA record a from master after the SOA query is
master [socket address] (source [socket completed.
address])
INFO refresh: dns_rdataset_first() failed Cannot move the rdata cursor to the first rdata in the record dataset
after the SOA query is completed.
INFO refresh: skipping [[zone transfer]or[NS Skipping zone transfer or NS query since master is unreachable
query]] as master [socket address] (cached) after the SOA query is completed.
(source [socket address]) is unreachable
(cached)

INFO hanged master from [previous server] The current master is switched to the best master candidate for
([previous latency] usec) to [new server] multi master zone based on a latency data.
([candidate latency] usec)

ERROR refresh: could not set file modification Cannot set master file modification time after the SOA query is
time of '[masterfile]': [error message] completed.

INFO serial number ([SOA serial]) received SOA serial number received from master is less than existing after
from master [master] < ours ([old serial]) the SOA query is completed.

WARNING SOA request probe failed for master SOA request probe failed for a master (please check configuration).
[master]; please check configuration

ERROR keys for zone: zone's view has no keys. Cannot find DHCP_UPDATER keys for zone. Zone's view has no keys.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 107 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR Cannot configure zone updater acl (view Cannot configure zone updater ACL. The view name is too long for
name is too long for updater key name; updater key name; must not exceed the specified number of bytes.
must not exceed [count] bytes)

ERROR Cannot configure zone updater acl (bad Cannot configure zone updater ACL because of a bad view name.
view name): [error message]

CRITICAL Cannot create new allow-update- Cannot create a new allow-update-forwarding ACL that has enough
forwarding ACL: [error message] room to contain the updater key and the elements of
<upper_level_fwd_acl>.
ERROR key for zone: [error message] Cannot find DHCP_UPDATER keys for a zone.

CRITICAL Cannot merge content into allow- Cannot merge content into allow-update-forwarding ACL.
update-forwarding ACL: [error message]
ERROR unable to find key: [error message] Cannot find a tsig key in the master statement.
ERROR unable to find TSIG key for [] Cannot find a tsig key for a server.
WARNING failed to request SOA probe for master Cannot request an SOA probe for a master. Check configuration.
[master]; please check configuration

ERROR refreshing stub: could not create Cannot create a database while refreshing a stub.
database: [error message]

INFO refreshing stub: dns_db_newversion() Cannot open a new version of a database for reading and writing
failed: [info message] while refreshing a stub.
INFO refreshing stub: dns_db_findnode() Cannot find the node for a zone origin while refreshing a stub.
failed: [error message]
INFO refreshing stub: dns_db_addrdataset() Cannot add a record dataset to a node while refreshing a stub.
failed: [info message]

ERROR unable to find key: [DNS name] Cannot find tsig key in the master statement.
ERROR could not deactivate zone timer: [error Cannot deactivate a zone timer.
message]

ERROR could not reset zone time Cannot reset a zone timer.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 108 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

N/A NOTIFY with no question section from: NOTIFY (SOA) with no question section received from the specified
[socket address] socket address.

N/A NOTIFY zone does not match NOTIFY zone does not match.
INFO refused notify from non-master: [socket A notify request from non-master is refused because zone notify
address] request ACL is empty.
INFO ignored notify from non-current master: Notifications from non-current masters for multimaster zones are
[socket address] ignored.
WARNING notify from [socket address] ignored: The notify request from a non-current master to trigger a refresh
zone is not available check is ignored because the zone is not available.

INFO notify from [socket address]: zone is up The notify request from non-master to trigger a refresh check
to date received. The zone is up to date.

INFO notify from [socket address]: refresh in Notify request from a non-master to trigger a refresh check. The
progress, refresh check queued refresh in progress, refresh check is queued.

N/A One [name record]: [message] A notify log message description.

N/A [[managed-keys-zone]or[redirect- A DNS zone log message description.

zone]or[zone]][name record]: [message]
managed-keys-zone : zone redirect-zone
: zone

N/A [[managed-keys-zone]or[redirect- A DNS zone log message description.

zone]or[zone]][name record]: [message]

N/A %s: %s %s: %s" zone A DNS zone debug log message description.

N/A [message] An update log message description.

ERROR corrupt journal file: '[journal]' Applying diffs from the raw zone's journal to the secure zone failed
because of a corrupt journal file.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 109 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

INFO serial [new serial] (unsigned [desired An old SOA RR serial number (unsigned desired SOA RR serial
serial]) number).
ERROR receive_secure_serial: [error message] The receive_secure_serial() function failed.

ERROR receive_secure_db: [error message] The receive_secure_db() function failed.

ERROR has [count] SOA records The specified number of SOA records is found while replacing the
existing zone database. There should be only one SOA record.
ERROR as no NS records No NS records are found while replacing the existing zone database.
ERROR retrieving SOA and NS records failed: Retrieving SOA and NS records for a zone failed while replacing the
[error message] existing zone database.

ERROR ixfr-from-differences: unable to get new Cannot get SOA RR serial number from a database while replacing
serial the existing zone database.

ERROR ixfr-from-differences: failed: new serial SOA RR serial number is out of range while replacing the existing
([serial]) out of range [[serial min] – zone database.
[serial max]]

ERROR dns_journal_compact failed: [error The DNS journal compacting failed.

message]

WARNING unable to remove masterfile Cannot remove the old masterfile while replacing the existing zone
'[masterfile]': '[error message]' database.

WARNING unable to remove journal '[masterfile]': Cannot remove the zone journal while replacing the existing zone
'[error message]' database.

ERROR transferred zone has [count] SOA The transferred zone has the specified number of SOA records.
record(s) There should only be one.

ERROR transferred zone has no NS records The transferred zone has no NS records.

INFO transferred serial [serial][DNS name] The serial number of a transferred zone.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 110 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR transfer: could not set file modification Transfer issue. Cannot set master file modification time.
time of '[masterfile]': [error message]

WARNING failed to transfer from master [master]; Cannot transfer from a master. Please check configuration.
please check configuration

ERROR dns_journal_compact failed: [error The DNS journal compacting failed.

message]
ERROR loading zdb zone: error establishing Cannot validate ZDB zone status while loading zdb zone. Redumping
validation status: [error message]. zone.
Redumping zone.

WARNING Removing out of sync journal file. The journal file is out of sync ('out of range') and removed as
obsolete.
ERROR Error applying updates: [error message] Cannot apply updates from a journal file to loaded zone.

ERROR loading zdb zone: initial load error: [error Loading a zdb zone failed due to the initial load error.
message]

ERROR loading zone: Rescheduling zone loading Rescheduling zone loading during zone dump failed.
during zone dump failed: [error
message]

INFO got_transfer_quota: skipping zone The got_transfer_quota() function: skipping zone transfer as master
transfer as master [socket address] (source) is unreachable (cached).
(source [socket address]) is unreachable
(cached)

ERROR could not get TSIG key for zone transfer: Cannot get TSIG key for a zone transfer.
[error message]

INFO could not forward dynamic update to Cannot forward a dynamic update to a master.
[socket address]: [info message]

WARNING forwarding dynamic update: unexpected An unexpected response is received because master returned an
response: master [socket address] error while forwarding a dynamic update.
returned: [rcode]

INFO Transfer started. Transfer started.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 111 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

WARNING unable to load from '[path]'; renaming Failed to load data from a zone file. This is renamed for failure
file to '[file name]' for failure analysis analysis and retransferring. Both old and new file names are
and retransferring. indicated.

INFO master [socket address] (source [socket The master (source) is deleted from an unreachable cache.
address]) deleted from unreachable
cache

N/A [DNS name]/[record datatype]: Owner name check for a zone failed.
[message]

N/A [DNS name]/[record datatype]: [DNS Record data check for a zone failed.
name]: [message]

N/A dns_zone_signwithkey(algorithm=[algori Values of an algorithm and a keyid of the dns_zone_signwithkey()

thm], keyid=[key id]) function.

N/A dns_zone_addnsec3chain(hash=[hash], Values of a hash, an iterations and a salt of the

iterations=[interactions], salt=[salt]) dns_zone_addnsec3chain() function.

ERROR sign_apex:find_zone_keys -> [error The sign_apex() function error: cannot find a zone keys.
message]
ERROR sign_apex:del_sigs -> [error message] The sign_apex() function error: cannot delete expired RRsigs and any
RRsigs that are about to be re-signed.
ERROR sign_apex:add_sigs -> [error message] The sign_apex() function error: cannot add RRsig that are about to
be re-signed.
ERROR sign_apex:update_sigs -> [error The sign_apex() function error: cannot update RRsig that are about
message] to be re-signed.
ERROR NSEC only DNSKEYs and NSEC3 chains NSEC only, DNSKEYs and NSEC3 chains are not allowed. There is at
not allowed least one DNSKEY with an algorithm that predates NSEC3, and
therefore a zone cannot have a valid NSEC3 chain.
INFO reconfiguring zone keys Reconfiguring zone keys.
ERROR couldn't update zone keys: [error Cannot update zone keys while reconfiguring zone keys.
message]
ERROR zone_signwithkey failed: [error message] Cannot remove any signatures from removed keys.

ERROR zone_signwithkey failed: [error message] Cannot sign the zone with all active keys, whether they're new or
not.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 112 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR zone_signwithkey failed: [error message] Cannot sign the full zone, but only with newly active keys.

ERROR zone_addnsec3chain failed: [error Cannot incrementally add a NSEC3 chain to a zone.
message]

INFO next key event: [time] Setting the key refresh timer for the next scheduled key event.
ERROR keydone:dns_db_newversion -> [error The keydone() function error: cannot open a new version of a
message] database for reading and writing.

ERROR setnsec3param:dns_db_newversion -> The setnsec3param() function error: cannot open a new version of a
[error message] database for reading and writing.

ERROR Loading zone. Attempt to reload non-DB Loading zone. Attempt to reload non-DB zone from a DB is rejected.
zone from DB rejected.

ERROR This zone is already loading." This zone is already loading.

ERROR Loading zone. Zone masterfile is not Zone masterfile is not configured while loading the zone.
configured: [error message]

ERROR Loading zone. Create zone db failed: Creating zone database failed while loading the zone.
[error message]

ERROR Loading zone. Load from DB failed: [error Loading from a database failed while loading the zone.
message]

ERROR Loading zone. Could not update SOA Cannot update an SOA mname while loading the zone.
mname: [error message]

WARNING Master addresses not available, cannot Master addresses are not available; cannot set an SOA mname.
set SOA mname
WARNING failed to write new master file to disk: Failed to write a new master file to a disk. The Journal and IXFR will
[warning message]; journal and IXFR will be disabled. Trying to restart the DNS service to fix the issue.
be disabled; try to restart DNS service to
fix the issue

WARNING failed to replace old master file with new Failed to replace old master file with new one. Journal and IXFR will
one: [warning message]; journal and be disabled. Restarting the DNS service may fix the issue.
IXFR will be disabled; try to restart DNS
service to fix the issue

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 113 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

WARNING failed to clean obsolete journal file: Failed to clean an obsolete journal file. The journal and IXFR will be
[warning message]; journal and IXFR will disabled. Trying to restart the DNS service to fix the issue.
be disabled; try to restart DNS service to
fix the issue

ERROR Error reloading zone from DB: [error Failed to reload a zone from a database. Possibly obsolete zone data
message]; possibly obsolete zone data will be used.
will be used.

INFO Finished reloading zone from database. Finished reloading zone from database.

ERROR full zone reload: failed to replace zone Cannot reload a zone from OneDB.
data
INFO Reloading zone from database. Reloading zone from a database.
ERROR full zone reload: attempt to reload non- The zone is not backed by ZDB.
DB zone from DB rejected.

ERROR full zone reload: unable to remove Cannot destroy the currently persisted zone file(s).
existing zone files
ERROR full zone reload: failed to allocate event. full zone reload() function: failed to allocate event for the task.

CRITICAL Cannot create new allow-update- Cannot clone the provided ACL.
forwarding ACL
WARNING failed to reset latency for master Failed to reset the latency for a master.
[master]: [warning message]

ERROR failure while adding zones into loading Cannot add zones into a loading queue.
queue: [error message]

N/A [[freezing]or[thawing]] zone The status of a dynamic zone. When a dynamic zone is frozen, only
'[zone]/[class]'[separator][view]: manual changes are allowed. When a dynamic zone is thawed, BIND
[message] services a zone as usual.

INFO [seen] seen for unloaded zone, An informational message that describes an unloaded zone status,
prioritizing its loading 'Prior access seen' or 'Autogenerated flag seen'. Prioritizing zone
loading.
WARNING duplicate attempt of queued zone A duplicate attempt to load a zone into a queue is ignored.
loading (ignored)

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 114 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR failed to schedule zone loading: [error Failed to schedule a zone loading.
message]
WARNING exiting… Exiting due to a timeout.
WARNING *** POKED TIMER *** The manager pokes a timer if it is 15 or more seconds behind.

ERROR remove '%s': failed Removing file 'templet' failed.

INFO prefix length for [net address] is The prefix length for the specified address is unknown so it is
unknown (assume 128) assumed to be equal to 128.

ERROR /proc/net/if_inet6:iter Process /proc/net/if_inet6 is not found.

ERROR /proc/net/if_inet6:sscanf() -> [count] The actual value of 'res' arguments. The expected value is six.
(expected 6)

ERROR "/proc/net/if_inet6:strlen(%s) != 32 Address length does not equal to 32.

ERROR retrieving the address of an IPv6 socket IPv6 structures in kernel and user space do not match.
from the kernel failed.

ERROR IPv6 is not supported. IPv6 is not supported.

ERROR IPv6 structures in kernel and user space IPv6 structures in kernel and user space do not match.
do not match.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 115 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR IPv6 is not supported. IPv6 is not supported.

ERROR failed to start watching FD (FD): [error Failed to start watching FD (File Descriptor) for the specified reason.
message]

N/A processing cmsg [message] Processing the specified control message.

INFO interface received on ifindex [interface An interface index.

number]

INFO sendto pktinfo data, ifindex [ifindex] The packet info is sent using the specified interface index.

N/A doio_recv: recvmsg([fd]) [cc] bytes, err The function 'doio_recv' received a message on the specified socket
[error number]/[error message] containing the specified number of bytes. Error code/error strings
are specified.

N/A dropping source port zero packet Dropping packet because the source port equals to zero.

N/A packet received correctly The packet is received correctly.

N/A destroying Destroying socket.

ERROR socket: file descriptor exceeds limit The number of socket file descriptors exceeds the maximum count
([fd]/[max socket]) of file descriptors allowed.

ERROR [isc_socket_create: fcntl]: [error System error: too many open files in a system or too many open
message] files.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 116 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

N/A fd [fd] receive buffer set to [size] The new UDP receive socket buffer size.

N/A socket fd = [fd], recvbuf = [size] Information regarding the socket number and a socket buffer size.

N/A dupped : created Socket status.

N/A fdwatch-created A new 'type' socket managed by the 'manager' is created.

N/A fdwatch-poked flags: [flags] The manager poked a socket to act according to the specified flags.

N/A dispatch_recv: event [event] -> task The function 'dispatch_recv': information regarding memory address
[event sender] for the specified event and a task.
N/A dispatch_send: event [event] -> task Information message. The event that was sent to a task.
[event sender]
N/A internal_accept called, locked socket The socket is locked.

ERROR [accept/fcntl]: too many open file System error: either too many open files or too many open files in a
descriptors system.

ERROR accept: file descriptor exceeds limit The number of socket file descriptors exceeds the maximum count
([fd]/[max sickets]) of file descriptors allowed.

N/A accepted connection, new socket [new Accepted connection and the specified new socket is created.
socket]

N/A internal_recv: task [task] got event Informational message. the specified task got the specified event.
[event]

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 117 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

N/A internal_send: task [task] got event Informational message. the specified task got the specified event.
[event]

N/A internal_fdwatch_write: task [task] got Informational message. the specified task got the specified event.
event [event]

N/A internal_fdwatch_read: task [task] got Informational message. the specified task got the specified event.
event [event]

N/A maximum number of FD events This is not an error, but something unexpected. If this happens, it
([number]) received may indicate the need to increase the ISC_SOCKET_MAXEVENTS
value.

N/A maximum number of FD events This is not an error, but something unexpected. If this happens, it
([number]) received may indicate the need to increase the ISC_SOCKET_MAXEVENTS
value.

N/A maximum number of FD events This is not an error, but something unexpected. If this happens, it
([number]) received may indicate the need to increase the ISC_SOCKET_MAXEVENTS
value.

N/A watcher got message [message] for The watcher got the specified message for the specified socket.
socket [fd]

N/A watcher exiting The watcher is exiting.

N/A sockets exist Socket exist. You have to wait.

N/A socket_recv: event [event] -> task [task] Informational message. the specified task got the specified event.

INFO pktinfo structure provided, ifindex The pktinfo index is set to zero to allow the kernel to decide on
[ifindex] (set to 0)" which interface it should send.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 118 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

N/A socket_send: event [event] -> task [task] The task got the specified event.

ERROR isc_socket_cleanunix: stat([path]): [error System call: stat() failed for the specified reason.
message]

ERROR isc_socket_cleanunix: [path]: not a This is not a socket.

socket

ERROR isc_socket_cleanunix: unlink([path]): System call: unlink failed for the specified reason.
[error message]

WARNING isc_socket_cleanunix: socket([path]): Cannot create a socket for the specified reason.
[error message]

WARNING isc_socket_cleanunix: stat([path]): [error System call: stat() failed for the specified reason.
message]

WARNING "isc_socket_cleanunix: [path]: not a This is not a socket.

socket

WARNING sc_socket_cleanunix: unlink([path]): System call: unlink failed for the specified reason.
[error message]

WARNING isc_socket_cleanunix: connect([path]): Connecting to the socket failed.

[error message]

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 119 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

ERROR isc_socket_permunix: chmod([path], System call: chmod failed for the specified reason.
[permition]): [error message]

ERROR isc_socket_permunix: chown([path], System call chown failed for the specified reason.
[owner], [group]): [error message]

N/A bound Address has been assigned to a socket.

N/A setsockopt(SO_ACCEPTFILTER): [error Failed to accept a filter for a socket due to the specified reason.
message]

ERROR socket: file descriptor exceeds limit The number of file descriptors exceeds the maximum count of file
([fd]/[max socket]) descriptors allowed.

ERROR [infoblox_socket_create_shadowudp: System error: either too many open files or too many open files in a
fcntl]: [error message] system.

ERROR iocompletionport_update: failed to open iocompletionport_update() function failed to open an I/O

io completion port: [error message] completion port.

ERROR queue_io_request: fd [fd] result [result] Cannot get another queue for a receiver.
error [error]

N/A sockmgr [socket manager]: [message] The socket manager information.

N/A socket [socket] line [line]: [message] Logging socket information if a socket address is unknown.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 120 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

N/A socket [socket] line [line] peer [peer]: Logging socket information if a socket address is known.
[message]

N/A alloc_buffer [buffer] [size] [buffer] [size] The information about internal region of a buffer in the SEND
constructor.

N/A alloc_buffer [buffer] [size] [buffer] [size] The information about used region of a buffer in the SEND
constructor.

N/A dropping source port zero packet Dropping a source port zero packet for a UDP socket.

N/A startio_send: internal_sendmsg([fd]) Cannot send data to a socket, using overlapped I/O.
[number] bytes, err [error
number]/[error message]

N/A allocated The socket is allocated.

N/A SOCKET INCONSISTENT:[crash reason] The socket state is inconsistent.

N/A freeing socket line [line] fd [fd] lock The information about line number in a source code file and
[lock] semaphore [lock semaphore] parameters of a socket: file descriptor, lock, semaphore.

N/A closed [pending receive] [pending send] Cannot prevent an incorrect behavior of the UDP socket.
[references] con_reset_fix_failed

N/A closed [pending receive] [pending send] Cannot make a non-blocking socket.
[references] make_nonblock_failed

N/A created [fd] type [type] The information about line number in a source code file and
parameters of the created socket: a file descriptor and a type.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 121 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

N/A detach_socket [pending receive] The information about line number in a source code file and
[pending send] [references] parameters of the detached socket: pending receive, pending send,
references.
N/A internal_accept called An attempt to create a new socket with an old address.

N/A internal_accept parent [socket] The information about an old socket is displayed while trying to
create a new socket with an old address.

N/A accepted_connection new_socket The information about a new socket is displayed while trying to
[socket] fd [fd] create a new socket with an old address.

N/A internal_connect: success The connection is accepted for a new socket while trying to create a
new socket with an old address.

N/A internal_recv: [number] bytes received The number of bytes receive by the socket.

N/A internal_send: task got socket event An attempt to send an event to the task it was destined for .
[event]

N/A free_buffer [buffer] [buffer] Freeing the private buffer while trying to send an event to the task it
was destined for.

N/A canceled_send Sending an event to the task it was destined for is canceled.
N/A Accept: errstatus=[error status] An information about a socket accept: error status, result.
isc_result=[result]
N/A restart_accept() failed: errstatus=[error The restart of a socket accept failed.
status] isc_result=[result]

N/A canceled_accept A socket accept is canceled.

N/A canceled_connect A socket connection is canceled.
N/A SocketIoThread exiting Exit completion port thread.

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 122 of 123
Rev. A 10/2/2014
DNS Log Message Reference

Level Log message Message description

N/A sockets exist The sockets are not yet destroyed.

N/A queue_receive_event: event [event] -> The request is enqueued.

task [task]
INFO pktinfo structure provided, ifindex The pktinfo structure is provided if an index is set to zero.
[ifindex] (set to 0)

N/A socket_send: event [event] -> task [task] The request is enqueued.

N/A bound The address is assigned to the socket.

N/A listening Named is listening on the specified socket.

N/A accepting for nsock [socket] fd [fd] A new socket is accepted.

ERROR acl loop detected: [ACL name] Validation detects a recursion.

WARNING undefined ACL '[ACL name]' The ACL name is undefined.

WARNING key name '[key name]' is not a valid The name of a key is not a valid domain name.
domain name

WARNING address match list contains unsupported Address match list contains an unsupported element type.
element type

© 2014 Infoblox Inc. All Rights Reserved. All registered trademarks are property of their respective owners. Page 123 of 123
Rev. A 10/2/2014