Child: child.parent.example.com. SOA ......
NS nameserver1.child.parent.example.com.
NS nameserver2.child.parent.example.com.
NS nameserver3.child.parent.example.com.
Currently, there are no parameters to edit ns_records of
/etc/designate/pools.yaml. To make them the same as parent's NS
records, we have to have a parameter to configure ns_records.
Reviewed: https:/ /review. opendev. org/c/openstack /tripleo- heat-templates/ +/883471 /opendev. org/openstack/ tripleo- heat-templates/ commit/ 1a1e69e373a8d0a f1d070f3ea3fdd9 c50ef41e4d
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/wallaby
commit 1a1e69e373a8d0a f1d070f3ea3fdd9 c50ef41e4d
Author: Yamato Tanaka <email address hidden>
Date: Thu Dec 8 20:04:58 2022 +0900
add parameter to change ns_records of /etc/designate/ pools.yaml
As the RFC 1034 mentions, parent's NS records and child's NS records
must be the same.
For example:
Parent:
parent. example. com. SOA ...... child.parent. example. com. child.parent. example. com. child.parent. example. com.
child NS nameserver1.
child NS nameserver2.
child NS nameserver3.
Child:
child. parent. example. com. SOA ...... child.parent. example. com. child.parent. example. com. child.parent. example. com.
NS nameserver1.
NS nameserver2.
NS nameserver3.
Currently, there are no parameters to edit ns_records of designate/ pools.yaml. To make them the same as parent's NS
/etc/
records, we have to have a parameter to configure ns_records.
Partial-Bug: 1999134 dca06c56f4cd031 46d8e38d363 4ea5485ccc8d4a6 d0531e0d791
Depends-On: Id4466cfb01cf69
Change-Id: I97c4f7c4785dba