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, ns_records of /etc/designate/pools.yaml always start with
nsX and are not changeable. To make them the same as parent's NS
records, we have to be able to change ns_records to any value.
As ns_records should end with ".", this change makes sure that it ends
with ".".
Reviewed: https:/ /review. opendev. org/c/openstack /tripleo- ansible/ +/883470 /opendev. org/openstack/ tripleo- ansible/ commit/ 73ccd0a8ab25156 192f46dcd4791bc bb01ec2db5
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/wallaby
commit 73ccd0a8ab25156 192f46dcd4791bc bb01ec2db5
Author: Yamato Tanaka <email address hidden>
Date: Thu Dec 8 19:40:29 2022 +0900
fix to be able to edit 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, ns_records of /etc/designate/ pools.yaml always start with
nsX and are not changeable. To make them the same as parent's NS
records, we have to be able to change ns_records to any value.
As ns_records should end with ".", this change makes sure that it ends
with ".".
Partial-Bug: 1999134 dca06c56f4cd031 46d8e38d363
Change-Id: Id4466cfb01cf69