Installed from ppa:maas/3.1-next, enlisted and commissioned a system ("free-parrot") with _two_ network interfaces in the subnet (as the 1st/PXE network interface does not get a PTR record with its name), and clicked 'Actions -> Edit Physical' and set their names to 'nic_one' (1st/PXE) and 'nic_two_test' (2nd/non-PXE), and clicked 'Deploy', which immediately updates the bind zone config.
The PTR record for network interface 'nic_two_test' (with underscores) is 'nic-two-test' (without underscores).
Verification done on maas 3.1.
Installed from ppa:maas/3.1-next, enlisted and commissioned a system ("free-parrot") with _two_ network interfaces in the subnet (as the 1st/PXE network interface does not get a PTR record with its name), and clicked 'Actions -> Edit Physical' and set their names to 'nic_one' (1st/PXE) and 'nic_two_test' (2nd/non-PXE), and clicked 'Deploy', which immediately updates the bind zone config.
The PTR record for network interface 'nic_two_test' (with underscores) is 'nic-two-test' (without underscores).
# maas admin machines read | jq '.[0] | .fqdn, ( .interface_set[] | .name, .links[].ip_address )' -r
free-parrot.maas
nic_one
10.0.0.7
nic_two_test
10.0.0.8
# grep free-parrot /etc/bind/ maas/zone. 0.0.10. in-addr. arpa test.free- parrot. maas.
7 30 IN PTR free-parrot.maas.
8 30 IN PTR nic-two-