Bright Versions: 8.1, 8.2, 9.0, 9.1, 9.2
BCM Versions: 10.0
On the cluster’s head node(s), the minimum TTL that is being used by the start-of-authority (SOA) record for the DNS service may be changed with the DNSSoaTTL AdvancedConfig directive.
If no AdvancedConfig directive is currently defined in the /cm/local/apps/cmd/etc/cmd.conf file on the cluster’s head node(s), then the following line may be added:
AdvancedConfig = { “DNSSoaTTL=value” }
If there are existing AdvancedConfig directives in place, then the DNSSoaTTL directive may be added to the existing AdvancedConfig directive with a comma separating it from the previously declared directive:
AdvancedConfig = { “Directive1=value”, “Directive2=value”, “DNSSoaTTL=value” }
For example, to change the TTL to be 1 day, which is 86400 in seconds, the following directive would be used:
AdvancedConfig = { “DNSSoaTTL=86400” }
After adding the directive, cmdaemon must be restarted to process it. If the cluster has two head nodes configured for high availability, then cmdaemon should be restarted on the active head node first and then on the passive head node:
# systemctl restart cmd
After a minute or two, the new TTL value should show up in the relevant zone files.
For example:
[root@sme-b10rocky9 ~]# grep TTL /var/named/cm.cluster.zone
$TTL 86400
86400 ) ; min TTL