Infoblox’s global team of threat hunters uncovers a DNS operation with the ability to bypass traditional security measures and control the Great Firewall of China. Read about “Muddling Meerkat” and the many other threat actors discovered by Infoblox Threat Intel here.



Authoritative vs Non-authoritative

Posts: 51
5207     0

Is there a list or comparison that details the features available when an Infoblox infrastructure is in an authoritative vs non-authoritative configuration?


For example, I assume the Grid & IPAM features (in addition to DNS/DHCP and many others) are only available when Infoblox is authoritative.  Whereas, DNS/DHCP services are available when in a non-authoritative state, but Grid & IPAM are not.  However, this allows a Legacy authoritative DNS/DHCP infrastructure to exist with Infoblox in a secondary role.


Are there any docs or technotes detailing this type of info?

Re: Authoritative vs Non-authoritative

Posts: 63
5208     0

You can operate a DNS zone as a secondary with the master in a legacy DNS system.  You can also update DNS records from the DHCP service in a system other an Infoblox.  This might work during transition, but there would not be any value in operating all of your DNS and DHCP services on other systems or integrating Infoblox as only a secondary DNS.


Also, be aware that you cannot directly convert a secondary DNS zone to a primary.  You can create a new zone on Infoblox for an existing zone in legacy platform, enable zone transfer from the legacy platform, and Infoblox will create the zone, perform a zone tranfer, and populate the transferred records into the new zone.


If you are looking for great IPAM, but want to keep Microsoft DNS/DHCP, maybe a purchase of Infoblox IPAM for Microsoft is a better fit?


I hope this helps some!?!?

Showing results for 
Search instead for 
Did you mean: 

Recommended for You

Demo: Infoblox IPAM plug-in integration with OpenStack Newton