Bug 1399577
| Summary: | [3.4] dnsmasq should not set strict-order | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Johnny Liu <jialiu> | |
| Component: | Installer | Assignee: | Scott Dodson <sdodson> | |
| Status: | CLOSED ERRATA | QA Contact: | Johnny Liu <jialiu> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | medium | |||
| Version: | 3.4.0 | CC: | aos-bugs, ghuang, javier.ramirez, jialiu, jokerman, mmccomas, wmeng | |
| Target Milestone: | --- | |||
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| 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.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1400130 (view as bug list) | Environment: | ||
| Last Closed: | 2017-01-18 12:56:10 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1400130, 1400139, 1400686 | |||
|
Comment 6
Scott Dodson
2016-11-30 13:39:30 UTC
Waiting to get errata puddle including the fix PR. 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. 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 |