Re: New netblock Geolocate wrong (Google)

2010-01-19 Thread Jed Smith
On Jan 18, 2010, at 5:27 PM, Rosenberry, Eric wrote: > Specifically Maxmind (http://www.maxmind.com/) thinks we are in Canada My employer dealt with this recently, but I am unsure who specifically they communicated with at MaxMind. What I did notice is that once informed of the actual location o

Re: New netblock Geolocate wrong (Google)

2010-01-19 Thread Andy Davidson
On 19/01/2010 12:13, Richard Barnes wrote: > FWIW, there has been some work in the IETF on creating protocols to > allow pretty rich location information to be published in reverse DNS. This would be good, but it must be remembered that this would only ever be one clue about where a user actually

Re: New netblock Geolocate wrong (Google)

2010-01-19 Thread Jim Mercer
On Tue, Jan 19, 2010 at 09:23:41PM +0900, Randy Bush wrote: > surely, with its vast talents, the ietf can make this more complex. > > after all, look at the inflate-and-embellish stupidity that made the > simple idea of bgp communities for data collecion, completely ueless, > draft-meyer-collectio

Re: New netblock Geolocate wrong (Google)

2010-01-19 Thread Randy Bush
> Just to be fair here, I appreciate that there's some additional > complexity here (not much -- I implemented a client for this yesterday > in ~80 lines of Javascript), but LOC records don't cover everything. > They're fine for stationary stuff, but not so great for anything that > moves with any

Re: New netblock Geolocate wrong (Google)

2010-01-19 Thread Richard Barnes
Just to be fair here, I appreciate that there's some additional complexity here (not much -- I implemented a client for this yesterday in ~80 lines of Javascript), but LOC records don't cover everything. They're fine for stationary stuff, but not so great for anything that moves with any frequency

Re: New netblock Geolocate wrong (Google)

2010-01-19 Thread Randy Bush
>>> Something that I have often wondered is how folks would feel about >>> publishing some sort of geo information in reverse DNS (something like >>> LOC records, with whatever precision you like) -- this would allow the >>> folks that geo stuff to automagically provide the best answer, and >>> bec

Re: New netblock Geolocate wrong (Google)

2010-01-19 Thread Richard Barnes
>> Something that I have often wondered is how folks would feel about >> publishing some sort of geo information in reverse DNS (something like >> LOC records, with whatever precision you like) -- this would allow the >> folks that geo stuff to automagically provide the best answer, and >> because

Re: New netblock Geolocate wrong (Google)

2010-01-18 Thread Randy Bush
> Something that I have often wondered is how folks would feel about > publishing some sort of geo information in reverse DNS (something like > LOC records, with whatever precision you like) -- this would allow the > folks that geo stuff to automagically provide the best answer, and > because you c

Re: New netblock Geolocate wrong (Google)

2010-01-18 Thread Warren Kumari
On Jan 18, 2010, at 8:38 PM, Steven Bellovin wrote: > > On Jan 18, 2010, at 8:22 PM, Warren Kumari wrote: > >> Something that I have often wondered is how folks would feel about >> publishing some sort of geo information in reverse DNS (something like LOC >> records, with whatever precision y

Re: New netblock Geolocate wrong (Google)

2010-01-18 Thread Christopher Morrow
On Mon, Jan 18, 2010 at 8:38 PM, Steven Bellovin wrote: > > On Jan 18, 2010, at 8:22 PM, Warren Kumari wrote: > >> Something that I have often wondered is how folks would feel about >> publishing some sort of geo information in reverse DNS (something like LOC >> records, with whatever precision

Re: New netblock Geolocate wrong (Google)

2010-01-18 Thread Patrick W. Gilmore
On Jan 18, 2010, at 8:38 PM, Steven Bellovin wrote: > On Jan 18, 2010, at 8:22 PM, Warren Kumari wrote: > >> Something that I have often wondered is how folks would feel about >> publishing some sort of geo information in reverse DNS (something like LOC >> records, with whatever precision you li

Re: New netblock Geolocate wrong (Google)

2010-01-18 Thread Steven Bellovin
On Jan 18, 2010, at 8:22 PM, Warren Kumari wrote: > Something that I have often wondered is how folks would feel about publishing > some sort of geo information in reverse DNS (something like LOC records, with > whatever precision you like) -- this would allow the folks that geo stuff to > aut

Re: New netblock Geolocate wrong (Google)

2010-01-18 Thread Warren Kumari
On Jan 18, 2010, at 5:27 PM, Rosenberry, Eric wrote: > I just lit up a new IP netblock (assigned directly from ARIN) and the > companies that provide Geolocate databases do not have the correct location > information available yet. > > Specifically Maxmind (http://www.maxmind.com/) thinks we a

Re: New netblock Geolocate wrong (Google)

2010-01-18 Thread Tim Lampman
Services such as Hulu could also be affected, certain youtube files even. D'Arcy J.M. Cain wrote: On Mon, 18 Jan 2010 14:27:30 -0800 "Rosenberry, Eric" wrote: I just lit up a new IP netblock (assigned directly from ARIN) and the companies that provide Geolocate databases do not have the co

Re: New netblock Geolocate wrong (Google)

2010-01-18 Thread D'Arcy J.M. Cain
On Mon, 18 Jan 2010 14:27:30 -0800 "Rosenberry, Eric" wrote: > I just lit up a new IP netblock (assigned directly from ARIN) and the > companies that provide Geolocate databases do not have the correct location > information available yet. > > Specifically Maxmind (http://www.maxmind.com/) thin

Re: New netblock Geolocate wrong (Google)

2010-01-18 Thread Olaf Baumert
Hi Eric, On 18/01/10 14:27 -0800, Rosenberry, Eric wrote: > So my questions to others are: > 1. How do I get my data updated in all of the geolocate providers > databases as quickly as possible? > 2. What geolocate database does Google use (is it homegrown?) and how > do I get them t