[178158] in North American Network Operators' Group
Re: OT - Small DNS "appliances" for remote offices.
daemon@ATHENA.MIT.EDU (Justin Wilson - MTIN)
Wed Feb 18 13:01:26 2015
X-Original-To: nanog@nanog.org
From: Justin Wilson - MTIN <lists@mtin.net>
In-Reply-To: <CAKib_RDX+qLnzqwKz2beV+2AzaSjbHvvYavN5-vdcJ4UVGBYCw@mail.gmail.com>
Date: Wed, 18 Feb 2015 13:01:22 -0500
To: NANOG <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
Have you looked at Mikrotik?
www.mikrotik.com=20
It may be lacking for DNS options you want, but worth a look.
Justin
Justin Wilson j2sw@mtin.net
http://www.mtin.net Managed Services =E2=80=93 xISP Solutions =E2=80=93 =
Data Centers
http://www.thebrotherswisp.com Podcast about xISP topics
http://www.midwest-ix.com Peering =E2=80=93 Transit =E2=80=93 Internet =
Exchange=20
> On Feb 18, 2015, at 12:32 PM, Michael Bubb <michael.bubb@gmail.com> =
wrote:
>=20
> What is your desired cost per unit?
>=20
> Reminds me of needing small pfsense based boxes a few years back. Used =
this
> company's hardware:
>=20
> http://www.logicsupply.com/computers/solutions/firewall-networking/
>=20
> I bet you could get something fairly rugged and low maintenance for =
$400 or
> so.
>=20
> On Wed, Feb 18, 2015 at 9:28 AM, Ray Van Dolson <rvandolson@esri.com> =
wrote:
>=20
>> Hopefully not too far off topic for this list.
>>=20
>> Am looking for options to deploy DNS caching resolvers at remote
>> locations where there may only be minimal infrastructure (FW and =
Cisco
>> equipment) and limited options for installing a noisier, more power
>> hugnry servers or appliances from a vendor. Stuff like Infoblox is
>> too expensive.
>>=20
>> We're BIND-based and leaning to stick that way, but open to other
>> options if they present themselves.
>>=20
>> Am considering the Soekris net6501-50. I can dump a Linux image on
>> there with our DNS config, indudstrial grade design, and OK
>> performance. If the thing fails, clients will hopefully not notice =
due
>> to anycast which will just hit another DNS server somewhere else on =
the
>> network albeit with additional latency. We ship out a replacement
>> device rather than mucking with trying to repair.
>>=20
>> There's also stuff like this[1] which probably gives me more =
horsepower
>> on my CPU, but maybe not as reliable.
>>=20
>> Maybe I'm overengineering this. What do others do at smaller remote
>> sites? Also considering putting resolvers only at "hub" locations in
>> our MPLS network based on some latency-based radius.
>>=20
>> Ray
>>=20
>> [1] =
http://www.newegg.com/Mini-Booksize-Barebone-PCs/SubCategory/ID-309
>>=20
>=20
>=20
>=20
> --=20
> Michael Bubb +1.646.783.8769 | KD2DTY
> Resume - http://mbubb.devio.us/res/resume.html
>=20
> *noli timere*
>=20
