Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
baremetal and friends: Set coredns forward policy to sequential
This was already done for openstack in #1527, but not for baremetal because we don't have any separation between external and internal hostnames. However, this behavior is unintuitive and we've found a number of instances where it has caused problems on the other platforms too. Switching the forward policy to sequential will avoid potentially confusing issues where a set of DNS servers works fine standalone but breaks when configured as the forwarding upstreams in coredns.
- Loading branch information
Showing
5 changed files
with
15 additions
and
5 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters