[OPLINLIST] Enhanced features for OPLIN provided OpenDNS accounts

Karl Jendretzky karl at oplin.ohio.gov
Wed Jan 27 10:03:53 EST 2016


All,

Wanted to make you aware of some enhancements to the OpenDNS product that
became available last week. As part of talks between OPLIN and OpenDNS, all
OPLIN provided OpenDNS accounts now have access to OpenDNS's roaming client
software and virtual appliances.

I think the roaming client is the one that will catch the attention of
quite a few libraries for use on things like children's or catalog
machines. After installing a small software client on a workstation, you
can now apply rules specific to that machine from the standard OpenDNS web
interface. You can download the client under Configuration -> Identities ->
Roaming Computers


​Neat thing is when you download that roaming client from your OpenDNS web
interface, it drops a little json file into the zip with your OpenDNS
account info in it. When you run the installer on the workstation, you
don't need to provide any info in the setup because the installer reads the
json file and associates the machine with your account automatically.
Nothing but hitting Next a few times, an icon pops up in the system tray,
and the machine appears in the OpenDNS web interface.


​
At that point you'd just select the machine under the policy settings to
apply security to it.


​For domains that need to be resolved internally rather than going to
OpenDNS (think active directory), you list them in the web interface under
System Settings -> Internal Domains.


​


I don't think the virtual appliance will be as interesting to most of you,
but its downloads and documentation is available under System Settings ->
Sites & Active Directory. The idea is that you stand up an appliance
through ESXi or Hyper-V that acts as a modified cacheless DNS server to sit
between your clients and AD server. This appliance is aware of your
internal domains (once you list them in the web ui) and allows those
requests to go on through to the AD, but other requests it sends directly
to OpenDNS, along with what private ip made the request. Knowing what
internal ip made the request allows you to setup filtering rules which
apply to specific internal ips or subnets.

Enjoy!

Karl Jendretzky
IT Manager - Ohio Public Library Information Network
(614) 728-1515karl at oplin.ohio.gov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.oplin.org/pipermail/oplinlist/attachments/20160127/12aa02b6/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot - 01192016 - 10:20:15 AM.png
Type: image/png
Size: 78063 bytes
Desc: not available
URL: <http://lists.oplin.org/pipermail/oplinlist/attachments/20160127/12aa02b6/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot - 01192016 - 10:16:19 AM.png
Type: image/png
Size: 61446 bytes
Desc: not available
URL: <http://lists.oplin.org/pipermail/oplinlist/attachments/20160127/12aa02b6/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot - 01192016 - 09:16:23 AM.png
Type: image/png
Size: 206077 bytes
Desc: not available
URL: <http://lists.oplin.org/pipermail/oplinlist/attachments/20160127/12aa02b6/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot - 01192016 - 10:17:14 AM.png
Type: image/png
Size: 99284 bytes
Desc: not available
URL: <http://lists.oplin.org/pipermail/oplinlist/attachments/20160127/12aa02b6/attachment-0007.png>


More information about the OPLINLIST mailing list