Skip to content
This repository has been archived by the owner on Jun 20, 2024. It is now read-only.

Commit

Permalink
removed bash formatting
Browse files Browse the repository at this point in the history
  • Loading branch information
abuehrle committed Apr 15, 2016
1 parent 5ade5cc commit fa3f1b2
Showing 1 changed file with 5 additions and 6 deletions.
11 changes: 5 additions & 6 deletions site/weavedns/managing-entries-weavedns.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ The following topics are discussed:
If you want to give the container a name in DNS *other* than its
hostname, you can register it using the `dns-add` command. For example:

```bash
```
$ C=$(docker run -ti ubuntu)
$ weave dns-add $C -h pingme2.weave.local
```
Expand All @@ -32,16 +32,15 @@ addresses to be registered against the container's hostname e.g.
The inverse operation can be carried out using the `dns-remove`
command:

```bash
```
$ weave dns-remove $C
```

By omitting the container name it is possible to add/remove DNS
records that associate names in the weaveDNS domain with IP addresses
that do not belong to containers, e.g. non-weave addresses of external
services:

```bash
```
$ weave dns-add 192.128.16.45 -h db.weave.local
```

Expand Down Expand Up @@ -71,7 +70,7 @@ By default, weaveDNS specifies a TTL of 30 seconds in responses to DNS
requests. However, you can force a different TTL value by launching
weave with the `--dns-ttl` argument:

```bash
```
$ weave launch --dns-ttl=10
```

Expand All @@ -82,6 +81,6 @@ weaveDNS instance will receive.

**See Also**

* [How Weave Finds Containers](/site/weave-docker-api.md)
* [How Weave Finds Containers](/site/how-works-weavedns.md)
* [Load Balancing and Fault Resilience with WeaveDNS](/site/weavedns/load-balance-fault-weavedns.md)
* [Managing Domains](/site/weavedns/managing-domains-weavedns.md)

0 comments on commit fa3f1b2

Please sign in to comment.