[159164] in North American Network Operators' Group
Re: really facebook?
daemon@ATHENA.MIT.EDU (joel jaeggli)
Thu Dec 27 12:26:24 2012
Date: Thu, 27 Dec 2012 09:25:58 -0800
From: joel jaeggli <joelja@bogus.com>
To: mike <mike@mtcc.com>
In-Reply-To: <50DC7FA1.6080504@mtcc.com>
Cc: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On 12/27/12 9:04 AM, mike wrote:
>
> I reloaded their app (yes, I know... sew me) and got this warning:
>
> IP address: 2600:100f:b119:c6bc:bd6f:fabb:ff30:2a3d
> Estimated location: Livingston, NJ, US
That's a rather good estimation of where many verizon wireless customers
appear to come from.
> Which seems pretty bizarre. I'm guessing they must be getting it from
> whois or something based on the address block for Verizon. The reverse
> map according to
>
> host 2600:100f:b119:c6bc:bd6f:fabb:ff30:2a3d
one assumes they have a an geoip database like they have for ipv4
>
> comes back with NXDOMAIN. I suppose the real issue here is with Vz
> and why they don't have v6 reverse maps, but it did throw me thinking
> that
> somebody in New Jersey might have hacked my account.
Well could certainly wildcard their responses, not sure that dynamic dns
updates would be either scalable or appropiate.
>
> Mike
>
