Hi,
while debugging dns in one of my stacks I’ve seen issues with the centos:centos6
(Rancher: v0.51.0, RancherOS 0.4.2)
Within stack (or via service links) centos6 will not resolve hostnames.
dig <service> will fail
dig <service>. succeeds
I was thinking this was an rancher issue, but I guess not.
Is there a way around this issue? (or should issues like this be noted in a FAQ somewhere?)
br hw
What does the /etc/resolv.conf in the container contain?
As I recall we added <service>.rancher.internal. into DNS and set the search path to rancher.internal because of a weird issue with older versions of the resolving library like ship with Cent 6.
Hi,
resolv.conf:
`# Generated by dhcpcd from eth0.dhcp
/etc/resolv.conf.head can replace this line
domain openstacklocal
nameserver 10.215.128.21
nameserver 10.215.128.22
/etc/resolv.conf.tail can replace this line
nameserver 169.254.169.250
`
br hw