You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 27, 2023. It is now read-only.
we need a new mantl-dns package that fixes the search config. The manual fix @BrianHicks figured out was to use the --domain='#'` option and consolidate /etc/resolv.conf.masq and /etc/resolv.conf.mantl-dns into a single file. I realized we don't have an issue open in the packing repo so I just created mantl/mantl-packaging#84
$ cat /etc/resolv.conf
# this config installed by mantl-dns
# search is added here so that the system can address nodes by their simplest
# name (x.node.consul becomes x.node or simply x.) This will work for service
# addressing as well, so you can use y.service instead of y.service.consul
options ndots:2
search node.consul consul c.asteris-mi.internal. google.internal. c.asteris-mi.internal
aws
$ cat /etc/resolv.conf
# this config installed by mantl-dns
# search is added here so that the system can address nodes by their simplest
# name (x.node.consul becomes x.node or simply x.) This will work for service
# addressing as well, so you can use y.service instead of y.service.consul
options ndots:2
search node.consul consul ec2.internal
ansible --version
): n/apython --version
): n/aterraform version
): n/aThe dnsmasq configuration needs to be updated so that search paths are properly respected. See #1367 for a detailed discussion.
The text was updated successfully, but these errors were encountered: