nanog mailing list archives
Re: New netblock Geolocate wrong (Google)
From: Randy Bush <randy () psg com>
Date: Tue, 19 Jan 2010 21:32:01 +0900
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 (unless you're willing to make the DNS really dynamic).
you want an rfc, or you want something actually deployed by operators? randy
Current thread:
- Re: New netblock Geolocate wrong (Google), (continued)
- Re: New netblock Geolocate wrong (Google) Tim Lampman (Jan 18)
- Re: New netblock Geolocate wrong (Google) Warren Kumari (Jan 18)
- Re: New netblock Geolocate wrong (Google) Steven Bellovin (Jan 18)
- Re: New netblock Geolocate wrong (Google) Patrick W. Gilmore (Jan 18)
- Re: New netblock Geolocate wrong (Google) Christopher Morrow (Jan 18)
- Re: New netblock Geolocate wrong (Google) Warren Kumari (Jan 18)
- Re: New netblock Geolocate wrong (Google) Randy Bush (Jan 18)
- Re: New netblock Geolocate wrong (Google) Richard Barnes (Jan 19)
- Re: New netblock Geolocate wrong (Google) Randy Bush (Jan 19)
- Re: New netblock Geolocate wrong (Google) Richard Barnes (Jan 19)
- Re: New netblock Geolocate wrong (Google) Randy Bush (Jan 19)
- Re: New netblock Geolocate wrong (Google) Jim Mercer (Jan 19)
- Re: New netblock Geolocate wrong (Google) Steven Bellovin (Jan 18)
- Re: New netblock Geolocate wrong (Google) Andy Davidson (Jan 19)