Installer Validate failed - Unable to resolve wildcard dns

book

Article ID: 198720

calendar_today

Updated On:

Products

DX Operational Intelligence CA Application Performance Management (APM / Wily / Introscope) DX Application Performance Management

Issue/Introduction

 

Preparation of environment for DX OI 20.2.

In process of running validation of the environment and executing the command: ./install.sh -u=xxxxxxx -p=xxxxxx --validate

The checks run fine until:

[nginx-version] [ OK ] Nginx Ingress Controller version has been verified successfully
Specify the wildcard DNS [1.2.3.4.nip.io]: adminui.<subdomain>
[router-host-validate] [ ERROR ] Failed to resolve adminui.<subdomain> to IP.

However ping succeeds due to wildcard DNS configuration


]# ping adminui.<subdomain>
PING oi-master (1.2.3.4) 56(84) bytes of data.
64 bytes from oi-master (1.2.3.4): icmp_seq=1 ttl=64 time=0.051 ms
64 bytes from oi-master (1.2.3.4): icmp_seq=2 ttl=64 time=0.032 ms


The docs state:

"Enter the wildcard DNS of the node running the Ingress Controller (Kubernetes), Router (OpenShift), or the load balancer.
Validation:
Installer verifies if this host is reachable by pinging this host."

 

 

Environment

Release : 20.2

Component : CA DOI AO PLATFORM COMPONENTS

Resolution

 

When entering the wildcard DNS, just enter the value for the subdomain

Specify the wildcard DNS [1.2.3.4.nip.io]: <subdomain>