The reporting metrics are great from an API standpoint, but it would be a little bit nicer if there was some type of dashboard around that. There should also be some type of reporting that's more executive-level focused.

We use the geo load balancing functionality and there are a couple of things that are helpful there. But the language itself is something we had to get used to a little bit. Some of my folks made a few mistakes in rolling out the Filter Chain. It doesn't return all of the multiple results by default. It returns only one. So we have to add a bunch of operations, like geo-target by first selecting a group in terms of regional proximity and then shuffle the list of potential endpoints and then select the first one. The Filter Chain setup is a bit hard to grasp at first. It would also be nice to have a way to simulate changes in addition to staging. 

Also, right now, as far as I understand, there is no way to do atomic changes to a DNS configuration. You need to make changes record by record and apply. But if someone wants to do more complex stuff like, for example, if I want to migrate from a CNAME to an A record being served, or vice versa, that's typically something that involves first taking out all of the CNAMEs and then adding all of the A records. That would require some downtime. It would be a lot easier if I could just have the new full record with the CNAME or A record, and then be able to replace the nodes directly in a single operation and I don't think they have that.

We would really like them to become a DNS registrar.

I would love to see improvement in the testing capabilities they provide. They have a simulate-filter feature so that you can simulate how your traffic would flow, based on their Filter Chains. I believe that was shut off for quite some time. Having that as a way to test our load-balanced CDN structure would be fantastic.

I would like to see the UI updated to allow me to do finer searches. I would also like to have the ability to get reports that can sort based on various metrics. For example, I would like to be able to say, "Show me the top 10 records by total queries" in an easy-to-digest format. If I wanted to do that today, given that we have 500 domains, I'd have to go into every single domain and browse through it to see what is getting hit the most. That kind of filtering functionality would help because our licensing model is based on the number of queries we serve per month. If something goes hog-wild, I want to be able to easily find what that is and then react to it.

We are an external DNS and still maintain an internal DNS. I would like it to have the external DNS separate from the internal DNS. This would give us a sense of security. For example, if there is a problem with the internal DNS, it would not affect the external DNS.

The Filter Chain simulation is really good in the UI, but it would be nice to have something similar in the API so that we could simulate and test things before we deploy them.

And while it's not exactly a problem, a nice-to-have would be a faster API. If we have to make a change to many things, it would be nice if there were a bulk change operation. For example, if we want to change TTL, we would just issue one bulk operation. We can make the calls simultaneously, but there are limits, even if you do things in parallel. 

We care about monitoring and telemetry work, and NS1 provides a pretty good system for monitoring. We can monitor our endpoints and points of presence around the world. If there are any issues, we can easily remove them from our network, but this area needs some improvement because it is not always reliable in NS1. In the past, we had a number of false-positive cases when the monitoring system told us about some problems in our infrastructure that were not true. NS1 is improving the system, and we are constantly talking about this with them. I know that they are releasing a new version of their monitoring system, which is really important for us, but this is a different area where we would expect them to improve.

There could maybe be additional ways to manage traffic. There are no major improvements we're looking for. It's a very complete solution.