Recently active topics

We are introducing DNS Splitview/Split Horizon at the moment. We have to Views on our BDDS Server, one external view and one internal view. BDDS is hidden Primary for both views. We have two PowerDNS servers as authoritative secondaries for the external view and two PowerDNS servers as auth secondary for the internal view. The deployment roles in the view are set to these servers.We use the supermaster feature of PowerDNS for zone transfer.The external view is working as expected. In the internal view the zone transfer is not really working it seems like the internal PowerDNS server seems to query the external view on the BDDS.How can we achive the split view in this setup? Is there a design error in our setup? 

When perusing Global->Transactions, if you click white space in the table the fly-out window presents a barebones representation of the transaction (just an object id, no IP or Name or other object-identifying data).  It also lists an Operations heading, but there are never any Operations underneath it.  It took me awhile to figure out that there ARE actually operations present, but for some reason they are not presented in the fly-out window.  You have to instead click on the Transaction operation link in the table which then loads the transaction and lists the operations.  Is this a bug in that the fly-out window is not showing operations (despite there being an Operations section in the window)?  Or just non-intuitive working as designed? 

When searching for a Resource Record in the API, how can I limit it to a particular DNS View?  Or if I find all records, how can I tell which View each record belongs to?  The Configuration is included as a value in the object, but the View seems to be missing.  Do I have to climb the tree up to the view each time?  That would be several API calls for each and every record.

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