z/VM: TCP/IP Messages and Codes - z/VM - IBM

DNS and Resolver Messagesare being received, then you can elect to investigate bycontacting the owner of the host that is sending the badpackets. Traces can also dump the inbound packets sothe content of these packets can be examined.RoutineName: Resetting refresh valueSeverity:Informational.Explanation: The zone-transfer refresh timer haspopped, and the name server has contacted a remotename server to see if our name server’s data needs tobe refreshed from the remote name server. The messageindicates a zone transfer is not required at this time.System Action:and restarted.User or Operator Response:The zone-transfer refresh timer is resetNone.RoutineName: Response from unexpected addressfromAddress, expected expectedAddressSeverity:Warning.Explanation: A name server query was forwarded to aremote name server for processing. The response wasreceived, but it was not received from the IP addressthat it was sent to. This situation happens infrequently,and usually when it does it is not an indication of aproblem. There is a small chance that the response wasnot returned by a name server and was intended tocause problems for your name server. If this messageoccurs frequently, it may be prudent to investigate theiroccurrence.System Action:Execution continues.User or Operator Response:None.RoutineName: Results from TcpStatusSeverity:Informational.Explanation: This is the header line preceding adisplay of the status of a TCP connection. The messageis only issued during diagnostic tracing.System Action:None.User or Operator Response:None.RoutineName: Sending domainName zoneSeverity:Informational.Explanation: This message indicates that the localname server is transferring the domainName zone tosome other host. This message is only displayed ifdiagnostic tracing is active.System Action:None.User or Operator Response:None.RoutineName: TABLES specified in PRIMARY orSECONDARY statements are conflictingSeverity:Error.Explanation: This indicates that a table we defined ina PRIMARY or SECONDARY statement in theconfiguration file does not exist or is defined in anotherPRIMARY or SECONDARY statement.System Action: Name server initialization will fail andthe name server will terminate.User or Operator Response:configuration file.Correct the error in theRoutineName: TCP table not defined, no zones definedSeverity:Error.Explanation: There do not appear to be any SQLtables defined, but there are configuration statementspresent that indicate the need to use SQL. A SQL tablecontaining resource records must be defined.System Action: The name server attempts to continue.It may be able to operate in a caching only mode.User or Operator Response: Correct the configurationerror either by creating an SQL table or using acaching-only configuration.RoutineName: TCP/IP service initiatedSeverity:Informational.Explanation: The name server’s TCP/IP initializationwas successful.System Action:None.User or Operator Response:None.RoutineName: tcpclose failed for active conn connNumSeverity:Warning.Explanation: After returning a query answer, thename server fails to close the TCP connection. Theremote host may have already closed the connection.System Action:None.User or Operator Response:None.RoutineName: The following traces are in effect:traceListSeverity:Informational.Explanation: This message shows the list of traces thatare currently active.System Action:None.User or Operator Response:None.28 z/VM: TCP/IP Messages and Codes