Marc Fournier <[email protected]> writes: > Simply adding "resolve-prefer ipv4" makes the symptom go away, so no big > deal. But I wanted to point this out, as it might bite others, and I'm > pretty sure 1.7.x didn't have this issue.
It turns out that "resolve-prefer ipv4" wasn't what fixed my problem after all. It was reordering the options on the server-template line which made the difference. So basically changing: server-template tutum 4 hello-world.tutum.rancher.internal:80 resolvers rancher check to: server-template tutum 4 hello-world.tutum.rancher.internal:80 check resolvers rancher With this change, tcpdump shows DNS queries/responses every 10s. Previously queries seemed to be sent only once, at start up/reload. If that's the expected behaviour, this statement in the documentation is misleading: The "server" and "default-server" keywords support a certain number of settings which are all passed as arguments on the server line. The order in which those arguments appear does not count, and they are all optional. nb: this problem seems to also happen with standard "server" definitions, not only with the new "server-template" one. Marc
