Add PTR to external-dns managed record types (#295)
Follow-up to #294: --create-ptr validates that PTR is in --managed-record-types, and setting that flag replaces the default list, so A/AAAA/CNAME are re-stated alongside PTR (verified against the v0.21.0 binary's --help: default A,AAAA,CNAME). Pod is crash-looping on config validation until this merges. - Adds --managed-record-types=A,AAAA,CNAME,PTR to the external-dns args MERGE ASAP. Reviewed-on: #295 Co-authored-by: Ben Vincent <ben@unkin.net> Co-committed-by: Ben Vincent <ben@unkin.net>
This commit was merged in pull request #295.
This commit is contained in:
@@ -52,6 +52,12 @@ extraArgs:
|
||||
# the forward zone (the reverse zone + resolver forwarder exist since #288;
|
||||
# without this flag nothing writes PTRs).
|
||||
- --create-ptr
|
||||
# --create-ptr requires PTR in the managed record types; setting the flag
|
||||
# replaces the default list (A,AAAA,CNAME), so re-state the defaults too.
|
||||
- --managed-record-types=A
|
||||
- --managed-record-types=AAAA
|
||||
- --managed-record-types=CNAME
|
||||
- --managed-record-types=PTR
|
||||
- --rfc2136-tsig-keyname=externaldns-key
|
||||
- --rfc2136-tsig-secret-alg=$(EXTERNAL_DNS_RFC2136_TSIG_ALGORITHM)
|
||||
- --rfc2136-tsig-axfr
|
||||
|
||||
Reference in New Issue
Block a user