Discuss BlueCat products

Hello, I started in 2008 with Bluecat. I requested many times to get the ability to manage VLAN in BAM. I am now in a migration from Efficient IP and also Infoblox. Both competitors support VLAN management, but Integrity NOT. For me it is a big challenge to try to implement VLAN Management into BAM, using Device and User defined Links. but this is not a good solution, it is like a Workaround to avoid the customer using back a Excel Sheet.Integrity integrates more and more with the network. WHY does Integrity still not support VLAN Management? Any comment is welcome to force Bluecat look at the feature for the next release.Pascal

We are excited to announce the release of BlueCat Integrity 26.1, the next evolution of our DDI platform. Building on the foundation established with Integrity X, this release expands beyond core DNS, DHCP, and IP Address Management to deliver greater visibility, automation, and operational intelligence across your network infrastructure.Integrity 26.1 is designed to help organizations accelerate operations, reduce manual effort, and gain deeper insight into increasingly complex hybrid and multi-cloud environments.Learn more

Integrity 26.1 Beta testing is still open! We’re currently running a beta program for Integrity 26.1 and there’s still time to get involved. Beta testers get early access to new features and the chance to make sure the things that matter to you work the way you expect.Here’s how to join:Request access by requesting to join the Integrity 26.1 beta group. Follow the instructions in the group and download the latest build (beta-2-candidate) from Dropbox Start testing and submit your feedbackThe program is actively ongoing and your feedback is already influencing fixes in real time. If you’re interested in testing the new ND&V module specifically, make sure to select that option when filling out the form.Questions? Drop them below or reach out to the beta team directly.Beta group: https://community.bluecatnetworks.com/groups/integrity-26-1-customer-beta-57

Hi everyone,We’re currently running the Integrity X 26.1 Beta and we are inviting interested Integrity users to participate.This beta gives you early access to v26.1.0 so you can test new capabilities in a UAT or lab environment and share feedback ahead of GA.What’s included in this release:Integrity Feature Modules within Address Manager Network Discovery & Visibility, Cloud Discovery & Visibility, and DDI Analytics EventBus API for real-time DDI event streaming Secure NTP (NTS) support JSON export + enhanced import capabilities Audit trail and platform improvementsThe beta is available through the NVIP Integrity X 26.1 Beta Group. Once approved, you’ll get access to:Announcements and updates Download instructions and documentation Direct engagement with Product Management A space to share feedback and questions👉 To join:Log into NVIP Navigate to the Integrity X 26.1 Beta Group Select Request to JoinNote:This beta is for test environments only (not production) ND&V, CD&am

Micetro is an extremely powerful orchestration tool. Providing a single GUI/API across disparate DNS & DHCP systems, together with discovery and IPAM. Giving that single pane of glass view into the entire network.This works great for centralising administration, audit logging plus wrapping around Role Based Access even for DNS and DHCP platforms that don’t natively support this. What isn’t necessarily fully appreciated (though I know some of our customers are doing this!) is how you can leverage the Micetro API, together with the DDI data Micetro has visibility into to help streamline Network provisioning. In order to highlight this, I’ve put together some sample Python code, built around the Micetro API to automate the provisioning of network interfaces on some VyOS devices.[ VyOS (https://vyos.io ) is an open source router/firewall. The command syntax is very similar to Junos OS] Although this example is written for VyOS I’ve tried to make the code easy to adapt for other platfor

I’ve been meaning to share this for a while…..One of the things that makes Micetro really useful when you start using it for Orchestration of your DNS and DHCP infrastructure is the centralised audit log for all DDI related changes. i.e. Who did what when!Normally this is only accessible via the Micetro GUI. However as the GUI is built on the API this can also be exposed using the GetHistory API command. In order to help illustrate this I’ve written a simple python script which can be run/scheduled from within Micetro which can read the audit log and send this to an external syslog server. Under the hood it uses the Python logger module which can support many other formats including HTTP and SMTP for example.https://github.com/worrabkram/audit2syslogPlease note…This is a personal project not linked to BlueCat.No warranty or support implied.Hopefully you find this usefulMark

Several years ago I asked BC about whether they would write/provide an octodns Provider module/plugin, to be on par on the dozen or so other Providers. E.g. Infoblox, Cloudfare, DigitalOcean, Route53 etc. See: https://github.com/octodns/octodns-route53 I was told: “No but we can quote you on a price”I wrote my own first using the v1 API then v2. I’ve recently put it up on github if others are interested.https://github.com/quistian/octodns-bluecatI’ve found octodns to be a very useful method to synchronize many authoritative DNS servers, using a central YAML data store.   

Join Cisco to learn about how Micetro works in Meraki environments. In this webinar, you’ll hear:Relatable stories from the field Practical insights on simplifying operations and maximizing ROI Clear answers to common branch networking challengesWhether you manage a handful of sites or thousands, see how Cisco and BlueCat together create a branch networking solution that’s ready for anything.   

I would be interested in how people are using UDLs in real life.  I have not used them yet, but it seems like I probably should somewhere.

Posting here for anybody subscribed to the Integrity channel The notes have been posted in the Layer 8 Lounge Group: Join the Layer 8 Lounge group to keep up to date with ​​​future events and notes from the calls👉 https://community.bluecatnetworks.com/groups/layer-8-lounge-43

Since ISC has announced the deprecation of the tkey-gssapi-credential and tkey-domain configuration statements in BIND, both of which are used by Integrity’s current GSSTSIG implementation, can we PLEASE use the refactoring opportunity to get better support for multi-realm GSSTSIG and keytab management?  We currently have to use postDeploy.sh scripting to get the resulting configuration that we want (jettisoning the BAM-generated single-realm keytab and substituting our own, commenting out the BAM-generated tkey-gssapi-credential and tkey-domain statements, and substituting a tkey-gssapi-keytab statement). Ideally BAM should either A) natively support generating a keytab that contains the needed principals and referencing it via the tkey-gssapi-keytab configuration statement (which is ISC’s go-forward requirement) or B) allow the user to import their own keytab and reference that (as other competing products do).I’m sure I have a feature-request for multi-realm support floating around

I’m often asked when I speak to customers and prospects about how to use the Micetro REST API. Hopefully this little guide will help…Getting started with Micetro APIs Some background on the various APIs that Micetro supports for automationhttps://docs.menandmice.com/en/latest/guides/user-manual/automation/Public link to REST/SOAP API documentation for all Micetro versionshttps://api.menandmice.com/Although all APIs continue to be supported it’s recommended going forward that customers focus on the REST API Swagger InterfaceMicetro includes a swagger interface which as well as documenting the REST API also allows you to test and try out API calls. This can be accessed by appending /mmws/api/doc/ to your Micetro web gui. Eg:http[s]://micetro.yourdomain.tld/mmws/api/docMicetro swaggerStarting with version 11.1 we now support Bearer tokens. Follow the link to sessions Eg:Fill out your credentials then click execute –Then click on authorise and copy the session returned in the response body

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 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