Installing Openshift Enterprise 2.1 on Amazon Web Services fails with Communication with "54.254.0.54#53 failed: timed outerror adding txt record name testrecord.example.com"

Solution Verified - Updated -

Environment

OpenShift Enterprise 2.1

Issue

oo-accept-broker had errors:

--BEGIN OUTPUT--
; Communication with 54.254.0.54#53 failed: timed out
could not talk to specified name server
FAIL: error adding txt record name testrecord.example.com to server 54.254.0.54: this_is_a_test
    -- is the nameserver running, reachable, and key auth working?
FAIL: txt record testrecord.example.com does not resolve on server 54.254.149.53
; Communication with 54.254.0.54#53 failed: timed out
could not talk to specified name server
FAIL: error deleteing txt record name testrecord.example.com to server 54.254.0.54: 
    -- is the nameserver running, reachable, and key auth working?
3 ERRORS

Resolution

the following file, which configures the DNS Ruby client used by the broker had the external IP address in it.

/etc/openshift/plugins.d/openshift-origin-dns-nsupdate.conf

updating it to 127.0.0.1, restarted the broker allows oo-accept-broker to pass

Root Cause

Amazon Web Services (AWS) have multiple IP address for the same host. From clients external to the AWS network, you can access the host using the 54.254.0.54 address, while internally it doesn't resolve correctly.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.