Discuss BlueCat products

Can anyone from Bluecat comment on the factors that went into the implementation choices for local RPZ zones? Rather than managing actions record-by-record in an RPZ, Integrity writes out a default policy for each zone in the named.conf (and then writes all the records’s (“response policy items” in BAM parlance) rdata as “CNAME .” in the zone file.)This means ALL response policy items in a given response policy (zone) have the same action.  If you want a different action, you have to create a different response policy - and BIND has an upper limit of 64 RPZs.  So essentially I can only have 64 unique responses via local RPZ under Integrity.RPZ itself (natively, in BIND) is much more flexible.  For any given RPZ I can have thousands of records in them each with their own unique action.  So if I have a one-off DNS zone or particular FQDN I want to override resolution for, I don’t have a burn one of my 64 available zones to do so, as Integrity is forcing us to do - I just place the record

Would be great if we can use BAM to view all cloud DHCP logs, monitor leases and MAC addresses. much easier than trying to run tools or create query statements just to find a DHCP lease for particular MAC. Does BlueCat have a roadmap and/or plans monitoring cloud DHCP lease data? May in the future pull this data into BAM from CDV?

I am wondering is the Integrity release replacing/upgrade to BlueCat Address Manager or is it a completely different product?

LiveAction is now part of the BlueCat family, bringing market-leading network performance monitoring (NPM) to Integrity users. Get a full picture of your network- from DNS-level insights to comprehensive traffic flows and performance monitoring across all protocols.[Learn more]

I would love to get the community’s thoughts on this topic.When working with Edge Service Points and various Edge services such DNS Resolver Service (DRS), Identity, Discovery etc, do you prefer to manage services and more specifically updates to services individually or would much rather prefer that the service updates be bundled inside the Service Point update (somewhat similar to BDDS and BIND/DHCPD package versions)?Since the launch of Service Points v4 we allow services to be independently deployed and upgraded as long as the service point version allows for that specific service version to run. As more services are added, is it getting complex to manage them individually? If you have another view on this please reply to this post. Looking forward to responses! :D

We are going to roll out BCIA, so if anyone has any good tips I’d love to hear them.