extended README.md

This commit is contained in:
nd 2020-05-15 10:12:05 +02:00
parent 97dda638a5
commit fb4667bd25
No known key found for this signature in database
GPG key ID: 21B5CD4DEE3670E9

View file

@ -15,7 +15,7 @@ config:
"guardian": "yes" "guardian": "yes"
"include-dir": "/etc/powerdns/pdns.d" "include-dir": "/etc/powerdns/pdns.d"
"launch": "launch":
bind: {} bind: {}
"master": "no" "master": "no"
"reuseport": "yes" "reuseport": "yes"
"setgid": pdns "setgid": pdns
@ -62,5 +62,42 @@ type: native
``` ```
## zone** ## zone**
The basic format is `<dns path>: { <record type>: [<value>, <value>] }`
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> }`
* 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
``` ```
"example.com.":
foo:
A: 1.1.1.1
bar:
A: 1.1.1.1
```
For the `SOA` record, `##sequence##` is replaced by a generated sqeuence number.
Example for a zone:
```
"example.de":
SOA: "ns.example.de zonefile.example.de ##sequence## 1d 2h 4w 1h"
CAA: 0 issue "letsencrypt.org"
NS:
- ns0.example.de
- ns1.example.de
ns:
CNAME: ns0.example.de.
ns0:
A: 1.1.1.1
AAAA: ::5
git:
A:
- 2.2.2.2
- 3.3.3.3
AAAA: ::6
``` ```