This request somewhat goes hand-in-hand with the request i just posted here...the ability on the DNS filtering page to import/export IP address settings.
For example, I can create a site name (which for my company's purpose would be the name of the company for which we are providing the DNS filtering services), then under that site, I can add any number of IP addresses that I want to be protected by the DNS filtering service.
In small numbers of IP addresses, this is relatively simple. However, when you are like us and have a need for dozens or hundreds of IP addresses under a single "Site", there currently is no way to add/edit these en masse.
However, it would be an extremely simple process to do this if I already had a .CSV file containing all the info required to set up a new IP address for all the sites I want to add, then just upload that .CSV and it would create an entry for each one all at the same time.
Also, an export feature would be very nice to have as well. This would allow you to export a full list of all the IP addresses listed there into a .CSV file so you can easily email it to someone else, or so you can quickly/easily make changes to the settings of those entries (such as changing from dynamic IP to static), then re-upload the .CSV file to the site in order to apply the changes.
It would be helpful if the first request I linked at the top of this post was completed prior to implementing this import/export feature, so that this tool only has to be done once.
... View more
Currently when you add an IP address to the DNS filtering tool, there are 3 fields that must be filled out: 1) static IP or dynamic IP setting 2) IP address 3) DNS policy There really needs to be a 4th field there called "Location Name" (or something similar) which allows you to add a name that means something to a person, as opposed to just the IP address, which means nothing to anyone. If you only have 1 or just a few sites, it's easy to keep track of them by the IP address. However, if you have someone who has dozens (or even hundreds) of IP addresses, those IP addresses start to lose any meaning whatsoever, and it would be extremely helpful to have something else to refer to that device/location by. And keeping track of spreadsheets tying them together is extremely cumbersome in any sort of large volume situation, especially since you currently cannot easily copy/paste all of the info into a spreadsheet, and/or export all the info to a .CSV file. If your IP address is a dynamic one, then the IP in Webroot and the IP on your spreadsheet no longer match, and you don't really have any other means of identifying the correct site anymore. I was told by a Webroot rep that there is a sort of "workaround" for this, which is to make copies of your DNS policy and name each one whatever you want to call that site. Again, this is OK in small numbers, but if someone has a large number of IP addresses using the same policy settings for a single client, and that client wants a change made, it becomes untenable to go edit dozens or hundreds of policies, one-by-one (hoping you don't miss any in the process), when you could simply make a change to a single policy applied to all those sites, one time, and you're done.
... View more