- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
How to setup common zones between views
[ Edited ]- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago - last edited 4 weeks ago
Hello
Im currently migrating a customer's DNS service from BIND to Infoblox NIOS. The client has 3 views (2 internal, 1 external). They manage them using include statements on the BIND configuration files (not the $INCLUDE standard from the RFC). They have around 200 zones common to the 3 views. ¿What is the best way to import it to NIOS? Meaning, the most maintainable and scalable way. I don't see any way to setup common zones, and I don't think creating the zones separately on each view is the best way to proceed. To add, the importing of these zones is done using the Infoblox CSV Import format. Therefore, the way to do it must support it.
Thanks
Re: How to setup common zones between views
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
@s4amuel-nologin wrote:Hello
Im currently migrating a customer's DNS service from BIND to Infoblox NIOS. The client has 3 views (2 internal, 1 external). They manage them using include statements on the BIND configuration files (not the $INCLUDE standard from the RFC). They have around 200 zones common to the 3 views. ¿What is the best way to import it to NIOS? Meaning, the most maintainable and scalable way. I don't see any way to setup common zones, and I don't think creating the zones separately on each view is the best way to proceed. To add, the importing of these zones is done using the Infoblox CSV Import format. Therefore, the way to do it must support it.
Thanks
Hello,
For a maintainable and scalable migration from BIND to Infoblox NIOS, consider using Infoblox's CSV Import format. This method allows you to import all 200 zones efficiently. Create a CSV file with the necessary fields and import it into NIOS. This approach supports common zones across multiple views and ensures consistency.
Best regards,
David Scott
Re: How to setup common zones between views
[ Edited ]- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
Hi
Yes. I am using the Infoblox CSV Import Format. I can import them easily using this method, even if they are common zones. The thing is, once on production, if they want to modify something from a common zone to the 3 views, they will need to do it separately 3 times for each view, as they behave as separated zones. Currently, in their BIND config, they only need to do it once, thanks to the include statements. I dont think they are going to like it when I tell them that on a paid tool is it more laborious to make modifications than on their currently free BIND. ¿Is there any workaround?
Regards,
Samuel
Re: How to setup common zones between views
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
There is no way in NIOS currently to reference the same zone file multiple times like you are referring to. However, if the customer is maintaining the same exact data between the views, then perhaps using shared record groups would be a good solution. https://docs.infoblox.com/space/nios90/280272365/Configuring+Shared+Record+Groups
Re: How to setup common zones between views
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi
Thanks Ross for your answer. I have tried using Shared Records, but they do not support CSV Import, therefore I am not able to upload the zones in bulk. I only see Shared Records useful for new zones, created on Infoblox, after migrating.
For the moment, the only way I see to do this, is to create the zones separately for each view (standard behaviour), use Infoblox CSV Import Format, and use the Copy Record feature when a new Record is created.
Kind regards
Re: How to setup common zones between views
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
You would have to have a separate zone per view, but for any records subsequently added to those zones, shared records could be used rather than copying (although copying is also a valid approach). Most likely, some type of API automation would be the most efficient path long term.
With that said, if the data in the zone is the same (or nearly the same) in each of the views, I would be inclined to do some further digging to see if views are truly even necessary. If the purpose for the views is just to allow a small subset of records to have different answers, I would heavily consider DTC as an alternative to separate views.
Re: How to setup common zones between views
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Why are they using views ?
if the records are the same for each zone, they don't need to be in seperate views at all.
If they have just a couple of records different, and the view ACL dicates the outcome, using DNS Traffic Control to create a LBDN would be MUCH easier and less complex than trying to maintain so many views.
little more details and we can help, but forklifting a complex configuration someone put together to get around the limitations of bind usually undermines the reason why you go to the 'paid' managment tool.