|
@@ -124,47 +124,11 @@ has been invoked.
|
|
|
This is a debug message issued when the Dhcp-Ddns application encounters an
|
|
|
unrecoverable error from within the event loop.
|
|
|
|
|
|
-% DHCP_DDNS_INVALID_NCR application received an invalid DNS update request: %1
|
|
|
-This is an error message that indicates that an invalid request to update
|
|
|
-a DNS entry was received by the application. Either the format or the content
|
|
|
-of the request is incorrect. The request will be ignored.
|
|
|
-
|
|
|
% DHCP_DDNS_INVALID_RESPONSE received response to DNS Update message is malformed: %1
|
|
|
This is a debug message issued when the DHCP-DDNS application encountered an
|
|
|
error while decoding a response to DNS Update message. Typically, this error
|
|
|
will be encountered when a response message is malformed.
|
|
|
|
|
|
-% DHCP_DDNS_NCR_LISTEN_CLOSE_ERROR application encountered an error while closing the listener used to receive NameChangeRequests : %1
|
|
|
-This is an error message that indicates the application was unable to close the
|
|
|
-listener connection used to receive NameChangeRequests. Closure may occur
|
|
|
-during the course of error recovery or during normal shutdown procedure. In
|
|
|
-either case the error is unlikely to impair the application's ability to
|
|
|
-process requests but it should be reported for analysis.
|
|
|
-
|
|
|
-% DHCP_DDNS_NCR_RECV_NEXT_ERROR application could not initiate the next read following a request receive.
|
|
|
-This is a error message indicating that NameChangeRequest listener could not
|
|
|
-start another read after receiving a request. While possible, this is highly
|
|
|
-unlikely and is probably a programmatic error. The application should recover
|
|
|
-on its own.
|
|
|
-
|
|
|
-% DHCP_DDNS_NCR_SEND_CLOSE_ERROR DHCP-DDNS client encountered an error while closing the sender connection used to send NameChangeRequests : %1
|
|
|
-This is an error message that indicates the DHCP-DDNS client was unable to
|
|
|
-close the connection used to send NameChangeRequests. Closure may occur during
|
|
|
-the course of error recovery or during normal shutdown procedure. In either
|
|
|
-case the error is unlikely to impair the client's ability to send requests but
|
|
|
-it should be reported for analysis.
|
|
|
-
|
|
|
-% DHCP_DDNS_NCR_SEND_NEXT_ERROR DHCP-DDNS client could not initiate the next request send following send completion.
|
|
|
-This is a error message indicating that NameChangeRequest sender could not
|
|
|
-start another send after completing the send of the previous request. While
|
|
|
-possible, this is highly unlikely and is probably a programmatic error. The
|
|
|
-application should recover on its own.
|
|
|
-
|
|
|
-% DHCP_DDNS_NCR_UDP_RECV_ERROR UDP socket receive error while listening for DNS Update requests: %1
|
|
|
-This is an error message indicating that an IO error occurred while listening
|
|
|
-over a UDP socket for DNS update requests. This could indicate a network
|
|
|
-connectivity or system resource issue.
|
|
|
-
|
|
|
% DHCP_DDNS_NO_MATCH No DNS servers match FQDN: %1
|
|
|
This is warning message issued when there are no domains in the configuration
|
|
|
which match the cited fully qualified domain name (FQDN). The DNS Update
|
|
@@ -185,15 +149,3 @@ in event loop.
|
|
|
% DHCP_DDNS_SHUTDOWN application is performing a normal shut down
|
|
|
This is a debug message issued when the application has been instructed
|
|
|
to shut down by the controller.
|
|
|
-
|
|
|
-% DHCP_DDNS_UNCAUGHT_NCR_RECV_HANDLER_ERROR unexpected exception thrown from the application receive completion handler: %1
|
|
|
-This is an error message that indicates that an exception was thrown but not
|
|
|
-caught in the application's request receive completion handler. This is a
|
|
|
-programmatic error that needs to be reported. Dependent upon the nature of
|
|
|
-the error the application may or may not continue operating normally.
|
|
|
-
|
|
|
-% DHCP_DDNS_UNCAUGHT_NCR_SEND_HANDLER_ERROR unexpected exception thrown from the DHCP-DDNS client send completion handler: %1
|
|
|
-This is an error message that indicates that an exception was thrown but not
|
|
|
-caught in the application's send completion handler. This is a programmatic
|
|
|
-error that needs to be reported. Dependent upon the nature of the error the
|
|
|
-client may or may not continue operating normally.
|