You can verify that an HCP secondary zone or stub zone is working properly from either a Windows command-prompt window or a Unix shell. In both cases, you use either the dig or nslookup command, depending on which is available. The syntax for this is:
The response to this command should be a list of the IP addresses of all the HCP storage nodes that have IP addresses defined for the network for which the secondary zone or stub zone is defined.
Here’s an example of the output from the nslookup command when six out of the ten nodes in the network are registered as master name servers for the secondary zone or stub zone:
#nslookup www.hcp-ma.example.com Server: adc1850.example.com Addresses: 192.168.80.45 2001:0db8::201 Name: www.hcp-ma.example.com Addresses: 192.168.210.11, 2001:0db8::101, 1192.168.210.12, 2001:0db8::102, 192.168.210.13, 2001:0db8::103, 192.168.210.14, 2001:0db8::104, 192.168.210.15, 2001:0db8::105, 192.168.210.16, 2001:0db8::106, 192.168.210.17, 2001:0db8::107, 192.168.210.18, 2001:0db8::108, 192.168.210.19, 2001:0db8::109, 192.168.210.20, 2001:0db8::10a
If you don’t see the expected node list, the secondary zone or stub zone is not defined correctly.