From f8ec75d6fbeba736e93d16aa9ce1953f4107b7da Mon Sep 17 00:00:00 2001 From: Matthias Radestock Date: Fri, 28 Nov 2014 10:35:28 +0000 Subject: [PATCH] document how to configure search across sub-domains --- weavedns/README.md | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/weavedns/README.md b/weavedns/README.md index fe5350ea..71e5e2c6 100644 --- a/weavedns/README.md +++ b/weavedns/README.md @@ -36,11 +36,17 @@ like `pingme`, in its own domain. That's why you can just say `ping pingme` above -- since the hostname is `ubuntu.weave.local`, it will look for `pingme.weave.local`. -If you want to supply other entries for the domain search path, you -will need *also* to supply the `weave.local` domain or subdomain: +If you want to supply other entries for the domain search path, +e.g. if you want containers in different sub-domains to resolve +hostnames across all sub-domains plus some external domains, you will +need *also* to supply the `weave.local` domain to retain the above +behaviour. ```bash -weave run --with-dns 10.1.1.4/24 -ti --dns-search=weave.local --dns-search=local ubuntu +weave run --with-dns 10.1.1.4/24 -ti \ + --dns-search=zone1.weave.local --dns-search=zone2.weave.local \ + --dns-search=corp1.com --dns-search=corp2.com \ + --dns-search=weave.local ubuntu ``` ## Doing things more manually