Default behavior when I add a second AD-integrated DNS server is that I get a second copy of every zone. While only one is needed for day-to-day management, I would like to add more DNS servers for redundancy, but have IPAM recognize that these are not actually duplicate zones. That would prevent IPAM from being interrupted by maintenance occurring on one of the DNS servers and without the clutter of all those duplicate zones. They add up quickly with all our reverse lookup zones!
It's OK by me if I have to pick one DNS server as a primary or such. Maybe have it ignore the other servers until the primary DNS node goes down. Whatever the mechanism, it would need to allow for multiple DNS failover clusters, each with its own "primary."
Prompted by case 775841
