coryHawkvelt/docker-bind
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Cleanup of Readme

Browse Source
This commit is contained in:
Ventz Petkov 2018-02-15 18:42:57 -05:00
parent 5f7cf398d7
commit 1695a7a4d6
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
README.md
View File

@ -40,9 +40,9 @@ A "/DATA/var/bind" directory for all of the master or slave zones. If it's for s
# How to run a BIND ("named") Docker Container?
# Default Example
# This is just to test it out - by default only allows queries from
# itself (127.0.0.1) -- pretty useless for real world usage
## Default Example:
This is just to test it out - by default only allows queries from
itself (127.0.0.1) -- pretty useless for real world usage
```
docker run --name=dns-test
-it -d \
@ -51,9 +51,9 @@ docker run --name=dns-test
ventz/bind
```
# Customer Override Example for Authoritative Master
# Edit: named.conf.local with your forward zone at least
# and create the file in /var/named/$yourdomain.tld
## Customer Override Example for Authoritative Master
Edit: named.conf.local with your forward zone at least
and create the file in /var/named/$yourdomain.tld
```
docker run --name=dns-master
-it -d \
@ -64,8 +64,8 @@ docker run --name=dns-master
ventz/bind
```
# Custom Override Example for Recursive Resolver/Cacher:
# Edit: named.conf.options -> change the "allow-recursion" and "allow-query" with your subnets
## Custom Override Example for Recursive Resolver/Cacher:
Edit: named.conf.options -> change the "allow-recursion" and "allow-query" with your subnets
```
docker run --name=dns-resolver
-it -d \