[162377] in North American Network Operators' Group
Re: Why are there no GeoDNS solutions anywhere in sight?
daemon@ATHENA.MIT.EDU (=?iso-8859-1?Q?Ask_Bj=F8rn_Hansen?)
Thu Apr 11 16:54:03 2013
From: =?iso-8859-1?Q?Ask_Bj=F8rn_Hansen?= <ask@develooper.com>
In-Reply-To: <CAPKkNb63hqpT4CLcQ-TiMfYZtrqqT=1TRouKkQGn-QwdHCJO3g@mail.gmail.com>
Date: Thu, 11 Apr 2013 13:53:49 -0700
To: Constantine A. Murenin <mureninc@gmail.com>
Cc: North American Network Operators' Group <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Mar 20, 2013, at 20:28, Constantine A. Murenin <mureninc@gmail.com> =
wrote:
> [...] but what other alternatives could be configured in 5 or 15 =
minutes?
You got a lot of answers telling you to not even try, and I don't know =
that you can configure any of them in 5 minutes.
That being said there are lots of options that might be "good enough":
- PowerDNS has a Geo backend - http://doc.powerdns.com/html/geo.html
- There are various patches for Bind
- Gdnsd - https://github.com/blblack/gdnsd
- GeoDNS - https://github.com/abh/geodns
I use the latter for the www.pool.ntp.org service where it sends users =
to one of about 4000 local servers ("pops") in about 100 countries about =
15 billion times a month.
Ask=
