Wrong Nameservers when creating ALIAS Virtual Server

When creating an Alias Virtual Server in a Virtual Server, the Nameservers get wrong despite the Virtual Server creation process does it right.

The Server template used creates for all virtual servers the nameservers ns1.example.com and ns2.example.com despite the name of the new virtual server domain which can be example2.com...

The Nameserver ns1.example.com is on the Webhost where the virtual servers are running, the ns2.example.com is on another virtualmin installation which is clustered with the ns1.example.com and running the slave domains. example.com is running on ns1. Both nameservers have a glue record on the registrar side.

I try to use ns1/ns2.example.com for all subsequent created virtual servers. This works well with top level virtual servers. But when I create an Alias domain Server mit name aliasdomain.com, the following gets created: SOA record gets the name ns1.aliasdomain.com NS record points to ns1.example.com NS record points to ns2.aliasdomain.com NS1.aliasdomain.com A record points to IP of Master NS (ns1.example.com) NS2.aliasdomain.com A record points to IP of Slave Clustered NS (ns2.example.com)

The webhost01 and webhost02 A records get properly pointed to the external IP and the SPF record gets also created properly with only the external IP in opposite to the creation of a Top level Vserver where the SPF gets the internal IP as well.

In the Server Template I use for both the Top Level and Alias VServers, there is the Master Nameserver configured with the "Hostname Option: ns1.example.com" and in the "Additional manually configured nameservers" is empty because the slave is clustered with this virtualmin instance.

It is really interesting how different the outcome is despite using the same Template. I try to use always for all domains on the server the ns1 and ns2.example.com to avoid using always a glue record on the registrar side.

Regards