[161818] in North American Network Operators' Group
Re: Open Resolver Problems
daemon@ATHENA.MIT.EDU (Jared Mauch)
Wed Mar 27 09:58:41 2013
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <5152EA72.5030203@foobar.org>
Date: Wed, 27 Mar 2013 09:56:57 -0400
To: Nick Hilliard <nick@foobar.org>
Cc: North American Operators' Group <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Mar 27, 2013, at 8:47 AM, Nick Hilliard <nick@foobar.org> wrote:
> then use a vpn and/or provide that service to your users. Sure, =
hotels and
> public access wifi does all sorts of stupid and obnoxious stuff, but =
the
> way to work around this is not by hardwiring your dns to some open =
resolver.
I've been in many a hotel where 4.2.2.1 is reachable with ttl=3D1
You must use a VPN or something else to get around places like that.
The hotel I'm typing from right now is even more broken..
Jareds-MacBook-Air:~ jared$ ping 4.2.2.1
PING 4.2.2.1 (4.2.2.1): 56 data bytes
64 bytes from 4.2.2.1: icmp_seq=3D0 ttl=3D53 time=3D17.159 ms
64 bytes from 4.2.2.1: icmp_seq=3D0 ttl=3D53 time=3D17.181 ms (DUP!)
64 bytes from 4.2.2.1: icmp_seq=3D1 ttl=3D53 time=3D16.787 ms
64 bytes from 4.2.2.1: icmp_seq=3D1 ttl=3D53 time=3D17.156 ms (DUP!)
64 bytes from 4.2.2.1: icmp_seq=3D2 ttl=3D53 time=3D22.056 ms
64 bytes from 4.2.2.1: icmp_seq=3D2 ttl=3D53 time=3D22.081 ms (DUP!)
^C
- Jared=
