infra/ansible-role-powerdns
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

updated readme

Browse source
This commit is contained in:
nd 2020-05-15 11:00:54 +02:00
parent 70bf2c35e7
commit e7f8d0071f
No known key found for this signature in database
GPG key ID: 21B5CD4DEE3670E9
1 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
README.md
View file

@ -6,8 +6,8 @@ All configuration is to be placed inside the `powerdns` dict.
# key:value of config values # key:value of config values
config: config:
"allow-axfr-ips": "allow-axfr-ips":
- ::1 - ::1
- 127.0.0.0/8 - 127.0.0.0/8
"bind-config": /etc/powerdns/backends/bind.conf "bind-config": /etc/powerdns/backends/bind.conf
"config-dir": /etc/powerdns "config-dir": /etc/powerdns
"daemon": "yes" "daemon": "yes"
@ -67,7 +67,7 @@ It is possible to do short hand notations:
* If there is only a single value for an entry, you can omit the array and use ``<dns path>: { <record type>: <value> }` * If there is only a single value for an entry, you can omit the array and use ``<dns path>: { <record type>: <value> }`
* YAML anchors and merges are recommend for situations where a `CNAME` is not possible * YAML anchors and merges are recommend for situations where a `CNAME` is not possible
* You can use hierachy to shorten paths. If you have `foo.example.com` and 'bar.example.com' you could write * You can use hierachy to shorten paths. If you have `foo.example.com` and `bar.example.com` you could write
``` ```
"example.com.": "example.com.":
foo: foo: