Bug 1400139
| Summary: | [3.2] dnsmasq should not set strict-order | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Scott Dodson <sdodson> |
| Component: | Installer | Assignee: | Scott Dodson <sdodson> |
| Status: | CLOSED ERRATA | QA Contact: | Johnny Liu <jialiu> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.2.1 | CC: | aos-bugs, ghuang, javier.ramirez, jialiu, jokerman, mmccomas, smunilla |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | 3.2.1 | ||
| 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 | Environment: | |
| Last Closed: | 2017-01-24 21:09:41 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: | 1399577, 1400130, 1400686 | ||
| Bug Blocks: | |||
|
Comment 4
errata-xmlrpc
2017-01-24 21:09:41 UTC
|