Hide Forgot
Document URL: Missing: https://bugzilla.redhat.com/show_bug.cgi?id=1372456 Section Number and Name: Missing https://bugzilla.redhat.com/show_bug.cgi?id=1372456 Describe the issue: Add the following note to the install docs that provides the following information. Certain containers do not properly move to the next nameserver when the first issues SERVFAIL, RHEL based containers do not suffer from this but certain versions of uclibc and musl do. This is also the method for which we will enable pushing to the registry via dns name rather than using the registry's service ip address. You could enable the same behavior by reproducing our dnsmasq setup which forwards 'cluster.local' to skydns and then configuring the node to use dnsmasq for resolution. Suggestions for improvement: https://bugzilla.redhat.com/show_bug.cgi?id=1372456 Additional information:
Work in progress: https://github.com/openshift/openshift-docs/pull/2844
*** Bug 1372456 has been marked as a duplicate of this bug. ***
Looks good to me. Move to verified.
Commits pushed to master at https://github.com/openshift/openshift-docs https://github.com/openshift/openshift-docs/commit/71c04a148e3961d54ea31212b4906b70106899dc Bug 1372457, explained the impact of disabling dnsmasq https://github.com/openshift/openshift-docs/commit/a5fe6b97fd760eaca0ab7ca37260e74100069b51 Merge pull request #2844 from ahardin-rh/disable-dnsmasq Bug 1372457, explained the impact of disabling dnsmasq
Content is now published: https://docs.openshift.com/container-platform/3.3/install_config/install/prerequisites.html#dns-config-prereq-disabling-dnsmasq