Troubleshoot StarOS DNS Client Errors

Available Languages

Download Options

  • PDF     (72.5 KB)
    View with Adobe Reader on a variety of devices
  • ePub     (79.4 KB)
    View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
  • Mobi (Kindle)     (64.1 KB)
    View on Kindle device or Kindle app on multiple devices
Updated:November 26, 2020
Document ID:216503

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

    Introduction

    This document describes the details of the Domain Name System (DNS) failure codes that are printed in the Syslogs when the DNS-Client feature is enabled on StarOS.

    Problem

    StarOS DNS Client prints Syslog messages with fail-reason codes when it encounters issues with the DNS queries. These Syslog messages mostly contain response error-codes. Understanding these error-codes can help you troubleshoot the DNS issues.

    Sample DNS Client related Syslog messages from StarOS

    Here are a few sample Syslog messages that show various fail-reason codes.

    [diameter-dns 92604 error] [3/1/44451 <diamproxy:20> er_dns_client.c:2938] [software internal security system syslog] Diameter DNS : response received with failreason : 4. Query : servername.dcca.example.com

    [diameter-dns 92604 error] [3/1/44451 <diamproxy:49> er_dns_client.c:2938] [software internal security system syslog] Diameter DNS : response received with failreason : 11. Query : servername.dcca.example.com

    [diameter-dns 92604 error] [3/1/44451 <diamproxy:31> er_dns_client.c:2938] [software internal security system syslog] Diameter DNS : response received with failreason : 12. Query : servername.dcca.example.com

    Solution

    This table provides an explanation of the fail-reason code that can be used to narrow down the problem and troubleshoot the issue further. Usually, the Syslog message states whether the failure is related to a message received or an internal issue with the DNS Client.

    Fail-Reason Code

    Details

    1

    No relevant answer for the record type

    2

    Unable to interpret the request. Format Error

    3

    Server internal failure

    4

    DNS record does not exist

    5

    Opcode not supported

    6

    Server refused to perform the operation

    11

    Connection Refused

    12

    DNS query timed out

    128

    DNS query depth exceeded

    Note: The StarOS Fail-Reason codes are different from the DNS Response RCODE values listed in RFC-6895

    Related Information

    TAC Authored

    Contributed by Cisco Engineers

    • Tariq Habibullah
      Technical Leader
    • Tomonobu Okada
      Principal Engineer

    Was this Document Helpful?

    FeedbackFeedback

    Contact Cisco

    This Document Applies to These Products