"Domain name not resolved" with FQDN based Service

"Domain name not resolved" with FQDN based Service

book

Article ID: CTX457078

calendar_today

Updated On:

Description

Add a server using FQDN

Bind this new server to a Service Group

Run the command "show serviceGroup New_Service_Group_Name"

Below result will be seen, with Last response as "Domain name not resolved"

Monitor Name: tcp-default       State: UNKNOWN  Passive: 0
                Probes: 0       Failed [Total: 0 Current: 0]
                Last response: Domain name not resolved.
                Response Time: 0 millisec

But, ADC can resolve the FQDN added above

Resolution

  1. Ensure the DNS server is configured in ADC, and able to resolve the new FQDN added
  2. Upgrade the firmware to 13.0-84.11 and above and check the behavior

Problem Cause

In some cases, the "Domain name not resolved” may be logged under "Last response:" where TCP Monitor is bound.

Though the FQDN name is resolved, the status above was misguiding and it's updated to show more appropriate status in latest builds.
Powered by Wolken Software