Offline
Member since 06-27-2017

Community record

19
Posts
4
Kudos
1
Solutions
Badges
Thats probably the only way. Is there a reason you can't deploy a small NIOS appliance into Azure to handle those functions? It can run as a stand alone DNS/DHCP server, or you might be able to connect it back to the main existing grid.
Not sure what you are asking. Would dig work?
just deploy the new licences. they will 'take over' for the temp licences. (you shouldnt' be able to have multiple NIOS licenses for the same appliance)
Assuming you have the zone delegated to another server, if you delete the delega...
If you want to keep the database of DNS and DHCP leases tidy, don't forget DNS ...
temp licenses are a 1 time use item that grants you a 60 day, full license for a feature. As long as you replace the license with one with a longer service date, there are no consequences to doing so.
Can you share a little more information on your config? Is your Infoblox system the owner/authoritative for the .local domain? Is it configured to allow dynamic updates? from where? is DHCP configured to send updates to that zone?
for api access to audit log, you need Infoblox Reporting Server and API access to same This post demonstrates how: https://community.infoblox.com/t5/best-practices/accessing-audit-log-information-from-the-reporting-server-via/ba-p/14020
maybe stop all of the reporting service on all appliances, then bring the reporting server back online, then enable reporting on each appliance one at a time? you should probably open a trouble ticket and let support check the support bundle.
And correct temp licenses or production licenses are installed that specify what model of NIOS it is? I seem to remember something similar where the user had installed all licenses except the NIOS license

Kudos given to

Kudos given to