My Oracle Support Banner

Running the Host Inspector on the BDA Raises "DNS lookup" Failures on a non-BDA Client/Edge Server Added into the Cluster (Doc ID 1913112.1)

Last updated on NOVEMBER 08, 2019

Applies to:

Big Data Appliance Integrated Software - Version 2.5.0 and later
x86_64

Symptoms

NOTE: In the examples that follow, user details, cluster names, hostnames, directory paths, filenames, etc. represent a fictitious sample (and are used to provide an illustrative example only).  Any similarity to actual persons, or entities, living or dead, is purely coincidental and not intended in any manner.

 

Running the Cloudera Manager Host Inspector raises DNS lookup failures on a non-BDA Client/Edge server added into the BDA cluster.

Running the Host Inspector (From CM > hosts > Host Inspector) reports errors like below for a non-BDA Client/Edge server added to the BDA cluster:

DNS lookup of host bdanode1.example.com on host bdaclient.example.com failed.
           Expected <private ip of bdanode1> but got <client ip of bdanode1>.
DNS reverse lookup of IP <private ip of bdanode1> on host bdaclient.example.com failed.
           Expected bdanode1.example.com but got <private ip of bdanode1>.

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.