Is there any way not to expose my member node names in NS records for authoritative zones on my grid? There are 2 reasons why this is desireable:
1) Our customers generally point their zones to ns1.ourcompany.com and ns2.ourcompany.com at their registrar. In order to be able to take advantage to the resiliency of our multi-member grid, those A records resolve to 2 Anycast IP addresses being advertised by our grid, rather than 2 specific member node IP addresses. The NS records in the customer's zone on our grid should match the NS records created at the registrar.
2) Many customers want to personalize their NS records to list ns1.theirdomain.com and ns2.theirdomain.com rather than pointing to something using our domain name (even though they point to the same IP addresses). This is entirely sound, technically, and a very common practice.
I've tried the following so far, with no luck:
1) Adding my grid members as stealth secondaries and manually creating the desired NS records. This doesn't work because NIOS forces you to have at least one non-stealth secondary.
2) Adding my grid members as external secondaries (with the same IP addresses but different names). This doesn't work because NIOS detects that those IP addresses are in use on the grid and won't let you use them as external servers.
Is there any way to achieve this? It seems like NIOS is being overly rigid in the way it forces NS record creation based on internally-configured member node names.
3961 
0
