Bug 1400130 - [3.3] dnsmasq should not set strict-order
Summary: [3.3] dnsmasq should not set strict-order
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.3.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.3.1
Assignee: Scott Dodson
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On: 1399577
Blocks: 1400139 1400686
TreeView+ depends on / blocked
 
Reported: 2016-11-30 13:53 UTC by Scott Dodson
Modified: 2017-01-24 21:09 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously the dnsmasq configuration included "strict-order" which meant that dnsmasq would iterate through the host's nameservers in order. This meant that if the first nameserver had failed a lengthy timeout is observed while dnsmasq waits before moving on to the next nameserver. By removing the strict-order option dnsmasq will prefer nameservers that it knows to be up over those which are unresponsive ensuring faster name resolution. If you wish add this or any other option please use the advanced installer option 'openshift_node_dnsmasq_additional_config_file' which allows you to provide the path to a dnsmasq configuration file that will be deployed on all nodes.
Clone Of: 1399577
: 1400139 1400686 (view as bug list)
Environment:
Last Closed: 2017-01-24 21:09:32 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0189 0 normal SHIPPED_LIVE Red Hat OpenShift Container Platform atomic-openshift-utils bug fix update 2017-01-25 02:08:43 UTC

Comment 3 Johnny Liu 2016-12-06 07:34:00 UTC
Verified this bug with openshift-ansible-3.3.57-1.git.0.f275588.el7, and PASS.


# cat /etc/dnsmasq.d/origin-dns.conf 
no-resolv
domain-needed
server=/cluster.local/172.30.0.1

Comment 5 errata-xmlrpc 2017-01-24 21:09:32 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:0189


Note You need to log in before you can comment on or make changes to this bug.