Raj Chaudhuri
e2db8a25bd
* Copied, rearranged and modified the contents of the old site directory for Jekyll static site generator, into the website directory * Added some Jekyll-specific things for looks, including: * _config.yaml, Gemfile.* and 404.html files * _data, _layouts and assets directories and their content * Added .github/workflows/github-pages-publish.yml workflow
1.4 KiB
1.4 KiB
title, menu_order, search_type
| title | menu_order | search_type |
|---|---|---|
| Troubleshooting and Present Limitations | 50 | Documentation |
Troubleshooting
The command:
weave status
reports on the current status of various Weave Net components, including DNS:
...
Service: dns
Domain: weave.local.
Upstream: 8.8.8.8, 8.8.4.4
TTL: 1
Entries: 9
...
The first section covers the router; see the [troubleshooting guide]({{ '/troubleshooting#weave-status' | relative_url }}) for more details.
The 'Service: dns' section is pertinent to weaveDNS, and includes:
- The local domain suffix which is being served
- The list of upstream servers used for resolving names not in the local domain
- The response ttl
- The total number of entries
You may also use weave status dns to obtain a [complete
dump]({{ '/troubleshooting#weave-status-dns' | relative_url }}) of all DNS registrations.
Information on the processing of queries, and the general operation of weaveDNS, can be obtained from the container logs with
docker logs weave
Present Limitations
- The server will not know about restarted containers, but if you re-attach a restarted container to the weave network, it will be re-registered with weaveDNS.
- The server may give unreachable IPs as answers, since it doesn't try to filter by reachability. If you use subnets, align your hostnames with the subnets.