github
/
consul
mirror of https://github.com/hashicorp/consul
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Cleanup for guides/forwarding.html

pull/1209/head
Ryan Breen 2015-08-30 12:01:49 -04:00
parent 4b57e74bf8
commit 8e8526de8f
1 changed files with 13 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
website/source/docs/guides/forwarding.html.markdown
View File

@ -13,20 +13,20 @@ requires elevated privileges. Instead of running Consul with an administrative
or root account, it is possible to instead forward appropriate queries to Consul, or root account, it is possible to instead forward appropriate queries to Consul,
running on an unprivileged port, from another DNS server. running on an unprivileged port, from another DNS server.
In this guide, we will demonstrate forwarding from [BIND](https://www.isc.org/downloads/bind/), In this guide, we will demonstrate forwarding from [BIND](https://www.isc.org/downloads/bind/)
as well as [dnsmasq](http://www.thekelleys.org.uk/dnsmasq/doc.html). as well as [dnsmasq](http://www.thekelleys.org.uk/dnsmasq/doc.html).
For the sake of simplicity, BIND and Consul are running on the same machine in this example, For the sake of simplicity, BIND and Consul are running on the same machine in this example,
but this is not required. but this is not required.
It is worth mentioning that, by default, consul does not resolve DNS It is worth mentioning that, by default, Consul does not resolve DNS
records outside the `.consul.` zone, unless the records outside the `.consul.` zone unless the
[recursors](/docs/agent/options.html#recursors) configuration option [recursors](/docs/agent/options.html#recursors) configuration option
has been set. An example of how this changes consul's behavior is: has been set. As an example of how this changes Consul's behavior,
When a consul DNS reply includes a CNAME record pointing outside suppose a Consul DNS reply includes a CNAME record pointing outside
`.consul.` the DNS reply includes only CNAME records. the `.consul` TLD. The DNS reply will only include CNAME records by
Contrastingly, when `recursors` is set and the upstream resolver is default. By contrast, when `recursors` is set and the upstream resolver is
functioning correctly, consul will try to resolve CNAMEs and include functioning correctly, Consul will try to resolve CNAMEs and include
any A/PTR records for them in its DNS reply. any records (e.g. A, AAAA, PTR) for them in its DNS reply.
### BIND Setup ### BIND Setup
@ -71,14 +71,15 @@ zone "consul" IN {
Here we assume Consul is running with default settings and is serving Here we assume Consul is running with default settings and is serving
DNS on port 8600. DNS on port 8600.
### Dnsmasq ### Dnsmasq Setup
Dnsmasq is typically configured via files in the `/etc/dnsmasq.d` directory. To configure Consul, create the file `/etc/dnsmasq.d/10-consul` with the following contents:
Add the following to your config. Typically `/etc/dnsmasq.d/` is enabled which should allow creation of a file `/etc/dnsmasq.d/10-consul`:
```text ```text
server=/consul/127.0.0.1#8600 server=/consul/127.0.0.1#8600
``` ```
restart the dnsmasq process after making configuration changes.
Once that configuration is created, restart the dnsmasq service.
### Testing ### Testing