QuickDNS Server is a full featured DNS Server for the Macintosh Platform. Below a list of the various log messages available in QuickDNS Server.
Users can configure the details of the messages that appear in the log. There are five log levels:
o Off: No logging is performed
o Minimum: Logs only critical errors
o Normal: Logs critical errors and useful information
o Thorough: Logs everything except queries and replies
o Debug Logs everything
o Note: The debug log level can generate very large log files on busy servers.
Following is a list of the messages which can appear in the log along with the log level they belong to. Higher log levels include all messages belonging to lower levels. For example the Thorough log level includes all the messages from both the Normal and the Minimum log levels but not messages from the Debug level.
Each line in the log file is preceded by date and time when the event occurred.
Minimum Log Level Messages:
Attempting to unload non-existing domain "mydemocompany.com."
This message appears if QuickDNS tries to unload a domain that has previously been unloaded.
Can't download zone "mydemocompany.com" from myself
This message appears when QuickDNS is configured to perform a zone transfer from itself. Opening up the Zone Options dialog for the zone in question and change the list of master servers for the server in question.
CNAME and data at "mydemocompany.com."
This message appears when QuickDNS loads a domain that contains a CNAME record and data under the same name. This indicates that the domain data is inconsistent. When this occurs, BIND keeps the first definition it sees.
Domain "mydemocompany.com." has expired
This message appears when QuickDNS determines that a secondary domain has expired. A secondary domain expires when QuickDNS has been unable to contact an authoritative name server for the domain for the time specified in the "Expire" file in the domain's SOA record. When a secondary domain expires, it is unloaded from memory and QuickDNS stops providing authoritative answers for the domain.
Domain "mydemocompany.com" not loaded
This message appears if QuickDNS cannot load a domain. This can happen if there is not enough memory available for QuickDNS to load a domain.
Domain "mydemocompany.com" unloaded
This message appears when QuickDNS unloads a domain. If the Restart command is issued, all domains are unloaded and then loaded again. When a domain is removed from the Primary Data folder, it is unloaded the next time QuickDNS scans the Primary Data folder. When a domain is modified the old version is unloaded, and the new one is loaded instead.
Error # in creating file spec for domain "mydemocompany.com."
This message appears when QuickDNS is unable to create a file specification for a secondary domain on the hard disk. This can happen, for example, if the disk is locked or if the Secondary Data folder has been deleted. # is the error number.
Error # while reading secondary domains file
This message appears if QuickDNS is unable to read the file Secondary Domains. This can happen if the file has an incorrect format or is corrupted. # is the error number.
Expecting SOA for "mydemocompany.com." as first record
This message appears if the first record during a zone transfer is not a SOA record. This indicates that the domain data QuickDNS is receiving is corrupted, and the zone transfer in progress is aborted.
Failed to lookup SOA info for domain "mydemocompany.com."
This message appears if QuickDNS is unable to lookup the SOA information for a secondary domain. This can happen if none of the name servers listed as authoritative for the domain in question responds to a SOA query.
Giving up on zone "mydemocompany.com."
When QuickDNS starts it checks if any of the secondary domains has been updated. This message appears if QuickDNS cannot contact an authoritative name server for the specified domain. QuickDNS will then check the domain every "Retry" second as specified in the SOA record for the domain.
Insufficient memory to load domain "mydemocompany.com"
This message appears when there is not enough memory available to load a domain.
Malformed packet received
This message appears when QuickDNS receives a malformed packed during a secondary zone transfer.
Malformed RR while transferring domain "mydemocompany.com.", aborting
This message appears when QuickDNS receives a malformed resource record during a secondary zone transfer. This indicates that the domain data is corrupted. When this happens, the zone transfer is aborted.
Multiple CNAMES or CNAME and data at "mydemocompany.com"
This message appears when QuickDNS loads a domain that contains multiple CNAMES or CNAME and data under the same name. This indicates that your domain data is inconsistent. When this occurs, BIND keeps the first definition it sees.
Multiple SOA records received
This message appears if a domain contains more than one SOA record for some reason. This indicates that the domain data QuickDNS is receiving is corrupted, and the zone transfer in progress is aborted.
Record "mydemocompany.com" outside domain - ignored
This message appears when QuickDNS loads a domain that contains a record which is outside the domain. For example, if domain mydemocompany.com contains a record named foo.com, that record is considered outside the domain.
Resource record too big
This message appears if QuickDNS receives a resource record which is too big for QuickDNS to handle. This indicates that the domain data QuickDNS is receiving is corrupted, and the zone transfer in progress is aborted.
Runt packet received
This message appears when QuickDNS receives a package which is too short to be a DNS package. This can happen for various reasons.
Server restarted
This message appears when restart of the server is complete.
Server shut down
This message appears when the server has performed necessary housekeeping prior to shutting down and is about to quit.
Server started
This message appears when the server has been initialised and is ready to load domains.
The file QuickDNS Options has been modified with a newer version of QuickDNS Admin
This message appears if the file QuickDNS Options has been modified with a newer version of QuickDNS Admin than 2.1. When this error is encountered, QuickDNS quits automatically.
Unable to allocate TCP listener
This message appears when QuickDNS is unable to allocate a TCP listener. This can happen if there is not enough memory available, or if MacTCPs limit of total 64 TCP streams is exceeded.
Unable to allocate UDP stream
This message appears when BIND is unable to allocate UDP streams.
Unable to bind to DNS port
This message appears if BIND cannot bind to the DNS port (port 53). This can happen if another name server is already running on the same machine. When this error is encountered, QuickDNS quits automatically.
Unable to connect to server
This message appears when QuickDNS is unable to connect to a server to download the secondary zone.
Unable to load zone "mydemocompany.com." from 192.168.1.1
This message appears when QuickDNS is unable to load a zone downloaded from the host specified. This can happen, for example, when QuickDNS doesn't have enough memory to load the zone.
Unable to open UDP stream
This message appears when BIND is unable to open a previously allocated UDP stream.
Unable to parse RR "name of resource record, type "type of resource record"
This message appears when QuickDNS receives a resource record type it doesn't know. When this happens, the unknown resource record is ignored.
Unable to start listener
This message appears when QuickDNS is unable to start a previously allocated TCP listener.
Unable to start UDP stream
This message appears when BIND is unable to start a previously opened UDP stream.
Unable to start zone transfer for domain "mydemocompany.com."
This message appears if QuickDNS cannot start a zone transfer for a secondary domain.
Write failed
This message appears when QuickDNS cannot write secondary domain data to disk. This can happen if the disk is write protected or becomes full during a write operation.
Wrong size read
This message appears when QuickDNS receives a packet of a different size than what it expects during a secondary zone transfer.
Zone "mydemocompany.com." load failed, error #
This message appears if QuickDNS cannot load a secondary domain. # is the error number.
Zone "mydemocompany.com." transfer to 192.168.1.1 failed
This message appears when a zone transfer to a specified host fails for some reason.
Zone "mydemocompany.com." - unable to start transfer to 192.168.1.1
This message appears if QuickDNS cannot start a zone transfer to a specified host.
Zone "mydemocompany.com" - unable to transfer to "192.168.1.1:2041"
This message appears when BIND cannot perform a zone transfer to another host.
Zone "mydemocompany.com." - unknown zone requested from "192.168.1.1:2041"
This message appears when a primary zone transfer for an unknown zone is requested. The message includes information on which domain requested and the IP address and port number of the host requesting the zone transfer.
Zone transfer requested via a datagram stream from "192.168.1.1:2041"
This message appears when a host requests a zone transfer from QuickDNS via a datagram stream.
Normal Log Level Messages
In addition to the minimal log messages:
Attempting to download zone "mydemocompany.com." with serial 123456, from 192.168.1.1
This message appears when QuickDNS has found an updated version of a domain it is secondary for and tries to download the updated domain.
Domain "mydemocompany.com" loaded
This message appears when QuickDNS completes loading a domain.
Done checking SOA for domain "mydemocompany.com.", no update needed
This message appears when QuickDNS has performed a check for a secondary domain and has determined that the domain information stored locally is up to date.
Loading domain "mydemocompany.com"
This message appears each time BIND loads a domain. When the server is started, every domain located in the Primary Data folder is loaded. If the Restart command is issued, all domains are unloaded and then loaded again. When a domain is added, it is loaded the next time QuickDNS scans the Primary Data folder. When a domain is modified, the old version is unloaded and the new one is loaded instead.
Server restarting
This message appears when the Restart command is issued.
Server shutting down
This message appears when a Quit message has been sent to the server.
Server Starting
This message is appears each time the server is started.
Shutting down TCP listener
This message appears when QuickDNS shuts down its TCP listener when quitting.
Shutting down open TCP streams
This message appears when QuickDNS shuts down its open TCP streams when quitting.
Shutting down UDP stream
This message appears when QuickDNS shuts down its UDP stream when quitting.
Starting check for domain "mydemocompany.com."
This message appears when QuickDNS starts checking if a secondary domain is up to date.
Zone "mydemocompany.com." successfully downloaded
This message appears when QuickDNS has successfully downloaded a secondary domain.
Zone "mydemocompany.com." - transfer started to "192.168.1.1:1966"
This message appears when a primary zone transfer is requested. The message includes information on which domain was transferred and the IP address and port number of the host requesting the zone transfer.
Zone "mydemocompany.com." transferred successfully to 192.168.1.1
This message appears when a zone has been transferred successfully to a specified host.
Thorough Log Level Messages
Thorough log level includes the messages from Minimal and Normal levels.
A delegation with no NS records from "192.168.19.10:53"
This message appears when QuickDNS receives a reply that is corrupted or incorrectly formed.
Dropping bogus reply from 192.168.1.1:53
This message appears when QuickDNS receives a reply to a query it did not send. This happens for example when a queried name server sends more than one reply to a single query.
Lame delegation for "1.1.168.192.in-addr.arpa." from "192.168.19.10:53"
This message appears when QuickDNS queries a given name server based on information gathered in a previous query to another name server. The queried name server, however, directs QuickDNS back to another server higher in the domain tree. This indicates that either the queried name server or the name server which pointed to the queried name server is incorrectly configured.
Debug Log Level Messages
Includes all other log messages.
Query: "mydemocompany.com" requested from "192.168.19.10:53"
This message appears when QuickDNS receives a query.
Querying "192.168.19.10:53" about "mydemocompany.com"
This message appears when QuickDNS sends a query to another name server.
Reply: "mydemocompany.com" - from "192.168.19.10:53"
This message appears when QuickDNS receives a reply to a question it queried another server.