Bug 1399577 - [3.4] dnsmasq should not set strict-order
Summary: [3.4] dnsmasq should not set strict-order
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.4.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Scott Dodson
QA Contact: Johnny Liu
URL:
Whiteboard:
: 1399756 (view as bug list)
Depends On:
Blocks: 1400130 1400139 1400686
TreeView+ depends on / blocked
 
Reported: 2016-11-29 10:37 UTC by Johnny Liu
Modified: 2017-03-08 18:43 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:
: 1400130 (view as bug list)
Environment:
Last Closed: 2017-01-18 12:56:10 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1399756 0 unspecified CLOSED Changes in dnsmasq to increase resilience when external primary DNS is down 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHBA-2017:0066 0 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.4 RPM Release Advisory 2017-01-18 17:23:26 UTC

Internal Links: 1399756

Comment 6 Scott Dodson 2016-11-30 13:39:30 UTC 
*** Bug 1399756 has been marked as a duplicate of this bug. ***
Comment 7 Scott Dodson 2016-11-30 19:08:00 UTC 
https://github.com/openshift/openshift-ansible/pull/2888
Comment 8 Scott Dodson 2016-12-01 20:08:58 UTC 
https://github.com/openshift/openshift-ansible/pull/2903
Comment 10 Johnny Liu 2016-12-05 06:49:32 UTC 
Waiting to get errata puddle including the fix PR.
Comment 11 Johnny Liu 2016-12-07 10:39:46 UTC 
Verified this bug with openshift-ansible-3.4.35-1.git.0.2e13650.el7, and PASS.

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

# cat /etc/dnsmasq.d/origin-upstream-dns.conf 
server=192.168.2.2
server=10.11.11.11


All the dns could be resolved by both 192.168.2.2 and 10.11.11.11.
Comment 13 errata-xmlrpc 2017-01-18 12:56:10 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:0066
Note You need to log in before you can comment on or make changes to this bug.