Infoblox DDI consolidate DNS, DHCP and IP address management into a single platform, deployed on-site and managed from a common console.
N/A
Oracle Dyn Managed DNS
Score 8.8 out of 10
Mid-Size Companies (51-1,000 employees)
Oracle Dyn DNS (domain name system) is an infrastructure-as-a-service that is touted by Oracle Dyne as one of the highest performance global networks existent. It is available as a managed DNS with secondary DNS available for more reliable business continuity on higher service tiers.
We have been using Infoblox DDI for 10+ years at Pitney Bowes. The experience has improved gradually. As far as DNS and DHCP go, they are amongst the top ones offering this service. The support is great and downtime is minimal. The IPAM is always scanning the network to update the IP database. The caching servers reduce the lookups towards the internet. All in all, this is a must-have in every data center.
Oracle managed DNS becomes very heavy when there is an ample amount of DNS being managed. However, the DNS creation and updating takes very less time to propagate and is very easy to use. So, for an organization, where there is a modest amount of DNS to manage, it works very well and gives a splendid experience. So, considering the complexity of managing the DNS for an IT company Oracle Dyn managed DNS is the best option to opt.
Reporting is an add-on feature, which requires another system. The basics are free.
Network systems management and reporting is another add-on. However, this is significantly expensive.
The pricing structure is somewhat ridiculous. It's the least expensive system for a duel site. It has 10s of thousands (for a full feature IP tool), but in our case is crazy expensive.
More responsive sales team to provide relevant QBRs to ensure proper and best practice use of the product/platform
Integration of the Dyn ECT Managed DNS with Dyn Domain Registration would be a nice feature as currently I have to manage two consoles and billing accounts.
It's generally easy to navigate through all of the menus. It's also very powerful in that there are many options available for configuration, allowing one to take advantage of IP address management tools. This tool is definitely a leader in the space, and provided you have the budget, is a very good investment. The team that uses it will appreciate the tool.
This is the only real gripe we have with Dyn; their web-UI can be remarkably painful to use. In the "simple" editor, DNS records are arranged in a kind of "node" view, where each record is a node and any records of the same name or longer (i.e. all records called "record.example.com" or "other.record.example.com") fall under it. This creates an odd sort of hierarchical view that's not really representative of the zone file. The "expert" editor doesn't have an actual delete button, just a checkbox. If you want to update conflicting record types (for example, replacing an A record with a CNAME) you have to check the box for the record being deleted, save changes, create the new record, save changes, and finally publish changes. Dyn uses a publish model for changes, where all changes you make are staged and can be reverted or published all at once. This is fine, except that the publish/revert dialog is in a different page. This is nice when you have many changes, but very annoying when you're changing just one or two records across multiple zones. These are relatively minor issues in an otherwise good platform; annoyances more than deal breakers.
The support team at Dyn has always been very helpful and have tried to answer our questions to the best of their knowledge. We have never had any issues from support tickets and they are often resolved in a few hours
Between Solarwinds IPAM and Infoblox, I'd still choose Infoblox even if Solarwinds is prettier to look at. Infoblox does a fantastic job at managing IP space and really doesn't have much competition in this space. Ease of use, being able to queue changes and having all this done via a web interface that just works is very convenient.
We use both Oracle Dyn Managed DNS and Amazon Route 53. We like having our main DNS provider outside our cloud provider in case there's an issue with Amazon and we need to point things somewhere else temporarily. But for all the smaller stuff and internal stuff, we use Route 53 successfully.
For the law firm its being used for, it keeps their remote users working. For law firms, time is money, usually every 15 minutes lost can be a big deal to them.
Sometimes it has switched when its not supposed to, and causes downtime. No real way to inform users when the switch is happening, it would be great to have an email alert we can not only send to ourselves but a notification to primary and technical partners in the firm so they don't have to yell at us like something is broken, instead they are aware it had to change.
