Skip to content

Commit

Permalink
docs: Readme
Browse files Browse the repository at this point in the history
  • Loading branch information
kroese authored Apr 15, 2024
1 parent cc768c1 commit c219c21
Showing 1 changed file with 7 additions and 7 deletions.
14 changes: 7 additions & 7 deletions readme.md
Original file line number Diff line number Diff line change
@@ -44,15 +44,15 @@ docker run -it --rm -p 53:53/udp -p 53:53/tcp -e "DNS1=1.0.0.1" -e "DNS2=1.1.1.1
You can set the `DNS1` and `DNS2` environment variables to change which upstream DNS
servers to use. In the examples above they are set to the public [Cloudflare](https://www.cloudflare.com/learning/dns/what-is-1.1.1.1/) servers.

You can add to or extend the [default configuration](https://github.com/dockur/dnsmasq/blob/master/dnsmasq.conf) with a volume that bind mounts a
You can extend the default configuration with a volume that mounts a
directory containing `*.conf` configuration files:

```yaml
volumes:
- /example/dnsmasq.d/:/etc/dnsmasq.d/
```
You can also override the [default configuration](https://github.com/dockur/dnsmasq/blob/master/dnsmasq.conf) completely with a volume that bind mounts a custom `dnsmasq.conf` file:
You can also override [dnsmasq.conf](https://github.com/dockur/dnsmasq/blob/master/dnsmasq.conf) completely with a volume that binds your custom configuration file:
```yaml
volumes:
@@ -61,9 +61,9 @@ You can also override the [default configuration](https://github.com/dockur/dnsm
## FAQ
* ### Something is already binding to port `53`, how do I workaround that?
* ### Port 53 is already in use?
If some process on the host is already binding port `53` you may see an error similar
If some process on the host is already binding to port `53`, you may see an error similar
to the following:

```
@@ -79,7 +79,7 @@ You can also override the [default configuration](https://github.com/dockur/dnsm
tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 197/systemd-resolve
```

On hosts running `# systemd`, such as in this example, you can workaround this by
On hosts running `systemd`, such as in this example, you can workaround this by
specifying the IP addresses on which to bind port `53`, for example:

```yaml
@@ -89,8 +89,8 @@ You can also override the [default configuration](https://github.com/dockur/dnsm
```
There are many other host-specific cases where some process and configuration binds
port `53`. It may be an unused DNS daemon, such as `# bind`, that needs to be
uninstalled or disabled or a number of other causes but finding out which process is
port `53`. It may be an unused DNS daemon, such as `bind` that needs to be
uninstalled or disabled, or a number of other causes. So finding out which process is
binding the port is a good place to start debugging.

## Stars

0 comments on commit c219c21

Please sign in to comment.